Kandinsky Posted May 19, 2013 Share Posted May 19, 2013 Dear Experts, I am getting the errors below which seem to be repeating themselves over a short period of time. Should I be worried, if so how can I identify which drive is looking dodgy please? I am using the latest 12a release. Now with full syslog attached. Not sure which drive I need to give any smart report on since I don't know which one it is. May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x800 action 0x6 frozen (Errors) May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) May 19 12:20:10 GOOGOLPLEX kernel: ata1: SError: { HostInt } (Errors) May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: failed command: IDENTIFY DEVICE (Minor Issues) May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) May 19 12:20:10 GOOGOLPLEX kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) (Errors) May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related) May 19 12:20:10 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:20:20 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues) May 19 12:20:20 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:20:30 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues) May 19 12:20:30 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:20:31 GOOGOLPLEX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 19 12:20:31 GOOGOLPLEX kernel: ata1.00: link online but device misclassified (Drive related) May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: qc timeout (cmd 0xec) (Drive related) May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (Errors) May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: revalidation failed (errno=-5) (Minor Issues) May 19 12:20:36 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:20:46 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues) May 19 12:20:46 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:20:56 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues) May 19 12:20:56 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:20:56 GOOGOLPLEX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 19 12:20:56 GOOGOLPLEX kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100) (Errors) May 19 12:20:56 GOOGOLPLEX kernel: ata1.00: revalidation failed (errno=-5) (Minor Issues) May 19 12:20:56 GOOGOLPLEX kernel: ata1: limiting SATA link speed to 1.5 Gbps (Drive related) May 19 12:21:01 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:21:02 GOOGOLPLEX kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) May 19 12:21:02 GOOGOLPLEX kernel: ata1.00: configured for UDMA/133 (Drive related) May 19 12:21:02 GOOGOLPLEX kernel: ata1: EH complete (Drive related) May 19 12:21:44 GOOGOLPLEX kernel: mdcmd (51): check CORRECT (unRAID engine) May 19 12:21:44 GOOGOLPLEX kernel: md: recovery thread woken up ... (unRAID engine) May 19 12:21:44 GOOGOLPLEX kernel: md: recovery thread checking parity... (unRAID engine) May 19 12:21:44 GOOGOLPLEX kernel: md: using 1536k window, over a total of 2930266532 blocks. (unRAID engine) May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x400801 action 0x6 frozen (Errors) May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) May 19 12:22:32 GOOGOLPLEX kernel: ata1: SError: { RecovData HostInt Handshk } (Errors) May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: failed command: READ DMA EXT (Minor Issues) May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: cmd 25/00:00:40:20:14/00:04:00:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 12:22:32 GOOGOLPLEX kernel: res 50/00:00:3f:20:14/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) (Errors) May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related) May 19 12:22:32 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) May 19 12:22:32 GOOGOLPLEX kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: configured for UDMA/133 (Drive related) May 19 12:22:32 GOOGOLPLEX kernel: ata1: EH complete (Drive related) May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x800 action 0x6 frozen (Errors) May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) May 19 12:22:33 GOOGOLPLEX kernel: ata1: SError: { HostInt } (Errors) May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: failed command: READ DMA EXT (Minor Issues) May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: cmd 25/00:00:40:80:14/00:04:00:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 12:22:33 GOOGOLPLEX kernel: res 50/00:00:3f:80:14/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) (Errors) May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related) syslog-2013-05-19.zip Quote Link to comment
dgaschk Posted May 21, 2013 Share Posted May 21, 2013 Looks like disk4. Try a new SATA cable. Quote Link to comment
Kandinsky Posted May 23, 2013 Author Share Posted May 23, 2013 Dear Experts, I both replaced the cable and the drive since I had a spare one. Please see attached the updated log. Am i getting drive problems again as now its ata4. How can I correlate the ATA errors to the relevant HDD please as I can't see the link in the logs? Cheers! syslog-2013-05-23.zip Quote Link to comment
dgaschk Posted May 23, 2013 Share Posted May 23, 2013 The errors indicate a SATA problem. Two of the drives, hda and hdb, are not configured as AHCI in BIOS. All of the drive designations should begin with sd. This may be causing the issue and should be fixed in any case. It is difficult to match ata numbers with device names or sd letter assignment. The device model is indicated here: May 21 08:40:59 GOOGOLPLEX kernel: ata4.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133 See here if the AHCI setting doesn't work: http://lime-technology.com/forum/index.php?topic=27414.msg241280#msg241280 Quote Link to comment
Joe L. Posted May 24, 2013 Share Posted May 24, 2013 The errors indicate a SATA problem. Two of the drives, hda and hdb, are not configured as AHCI in BIOS. All of the drive designations should begin with sd. This may be causing the issue and should be fixed in any case. It is difficult to match ata numbers with device names or sd letter assignment. The device model is indicated here: May 21 08:40:59 GOOGOLPLEX kernel: ata4.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133 See here if the AHCI setting doesn't work: http://lime-technology.com/forum/index.php?topic=27414.msg241280#msg241280 Look here for a possible way to match ataX device name to /dev device: http://lime-technology.com/forum/index.php?topic=27414.msg241280;topicseen#msg241280 Quote Link to comment
Kandinsky Posted May 24, 2013 Author Share Posted May 24, 2013 The errors indicate a SATA problem. Two of the drives, hda and hdb, are not configured as AHCI in BIOS. All of the drive designations should begin with sd. This may be causing the issue and should be fixed in any case. It is difficult to match ata numbers with device names or sd letter assignment. The device model is indicated here: May 21 08:40:59 GOOGOLPLEX kernel: ata4.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133 See here if the AHCI setting doesn't work: http://lime-technology.com/forum/index.php?topic=27414.msg241280#msg241280 Since I set the BIOS originally for AHCI, how can I have some HDD's showing up as sdX and some as hdx? Could it have anything to do with the drives themselves please? Quote Link to comment
Joe L. Posted May 24, 2013 Share Posted May 24, 2013 The errors indicate a SATA problem. Two of the drives, hda and hdb, are not configured as AHCI in BIOS. All of the drive designations should begin with sd. This may be causing the issue and should be fixed in any case. It is difficult to match ata numbers with device names or sd letter assignment. The device model is indicated here: May 21 08:40:59 GOOGOLPLEX kernel: ata4.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133 See here if the AHCI setting doesn't work: http://lime-technology.com/forum/index.php?topic=27414.msg241280#msg241280 Since I set the BIOS originally for AHCI, how can I have some HDD's showing up as sdX and some as hdx? Could it have anything to do with the drives themselves please? Unless you have older IDE drives connected to an IDE disk controller, no disks should show as hdX. Frequently, there are two separate settings in the BIOS, especially if there are more than 4 SATA ports, as frequently 2 or more of the SATA ports are on a different disk controller chip. (Windows XP and prior have no SATA drivers, so all the BIOS emulate IDE drives on some ports by default, so those Older MS-windows OS can boot. Otherwise, there would be a lot of returned MB and disks) Look for a second BIOS setting for the second set of disk controller ports. It has absolutely nothing to do with the drives themselves. Joe L. Quote Link to comment
dgaschk Posted May 24, 2013 Share Posted May 24, 2013 How are the drives connected? Some SATA cards have their own BIOS that is distinct from the MB BIOS. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.