linux-kernel - Re: Problem with ata layer in 2.6.24

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Jan 2008 13:20:36 -0500
From:	Mark Lord <lkml@....ca>
To:	Gene Heskett <gene.heskett@...il.com>
Cc:	Mikael Pettersson <mikpe@...uu.se>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux ide Mailing list <linux-ide@...r.kernel.org>
Subject: Re: Problem with ata layer in 2.6.24

> [   64.037975] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [   64.038102] ata1.00: BMDMA stat 0x65
> [   64.038227] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
> [   64.038229]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
> [   64.038432] ata1.00: status: { DRDY ERR }
> [   64.038555] ata1.00: error: { UNC }
> [   64.050125] ata1.00: configured for UDMA/100
> [   64.050134] sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
> [   64.050138] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
> [   64.050142] Descriptor sense data with sense descriptors (in hex):
> [   64.050143]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
> [   64.050149]         00 07 3d 8b 
> [   64.050152] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
> [   64.050155] end_request: I/O error, dev sda, sector 474507
..

This error looks somewhat different from the samples posted earlier.
This one is quite definitively a "bad sector".

It should also show up in "smartctl -a -data /dev/sda" (near the bottom)
if SMART was enabled on this drive at boot.

You could try reading that specific sector again just to make sure.
One way is to figure out how to use "dd" for this.
Another way is to use the "make_bad_sector" utility that
is included in the source tarball for hdparm-7.7, as follows:

   make_bad_sector --readback /dev/sda 474507

(when invoked as above, it does *not* "make" a bad sector; no worries).

If it reports an I/O error consistently on that, then the sector is
indeed faulty, and it's contents have long been lost.

You can repair the bad sector (but not the original contents) like this:

   make_bad_sector --rewrite /dev/sda 474507

Cheers

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/