April 4, 20251 yr I'll sum up the issues i had that lead to this situation: - I had a failure with my DAS, causing drives to give read errors. Drive 8 got put into disabled state so had to be rebuild. - Decided to fix things and get a proper HBA setup going. All drives are recognized and i started rebuilding - UnRAID errored out during rebuild claiming that the drive had write errors still (i tested and pre-cleared the "failed" drive before with zero issues) - After reboot, array does not start anymore. Googling on this said to many that ZFS cache would probably be the culprit. I disabled my cache drive and this is when the WebUI started crashing on array start - Disabled VM Manager and Docker. WebUI does not crash anymore. But it's stuck on array starting. This is where i'm at right now. I have no clue how to continue further... - Did memtest, came out ok - Replaced flash drive with fresh install and moved over config, no change What can i do? I do not want any data to be lost but i'm completely stuck to where i can't even mount my data anymore to back it up elsewhere. Regards, Paul gravityserver-diagnostics-20250404-1735.zip
April 4, 20251 yr Author Just noticed Disk 6 till 9 are all spamming read errors in dmesg. Which is weird since these are all tested and fine. Edited April 4, 20251 yr by GravitySandwich
April 4, 20251 yr Community Expert Solution Apr 4 17:26:38 GravityServer kernel: mpt3sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready Apr 4 17:26:38 GravityServer kernel: mpt3sas_cm0: fault_state(0x5854)! Apr 4 17:26:38 GravityServer kernel: mpt3sas_cm0: sending diag reset !! HBA issues, make sure the HBA is well seated and sufficiently cooled, you can also try a different PCIe slot.
April 4, 20251 yr Author Swapped my GPU and HBA and it seems to be happy now. Let's see what happens! Array atleast started again.
April 6, 20251 yr Author Array has rebuild "successfully". However, i still lost over 8TB of data from that drive. it only managed to recover around 600gb from rebuilding. Quite bummed about this honestly. You expect this to not happen when your parity checks were all fine and the rebuild is "succesfull"
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.