May 8, 201511 yr Was experiencing power surges at my home in the middle of a storm. The house had a power surge and put the server into a parity check. I stopped the parity in the middle while it was checking and did a safe power down. The next morning I see the error of Too many wrong and/or missing disks! What can I do to fix this? Not too sure where to start. Attached syslog just incase. syslog-2015-05-08.txt
May 8, 201511 yr Post a screenshot. What is your hardware? If you have multiple disks missing, are they on the same SATA controller?
May 8, 201511 yr Does your system have a UPS? If not, you may have had an actual surge the "took out" more than one of your disks (or SATA ports). As noted above, post a screenshot so we can see exactly what the GUI is "telling" you.
May 9, 201511 yr You didn't answer my question r.e. a UPS => Do you have one? I suspect the answer is No ... and that your system had a power surge that "took out" a secondary SATA controller that has 4 ports on it (the 4 ports your "missing" disks are connected to). Did you do anything to the server in between shutting it down and trying to restart it? .... Move it; open the case and blow out the dust; etc. If so, that could account for some loose cables or a loose add-in controller card. Otherwise that card has most probably failed. Just to be sure that's the issue, post your EXACT configuration => motherboard; add-in cards; etc. In any event, DO NOT attempt to Start your array; DO NOT do ANYTHING to the configuration; and DO NOT attempt to read your disks on any other system. ANY activity on the disks could invalidate your parity information; and just in case you actually have a failed disk you won't be able to recover it. Unless your card is not seated properly (possible if you moved the server or worked inside of it), I suspect you simply have a failed SATA card. You might want to try re-seating it ... remove it from the slot and then push it back in firmly. That MAY be all that's needed here.
May 9, 201511 yr Author I don't have a UPS. I also did not try to do anything between shutting it down and trying to restart. What happened is there was a storm and the lights in the house started flickering. I had noticed that the server had experienced a surge and it automatically started doing a parity check from it. Since the storm was getting pretty bad I immediately stopped the array and did a clean power down. The following day I booted it up and saw the error. I didn't physically touch the server in anyway. Below is my setup. Running UnRaid V4.7 G.SKILL 4GB (2 x 2GB) Dual Channel Kit Desktop Memory 3 NORCO SS-500 5 Bay SATA / SAS Hot Swap Rack Modules Intel Pentium E6700 Wolfdale 3.2GHz LGA 775 65W Dual-Core Processor 2 Serial ATA forward breakout cables SUPERMICRO MBD-C2SEA-O HDMI Intel Motherboard SUPERMICRO AOC-SASLP-MV8 PCI Express x4 Low Profile SAS RAID Controller Corsair 650W Powersupply
May 9, 201511 yr Assuming you have 6 disks connected to the 6 motherboard SATA ports; and the remaining 4 connected to your AOC-SASLP-MV8; then I think it's very likely that your SASLP-MV8 has failed. It's POSSIBLE that the slot on the motherboard failed, and not the card ... but that's fairly unlikely, since the system is otherwise running fine. I'd just replace the SATA card ... either with another SASLP-MV8, the newer SAS2LP-MV8, or with an Adaptec 1430SA, which is an excellent 4-port card that's obsolete but available on e-bay for a lot less than the SuperMicro cards would cost. The SuperMicro cards are better choices going forward (especially the newer SAS2LP version), as they'd be better for moving to a newer system should you upgrade your motherboard at some point; but the 1430SA's are good little workhorses and can be purchased for ~ $30 on e-bay. ... and buy yourself a good UPS !! [be sure it has AVR ... the really inexpensive units do not] This is a good choice for your system: http://www.newegg.com/Product/Product.aspx?Item=N82E16842101381
May 9, 201511 yr ... Note: If you happen to get a 1430SA, you have to disable the BIOS on it before using it to start your array. It's a very simple process => you just hit Ctrl-A during the POST when you first boot, and that will take you to the card's BIOS. You then just disable the onboard BIOS. Done Just reboot and UnRAID will load fine.
May 9, 201511 yr Just reboot and UnRAID will load fine.Except that he is running 4.7. Disk slot assignments will have to be manually verified and possibly corrected, as 4.7 is sensitive to port assignments. It wasn't until the 5.x series that unraid started identifying disk position by serial number.
May 9, 201511 yr ... Note: If you happen to get a 1430SA, you have to disable the BIOS on it before using it to start your array. It's a very simple process => you just hit Ctrl-A during the POST when you first boot, and that will take you to the card's BIOS. You then just disable the onboard BIOS. Done If you plan to attach disks > 2.2T to the 1430SA, make sure it has the latest firmware installed (downloadable from the Adaptec site).
May 9, 201511 yr ... Note: If you happen to get a 1430SA, you have to disable the BIOS on it before using it to start your array. It's a very simple process => you just hit Ctrl-A during the POST when you first boot, and that will take you to the card's BIOS. You then just disable the onboard BIOS. Done If you plan to attach disks > 2.2T to the 1430SA, make sure it has the latest firmware installed (downloadable from the Adaptec site). True -- HOWEVER, since he's running v4.7 that's clearly not an issue. [Would not, of course, hurt to just go ahead and do the firmware upgrade (if needed), so if he later decides to upgrade to v5/6 and larger disk sizes there's no issue at that point]
May 9, 201511 yr Just reboot and UnRAID will load fine.Except that he is running 4.7. Disk slot assignments will have to be manually verified and possibly corrected, as 4.7 is sensitive to port assignments. It wasn't until the 5.x series that unraid started identifying disk position by serial number. Good point => lianregnif ... be sure you confirm the disk assignments before starting the array. Since you've already posted them here, you've already got the serial numbers that need to be assigned to each of the "missing" slots.
May 9, 201511 yr True -- HOWEVER, since he's running v4.7 that's clearly not an issue. Of course you are right ... but I was thinking about the future
May 9, 201511 yr One other note: When you get a new controller and have all the disks assigned correctly and "seen" okay, I would expect the array will start just fine. But UnRAID MAY balk at the # of disks that were formerly missing and now assigned => if that's the case it will re-generate parity. There's no way in that situation to actually confirm that your drives themselves are okay unless you have good backups to compare the data to. But as long as your parity was good before, then your data's probably just fine as long as the surge that took out your controller didn't also take out any of the attached drives.
May 10, 201511 yr Author Thanks everyone...especially @garycase I'm going to unplug and plug in the sata card to see if that makes a difference. If not I will order another replacement SASLP-MV8. Will update if all is good.
May 10, 201511 yr Just to be CERTAIN that's the issue, you should confirm that the card indeed has 4 drives plugged in to it and that they're the 4 drives shown as missing ... Doesn't seem to be much doubt about that; but only YOU have direct access to the system to confirm that
May 17, 201511 yr Author Funny story..... I opened up the case and unplugged/replugged the sata card. Rebooted...and it recognized all the disks as if nothing had happened. I'm breathing such a big sigh of relief and am thankful it is not anything more than this. Guess I can return my spare back. Thank you everyone for helping! I feel embarrassed that I didn't try this before jumping on the community.
May 17, 201511 yr Perhaps you should have read my post from a week ago (May 9th) a bit closer ... or a loose add-in controller card ... ... You might want to try re-seating it ... remove it from the slot and then push it back in firmly. That MAY be all that's needed here.
Archived
This topic is now archived and is closed to further replies.