SoftRAID says Rebuilding, waiting for mount, Current Offset stopped counting.
Okay HFS+ Time Machine RAID 5 Five drive setup 8TB each. Had a drive go bad and I successfully removed and replaced the bad drive. Now it's stuck. I have to go back the RAID5 Volume and choose Mount, with right click so that the Current offset will start to count again. What is going on here? What am i doing wrong?
Any help would be wonderful.
Rebuilds require that the volume is mounted normally. Does the volume mount at all? I am a little confused, as you say you need to mount it to get the counters to increment, which would be correct. Are you unmounting the volume after that?
If the volume does not mount, did it ever mount after you replaced the disk?
Yes. The disk will mount. I switched to a virgin Boot drive and it still does the same thing. Will NOT do the rebuild. Says it is, but the drives are not being accessed. When I tell it to mount it will start the rebuild. If it's mounted, to rebuild the RIAD I have to eject the RAID then tell it to mount the drive, then and only then will it start the rebuild.
Then shortly after I can see the offset count raising from where it left off. I can also see the individual drive I/O requests counting upward. Again, this only lasts for a few minutes.
Do you have optimization set for a video or Audio optimization? They are designed to never interrupt your work, so rebuilds do not happen when you are working. Set to workstation and that will rebuild 50% when you are using the computer, then full speed when you are away.
It's set to workstation. I have had this running 3 days now. and every time I check the RAID, it's cold. It only gets warm if I keep telling SoftRAID to mount the RAID. Also that is the only time I see any disk activity with Activity Monitor. At my wits end waiting for this to rebuild. Was trying to write a script to tell SoftRAID to mount the drive every 5 minutes.
I don't know what I am doing wrong here but it seems like everything :(
Thank you so much for your help.
Help me understand here. You start the rebuilding and then the volume dismounts on its own?
Yes I have to eject the RAID in order to have it rebuild. It does not seem to work any other way. The app says it is rebuilding it but yet the RAID case stays cold and no access lights are lit up. If I eject it and tell it to rebuild it will. But then it stops, after that I have to choose mount for it to continue on. I have to do that every few minutes in order for it to do anything.
This does not quite match up to any problem I can think of. Attach a SoftRAID Tech Support file.
Do you get any warning from macOS that hte volume is mounting read only?
DO you have Disk Warrior? If so, run it on this volume.
The only warning I get from SoftRAID is about slow access to the RAID and that I should back it up. macOS says it can not repair the RAID. I did not tell macOS to do anything. So it's just upon mounting that I get the macOS message. Which has had me confused.
PS: the two photos are showing the IO from Activity Monitor when it starts the rebuild and when it just stops.
This is the key clue I was missing:
"macOS says it can not repair the RAID."
The volume directory is damaged and the volume is mounted read only ,so it cannot rebuild.
If you have Disk Warrior, use it to repair the directory. otherwise you will need to backup restore.
A volume with a directory that is damaged cannot rebuild.
Yes I have Disk Warrior but sadly this is a Time Machine raid and it cant do much with it. So I will have to back this up to a new RAID 5 set. Unless there is some other trick you might know about.
Thank you for your help
Yes it says it can't because macOS security issues. It's a Time Machine backup. I'm gonna have to port it to a different raid, make a new RAID 5 and then port it back.
Thank you so much for your help in this matter. I felt like I was loosing it. Thank goodness for caffeine and this Forum!
Do not delete the volume, just backup/restore. If you delete the volume, you will have a extremely challenging time getting your prior Time Machine archive to work. If you just restore, it should work again. the key is the volumeID, which even an "erase" will change. See if you can avoid that.