January 2, 201115 yr Is this anything to be worried about? I just saw this errors. Jan 2 03:30:01 Tower logger: mover finished Jan 2 04:08:54 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen Jan 2 04:08:54 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error Jan 2 04:08:54 Tower kernel: ata1: SError: { Handshk } Jan 2 04:08:54 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jan 2 04:08:54 Tower kernel: ata1.00: cmd 35/00:d8:a7:37:de/00:03:02:00:00/e0 tag 0 dma 503808 out Jan 2 04:08:54 Tower kernel: res 50/00:00:a6:37:de/00:00:02:00:00/e0 Emask 0x10 (ATA bus error) Jan 2 04:08:54 Tower kernel: ata1.00: status: { DRDY } Jan 2 04:08:54 Tower kernel: ata1: hard resetting link Jan 2 04:08:54 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 2 04:08:54 Tower kernel: ata1.00: configured for UDMA/133 Jan 2 04:08:54 Tower kernel: ata1: EH complete Thx in advance
January 2, 201115 yr Check that the power connection and the SATA cable connections are well seated. These type of errors tend to pop up with either of those being the culprit. Post a full system spec and we might be able to point out what might be causing the issue.
January 2, 201115 yr Just to add, I started getting the same errors when I upgraded to 4.6. I've reseated the cables, ran a Long Smart test and everything was fine. Can this be something with the new version of unRAID? I'm curious if re-seating the cables will work for slarco.
January 4, 201115 yr Bump, curious what else this can be aside from cables or connection. Did re-seating the cables fix the issue for you slarco?
January 4, 201115 yr This is def a drive related issue and not something specific to unRAID. It might be that a newer kernel is in unRAID that has "tighter" timing then the older one. Also, the above snippet shows SATA 6.0Gbps and it might be an incompatibility between the disk being SATA 2 (i.e. 3.0 Gbps) and SATA 3 (i.e. 6.0 Gbps). I have heard of SATA 3.0 Gbps drives not working properly on SATA 1.5 Gbps controllers until the drive was jumpered to run at only 1.5 Gbps speed.
Archived
This topic is now archived and is closed to further replies.