| 1 |
on 08/01/2013 01:10 AM Bruce Hill wrote the following: |
| 2 |
> On Wed, Jul 31, 2013 at 11:17:02PM +0300, Thanasis wrote: |
| 3 |
>> on 07/31/2013 10:06 PM Paul Hartman wrote the following: |
| 4 |
>>> |
| 5 |
>>> There are a few approaches to try figuring it out explained here: |
| 6 |
>>> |
| 7 |
>>> http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name |
| 8 |
>>> |
| 9 |
>> |
| 10 |
>> Looking into /sys/dev/block it seems like /dev/sda is on ata1 and |
| 11 |
>> /dev/sdb is on ata2, and since there is nothing else attached to the |
| 12 |
>> system, the ata6 problem may be related to a controller (as Bruce said), |
| 13 |
>> and hopefully not a disk drive. |
| 14 |
> |
| 15 |
> Sorry I don't have time to reply atm. If either drive has errors continuing, |
| 16 |
> please change the SATA cable for a new one. Or, at least, reseat them, and |
| 17 |
> aftewards report results. |
| 18 |
> |
| 19 |
|
| 20 |
I keep the cable connected to both the motherboard's sata port and to |
| 21 |
the external eSata disk enclosure. |
| 22 |
I noticed that the cable indeed needed reseating, but on the other hand, |
| 23 |
the external disk had *not* been powered on since last reboot, i.e. |
| 24 |
before these "errors or warnings" in dmesg had appeared. |
| 25 |
|
| 26 |
FWIW, after reseating the cable, I powered the external disk on, run a |
| 27 |
forced fsck on it, and no errors where reported. |
Archives