I've been using unraid for many years.

I've done upgrades of all my hardware through the years.

 

Even with my latest hardware upgrade I get these errors

in my syslog.

They don't seem to affect my files or cause damage, but I would like

to know what could be causing it.

 

This is a section with the errors.

 

Nov 26 19:31:03 Tower kernel: mdcmd (82): clear

Nov 26 19:50:03 Tower kernel: mdcmd (83): clear

Nov 26 22:23:54 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Nov 26 22:23:54 Tower kernel: ata2.00: failed command: CHECK POWER MODE

Nov 26 22:23:54 Tower kernel: ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0

Nov 26 22:23:54 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Nov 26 22:23:54 Tower kernel: ata2.00: status: { DRDY }

Nov 26 22:23:54 Tower kernel: ata2: hard resetting link

Nov 26 22:23:55 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 26 22:23:55 Tower kernel: ata2.00: configured for UDMA/133

Nov 26 22:23:55 Tower kernel: ata2: EH complete

Nov 26 22:25:29 Tower kernel: mdcmd (84): clear

Nov 26 22:30:52 Tower kernel: mdcmd (85): spindown 3

Nov 26 22:30:52 Tower kernel: mdcmd (86): spindown 11

Nov 26 22:30:52 Tower kernel: mdcmd (87): spindown 14

Nov 26 22:35:27 Tower kernel: mdcmd (88): clear

 

Thanks

It happened again today on two different drives.

Here is the section of the log.

 

 

Nov 27 13:51:06 Tower kernel: mdcmd (158): spindown 10

Nov 27 16:10:45 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Nov 27 16:10:45 Tower kernel: ata8.00: failed command: CHECK POWER MODE

Nov 27 16:10:45 Tower kernel: ata8.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0

Nov 27 16:10:45 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Nov 27 16:10:45 Tower kernel: ata8.00: status: { DRDY }

Nov 27 16:10:45 Tower kernel: ata8: hard resetting link

Nov 27 16:10:46 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 27 16:10:46 Tower kernel: ata8.00: configured for UDMA/133

Nov 27 16:10:46 Tower kernel: ata8: EH complete

Nov 27 16:21:24 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Nov 27 16:21:24 Tower kernel: ata2.00: failed command: CHECK POWER MODE

Nov 27 16:21:24 Tower kernel: ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0

Nov 27 16:21:24 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Nov 27 16:21:24 Tower kernel: ata2.00: status: { DRDY }

Nov 27 16:21:24 Tower kernel: ata2: hard resetting link

Nov 27 16:21:25 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 27 16:21:25 Tower kernel: ata2.00: configured for UDMA/133

Nov 27 16:21:25 Tower kernel: ata2: EH complete

Nov 27 17:49:41 Tower kernel: mdcmd (159): clear

 

 

Happened again.

Any ideas?

 

Nov 30 12:14:23 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Nov 30 12:14:23 Tower kernel: ata2.00: failed command: CHECK POWER MODE

Nov 30 12:14:23 Tower kernel: ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0

Nov 30 12:14:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Nov 30 12:14:23 Tower kernel: ata2.00: status: { DRDY }

Nov 30 12:14:23 Tower kernel: ata2: hard resetting link

Nov 30 12:14:23 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 30 12:14:24 Tower kernel: ata2.00: configured for UDMA/133

Nov 30 12:14:24 Tower kernel: ata2: EH complete

Nov 30 12:26:16 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Nov 30 12:26:16 Tower kernel: ata7.00: failed command: CHECK POWER MODE

Nov 30 12:26:16 Tower kernel: ata7.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0

Nov 30 12:26:16 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Nov 30 12:26:16 Tower kernel: ata7.00: status: { DRDY }

Nov 30 12:26:16 Tower kernel: ata7: hard resetting link

Nov 30 12:26:16 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 30 12:26:17 Tower kernel: ata7.00: configured for UDMA/133

Nov 30 12:26:17 Tower kernel: ata7: EH complete

Nov 30 15:05:37 Tower kernel: mdcmd (144): spindown 0

Nov 30 15:05:37 Tower kernel: mdcmd (145): spindown 1

Nov 30 15:05:37 Tower kernel: mdcmd (146): spindown 2

Nov 30 15:05:38 Tower kernel: mdcmd (147): spindown 3

Nov 30 15:05:38 Tower kernel: mdcmd (148): spindown 4

Nov 30 16:16:19 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Nov 30 16:16:19 Tower kernel: ata6.00: failed command: CHECK POWER MODE

Nov 30 16:16:19 Tower kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0

Nov 30 16:16:19 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Nov 30 16:16:19 Tower kernel: ata6.00: status: { DRDY }

Nov 30 16:16:19 Tower kernel: ata6: hard resetting link

Nov 30 16:16:20 Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 30 16:16:20 Tower kernel: ata6.00: configured for UDMA/133

Nov 30 16:16:20 Tower kernel: ata6: EH complete

 

 

Looks like a kernel bug...but nothing serious.

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=630342

 

 

Edit: from linked bug#549981

2) I can replicate the primary problem as originally reported  (exception Emask

0x0 SAct 0x0 SErr 0x0 action 0x6 frozen) with no filesystem access to the disks

at all (the RAID array is stopped) just by issuing smartctl -a /dev/sdd

commands repeatedly. The problem usually occurs within about 10-15 executions.

 

 

Do other people see this alot?

The reason I ask is that over the years I have change hardware multiple times ( MB, Ram, Upgraded Drives, Power Supply, Etc. ) and seem to still

get this error every now and then.

 

Do other people see this alot?

The reason I ask is that over the years I have change hardware multiple times ( MB, Ram, Upgraded Drives, Power Supply, Etc. ) and seem to still

get this error every now and then.

 

Based on a quick search - yes.

 

Looks like an "exception" when the drive is slow in responding to a command, resulting in a driver timeout.  This bug thread has a lot of information.  It appears to be mostly harmless..based on my quick review- the Marvell controllers and Samsung drives tend to have more of these errors, but not the only hardware that can display this kernel bug.