Re: Raid and badblocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



NeilBrown wrote:

> If you want to write to it which might make the drive think it isn't
> bad any more, you could
>    dd if=/dev/zero of=/dev/sdj seek=1953103080 count=1
> 
> But if it were me, I would do
>    dd if=/dev/sdj of=/dev/null skip=1953103080 count=1
> and confirm that gives and error, just to double check the numbers.

Thanks very much for your help. I managed to get rid of the bad block. 
However I had to write 4kB at once to the bad region (bs=4096) for the drive 
to correct the block. Using bs=1 didn't seem able to get rid of the errors.

Strangely, the Reallocated_Sector_Ct is still zero on the drive even though 
Current_Pending_Sector is now zero. This is a Samsung HD103UJ by the way.

Jeremy

-- 
Jeremy Sanders <jss@xxxxxxxxxxxxx>   http://www-xray.ast.cam.ac.uk/~jss/
X-Ray Group, Institute of Astronomy, University of Cambridge, UK.
Public Key Server PGP Key ID: E1AAE053


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux