September 8, 20205 yr Greetings! I have been running UnRaid for a couple years now but still don't know that much about it. I recently lost one of my parity drives and one of the data drives, so I set about replacing them. I have a total of 2 Parity drives, both 6TB and 14 data drives, varying from 2TB to 6TB, all in a rackmount server case. I'm running a Supermicro X8DT3 version 2.0 board I through in a replacement drive for my parity, but it is not showing up in the unassigned devices at all. I thought maybe I got a DOA drive so I swapped it for another new drive with the same result. I also swapped it to a different slot and different cable to make sure it wasn't the cable. I also notice that my log is at 100% and am not sure how to clear it. I've included that here too. I appreciate the help, let me know what other info I can give to facilitate this. ~Conan metroplex-diagnostics-20200907-2207.zip metroplex-syslog-20200908-0217.zip
September 8, 20205 yr Community Expert Log has filled with parity2 errors because it has disconnected. Are you sure you don't have a power problem? Unrelated, but why do you have 100G allocated to docker.img? Have you had problems filling it? 20G should be more than enough. And your system share has files on the array.
September 8, 20205 yr Author Thanks for the quick response. I don't think I have a power problem, what would be the best way for me to test that? I'll look at the server and see if any drives are loose. ~Conan
September 8, 20205 yr Author WTF? I powered down, checked connections, started back up and suddenly have 4 drives saying they are unmountable with no file system! Trying to run another diagnostic but it's taking forever.
September 8, 20205 yr Community Expert There are errors on multiple disks, this suggests a controller/connection/power problem, rebooting should bring the unmountable disks online, at least most of them, some might need a filesystem check, but don't try to do it before rebooting, also try to at least get the syslog before rebooting, even if you need to do it manually: cp /var/log/syslog /boot/syslog.txt
Archived
This topic is now archived and is closed to further replies.