Determining a disk from an ATA number

[dalben]

I'm getting some errors thrown up, like this

Jan 11 20:21:19 tdm kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

 

I'm pretty sure it's my cache drive but I'd like to be certain.  What's the easiest way to correlate the 'ata6' the error is giving me with unRaid's description of the disks ?  (Hopefully without running to the basement, digging into a cupboard, plugging in a monitor and keyboard and rebooting the box)

[prostuff1]

I'm getting some errors thrown up, like this

Jan 11 20:21:19 tdm kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

 

I'm pretty sure it's my cache drive but I'd like to be certain.  What's the easiest way to correlate the 'ata6' the error is giving me with unRaid's description of the disks ?  (Hopefully without running to the basement, digging into a cupboard, plugging in a monitor and keyboard and rebooting the box)

The syslog

[dalben]

Thanks for that.

 

I was about to reply with a narky comment about how I obviously looked at the syslog first before posting.  Thankfully I took another more detailed look and found where ata6 and sde are tied together which sorted it all out.

 

I wonder if unRAID core or unMeno disk info might consider adding the ATA number of a drive to the stats/reports seeing as most of the disk errors I have received seem to report the ATA number exclusively.

[dgaschk]

It's not always possible to determine the the sdX label form the ata number. It is always possible to determine the type of drive but unfortunately not sdX. Also the sdX value can change between boots. Please post the lines that you used to determine the sdX value.

[prostuff1]

It's not always possible to determine the the sdX label form the ata number. It is always possible to determine the type of drive but unfortunately not sdX. Also the sdX value can change between boots. Please post the lines that you used to determine the sdX value.

not quite true.

 

you can correlate the sdx (or hdx) with a specific drive, especially if you know the serial number.  the /dev/disk/by-id/ will give you the disk identification information (like serial number) and also the sdX assignment.

 

NOW, correlating that to an ata number can be more difficult.  You can generally get pretty close...

[dgaschk]

It's not always possible to determine the the sdX label form the ata number. It is always possible to determine the type of drive but unfortunately not sdX. Also the sdX value can change between boots. Please post the lines that you used to determine the sdX value.

not quite true.

 

you can correlate the sdx (or hdx) with a specific drive, especially if you know the serial number.  the /dev/disk/by-id/ will give you the disk identification information (like serial number) and also the sdX assignment.

 

NOW, correlating that to an ata number can be more difficult.  You can generally get pretty close...

 

This is what I meant. I should have said, "Please post the syslog lines that you used to determine the sdX value from the ataY value."

[dalben]

It's not always possible to determine the the sdX label form the ata number. It is always possible to determine the type of drive but unfortunately not sdX. Also the sdX value can change between boots. Please post the lines that you used to determine the sdX value.

not quite true.

 

you can correlate the sdx (or hdx) with a specific drive, especially if you know the serial number.  the /dev/disk/by-id/ will give you the disk identification information (like serial number) and also the sdX assignment.

 

NOW, correlating that to an ata number can be more difficult.  You can generally get pretty close...

 

This is what I meant. I should have said, "Please post the syslog lines that you used to determine the sdX value from the ataY value."

 

There was a bit of guesswork on my end.  I was getting reams of disk errors with ATA6 and in one recurring sequence of errors it didn't reference ATA6 but SDE.  That was all I needed to make the right assumption as I was pretty sure I knew which disk it already was.