March 8, 20188 yr I received an email saying the "Parity disk in error state" and now have the red X next to my parity drive. The SMART diagnosis on that drive says, "A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options, unraid". Not sure how to proceed, any help would be great. I'm running 6.4.1 and I've attached my Syslog here. tower-diagnostics-20180308-0647.zip Edited March 13, 20188 yr by emo_boy
March 8, 20188 yr Community Expert Yep, disk dropped offline, since it's on a SASLP it could also be the controller's fault, but we'll need new diags after reboot.
March 12, 20188 yr Author Solved. I checked the connections and restarted, everything is good after the parity check. I should have thought to just check the connections first. It seems like every time I boot up, one of the four drives (it's not always the same one) on the controller SATA card I have isn't found when Unraid starts. So I always have to power down, and double check all the connections and boot back up. After 2 or 3 tries, the drive shows up and everything works fine. But I've never had a problem like this, with a drive off the controller and causing an issue that's not at first boot. I guess it may be time to look at upgrading some of the equipment like the motherboard.
March 12, 20188 yr Community Expert 1 hour ago, emo_boy said: I guess it may be time to look at upgrading some of the equipment like the motherboard I would start by upgrading the HBA to an LSI.
March 13, 20188 yr Author On 3/12/2018 at 5:57 PM, johnnie.black said: I would start by upgrading the HBA to an LSI. So I began to do some research on different HBA's, given your suggestion of updating my current SUPERMICRO AOC-SASLP-MV8 to an LSI (I'm considering an LSI SAS9211-8I). Anyways, I wanted to go through some troubleshooting on the MV8 first. So I plugged it into a different PCI-e slot (made sure it was snug), used the other port on the controller card (it has 2) and disabled int13. However, when I booted back up, same symptoms occurred (my parity drive and a drive plugged into the controller card) weren't detected nor assigned when Unraid started. I made sure to get a diagnostics report, see attached. When I rebooted the server once more, everything worked just fine. Not sure what the issue is. Typically, once it finally boots up clean everything runs fine until I need to reboot again. But it's definitely annoying to have to reboot 5+ times after every update, etc. Any thoughts? tower-diagnostics-20180313-1747.zip Edited March 13, 20188 yr by emo_boy
March 13, 20188 yr Community Expert Has it always been like this or started doing this at some point? Could be the controller, could be some compatibility issue.
March 14, 20188 yr Author It hasn't always been this way. I've ran Unraid with this machine for 5 years. But it's been like this for a while, I'd say for the past 6 months to a year it's been acting up after a reboot. It almost always takes 2-5 reboots before the drives all come back properly for Unraid.
March 14, 20188 yr Community Expert Sound more like a hardware problem then, most likely the controller.
March 14, 20188 yr 7 hours ago, emo_boy said: It hasn't always been this way. I've ran Unraid with this machine for 5 years. But it's been like this for a while, I'd say for the past 6 months to a year it's been acting up after a reboot. It almost always takes 2-5 reboots before the drives all come back properly for Unraid. As @johnnie.black says, the controller is a good suspect. But if drives are missing after a power up from off, but are less often missing after a reboot then it would be worth seeing if you can check the power supply (maybe a temporay swap from another machine?). Power supplies do age, and over time can loose their capacity to provide the higher currents needed at start up.
March 14, 20188 yr Author 5 hours ago, S80_UK said: As @johnnie.black says, the controller is a good suspect. But if drives are missing after a power up from off, but are less often missing after a reboot then it would be worth seeing if you can check the power supply (maybe a temporay swap from another machine?). Power supplies do age, and over time can loose their capacity to provide the higher currents needed at start up. Yeah, I was wondering if it was the power supply since now some drives (such as the Parity) are starting to not show up after the first reboot that aren't on the controller card. Unfortunately, I don't have a spare power supply at the moment, so I'll need to decide which to buy and try first (a new HBA or power supply).
Archived
This topic is now archived and is closed to further replies.