I have attached the syslog and smart reports for all drives

Thanks

syslog.txt

Would be helpful if you described the problems as well. I realize what the errors are but is there anything you do that causes this or is it every time you reboot. General information,

The syslog file names do not correlate correctly with disk#. Please correct the syslog file names.

Seems to happen when I reboot. It takes a long time for all the drives to mount.

I also have a orange colored dot on disk3 in the web interface.

 

Seems to happen when I reboot. It takes a long time for all the drives to mount.

I also have a orange colored dot on disk3 in the web interface.

I think disk3 was removed from service when a "write" to it failed.

Mar 26 15:35:55 Tower2 kernel: handle_stripe read error: 9040304/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 read error

Mar 26 15:35:55 Tower2 kernel: handle_stripe read error: 9040312/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 read error

Mar 26 15:35:55 Tower2 kernel: handle_stripe read error: 9040320/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 read error

Mar 26 15:35:55 Tower2 kernel: handle_stripe read error: 9040328/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 read error

Mar 26 15:35:55 Tower2 kernel: handle_stripe read error: 9040336/3, count: 1

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] Unhandled error code

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x04 driverbyte=0x00

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x2a: 2a 00 00 89 e9 17 00 04 00 00

Mar 26 15:35:55 Tower2 kernel: end_request: I/O error, dev sdd, sector 9038103

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] Unhandled error code

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x04 driverbyte=0x00

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x2a: 2a 00 00 89 ed 17 00 04 00 00

Mar 26 15:35:55 Tower2 kernel: end_request: I/O error, dev sdd, sector 9039127

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] Unhandled error code

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x04 driverbyte=0x00

Mar 26 15:35:55 Tower2 kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x2a: 2a 00 00 89 f1 17 00 01 00 00

Mar 26 15:35:55 Tower2 kernel: end_request: I/O error, dev sdd, sector 9040151

Mar 26 15:35:55 Tower2 kernel: md: disk3 write error

Mar 26 15:35:55 Tower2 kernel: handle_stripe write error: 9038040/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 write error

Mar 26 15:35:55 Tower2 kernel: handle_stripe write error: 9038048/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 write error

Mar 26 15:35:55 Tower2 kernel: handle_stripe write error: 9038056/3, count: 1

Mar 26 15:35:55 Tower2 kernel: md: disk3 write error

How do you reboot?

I use the web interface to stop and powerdown

 

I just stopped and rebooted and disk3 is still orange. I can still access the disk3 share so I am not sure how to fix this

 

Post a SMART report for disk3.

Here are the updated smart reports. The previous ones were incorrect. Sorry for that

TOWER2_smart_reports.zip

See here: http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues#Drive_interface_issue_.234

I will check it but I have not had it open in months.

 

I opened up the tower and checked all cables and everything was fine. I replaced the sata cable going to disk3 and restarted the tower

I am still seeing reddish/orange dot beside disk3 in the web page.

 

I have attached a recent syslog and a smart report of disk3

 

Here is a screenshot of the web page. I no longer see anything about the status of parity.

 

Screenshot

 

Thanks

syslog.txt

smart_report_disk3.txt

A drive that has a "red" indicator has had a "write" to it fail.

 

To get it back in service, it must be re-constructed (if it was just a loose cable)

 

See the wiki for instructions on how to get the drive to be recognized as its own replacement so it can be re-constructed.

 

http://lime-technology.com/wiki/index.php/FAQ#What_does_the_Red_Ball_mean.3F

Thanks Joe.

I am very confident that the drive is ok and the data is ok on it.

I have parity rebuilding on the drive now.