July 22, 20169 yr So i had a drive fail in my array a few months back, in the process of rebooting and rebuilding a new drive i all the sudden had my bios start asking for a HDD password on a different drive in the array, and wouldn't boot with that drive in the array, after running around with super micro in emails, another drive began asking for a password as well. Eventually after trying different bios builds with them, the threw their hands up and said it was a HDD issue. Needless to say i had never set a password and they were drives that worked merely days before. Tried loading them in another system with g-parted and couldn't see them, so resulted to the fact that they were lost. i inserted new drives and pre cleared them (2 data and 1 parity) and set up a new array. Build seemed to work so i started by running a non parity correction while i was at work and came home to a crazy amount of red drives and errors. Ive attached diagnostics. i have a feeling that something is totally screwed in the system and i can't seem to figure it out. Anyone have any advice on how to proceed? Using a super micro X10SAE board and 2 sas2lp-mv8 cards Thanks tower-diagnostics-20160626-2240.zip
August 2, 20169 yr Community Expert That PSU has two +12V rails with only 25A available for your 15 drives. Might be enough but rebuilds and parity checks require all all drives running at the same time. The recommendation for unRAID is to only use PSUs with a single +12V.
August 16, 20169 yr Author Ok, picked up a corsair RM1000x. Installed, replaced a failed drive, rebuilt everything and all seems to be running well through parity checks. attached latest diagnostic. Everything seem to be in working order now? any idea on the HDD password issue? tower-diagnostics-20160808-0038.zip
Archived
This topic is now archived and is closed to further replies.