knohm Posted December 1, 2011 Posted December 1, 2011 Hi, I keep getting the following errors in my syslog Dec 1 10:20:21 JAMES-NAS kernel: ata5: hard resetting link (Minor Issues) Dec 1 10:20:22 JAMES-NAS kernel: ata5: SATA link down (SStatus 0 SControl 300) (Drive related) Dec 1 10:20:22 JAMES-NAS kernel: ata5: EH complete (Drive related) Dec 1 10:20:45 JAMES-NAS kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen (Errors) Dec 1 10:20:45 JAMES-NAS kernel: ata5: irq_stat 0x00000040, connection status changed (Drive related) Dec 1 10:20:45 JAMES-NAS kernel: ata5: SError: { DevExch } (Errors) Dec 1 10:20:45 JAMES-NAS kernel: ata5: hard resetting link (Minor Issues) Dec 1 10:20:46 JAMES-NAS kernel: ata5: SATA link down (SStatus 0 SControl 300) (Drive related) Dec 1 10:20:46 JAMES-NAS kernel: ata5: EH complete (Drive related) Dec 1 10:20:49 JAMES-NAS kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen (Errors) Dec 1 10:20:49 JAMES-NAS kernel: ata5: irq_stat 0x00000040, connection status changed (Drive related) Dec 1 10:20:49 JAMES-NAS kernel: ata5: SError: { DevExch } (Errors) Dec 1 10:20:49 JAMES-NAS kernel: ata5: limiting SATA link speed to 1.5 Gbps (Drive related) Dec 1 10:20:49 JAMES-NAS kernel: ata5: hard resetting link (Minor Issues) Dec 1 10:20:50 JAMES-NAS kernel: ata5: SATA link down (SStatus 0 SControl 310) (Drive related) Dec 1 10:20:50 JAMES-NAS kernel: ata5: EH complete (Drive related) I have progressively removed hardware in an effort to isolate the problem however late last night with just the unraid flash drive and no drives connected I was still getting the ata5 errors which caused me to throw my hands in the air and walk away. I was getting the issues on 5b13 and 5b12. Currently I am running 5b11 The hardware: Asus P5k Intel Q6600 4gig gskill ddr2 No name pci vga card supermicro SASLVP-mv8 (pciex4) The log above and attached was taken when after I had removed the SASLVP-MV8 and all the drives bar 2 hitachi 2tb drives (a 5400 and a 7200rpm). Both drives are new and have been run through 4 preclears each with no issues. The version being used in this log is 5b11 Does anyone have any suggestions? Currently I am pointing the finger at the P5k but was hoping someone might have some suggestions before I go buying a new board. syslog-2011-12-01.txt
sacretagent Posted December 1, 2011 Posted December 1, 2011 HI the ata5 stands for disk 5 i had mine trow this similar error at me on ata13 .. after checking the disk and seeing a bunch of pending sectors .... and replacing the disk did it stop weird thing is that it seems you have nothing connected to port 5 Nov 30 23:05:22 JAMES-NAS kernel: ata5: SATA max UDMA/133 abar m8192@0xfbffe000 port 0xfbffe100 irq 16 Nov 30 23:05:22 JAMES-NAS kernel: ata6: SATA max UDMA/133 abar m8192@0xfbffe000 port 0xfbffe180 irq 16 Nov 30 23:05:22 JAMES-NAS kernel: ata5: SATA link down (SStatus 0 SControl 300) Nov 30 23:05:22 JAMES-NAS kernel: ata6: SATA link down (SStatus 0 SControl 300) so try disabling the port from the bios ... if there is something connected to port 5 then check the sata cable and/or the power cable also run a smart report to see if there is nothing wrong with the disk if there is one connected for any case hope this helps
dgaschk Posted December 1, 2011 Posted December 1, 2011 ata 5 does not stand for disk5. ata numbers are related to the physical SATA port connections and disk number is user assigned. There are known incompatibilities between b12, b13 and SASLVP-mv8. These have been reported in the respective Announcement threads. Please read the Announcements thread.
knohm Posted December 1, 2011 Author Posted December 1, 2011 Yes, I am aware of the issues that have been discovered... hence the rollback to b11 during my testing. The errors persisted with our without the SASLVP-mv8 on each version. As I posted, the log I have attached is of 2 drives running off the motherboard sata ports. All other cards and drives have been removed. The 2 drives are known good drives that perform with no issues on another unraid setup. What leaves me scratching my head, is the fact that the same errors appear when there are no drives connected at all and no cards installed (sata card or vid card) I have disabled a few things in the bios of the board, I will post back with results.
generalz Posted December 4, 2011 Posted December 4, 2011 I've seen this too. Not sure whats causing it. My log also specifies no drive installed on ata5
Recommended Posts
Archived
This topic is now archived and is closed to further replies.