The syslog seems to indicate the drives stop responding, as if they were unplugged.

un 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 4 irq sts = 0x1000000

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 4 ctrl sts=0x89800.

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 4 irq sts = 0x1001001

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy4 Unplug Notice

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 4 ctrl sts=0x199800.

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 4 irq sts = 0x1001081

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 906:SATA/STP port 2 does not attachdevice.

Jun 19 23:15:37 Tower kernel: sas: sas_ata_task_done: SAS error 8a

Jun 19 23:15:37 Tower kernel: sas: Enter sas_scsi_recover_host

Jun 19 23:15:37 Tower kernel: ata7: sas eh calling libata cmd error handler

Jun 19 23:15:37 Tower kernel: ata5: sas eh calling libata port error handler

Jun 19 23:15:37 Tower kernel: ata6: sas eh calling libata port error handler

Jun 19 23:15:37 Tower kernel: ata7: sas eh calling libata port error handler

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 906:SATA/STP port 2 does not attachdevice.

Jun 19 23:15:37 Tower kernel: sas: sas_ata_task_done: SAS error 8a

Jun 19 23:15:37 Tower kernel: ata7: failed to read log page 10h (errno=-5)

Jun 19 23:15:37 Tower kernel: ata7.00: exception Emask 0x1 SAct 0x1 SErr 0x0 action 0x6

Jun 19 23:15:37 Tower kernel: ata7.00: failed command: READ FPDMA QUEUED

Jun 19 23:15:37 Tower kernel: ata7.00: cmd 60/00:00:b0:f4:4e/02:00:73:00:00/40 tag 0 ncq 262144 in

Jun 19 23:15:37 Tower kernel:          res 01/04:00:b0:f2:4e/00:00:73:00:00/40 Emask 0x3 (HSM violation)

Jun 19 23:15:37 Tower kernel: ata7.00: status: { ERR }

Jun 19 23:15:37 Tower kernel: ata7.00: error: { ABRT }

Jun 19 23:15:37 Tower kernel: ata7: hard resetting link

Jun 19 23:15:37 Tower kernel: sas: sas_ata_hard_reset: Found ATA device.

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 906:SATA/STP port 2 does not attachdevice.

Jun 19 23:15:37 Tower kernel: sas: sas_ata_task_done: SAS error 8a

Jun 19 23:15:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 906:SATA/STP port 2 does not attachdevice.

Jun 19 23:15:37 Tower kernel: sas: sas_ata_task_done: SAS error 8a

Jun 19 23:15:37 Tower kernel: ata7.00: both IDENTIFYs aborted, assuming NODEV

Jun 19 23:15:37 Tower kernel: ata7.00: revalidation failed (errno=-2)

Jun 19 23:15:39 Tower kernel: mvsas 0000:02:00.0: Phy4 : No sig fis

Jun 19 23:15:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2139:phy4 Attached Device

Jun 19 23:15:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 4 ctrl sts=0x89800.

Jun 19 23:15:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 4 irq sts = 0x1001001

Jun 19 23:15:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy4 Unplug Notice

Jun 19 23:15:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 4 ctrl sts=0x199800.

Jun 19 23:15:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 4 irq sts = 0x81

 

I'd look for a poor power connection or bad power splitter.

Once again, thank you.  I rebuilt the drive and replaced all the wires, double checked all the connections.  I'm really hoping this was just a coincidence and not a continuation of my problem.  I post back with my results in a few days.

Based on those Unplug notices, by any chance are these Seagate drives?

 

I have a 1TB Seagate drive (recently purchased) that would suddenly remove itself from system inventory and be totally unresponsive as if it wasn't plugged in until a cold boot.

I just replaced a another seagate, this time a 1.5 TB drive.

 

Are you using m1015 controller?

Based on those Unplug notices, by any chance are these Seagate drives?

 

I have a 1TB Seagate drive (recently purchased) that would suddenly remove itself from system inventory and be totally unresponsive as if it wasn't plugged in until a cold boot.

 

Yes, as a matter of fact they are all seagate 3TB drives.  What more can you tell me? Is there a solution to the problem?  Anything I can check to see if I'm having the same problem you did?

 

 

 

Once again, thank you.  I rebuilt the drive and replaced all the wires, double checked all the connections.  I'm really hoping this was just a coincidence and not a continuation of my problem.  I post back with my results in a few days.

 

Got another red ball on disk2.  Array wasn't even up 48 hours before it happened.  On the console I am getting a message saying

 

/dev/sda: No such file or directory
/dev/sdd: No such file or directory
/dev/sda: No such file or directory
/dev/sdd: No such file or directory
/dev/sda: No such file or directory
/dev/sdd: No such file or directory
/dev/sda: No such file or directory
/dev/sdd: No such file or directory

 

This refreshes every 10 seconds or so and continuously says the same thing over and over.  Attached is a syslog.

syslog-2012-06-23.txt.zip

I have had a glimmer of hope.  My server has been running for 13 days now with no red disks.  What I've done different was to preclear a spare drive and then used it to replace the parity drive.  Rebuilt parity and haven't had any problems.  I won't call this problem solved just yet, but I am very happy to at least see some progress.

 

Anyone have any idea why this seems to have helped...or why the parity drive could cause random disks to fail?