akroeze

That was a good thought! Just repeated the test removing only the SATA cables and leaving the drives themselves still powered and it still boots fine when I pull it down to 12 drives connected with data. So not an easy fix like that unfortunately.

My system loads fine when I have a total of 12 drives however when I try to add my 13th+ drive it immediately starts saying that it can't find a boot drive. I take the 13th+ drive back out of the loop it boots fine again. When I load into the BIOS it does see all 13/14 drives. When I go to the boot order it still shows only the USB key as the boot device however it has the [ ] brackets around it indicating a problem and it isn't bootable. Once I go back to 12 they [ ] disappear. I have looked through the manual and see no mention of a maximum number of drives. Is there one that I'm just not aware of? What else could I do? I'd prefer to not have to get all new motherboard/cpu/ram. I have the following: Supermicro x8dti-f 2 x SATA SSD 11 x WD Red drives 1 x USB key (boot drive) All drives (except USB of course) are connected to LSI HBAs

🤦‍♂️ The idiot check found an idiot! Apparently someone had been in the mechanical room and didn't realize that they bumped the server. The hot swap tray was popped out in the process. That drive is currently being rebuilt. Thank you for the help!

I think I have attached the correct diagnostics file. It shows that unraid has disabled the disk and is emulating it. Is it dead? What should I do or is it a straight up replace situation? zapp-brannigan-diagnostics-20220808-1514.zip

When I try to connect to the WebUI: Warning: session_write_close(): write failed: No space left on device (28) in /usr/local/emhttp/login.php on line 96 Warning: session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php) in /usr/local/emhttp/login.php on line 96 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/emhttp/login.php:96) in /usr/local/emhttp/login.php on line 98 When I telnet in: "login: write lastlog failed: No space left on device" When I reboot via telnet the webUI becomes available for a bit, but then we repeat the cycle. Thoughts? Attaching diagnostics log after reboot. zapp-brannigan-diagnostics-20210614-1009.zip