Drives on different volumes become uninitialised on the same day.
I have been running softraid on a raid 5 and a stripe volume, fine for a few years with no errors or warnings of disk failures.
Until recently 2 volumes have failed to mount at the same time. It seems like 1 drive on each volume has become un-initialised. Does this mean they have failed/died?
Attached below log and screen shots of the volumes. You can see at the bottom of the disks list the drives that should be apart of the volume above them. Is there a way I can add the drives back into the volumes without wiping/initialising them? And will it be possible to rebuild the Raid 5 volume?
Could Mac or softraid caused this during an update? it seems unlikely for this to happen simultaneously.
Running Mac OS 11.6, problem occurred on softraid 6.05. Tried updating to versions 6.1b18 and now 6.1 which show same errors.
Thanks in advance.
Hi, sorry couldn't work out how to edit my first post but I have attached an updated tech report (I can't remember if I had both drives attached when running the original report)
What I see is part of the EFI partitions overwritten onto the partition map of these two disks.
What happened just before this? Was there a crash?
The Archive volume should be mountable. Is it?
Is the Silverstone volume backed up?
There may have been a crash/reboot that I missed just before but I am unsure, The archive volume isn't mounting but softraid shows 4 disks with no errors, so I am a bit confused by that. I had actually just validated the archive volume not long before this which came back with no errors.
The stripe volume was in the process of backup to cloud :(
FYI: SoftRAID creates a "container" for your volume. It does nto know what is inside the volume, nor control what gets written to it. Its more of a traffic cop, sending traffic into the volume. It is up to macOS to manage that data. So a validate confirms the volume is OK, but that does not analyse or repair any files inside the volume container.
What appears to be the case is the partition maps on the stripe are damaged on one disk. Archive appears to have damage to the volume header, but SoftRAID cannot read enough of the volume header intelligibly to create a mount point for the volume. So notice it does not have mount point (disk identifier)
This could have been caused by a USB glitch, cable glitch or enclosure issue, I really do not know. When volumes are mounted, nothing should have access to those parts of the disk.
We may be able to rescue the RAID 0 for you, I would have to ask engineering. the archive may be more difficult, I am not sure. Backups would be the better approach if you can restore from backup on that.
Ah I see thanks for the information, I was hoping the problem wouldn't be as complicated as that which is a shame. Both those volumes were in the process of cloud backup and were about half way done (my bad for not having second hard backup, was hoping the raid 5 would offer me some reliable redundancy). So if there is anything we can try to salvage I would really appreciate any further assistance. I can be available for walkthrough on the phone if easier.
Maybe there is some terminal commands or something in disk utility I can try to sort out the partition maps, I wouldn't know what to try or start with though.
Hi, If it adds any useful information I have just tried Disk Warrior which has come back with the following error for both drives - 'directory cannot be rebuilt, the partition map may be corrupt'
Not good news. this issue was caused by a known bug in USB 3 with Mac's and many USB enclosures. this can damage bot volumes and in SoftRAID's case, the Status partitions, (which is why the volumes are missing disks)
We have the ability to fix this, but it there would be a significant fee. I can discuss this with you off line if you want.
ok thanks for looking into it. Yes please let me know the cost to fix. Will I need to send the drives off or can it be done remotely?
We can repair the volumes remotely. If you need additional recovery, you would have to send the disks here, we can do basic recoveries. I do not expect more than what we can do remotely.