Hi guys,

 

I had a drive fail on me this morning (red dot appeared). I moved it out of the array, and started a rebuild with a new drive.

When I returned from work this evening, I noticed the new drive now also has a red dot on it too, so am unsure if the rebuild finished correctly.

 

To give some background, I have a 24 bay norco server. I have 17 active disks, a parity drive and some spares. Yesterday I installed a SIL3132 card into the server so I would be able to expand the array. After restarting, I copied a bunch of files to disk 17 (which was about 60% full) and went to bed. When I woke up I saw that not all the files had copied, and the drive had a red dot, and thus started the rebuild with the new drive.

 

I'm not sure the best way to proceed now. Try another disk? Remove the SIL3132?

 

As the attachment facility isn't currently working, I've put my syslog here:

 

https://www.dropbox.com/s/s7cyywn2anzy3a4/systlog.1.zip

 

I'm running Unraid 5.0-beta9. Any help greatly appreciated.

 

 

Since the problem started when you opened up the case to install the  SIL3132, maybe you knock a cable loose.  Go back and make sure all the cables are securely attached.

Should I swap back in my old (seemingly failed) drive for this test? I'm not sure how much of the new drive unraid managed to rebuild. There seems to be a bunch of working files on there, but this drive doesn't appear on the stats screen of the unraid menu.

 

I'm not sure what state my parity drive will be in after this partial rebuild, and whether its best to go back to the old drive, stick with the partially built drive or put a new drive into this slot.

 

I powered down,  checked all the cabling, powered up again. The server seemed to work ok, apart from the red dot on the latest drive. I replaced this drive and started a rebuild last night.

 

Coming back to it this morning, the web interface is unresponsive - can't seem to connect, and my syslog is huge and full of errors:

 

Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy2 : No sig fis

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy2 Attached Device

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 2 ctrl sts=0x89800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 2 irq sts = 0x1001

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy2 Unplug Notice

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 2 ctrl sts=0x199800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 2 irq sts = 0x81

Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy3 : No sig fis

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy3 Attached Device

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 3 ctrl sts=0x89800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 3 irq sts = 0x1001001

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy3 Unplug Notice

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 3 ctrl sts=0x199800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 3 irq sts = 0x81

Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy7 : No sig fis

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy7 Attached Device

Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy5 : No sig fis

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy5 Attached Device

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 5 ctrl sts=0x89800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 5 irq sts = 0x1001

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy5 Unplug Notice

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1081

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy7 Unplug Notice

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 5 ctrl sts=0x199800.

Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 5 irq sts = 0x81

 

Full file here:

 

https://www.dropbox.com/s/z7v9pvyi0n7p18d/syslog_today.zip

 

I'm not sure what to do. I don't want to reboot as it is in the middle of data rebuild, but server seems to be unresponsive and just constantly spamming errors to the syslog.

 

 

Check for BIOS and firmware updates.

Did you expand your array onto a new drive on the SIL card, or were you just coping files onto an existing disk in the array?

 

Did you try to preclear a disk on the SIL card? If not, and if you have enough ports to run your array without the new card, I would definitely yank it and get the server back to a stable condition where you are able to successfully rebuild the failed disk (preferably onto a spare). When rebuild, run a non-correcting parity check to make sure the rebuild was really successfull. Once you get there, you can hook up the new SIL card again and try to preclear your failed drive while hooked up to the SIL card. If that works, try running a non-correcting parity check while also preclearing the drive on the SIL card.