isellion

Duh, Diagnostics added to the OP. Thanks!

Hey there, looking for some help with my server. Just updated to 6.11.5 yesterday, but had recently recovered from a random freeze. Did it again last night. I had thankfully enabled syslog mirroring to the flash drive to see what's going on. I've attached my syslog, but I think this is the relevant line that indicates the problem: Feb 25 03:54:04 PhoenixServer Crond[1457]: Exit Status 1 From User Root /Usr/Local/Sbin/Mover &> /Dev/Null Prior to that line, the server looks like it's just doing some normal updates in the middle of the night. I've got the Mover scheduled to run at 3:40am everyday, and that's what causing issues, I think... Either way, I woke up this morning, and the server was powered up, but couldn't access webgui, ssh wasn't working, and even pinging the address returned nothing. Curious if anyone can take a look and help me figure out what's going on, and how to fix it? Thanks again, great community here. syslog phoenixserver-diagnostics-20230225-1207.zip

Good to know, Thanks again!

Thanks for the help! So, easiest way to fix this would be to power down, remove both failed drives, add new drives, power back up, and reassign the new disks to the missing slots, and then have it do a rebuild? I didn't know it could do both at the same time. Very cool. Does it matter which parity drive is larger? I'm guessing not, but maybe?

Hey guys, been doing a lot of digging on this one, and am starting to confuse myself, so I'm hoping I can get some clarity from more knowledgeable individuals. Here's the story: Bought two used 6tb WD Red drives middle of last year, added one to data (Disk 5) and one to Parity 2. Haven't noticed any issues since installing them. Last week, noticed that Disk 5 was disabled and emulated. Ran a SMART test, and then an Extended SMART test. First one was fine, second was showing a read failure. Also noticed that errors were showing on the main dashboard, and my Parity 2 drive was showing errors as well. Checked the last parity check, and there was 1 error. I ran the same two SMART tests on the Parity 2 drive with the same results as Disk 5. Screenshot of my dashboard Main-Array Devices attached. Did a lot of digging, and seems that the SMART tests could be showing either the drives are failing, or it's a cable issue. Haven't been able to figure out how to figure that out yet. I've attached the SMART test results for both drives. I've also attached my diagnostic file. Curious what people think about these two drives, and what the next course of action would be? I've got a 12tb drive enroute to help with things, and I'd like to end up with that being Parity 1 and my 8tb being Parity 2. I'd love to keep the 6tb drives if it's just a cabling issue, but need to make sure they aren't actually failing. Let me know if I left anything out. Thanks! Disk-5-smart-20230127-0815.zip Parity-2-smart-20230127-0816.zip diagnostics-20230127-0820.zip