On November 23, 2016 7:49:57 AM PST, Malcolm
On Wed 23 Nov 2016 04:42:15 PM CST, Istvan Gabor wrote:
Knurpht - Gertjan Lettink írta:
Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:
ata1.00: device reported invalid CHS sector 0
A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run
ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => \1/'
Thanks, running this gives:
ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => \1/' ata1 => sda ata3 => sdb ata4 => sdc
ls for these devices gives:
ls -gG /sys/block/ lrwxrwxrwx 1 0 Nov 23 11:04 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 0 Nov 23 11:04 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lrwxrwxrwx 1 0 Nov 23 11:04 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly? Why is .00 attached to the device name in dmesg? What does it mean?
Thanks,
Istvan
Hi The hwinfo --disk command should give you all the info, device files etc which should help clarify?
More to the point he already knows which drive is ata1 and it's time to order a new drive. It's failing. Smartctl might show some info, but to what purpose? He needs to start moving that data now. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org