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.

strange errors

Featured Replies

Jul  8 03:31:56 unRAID kernel: ata1.00: exception Emask 0x50 SAct 0x7800 SErr 0x400800 action 0x6 frozen (Errors)

Jul  8 03:31:56 unRAID kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)

Jul  8 03:31:56 unRAID kernel: ata1: SError: { HostInt Handshk } (Errors)

Jul  8 03:31:56 unRAID kernel: ata1.00: failed command: WRITE FPDMA QUEUED (Minor Issues)

Jul  8 03:31:56 unRAID kernel: ata1.00: cmd 61/e0:58:bf:d6:51/03:00:09:00:00/40 tag 11 ncq 507904 out (Drive related)

Jul  8 03:31:56 unRAID kernel:          res 40/00:70:e7:dd:12/00:00:0e:00:00/40 Emask 0x50 (ATA bus error) (Errors)

Jul  8 03:31:56 unRAID kernel: ata1.00: status: { DRDY } (Drive related)

Jul  8 03:31:56 unRAID kernel: ata1.00: failed command: WRITE FPDMA QUEUED (Minor Issues)

Jul  8 03:31:56 unRAID kernel: ata1.00: cmd 61/00:60:a7:da:51/04:00:09:00:00/40 tag 12 ncq 524288 out (Drive related)

Jul  8 03:31:56 unRAID kernel:          res 40/00:70:e7:dd:12/00:00:0e:00:00/40 Emask 0x50 (ATA bus error) (Errors)

Jul  8 03:31:56 unRAID kernel: ata1.00: status: { DRDY } (Drive related)

Jul  8 03:31:56 unRAID kernel: ata1.00: failed command: WRITE FPDMA QUEUED (Minor Issues)

Jul  8 03:31:56 unRAID kernel: ata1.00: cmd 61/30:68:a7:de:51/01:00:09:00:00/40 tag 13 ncq 155648 out (Drive related)

Jul  8 03:31:56 unRAID kernel:          res 40/00:70:e7:dd:12/00:00:0e:00:00/40 Emask 0x50 (ATA bus error) (Errors)

Jul  8 03:31:56 unRAID kernel: ata1.00: status: { DRDY } (Drive related)

Jul  8 03:31:56 unRAID kernel: ata1.00: failed command: READ FPDMA QUEUED (Minor Issues)

Jul  8 03:31:56 unRAID kernel: ata1.00: cmd 60/00:70:e7:dd:12/02:00:0e:00:00/40 tag 14 ncq 262144 in (Drive related)

Jul  8 03:31:56 unRAID kernel:          res 40/00:70:e7:dd:12/00:00:0e:00:00/40 Emask 0x50 (ATA bus error) (Errors)

Jul  8 03:31:56 unRAID kernel: ata1.00: status: { DRDY } (Drive related)

Jul  8 03:31:56 unRAID kernel: ata1: hard resetting link (Minor Issues)

Jul  8 03:31:57 unRAID kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) (Drive related)

Jul  8 03:31:57 unRAID kernel: ata1.00: configured for UDMA/133 (Drive related)

Jul  8 03:31:57 unRAID kernel: ata1: EH complete (Drive related)

 

 

I am not sure what is going on here, but as you can see, I am getting these error... I am not quite sure where the issue is, or if it is a drive, or controller issue?

 

I am running an ASROCK A785GM-LE/128M mother board, with an athlon x640 processor, it has 6 onboard SATA ports, and then I have 2x VANTEC UGT-ST310R controller cards (PCI 4port sata).

 

I've never had any issue, until last week when I changed my case out for a better air flowing case, then for some reason, i had a drive failure (ended up with TONNES of errors), so I swapped the drive out, and it rebuilt fine.  I am in the midst of preclearing another drive as I have < 200GB free in the array

 

oh yeah, my array consists of 9 (soon to be 10) WD20EARS drives (jumpered 7/8) and a single 160GB sata drive I use as my download drive (not attached to the array)

 

Any pointers in the right direction to why i am getting these errrors, or what you think they are... would be helpful.

 

thanks in advance!

 

TheStapler  (steve)

  • Author

So, I did a smart scan on my "other drive" that is not part of the array...

 

http://pastebin.com/H8zxbWEM

 

maybe this is the problem?

Jul  8 03:31:57 unRAID kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) (Drive related)

 

This is indicating you have a SATA cable problem, assuming the drive is connected to a SATA II or SATA III port. Try a new SATA cable.

 

Peter

 

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.