Device: /dev/sda, 1 Currently unreadable (pending) sectors

I sometimes get these annoying messages from smartd. They only occur with Samsung HD103SIS SATA disks. According to my google research, these messages are not harmful and a Samsung speciality. One reason for me to avoid Samsung in future. The messages should disappear after a reboot. However, since the disks are built into a RAID1 on a 24x7 server I want to avoid rebooting the server. Instead I can get rid of these messages without a reboot when overwriting the whole disk with zeros. Please click here for details.

Comments

<comments />

Niki Hammler meinte …

<comment date="2012-08-30T08:30:04Z" name="Niki Hammler"> One additional comment: The problem is NOT solved by rebooting. It seems that zeroing out is necessary :-( </comment>

mike meinte …

<comment date="2012-12-26T17:07:31Z" name="mike"> hello! i have /dev/sdb 3TB how to perform Zeroing the disk for 3TB

cat /dev/zero | pv -s 3000G | dd of=/dev/sda bs=100M

or this is not right ? please show the correct command

I'm afraid to make a mistake

</comment>

Niki meinte …

<comment date="2012-12-29T17:29:49Z" name="Niki"> Are you sure you have the same config as I (RAID1)? Only in this case my howto makes sense, otherwise you will destroy all your data!!

If you are sure (really sure!) then the disk in the command must match:

cat /dev/zero | pv -s 3000G | dd of=/dev/sdb bs=100M 

</comment>

James Hightower meinte …

<comment date="2013-06-13T15:37:50Z" name="James Hightower"> I think your can skip the zero-ing part. Unless you have write-intent bitmaps enabled, then just removing and re-adding a drive will cause MD to overwrite the entire disk, including your pending-bad blocks. Thiis has worked for me many times. Remember, though, that the SMART Offline_Uncorrectable won't get updated until the next offline collection occours, like with smartctl -t offline. </comment>

Niki meinte …

<comment date="2013-06-14T05:27:11Z" name="Niki"> Dear James,

Thank your for your comment! I will try it our the next time I encounter the message!

Niki </comment>