Andrea Conti <[email protected]> [10-05-27 17:20]:
> > I was more thinking of a tool, which test the whole disc surface
> > and reports every bad sector.
>
> badblocks -wvs (which takes forever, but in my experience is quite good
> at make failing disks actually fail ;)
>
> During the test you can monitor the smart attributes (smartctl -A, esp.
> the reallocated sector count) to see what is actually going on.
>
> Warning: backup your data as badblocks in destructive mode will wipe the
> disk clean.
>
> Also, you can run a SMART offline long test (smartctl -t long), which
> will scan the whole surface. But on most disks the test stops at the
> first error, so you don't get a complete picture.
>
> > Smarts is more of statistical kind: It counts events and tries
> > to calculate dooms day from that ;)
>
> That's just a part of it. Attribute values and the error log actually
> provide useful information about the status of the disk.
>
> andrea
>
"Badblocks" is running since yesterday on one of both harrdisks (and is still
running...for more then 10 hours now (1TB to check)) and I
got thise errors visible via dmesg:
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:f5:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:0f:80:f5:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:40:d4/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:6f:80:40:d4/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:a1:40/00:00:00:00:00/e1 tag 0 dma 65536 in
res 51/84:2f:80:a1:40/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
(I dont know, where the report sequence starts, so I put some
repetitions here in)
They do not grow in count and badblocks did not report anything
onto the console where I start it.
I started it with
solfire:/root>badblocks -v -n /dev/sda
At midnight, the DSL connection had been cut by the provider
and automagically reestablished by my linux box, but I dont
think, that this has something do to with it.
Additionall smartd is running in the background...
Smartd's smartd.conf contains this (first try...;)
/dev/sda -a -d sat -o on
/dev/sdb -a -d sat -o on
What the heck is going on in my system?
Thanks a lot in advance for any help !
Best regards,
worried,
mcc
--
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
