March 26, 201214 yr I APOLOGIZE. THIS WAS SUPPOSED TO BE POSTED IN GENERAL SUPPORT. so i had been struggling with a drive these past few days. just a quick rundown of how my server is setup. biostar a880g+ 3x norco ss-400 hotswap bays supermicro AOC-SASLP-MV8 card so this is how the problem goes. my setup was to put my first 4 drives on the topmost hotswap bay (we'll refer to this one as hotswap bay 1), which is connected to the supermicro card. at first, everything was fine. then all of a sudden, i started receiving read/write/io errors on disk2 (disk is in the third slot of hotswap bay 1). i ran a few SMART tests on the drive and they all passed. now, i decided to run another preclear on the drive. i removed it from hotswap bay 1, and put into hotswap bay 3 (bottom-most hotswap bay, which is connected directly to onboard sata ports on mobo). preclear ran fine, no errors. i ran another smart report on the drive and all was fine. so, in order to keep things organized, i shutdown, removed the drive from hotswap bay 3 and back into the empty slot in hotswap bay 1. booted up, started the parity with the disk2 unassigned, stopped, assigned the drive to disk2 and started parity (so it could rebuild the drive). right away, the web menu showed 320+ errors. (syslog is attached). ran another smart report, all gravy! so by this time i figured "oh well, drive is toast." let a few hours go by and decided "hey, just for the sake of argument, let me try putting it back into hotswap bay 3 and see if it works that way." so went back and swapped it into hotswap bay 3, boot up, stopped parity, assigned drive to disk2, started parity and rebuild is going fine now. this leads me to believe that the problem lies in a few places. 1) one of the sata cables connected to hotswap bay 1 is loose or bad. it's a breakout sas cable so i checked and everything seemed ok on both ends. i even swapped to another breakout cable to ensure it wasn't a cable issue. 2) something is wrong with the supermicro card (unlikely since every other drive is working). 3) something is wrong with the backplane of the hotswap bay 1. all the other ports on it work just fine apparently, but i have seen weirder things happen! expert opinions please? this was driving me crazy all weekend and i was almost CERTAIN it was the drive. thanks for taking the time to read! syslog-2012-03-24.zip
Archived
This topic is now archived and is closed to further replies.