Disk keeps ejecting itself and mounts itself a short time later

[Gwendolini]

Hi.

I have a strange problem, where an external USB 3 2.5" Seagate HDD with 2 TB storage keeps ejecting itself and then mounts itself a short time later.
Sometimes the volume is also not mounting, but recognized in Disk Utility, but I cannot mount it with Disk Utility.

Once the disk was partitioned with a 1.5 TB volume (first partition) and 500 GB volume (second partition), but since then I have deleted the 500 GB volume and expanded the 1.5 TB volume to 2 TB.
The 1.5 TB volume was called "1.5 TB Daten", the 2 TB volume is now called "Daten mobil 2 TB".
The volume is also encrypted, since its 1.5 TB days, with FileVault.

Now Console gives me infos like this:

27.08.16 22:46:22,000 kernel[0]: CoreStorage::recover() PV E3C62021-F7EC-47D0-9452-46ADF43AD53A from group "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16) has been marked missing.
27.08.16 22:46:22,000 kernel[0]: hfs: unmount initiated on Daten mobil 2TB on device disk3
27.08.16 22:46:22,000 kernel[0]: CoreStorage: terminating group "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16) is BUSY
27.08.16 22:46:22,296 fseventsd[48]: disk logger: failed to open output file /Volumes/Daten mobil 2TB/.fseventsd/fc0075c51266dc47 (No such file or directory). mount point /Volumes/Daten mobil 2TB/.fseventsd
27.08.16 22:46:22,297 fseventsd[48]: disk logger: failed to open output file /Volumes/Daten mobil 2TB/.fseventsd/fc0075c51266dc47 (No such file or directory). mount point /Volumes/Daten mobil 2TB/.fseventsd
27.08.16 22:46:25,000 kernel[0]: hfs: mounted Daten mobil 2TB on device disk3
27.08.16 22:46:25,696 fseventsd[48]: event logs in /Volumes/Daten mobil 2TB/.fseventsd out of sync with volume.  destroying old logs. (127 2 250)
27.08.16 22:46:25,753 fseventsd[48]: log dir: /Volumes/Daten mobil 2TB/.fseventsd getting new uuid: 5E79185D-A9A1-44E3-8CD9-27B6A7B8898A
27.08.16 22:47:38,000 kernel[0]: CoreStorage::recover() PV E3C62021-F7EC-47D0-9452-46ADF43AD53A from group "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16) has been marked missing.
27.08.16 22:47:38,000 kernel[0]: hfs: unmount initiated on Daten mobil 2TB on device disk3
27.08.16 22:47:38,000 kernel[0]: CoreStorage: terminating group "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16) is BUSY
27.08.16 22:47:38,554 fseventsd[48]: disk logger: failed to open output file /Volumes/Daten mobil 2TB/.fseventsd/fc0075c51266e6a6 (No such file or directory). mount point /Volumes/Daten mobil 2TB/.fseventsd
27.08.16 22:47:38,554 fseventsd[48]: disk logger: failed to open output file /Volumes/Daten mobil 2TB/.fseventsd/fc0075c51266e6a6 (No such file or directory). mount point /Volumes/Daten mobil 2TB/.fseventsd
27.08.16 22:47:41,000 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002d9 detected for LVG "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16), pv E3C62021-F7EC-47D0-9452-46ADF43AD53A, near LV byte offset = 13635584.
27.08.16 22:47:41,000 kernel[0]: CoreStorage::recover() PV E3C62021-F7EC-47D0-9452-46ADF43AD53A from group "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16) has been marked missing.
27.08.16 22:47:41,000 kernel[0]: HFS: bitmap scan range error: 6 on vol=Daten mobil 2TB
27.08.16 22:47:41,000 kernel[0]: CoreStorage: terminating group "1.5 TB Daten" (C4B849BD-64C8-455F-9B5E-4D14675E9E16) is BUSY
27.08.16 22:47:46,000 kernel[0]: hfs: mounted Daten mobil 2TB on device disk3
27.08.16 22:47:46,130 coreservicesd[137]: failed to fetch IOKit properties for /Volumes/Daten mobil 2TB
27.08.16 22:47:46,000 kernel[0]: hfs: unmount initiated on Daten mobil 2TB on device disk3
27.08.16 22:47:46,180 fseventsd[48]: failed to make the directory /Volumes/Daten mobil 2TB/.fseventsd (2/No such file or directory)
27.08.16 22:47:47,000 kernel[0]: hfs: mounted Daten mobil 2TB on device disk3

I thought about cloning the volume to another disk I have lying around, then formatting the troublesome disk, and then cloning all the data back. Since is only 1 TB of data, it will not take more than a night and such, but maybe I can circumvent that with something clever I haven't thought of yet.

Anyone having read this with an idea how to solve this great mystery of this second?

Thanks.

Sorry for the lack of emoticons, I only know two or three, and those are mostly used on message boards for throat singing.

 

[JohnDS]

Perhaps a bad USB cable?

 

[Gwendolini]

Perhaps a bad USB cable?

I tried several cables, it is not my only USB 3 2.5" HDD.

I just cloned and reformatted and cloned that thing, since then it has been behaving like it should.

 

[Harry Harm]

I searched for this error code - error 0xe00002d9 and this thread started by Gwendolini showed up. I have a 5 TB LaCie USB3 drive connected to my 2017 MacBook Pro 15". I use a USB 3 to USB C adapter from Apple. The drive would unmount. The drive is encrypted so I have to enter a password when it tries to remount. Sometimes when it would remount, I would enter the password and MacOS would report that the drive was not initialised and needed to be initialised. Sometimes it would not show up at all. I tried different cables, different adapters and with and without hub. As insurance I reset the PRAM and SMC. Nothing helped.

I bought a 2.5" LaCie Porsche 5 TB USB C drive to replace it. This brand new drive started to exhibit similar problems. It took me all weekend to clone the drive from a backup I have.

I have other drives which are not having a problem. One working hypothesis is perhaps a transient drop in the power provided by the USB C ports. It may be that certain drives are just more sensitive to a power drop.

Another hypothesis is that this is connected to a strange OS bug. I have other symptoms. In trying to track down the cause of the drives ejecting I tried to boot into Safe Mode and I could not. I was thinking that because I have my boot disk encrypted it prevented my computer booting into Safe Mode so I tried to turn off FileVault. I could not do that either. FileVault also warns me that "Some users are not able to unlock the disk." There is a button to "Enable Users". That button does not work either. I only have one user in this computer and Guest User is not allowed.

Does anyone know what is the meaning of error 0xe00002d9?

Blessings,

Harry