Hi I have this error in my syslog, is this something to take some action on ?

 

Jan 5 12:47:51 Tower kernel: sd 2:0:0:0: [sda] Starting disk

Jan 5 12:47:51 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Jan 5 12:47:51 Tower kernel: ata4: SError: { DevExch }

Jan 5 12:47:51 Tower kernel: ata4.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 0

Jan 5 12:47:51 Tower kernel: res 7f/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x12 (ATA bus error)

 

Jan 5 12:47:51 Tower kernel: sd 4:0:0:0: [sdb] Starting disk

Jan 5 12:47:51 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Jan 5 12:47:51 Tower kernel: ata4: SError: { DevExch }

Jan 5 12:47:51 Tower kernel: ata4.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 0

Jan 5 12:47:51 Tower kernel: res 7f/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x12 (ATA bus error)

 

 

EDIT

 

These 2 disk are on my new adaptec 1430SA card

 

Hi I have this error in my syslog, is this something to take some action on ?

 

Jan 5 12:47:51 Tower kernel: sd 2:0:0:0: [sda] Starting disk

Jan 5 12:47:51 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Jan 5 12:47:51 Tower kernel: ata4: SError: { DevExch }

Jan 5 12:47:51 Tower kernel: ata4.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 0

Jan 5 12:47:51 Tower kernel: res 7f/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x12 (ATA bus error)

 

Jan 5 12:47:51 Tower kernel: sd 4:0:0:0: [sdb] Starting disk

Jan 5 12:47:51 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Jan 5 12:47:51 Tower kernel: ata4: SError: { DevExch }

Jan 5 12:47:51 Tower kernel: ata4.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 0

Jan 5 12:47:51 Tower kernel: res 7f/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x12 (ATA bus error)

 

 

EDIT

 

These 2 disk are on my new adaptec 1430SA card

 

These errors come after putting your server to s3 sleep. 

 

Either

1. Do not put your server to sleep, as it is not supported by unRAID.

or

2. Ignore the errors you get as hardware wakes up after putting your server to sleep.  Expect them.  Many drivers/hardware combinations do not expect to be turned off, but do remarkably well in resetting, once turned back on.

 

and

 

3.  Google is your friend. 

 

Joe L.

Thanks Joe for a quick answer.

 

I'm going to google this and see if the problem could be in the kernel..... or my hardware 

 

 

I need to have the server in sleepmode when we don't watch any movies, so I hope this can be "supported in the version 5 

 

//Peter

Thanks Joe for a quick answer.

 

I'm going to google this and see if the problem could be in the kernel..... or my hardware 

 

 

I need to have the server in sleepmode when we don't watch any movies, so I hope this can be "supported in the version 5 

 

//Peter

As I already said , your hardware needs to be reset when waking.  The errors are just the kernel showing its resetting the hardware. 

Expect the errors stating your hardware needs to be reset after waking, learn to live with them.  They will not go away when waking from s3 sleep.

Even if  you don't wish to see the errors in your case, there are other situations where a true hardware error needs reporting, so the driver developer will probably never remove the messages from the kernel. (intermittent cabling could cause similar errors where the drive needs to be reset)

 

The error reporting has nothing to do with unRAID, but are from kernel level interfaces from the SATA driver communicating with your disks... and nothing in version 5 of unRAID is likely to change the fact that your disk hardware needs to be reset when waking from s3 sleep.  Version 5.0 of unRAID might (and probably will) use newer linux kernels, and they might get better at waking up, but the fact is they will still need to reset your disk hardware when waking.

 

Tom mentioned the focus of version 5 in the 4.5 release notes. Those comments are as close to a "future" roadmap as we have at this point.  It will focus on two items.

 

1. A change in handling file permissions across the various types of networking interface. (NFS, SAMBA, etc)

and

2. A re-design 0f the user-interface to allow for better integration with add-on scripts and web-pages.  It might change its appearance, it might not.  The change will be in how it is structured internally.  Many of us are expecting it to use an extensible lightweight web-server communicating with an emhttp "API".

 

Joe L.