Booted in a live usb session and did
sudo dd if=/dev/urandom of=/dev/sda bs=1M
But that didn't seem o work as I wanted, as the light for the processor working was mostly off (or is it the hdd light?), while the cooler was very loud.
Then I read that the urandom command is very slow as it is really trying to produce really random numbers. I was not interested in wiping all the data for security, but just in clearing off all partitions (something was wrong with them), so I stopped the procedure and did:
sudo dd if=/dev/zero of=/dev/sda bs=1M
With this the cooler calmed down while that "working light" was there permanently.
And to see the progress of this, I opened a separate terminal window and did
watch -n5 'sudo kill -USR1 `pgrep ^dd`'
which every 5 secs reports the progress in the initial terminal window (source)
245423407104 bytes (245 GB) copied, 3430.82 s, 71.5 MB/s
234354+0 records in
234354+0 records out
245737979904 bytes (246 GB) copied, 3435.84 s, 71.5 MB/s
234655+0 records in
234655+0 records out
246053601280 bytes (246 GB) copied, 3440.88 s, 71.5 MB/s
234956+0 records in
234956+0 records out
246369222656 bytes (246 GB) copied, 3445.91 s, 71.5 MB/s
... it took 2 hours and thirty minutes for a 500GB HDD on a 4-year average laptop with 4GB ram.
notrunc
shouldn't affect block devices one way or the other - but maybe useful for disk images. – muru Feb 20 '15 at 13:37sda1
instead ofsda
(as indicated bysdXXX
), only that partition will be affected. personally, I'd just stick with the 512-byte ones. – muru Feb 20 '15 at 13:50dd if=/dev/urandom of=/dev/sda bs=1M
from @Mitch. it's already running: how long such a procedure should take on a 500 GB hdd? – Feb 20 '15 at 14:24