On Mon, Feb 8, 2010 at 9:10 AM, Boris Epstein wrote:

On Mon, Feb 8, 2010 at 9:05 AM, Constant Brouerius van Nidek wrote:

...

In the dmesg I find an information telling me that I have a bad sector which according to the rest of the text is not liked by the system. It tells me that sector id 34777476 is the culprit. How can I find out where that sector is situated. I remember in former versions I could find the sectors of a partition. I think somewhere in the partition manager or with sfdisk or one of the other disk managers. Before I try to find out where this sector is situated (curiousness) I would like to know what the best way would be without doing any damage to my partitions. -- Linux User 183145 using a Pentium III , powered by openSUSE 11.2 (i586) Kernel: 2.6.31.8-0.1-desktop KDE Development Platform: 4.3.98 (KDE 4.3.98 (KDE 4.4 RC3)) "release 218"  20:55pm  up   0:33,  3 users,  load average: 1.06, 0.66, 0.59 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I might not know how to tell exactly where the sector is... but I'd say it is time to start planning on replacing the drive the sector is not. Usually such sectors multiply in number and eventually make the disk unusable.

What I do to test the disk is:

dd if=<device for the disk> of=/dev/null

(Example: dd if=/dev/sda of=/dev/null)

If there is any error while the disk is read it is in my opinion time to start considering replacement of that disk drive.

Boris.

Boris, Back in the day, that might have been good advice. With 1TB drives it can be an expensive way to operate. iirc, the bit error rate on drives has been 1 in 1^15 (or some such) for a long time. That means that on a 1TB drive, there is a 1 in 67 chance of having a bad sector somewhere on the drive. You can of course replace that drive, but more efficient thing would be to trigger a remap to replace the sector with a spare. That is done by writing new data to the sector. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer Preservation and Forensic processing of Exchange Repositories White Paper - http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday 08 February 2010 17:59:56 David wrote:

On Monday 08 February 2010 09:05:17 am Constant Brouerius van Nidek wrote:

...

In the dmesg I find an information telling me that I have a bad sector which according to the rest of the text is not liked by the system. It tells me that sector id 34777476 is the culprit. How can I find out where that sector is situated. I remember in former

fdisk /dev/sda

Select "u" to change units to sectors. "p" to print partition table. Sample:

Command (m for help): u Changing display/entry units to sectors

Command (m for help): p

Disk /dev/sda: 74.4 GB, 74355769344 bytes 255 heads, 63 sectors/track, 9039 cylinders, total 145226112 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xf08172f5

Device Boot Start End Blocks Id System /dev/sda1 * 63 144584 72261 83 Linux /dev/sda2 144585 31567724 15711570 8e Linux LVM

Isnt there a way to map sectors to inodes, and from there to what file occupies the damaged sector? -- /Rikard Johnels