Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ATA Error every 6 seconds

Featured Replies

After years of minimal issues, it looked like a drive was failing so I replaced it. Now, I can't seem to keep anything up and running. Tried new drives, swapping cables, everything. Do I need a new power supply? A new mobo? Is it a SATA controller? This is my log, and it repeats this way every 6 seconds forever:

 

Jan 5 18:53:19 tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
Jan 5 18:53:19 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Jan 5 18:53:19 tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Jan 5 18:53:19 tower kernel: ata2.00: failed command: READ DMA EXT
Jan 5 18:53:19 tower kernel: ata2.00: cmd 25/00:40:c0:ae:11/00:05:2f:00:00/e0 tag 5 dma 688128 in
Jan 5 18:53:19 tower kernel: res 50/00:00:bf:ae:11/00:00:2f:00:00/e0 Emask 0x50 (ATA bus error)
Jan 5 18:53:19 tower kernel: ata2.00: status: { DRDY }
Jan 5 18:53:19 tower kernel: ata2: hard resetting link
Jan 5 18:53:24 tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 18:53:24 tower kernel: ata2.00: configured for UDMA/33
Jan 5 18:53:24 tower kernel: ata2: EH complete
Jan 5 18:53:24 tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
Jan 5 18:53:24 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Jan 5 18:53:24 tower kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Jan 5 18:53:24 tower kernel: ata2.00: failed command: READ DMA EXT
Jan 5 18:53:24 tower kernel: ata2.00: cmd 25/00:40:40:d1:11/00:05:2f:00:00/e0 tag 29 dma 688128 in
Jan 5 18:53:24 tower kernel: res 50/00:00:3f:d1:11/00:00:2f:00:00/e0 Emask 0x10 (ATA bus error)
Jan 5 18:53:24 tower kernel: ata2.00: status: { DRDY }
Jan 5 18:53:24 tower kernel: ata2: hard resetting link
Jan 5 18:53:30 tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 18:53:30 tower kernel: ata2.00: configured for UDMA/33
Jan 5 18:53:30 tower kernel: ata2: EH complete
Jan 5 18:53:30 tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
Jan 5 18:53:30 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Jan 5 18:53:30 tower kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Jan 5 18:53:30 tower kernel: ata2.00: failed command: READ DMA EXT
Jan 5 18:53:30 tower kernel: ata2.00: cmd 25/00:80:40:0a:12/00:01:2f:00:00/e0 tag 27 dma 196608 in
Jan 5 18:53:30 tower kernel: res 50/00:00:3f:0a:12/00:00:2f:00:00/e0 Emask 0x10 (ATA bus error)
Jan 5 18:53:30 tower kernel: ata2.00: status: { DRDY }
Jan 5 18:53:30 tower kernel: ata2: hard resetting link
Jan 5 18:53:36 tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 18:53:36 tower kernel: ata2.00: configured for UDMA/33
Jan 5 18:53:36 tower kernel: ata2: EH complete
Jan 5 18:53:36 tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
Jan 5 18:53:36 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Jan 5 18:53:36 tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Jan 5 18:53:36 tower kernel: ata2.00: failed command: READ DMA EXT
Jan 5 18:53:36 tower kernel: ata2.00: cmd 25/00:40:c0:68:12/00:05:2f:00:00/e0 tag 4 dma 688128 in
Jan 5 18:53:36 tower kernel: res 50/00:00:bf:68:12/00:00:2f:00:00/e0 Emask 0x50 (ATA bus error)
Jan 5 18:53:36 tower kernel: ata2.00: status: { DRDY }
Jan 5 18:53:36 tower kernel: ata2: hard resetting link

  • 2 weeks later...
  • Author

I got frustrated and replaced all cables in the box, and that seems to have stopped the error. So frustrating 😖

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.