Notifications
Clear all
Functionality Issues
15
Posts
2
Users
0
Reactions
1,496
Views
Topic starter
I have four 4TB HDDs in RAID 5 hooked up to a M1 mac mini that has worked great since early 2021. Earlier this week I had a drive fail and followed this guide to get it replaced. Followed each step and am now stuck because my volume will not mount to be rebuilt. All four drives are showing, with the new replacement one showing as out of sync. The volume says rebuilding, waiting on mount.
I have made sure it has full disk access and reduced the security permissions through the startup options with no change. I bought DiskWarrior yesterday after reading about it here hoping it would solve my issues. I installed it and let it run the rebuild command on the softraid volume overnight and it never got past Step 1 Searching for volume information. I cancelled it this morning and gave DiskWarrior full disk access as well hoping that might solve it. Now it causes the entire OS to crash a few seconds after I hit rebuild. I removed full disk access and now it is back to normal behavior of loading on step 1 for seemingly forever.
Not sure what details matter as this is all new ground for me, but the drives all show up in disk utility and are lit up. The volume also appears but is greyed out. DiskWarrior is able to see all of the file info on the volume when I hit the info button. There is about 10TB of content on the volume right now. I learned with the certification of the replacement drive how long some of this can take, so not sure if I should just be patient? If everything needs to start from scratch, is there any hope for recovering the data on the drives?
Any help is hugely appreciated!
Posted : 24/03/2024 10:27 am
Really sorry about this.
First try is remove the newly added disk. see if you can run Disk Warrior?
What about doing a clean install and running Disk Warrior from that. Its easy and does not affect your main volume:
Run Disk utility
Click on your internal and click + volume
startup in recovery mode, options, and then "reinstall MacOS".
point it to the new volume. When done, do not import data, use the same admin name.
Now, see if you can run Disk Warrior.
Posted : 24/03/2024 11:32 am
Topic starter
@softraid-support Thanks for the reply! Finally had time to dive into this today and unfortunately no luck. First tried just removing the new drive and there was no change. Next I created a new volume cleverly named 'New Volume' and reinstalled MacOS on it. After going through all that I was able to pull up DiskWarrior and it still crashed the entire computer and caused it to restart. That was all with the new drive removed from the enclosure.
Posted : 25/03/2024 10:03 pm
Attach a SoftRAID tech support file and I can take a look. If the problem is "outside" the volume, ie, the partition maps, we can help.
Posted : 26/03/2024 10:12 am
Topic starter
@softraid-support File is attached! This is with only the 3 original drives connected. Let me know if another one that includes the new 4th drive also connected would be helpful.
Posted : 26/03/2024 7:40 pm
The volume directory is very damaged, macOS cannot recognize the file system on it. I can perhaps see why Disk warrior is crashing. try one or two more times. Otherwise you are going to need to "recover" the data using diskdrill (cleverfiles.com) or R-Studio, unfortunately.
Posted : 26/03/2024 11:47 pm
Topic starter
@softraid-support Bummer. Thanks for looking at it! Any idea how this happened or general things to avoid in the future? Or is this a side effect of the drive failing?
I’ll report back if I am able to recover anything!
Posted : 27/03/2024 8:16 am
Possible it was the drive failing throwing noise onto the Thunderbolt bus, causing damage to the volume directory, I do not know.
Its pretty unusual for "unknown" file system, however. That says the portion of the volume header that identifies the file system was damaged.
Posted : 27/03/2024 9:03 am
BTW: You can add a support file with all 4, I can take a look.
Posted : 27/03/2024 9:08 am
Topic starter
@softraid-support Sounds good! Didn't know that what I had selected impacted the report. I'm attaching two here, one with the volume highlighted when I hit generate and another with all four drives highlighted. This is back on the original boot volume, not sure if that makes a difference.
I am going to check out diskdrill and R-Studio tonight!
Posted : 27/03/2024 7:41 pm
What is selected does not matter, but the extra disk did matter here.
What I see now is it is possible Disk Warrior can rebuild your directory if you have it, or want to buy it and try it. It allows an "in place" repair.
Posted : 27/03/2024 8:33 pm
Topic starter
@softraid-support I tried out DiskWarrior a bit more to see if I could get it to work but even after a clean install, I am still getting full system crashes. When I boot back up it gives me an alert the computer restarted because of a problem. The error log starts with:
watchdog timeout: no checkins from watchdogd in 92 seconds (18 total checkins since monitoring last enabled)
Debugger message: panic
The message just being 'panic' made me laugh a little, but overall don't know what it means. Right now my plan is to try installing DiskWarrior on my laptop and plugging the OWC bay into it and seeing if it will run from that. The goal is still definitely to fix the mapping if possible rather than file recovery! I will keep you posted on how the laptop goes. Let me know if there is anything else I can send over to you that might help troubleshoot.
Posted : 28/03/2024 7:26 pm
That panic is one Apple is aware of, its generally when disks are taking time shutting down, not responding, so that is interesting.
A different system is definitely worth trying.
I did not check for panics in your support file, but yes, it is triggered by:
Kernel Extensions in backtrace:
com.apple.driver.AppleInterruptController(1.0d1)[9076A4BD-0A3E-3F03-AF0E-1B0F32506359]@0xfffffe00260881a0->0xfffffe002608bf5f
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[AD3F5117-23EA-3BEE-954C-D6C0546887F7]@0xfffffe0025784880->0xfffffe00257d5623
com.apple.driver.AppleARMWatchdogTimer(1.0)[167C5181-F733-32C4-94E3-5A8006F80009]@0xfffffe00257d5630->0xfffffe00257da4d7
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[AD3F5117-23EA-3BEE-954C-D6C0546887F7]@0xfffffe0025784880->0xfffffe00257d5623
what that means, I do not know, but will ask.
Posted : 28/03/2024 11:31 pm
Topic starter
@softraid-support I tried out DiskWarrior on my laptop and got hit with the exact same situation. Both the mini and the MacBook are both on M1 and current software. Not sure if that is causing the issue? Unfortunately don’t have any other hardware I could try it out on.
Posted : 29/03/2024 12:40 am
I guess next step is report to Alsoft. Save the kernel panic as a file. (it should be locatable using Console.app, look for diagnostic/spin/crash reports, and other folders that seem to be panic related, I am not sure where this one is saved.) Save a System Report, also. (System Settings/general/about, scroll to bottom, and just save it.) Submit these to Alsoft. It may take a bit and they may want to remote login, but they generally have great support capabilities. I am sure this is one that would interest them in figuring out and finding the cause, in addition to fixing it on your machine.
Posted : 29/03/2024 11:07 am
