mordhau5

So weeks later and some troubleshooting (because I wasn't even able to get logs due to crashing) ....turns out it was either a bad drive, bad sata cable, or bad sata port on the board causing the system to see the drive getting connected and disconnected. The drive's name in BIOS even kept changing 😮 . It wasn't a drive in the array (an extra SSD) and wasn't necessary so I removed it and now things are booting reliably. Thank you for pointing out where the diagnostics and syslog server can be found.

New guy here. Just got my machine together with the hardware listed below. Bios boot options configured, static IP reserved by router, device was confirmed online. Got into the Web UI, started a trial, configured my array, and started the array as per the "getting started" guide. The parity drive is 12TB so the operation was going to take a while. Fast forward to next morning, and I when come back to check on it in the UI, it doesn't respond and its not even on the network anymore. Ok, so maybe it restarted automatically. I plug in a monitor and keyboard, and don't get any video signal (was expecting to see terminal prompt). The machine is running, though I can't see the mobo inside this case for error LED, and its really not easy to safely expose it without powering off and unplugging everything. So I'm really not sure of the state of the system. Any idea what the best course of action is here? I guess worst case I can just shut it off and have to do the parity check again. Enough time has passed that it should definitely be done. Just don't want to permanently corrupt/damage anything. Thanks! Mobo: Gigabyte GA-H270N-WIFI CPU: 6700K (no-oc) RAM: 16GB 2400 DDR4 Case: Jonsbo N1 Cooler: NH-L9i PSU: Anode SFX 450W Bronze (scavenged from Fractal Design Node 202) HDDs: 2x 12TB Ironwolf ST12000VN0007, 1x 12TB Ironwolf ST12000VN0008 (parity) SSDs: Sabrent 1TB Rocket4 Plus (Cache Pool), Kingston DataCenter 480GB (unused presently)