Notifications
Clear all
Functionality Issues
12
Posts
2
Users
0
Reactions
1,000
Views
Topic starter
I have a ThunderBay 8 connected to a Mac studio M1 max with the most recent OS on it. In the last month, it’s been having one-off issues where the screen will flash pink and then reboot. However, I’ve always been able to start up and connect. However, in the last week it’s gotten worse and worse and a couple days ago it now just automatically crashes the computer and won’t connect. The only way my computer boots and up and stops crashing is if I don’t have the thunderBay turned on or connected at all
I’ve also tried connecting the TB8 to my MacBook Pro, as well as an Intel based iMac 27", and the TB8 does the same thing and won’t load and just crashes each computer instantly. I’m attaching the error code that the Mac creates after it reboot. It looks like it’s saying something about a kernel panic
------
This topic was modified 2 years ago by SoftRAID Support
Posted : 26/09/2024 1:54 pm
Panic logs in the message make the forum difficult to read, its better to save them as plain text in Text Edit and attach.
However, posting a SoftRAID tech support file is what I need to start diagnosing your issue. Can you attach one?
Posted : 26/09/2024 6:03 pm
Topic starter
THanks :) I actually tried attache a .TXT and also a PDF but the site wouldn't allow it, and it wasn't max size. Not sure what caused but just to be aware. How do I get that support file? Also to be clear, my computer crashes within 10seconds of the TB8 being turned on or connected
Posted : 26/09/2024 6:09 pm
Text Edit saves all files as RTF, unless you use the "make plain text" command.
Maybe you can get the support file, I need that. Utilities menu in SoftRAID.
If you cannot create one because of crashes, pull out two disks, save a support file, then put them in and connect the rest and save another support file. Then attach both support files.
Posted : 26/09/2024 8:05 pm
Topic starter
Posted : 26/09/2024 8:31 pm
I would really like a support file with drives attached. that way I can inspect the drives. As mentioned, if it crashes quickly when drives are connected, remove two, connect & ave a support file, then pull those drives out a bit, and push in the two. removed, and save another support file when they show up in SoftRAID.
I can tell so much more when drives are connected...
Posted : 27/09/2024 7:12 am
Topic starter
Ok gotcha, I'll be back at my home office tmrw and will try that method. So I have the Thunderbay 8 and all 8 drives are used. I do have two clusters setup as two separate DAS's. So 4 drives are one DAS, and the other 4 for the other DAS. Do I still do the method you mention about removing 2 drives, etc?
Posted : 27/09/2024 10:30 am
Try removing one volume of drives, connecting and see if it crashes.
then the other 4. that is best if possible. also it may tell you which RAID is causing the problem.
Posted : 27/09/2024 7:27 pm
Topic starter
Ok, so i did the unplug and plugin method, adn curently looks like my 2nd Volume is the one causing issues. Screenshots showing the 4 warnings i got from Softraid, and also a screenshot of my Softraid Log. Let me know if you feel that 1 drive is corrupting all 4 or if all 4 need replacing....
For now im able to connect to that Volume, even thought its saying its degraded and corrupt. Im moving some imporatnt files to a backup drive for now, and I have a Synology on RAID0 that has been backing up my ThunderBay8 so i have all my files backed up
Posted : 29/09/2024 2:44 am
BTW: Screen shorts are not necessary if you are sending a support file. It has everything I need to see.
the panics you are getting are a specific type that we are working on with Apple. Usually caused by a faulty disk that is stalling the system, but also seems to be involved in file systems that are damaged.
Your disks appear OK, the IO error on each disk is from the kernel panics probably.
I am concerned about the panics coming back, its possible MacOS fixed the issue.
If you are sure your volume is stable, then use the SoftRAID volumes command "recover failed disks". this will fix the state and verify the volume, which you need to allow. It will take a while, but you can use the volume in the mean time. Then clear the io counters on the disks, and your volume will be whole.
but do not do that unless your volume no longer is causing panics.
Posted : 29/09/2024 3:28 am
Topic starter
Ok thanks! ALl my files are backed up and I've started the RECOVER FAILED DISKS command. Its currenntly running that (see screenshot). Looks like it'll take about 15hours to finish. Ill update once its done
Posted : 30/09/2024 12:50 am
Topic starter
Ok that worked! finished the RECOVERED FAILED DISKS and restarted it all and NO MORE ISSUES :) Thansk so much for your help
Posted : 01/10/2024 9:49 pm
