Notifications
Clear all

Sudden disk ejection, RAID 0 Lacie 2-Big enclosure

(@psg)
Eminent Member Customer

This Lacie 2-Big enclosure, running RAID 0, has been working fine for years, more recently on a 2017 iMac. I moved the drive to an older Mac Mini (2012 server model) last week. The Lacie is a Thunderbolt 2 model , one of the earlier ones. It had been up and running fine for about 4 days on the Mini when the issue occurred.

Today, I was running a backup job from another Mac to the Lacie drive attached to the Mini and it suddenly ejected (see below) with an "error (E00002E4)". Can you tell me what that means?

(Note: I powered off the drive, powered it backup restarted the backup job, and all completed normally and the drive seems normal).

SOFTRAID LOG.......:

Apr 12 0730 - SoftRAID Driver: A disk (disk3, SoftRAID ID: 06DFBA1F786F5680) for the SoftRAID volume "Backup Volume1" (disk5) was removed or stopped responding while the volume was mounted and in use.

Apr 12 0730 - SoftRAID Driver: A disk (disk4, SoftRAID ID: 06DF14272CFC57C0) for the SoftRAID volume "Backup Volume1" (disk5) was removed or stopped responding while the volume was mounted and in use.

Apr 12 0730 - SoftRAID Driver: The SoftRAID volume "Backup Volume1" (disk5) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.

Quote
Topic starter Posted : 12/04/2019 7:41 am
(@softraid-support)
Member Admin

I think you just got hit with this OS X thunderbolt disk ejection issue.

See if it happens again. Apple does not seem to be paying attention to this issue, despite the complaints about it.

ReplyQuote
Posted : 12/04/2019 2:37 pm
(@psg)
Eminent Member Customer

I thought that might be it too, but I powered off, back on, and ran a validation and I got this after it ran for an hour:

"Softraid Driver: The volume 'Backup Volume1' (disk6) failed to validate because one the disks encountered a read error. The disk (disk3, Softraid ID: 06DFBA1F786F5680) was unable to read sectors (offset 1520938516480, i/o block size 8338608, error E00002C0). The disk should be replaced."

Seems like I need to replace the drive. Does that make sense? or could I be getting a false error message?

ReplyQuote
Topic starter Posted : 12/04/2019 3:14 pm
(@softraid-support)
Member Admin

Probably it had a problem.

"Verify disk" on that drive (identified by the SoftRAID ID, which you can find in the disks column.

This is not a rigorous test, it just reads the drive. See if it completes OK.

ReplyQuote
Posted : 12/04/2019 4:15 pm
(@psg)
Eminent Member Customer

This is strange. I ran the Verify Disk and got two messages within 2 seconds which contradict each other

2) "... Hung while reading (offset 5,000,969,322,496, i/o block size 11,755,520). This disk should be replaced immediately"

2 seconds later, I get "the verify disk command for disk disk3, SoftRAID ID: 06DFBA1F786F5680, SATA bus 0, id 2 (Thunderbolt) completed successfully."

See attached screen snags. I assume the drive is bad at this point, I have a new one on the way and will try it in next day or two, but if you can explain those two messages I'm all ears.

ReplyQuote
Topic starter Posted : 13/04/2019 2:18 pm
(@softraid-support)
Member Admin

This is someting we are going to fix or work around. For some reason, the very last IO to a device can trigger an error. SoftRAID is reporting it.

Note this is the last sector on the disk.

SoftRAID will report any disk error, regardless of what triggered it.

ReplyQuote
Posted : 13/04/2019 4:38 pm
(@psg)
Eminent Member Customer

I'm not sure what to do with your reply. It sounds like the "completed successfully" message is the correct one and you are working on a "fix" for the "Hung while reading" message which was in error. Is that right?

ReplyQuote
Topic starter Posted : 13/04/2019 5:40 pm
(@softraid-support)
Member Admin

More or less yes. We are pretty certain this is not a failure message, but do not yet know what causes this.

Most likely it has to do with the size of the drive not as big as it should be (by its reported capacity)

ReplyQuote
Posted : 13/04/2019 8:30 pm
Share:
close
open