On Tue, 2011-02-08 at 16:24 +0530, vishesh kumar wrote:
> Thanks for response
> Is there any option to gt the list of damaged blocks.
> 

Use smartctl to get a count of remapped sectors and run tests.  Modern
disks hide bad sectors by remapping them.  If you have a large number of
remapped sectors its time to get a different disk.  The remapping is
silent on writes (if the write fails it just writes it to a remapped
sector) but will give i/o errors on read, at least as I understand it.

skdump is also good for reading the smart information.

Brian

> Thanks
> 
> 
> On Mon, Feb 7, 2011 at 10:27 PM, John Haxby <[email protected]>
> wrote:
>         
>         
>         On 7 February 2011 16:21, Robert G. (Doc) Savage
>         <[email protected]> wrote:
>                 On Mon, 2011-02-07 at 21:37 +0530, vishesh kumar
>                 wrote:
>                 > Dear all
>                 >   I suspect one of my hard disk have corruption. I
>                 want to perform
>                 > surface scan to get idea of corrupted hard disk
>                 sectors. What command
>                 > will be most appropriate for this purpose on RHEL 5.
>                 > Does 'badblocks' is right command to use in this
>                 scenario ?
>                 
>                 
>                 Vinesh,
>                 
>                 >From 'man badblocks':
>                 
>                 Important  note:  If the output of badblocks is going
>                 to be fed to the
>                 e2fsck or mke2fs programs, it is important that the
>                 block size is
>                 properly specified, since the block numbers which are
>                 generated  are
>                 very  dependent  on the block size in use by the
>                 filesystem.  For this
>                 reason, it is strongly recommended that users not run
>                 badblocks
>                 directly, but rather use the -c option  of  the e2fsck
>                 and mke2fs
>                 programs.
>                 
>                 Hope this helps...
>                 
>         
>         
>         That's also somewhat dated now.
>         
>         You can often recover bad blocks simply by writing to them and
>         letting the disk allocate replacements -- badblocks -n can be
>         useful for this.
>         
>         You should also look at smartctl -- it'll tell you whether or
>         not it thinks the disk is healthy.
>         
>         Usually when a disk is throwing errors I bin it on the grounds
>         that once it's started to have problems it's only going to get
>         worse.   Disks are not generally cheaper than the data they
>         store :-)
>         
>         jch
>         
>         
>         _______________________________________________
>         rhelv5-list mailing list
>         [email protected]
>         https://www.redhat.com/mailman/listinfo/rhelv5-list
>         
> 
> 
> 
> -- 
> http://linuxmantra.com
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list


_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to