Re: Bad block repair
From: Matty (matty_at_daemons.net)
Date: 12/24/04
- Next message: Hamilcar Barca: "Re: Linux Advocates: Only bad thing is the license!"
- Previous message: palowoda: "Re: If you *need* blastwave in your work, PLEASE SAY SO HERE"
- In reply to:(deleted message) Michael Vilain: "Re: Bad block repair"
- Next in thread: Andrew Gabriel: "Re: Bad block repair"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 23 Dec 2004 23:09:13 -0500
Michael Vilain wrote:
> In article <cq7dpa$7oj$1@bluegill.adi.com>,
> schulz@adi.com (Thomas Schulz) wrote:
>
>
>>We have an Ultra 10 with a Maxtor 6L080J4 connected to the internal ide
>>controller. The disk recently developed a bad block and I thought to
>>repair it using format. As the disk is only a few months old and there
>>is only one bad block, I thought that it would be safe to keep using
>>the disk. I used the analyze command in format to find the bad block
>>and to hopefully repair it. The block was found, but no repair was done.
>>Since the exact block was displayed in /var/adm/messages, I thought to
>>try the repair command in format. I got the following output:
>>
>>format> repair
>>Controller does not support repairing.
>>or disk supports automatic defect management.
>>format>
>>
>>The lines in /var/adm/messages are:
>>
>>Dec 19 12:18:02 seahorse dada: [ID 107833 kern.warning] WARNING:
>>/pci@1f,0/pci@1,1/ide@3/dad@0,0 (dad0):
>>Dec 19 12:18:02 seahorse Uncorrectable data Error: Block 1abc99
>>Dec 19 12:18:04 seahorse dada: [ID 107833 kern.warning] WARNING:
>>/pci@1f,0/pci@1,1/ide@3/dad@0,0 (dad0):
>>Dec 19 12:18:04 seahorse disk not responding to selection
>>Dec 19 12:18:04 seahorse dada: [ID 107833 kern.notice] dad0: disk okay
>>
>>Is this a limitation of this particular disk drive, or a limitation of
>>the controller in the Ultra 10? I had to change the partitions to avoid
>>the bad block and was unable to save the file system that contained the
>>block. Fortunately I had backups. Is there anything that I could have
>>done to repair this bad block and save the file system?
>
>
> Ages ago, I recall many vendors of SCSI disks having the ability to do
> bad block replacement, but not repair. The controller would
> automatically move blocks that started giving write retries to a bad
> block list on the drive, then remap that block to a known good block.
> The drive's bad block list would eventually grow to a certain size and
> the drive would stop doing the replacements and you'd start getting
> retry errors in the log file. That was a sign to backup and replace, in
> my book. Some may choose to reformat, which may or may not fix things.
>
> Perhaps IDE drives don't bother with this because they're so cheap. Why
> not just backup, replace, and restore? Is your data so worthless?
>
You should be able to pull bad block stats through a S.M.A.R.T compliant
utility. These usually list the # of blocks in the bad block list and
the # of blocks that are available for remapping.
- Ryan
- Next message: Hamilcar Barca: "Re: Linux Advocates: Only bad thing is the license!"
- Previous message: palowoda: "Re: If you *need* blastwave in your work, PLEASE SAY SO HERE"
- In reply to:(deleted message) Michael Vilain: "Re: Bad block repair"
- Next in thread: Andrew Gabriel: "Re: Bad block repair"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
