BADTRK/SCSIBADBLK ?

[jimbolya]

First off I don't think there is a difference because scsibadblk seems to invoke badtrk on 5.0.5 so I will assume they are the same.

My boss will not let me replace a hard drive which is currently reading 29 bad blocks on root (full partition). So when I run badtrk and the blocks are displayed, I try to re-allocate them and move on. However that does not seem to make a difference and the attempt to read them is still made. I must be missing something. I even tried to just leave the bad block table populated but it seems to clear everytime I quit.

How do I keep these in the bad block table?

Thanks

 

[Annihilannic]

It actually says at the beginning of the badtrk man page "scsibadblk- obsolete command replaced by badtrk".

Have you scanned the disk for flaws using badtrk? There's a note that says for SCSI disks "Do not use the block number that the device driver report with badtrk. Use the block number that badtrk reports after the scan finishes." Perhaps that's where the discrepancy lies?

I have no experience of this, I was just reading up on it 'cause I was interested. ;-) Annihilannic.