Here is the systemlog from last night while it was doing a Parity rebuild...

 

http://www.sendspace.com/file/qn8m2p

When I get home first thing I'm going to do is try and add the second Molex and see if that doesn't help...

Please do. That has caused issues for a number of people.

 

Peter

Well I added the 2nd set of molex to the backplane. Disk10 is coming up unformatted! This without a question has data on it! What do I do?!?!

I have a debian linux box here if I should just bring this thing into linux and get the data off it (all i care about)

Oh and I also care about keeping the data on all the other drives

Well I mounted disk10 into my debian box and copying the data off now.

So what is my next step? I have disk10 missing with a bad parity drive.... Should I do a New Config and forget Disk10, build new parity, add new drive and then copy over the older data from Disk10?

Yes, I think that's about all you can do now.

You have 2 option for disk 10 recovery:

 

1. Run reiserfsck on the drive.

 

2. Put the drive in another machine and try to read the contents.

You have 2 option for disk 10 recovery:

 

1. Run reiserfsck on the drive.

 

2. Put the drive in another machine and try to read the contents.

 

Yup I mounted it in my debian box and pulled all the data off of it. It seems to be fine in this debian box, but it has me wondering about the status of that drive spot/card/cable.

Damn, errors are still flooding the system log even after I switched out the SASLP card with a known working one. I guess the next step is to swap that cable and see if the errors move to the other card.

 

May 13 15:10:02 unraid kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! (Drive related)
May 13 15:10:04 unraid kernel: drivers/scsi/mvsas/mv_sas.c 1586:mvs_I_T_nexus_reset for device[1]:rc= 0 (System)
May 13 15:10:04 unraid kernel: sas: I_T 0100000000000000 recovered (Drive related)
May 13 15:10:04 unraid kernel: sas: sas_ata_task_done: SAS error 8d (Errors)
May 13 15:10:04 unraid kernel: ata8: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related)
May 13 15:10:04 unraid kernel: ata8: status=0x01 { Error } (Errors)
May 13 15:10:04 unraid kernel: ata8: error=0x04 { DriveStatusError } (Errors)
May 13 15:10:04 unraid kernel: sas: --- Exit sas_scsi_recover_host (Drive related)
May 13 15:10:04 unraid kernel: sas: sas_to_ata_err: Saw error 2.  What to do? (Errors)
May 13 15:10:04 unraid kernel: sas: sas_ata_task_done: SAS error 2 (Errors)
May 13 15:10:04 unraid kernel: ata8: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related)
May 13 15:10:04 unraid kernel: ata8: status=0x01 { Error } (Errors)
May 13 15:10:04 unraid kernel: ata8: error=0x04 { DriveStatusError } (Errors)
May 13 15:10:04 unraid kernel: sas: sas_to_ata_err: Saw error 2.  What to do? (Errors)
May 13 15:10:04 unraid kernel: sas: sas_ata_task_done: SAS error 2 (Errors)
May 13 15:10:04 unraid kernel: ata10: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related)
May 13 15:10:04 unraid kernel: ata10: status=0x01 { Error } (Errors)
May 13 15:10:04 unraid kernel: ata10: error=0x04 { DriveStatusError } (Errors)
May 13 15:10:04 unraid kernel: sas: sas_to_ata_err: Saw error 2.  What to do? (Errors)
May 13 15:10:04 unraid kernel: sas: sas_ata_task_done: SAS error 2 (Errors)
May 13 15:10:04 unraid kernel: ata12: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related)
May 13 15:10:04 unraid kernel: ata12: status=0x01 { Error } (Errors)
May 13 15:10:04 unraid kernel: ata12: error=0x04 { DriveStatusError } (Errors)
May 13 15:10:04 unraid kernel: sas: sas_to_ata_err: Saw error 2.  What to do? (Errors)
May 13 15:10:04 unraid kernel: sas: sas_ata_task_done: SAS error 2 (Errors)
May 13 15:10:04 unraid kernel: ata8: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related)
May 13 15:10:04 unraid kernel: ata8: status=0x01 { Error } (Errors)
May 13 15:10:04 unraid kernel: ata8: error=0x04 { DriveStatusError } (Errors)
May 13 15:10:04 unraid kernel: sas: sas_to_ata_err: Saw error 2.  What to do? (Errors)
May 13 15:10:04 unraid kernel: sas: sas_ata_task_done: SAS error 2 (Errors)
May 13 15:10:04 unraid kernel: ata8: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related)
May 13 15:10:04 unraid kernel: ata8.00: device reported invalid CHS sector 0 (Drive related)
May 13 15:10:04 unraid kernel: ata8: status=0x01 { Error } (Errors)
May 13 15:10:04 unraid kernel: ata8: error=0x04 { DriveStatusError } (Errors)

Well I swapped the cable that connects to the card and the backplane and the same errors are still showing up. I'm starting to think that this backplane might be bad...

 

Has anyone dealt with Norco and replacing/RMA'ing the backplanes?

I got one replaced by them with no issue at all, in fact they seemed to go out of their way to make me happy.

I know there was another post were a user got a brand new Norco with damaged parts and they seemd pretty quick to setup an RMA. Contact them, they seem to have good support.

 

Shawn

 

I got one replaced by them with no issue at all, in fact they seemed to go out of their way to make me happy.

 

Great news!! I'm wondering how you the heck you go about removing the blackplane? Is there a diagram that shows the steps to remove just one? The one that I'm having problems with is the third one from the top...

 

Thank you,

just remove the silver thumbscrews. it will just slide out (into the  case)...

 

the bad part is.... you might have to take the fanwall out.

 

i think they hired a gorilla to to put some of my thumbscrews in... i needed screwdriver for those.

 

you could try swapping 2 backplains and see if the trouble migrates with the backplane...

 

also, if you have a regular breakout cable and enough  sata power connectors.. you could just bypass the backplane and plug right into the back of the drives to test (and use while backplane is in transit)

What is this error that repeats over and over in my system log (unmenu has it highlighted in blue)

 

May 15 14:38:39 unraid kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 4 irq sts = 0x1000000 (System)
May 15 14:38:43 unraid kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 4 ctrl sts=0x199800. (System)

What is this error that repeats over and over in my system log (unmenu has it highlighted in blue)

 

May 15 14:38:39 unraid kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 4 irq sts = 0x1000000 (System)
May 15 14:38:43 unraid kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 4 ctrl sts=0x199800. (System)

what makes you think that is an error?  It looks more like a status message to me.

Joe,

 

There are thousands upon thousands of lines in my system log with that message... Just trying to understand that it's saying to try and fix it.

Joe,

 

FYI I just checked my Systemlog through unMENU and all 5000 lines are all those two 'errors'...

hrmm... it looks like the internet search engine called google found others in the linux world having these errors

 

http://linux.derkeiler.com/Mailing-Lists/Kernel/2010-10/msg12718.html

 

Thoughts?

i think it is a bad drive, once i swapped my drive, that error went away.

 

have you moved the drive to another slot in the norco and see if the  error changes port id?

i think it is a bad drive, once i swapped my drive, that error went away.

 

have you moved the drive to another slot in the norco and see if the  error changes port id?

 

I don;t know which drive it is... that is main problem

Port 4, sounds like the 4th port or the drive connected to the 4th port on one of the cards is acting up. I'm just not sure if they number 0 to 7 or 1 to 8.

 

I think you're going to have to unassign a single drive at a time and see if you can find one  that is causing the issue. If you have a free port or 2 on the motherboard or another different card then you could likely keep swapping drives over to that spot. Otherwise, you'll likely have to keep unassigning and unconnecting them and then putting them back. I'd honestly consider just unassigning parity to make it go easier until you figure out where the problem is. But then, at that point you could just drop groups of drives out and narrow it down that way. You know, pull half of the drives. If the problem remains pull half of the remaining ones. Otherwise, stick in the other half and if the problem comes back then pull half of them. You could also move them around on different groups of ports. Keep going until you find the issue.

 

Peter