SoftRaid Volume Rea...
 
Notifications
Clear all

SoftRaid Volume ReadOnly after 5.5.5 Upgrade

6 Posts
3 Users
0 Reactions
15.6 K Views
 sean
(@sean)
Posts: 2
Member
Topic starter
 

I upgraded to SoftRAID 5.5.5 today (from 5.5), and after reboot my RAID 5 volume is read only, and OS X (10.11.6) Disk Utility says it needs to be repaired, but is unrepairable.

===
Repairing file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Invalid key length
The volume DATA could not be verified completely.
File system check exit code is 8.
File system verify or repair failed.
Operation failed...
===

This is my first upgrade experience with SoftRAID. :(

 
Posted : 30/08/2016 9:48 am
(@softraid-support)
Posts: 9200
Member Admin
 

About a week ago, you had a couple incidents where you had disks "dropping off the bus" events. Its my opinion that these events are what actually caused the problem with your directory, but until a restart, the symptoms did not trigger OS X to make the volume "read only".

Disk Warrior is your friend here.

 
Posted : 30/08/2016 12:45 pm
 sean
(@sean)
Posts: 2
Member
Topic starter
 

Since I had excess capacity elsewhere, I was able to copy off all the data, recreate the SoftRAID volume, and am currently in the process of copying it back. It's annoying, but so it goes. :)

Sadly, I had run Disk Repair on the volume after the bus reset, and Disk Utility was quick to say "All Good!". Another example of why it's good to have multiple backups. :)

 
Posted : 31/08/2016 10:12 am
(@utahone)
Posts: 2
Member
 

Exact same issue here, one week old Thunderbay 4 8tb setup RAID 5 with 6tb usable, got the update note for softRAID 5.5.5 and now it's read only with OS X popup about unable to repair and recommend I copy all files and clear drive. Is disk warrior my only option too?

 
Posted : 02/09/2016 10:59 am
(@softraid-support)
Posts: 9200
Member Admin
 

1 week old?

Maybe it is easier to backup and erase the volume, then copy the data back.

 
Posted : 02/09/2016 1:18 pm
(@utahone)
Posts: 2
Member
 

Yep still not sure what went wrong but that's what I'm doing now. Bummer to loose hours of time backing up everything. The original post came up when I Googled my problem and sounds like same issue based on error and symptoms.

1 week old?

Maybe it is easier to backup and erase the volume, then copy the data back.

 
Posted : 03/09/2016 12:03 pm
Share:
close
open