| 1 |
On Wednesday 08 Aug 2012 05:21:31 Adam Carter wrote: |
| 2 |
> > To wipe a drive use dban. - live CD which uses (US) gov approved |
| 3 |
> > standards of wipe methods/patterns. |
| 4 |
> |
| 5 |
> Or shred, which comes with coreutils. |
| 6 |
> |
| 7 |
> > dd is only going to show sectors on a failed drive - too late! |
| 8 |
> > |
| 9 |
> > To explain, modern drives have a store of locations they can use to |
| 10 |
> > transparently replace any failed locations (apparently similar to the |
| 11 |
> > way SSD's do it) - the internal drive electronics handle this and its |
| 12 |
> > not visible externally though smart data seems to show it, but as google |
| 13 |
> > says, smart is a bit suspect. The problem of a bad sector will only |
| 14 |
> > show once all the reserved locations are used up, by which time the |
| 15 |
> > drive is usually in rampant failure. |
| 16 |
> > |
| 17 |
> > I do suspect this is one reason for googles results - actual failures of |
| 18 |
> > the media (as against the motors/electronics are much as they always |
| 19 |
> > have been, but the drives are not reporting them until its too late. |
| 20 |
> |
| 21 |
> Ahh - go to know. My reasoning assumed that smart reports all remaps. |
| 22 |
|
| 23 |
May be it does, but I understand that dd or shred won't overwrite them, or any |
| 24 |
bad blocks. You'll need the hdparm ATA secure erase (or enhanced secure |
| 25 |
erase) feature for that. |
| 26 |
|
| 27 |
BTW, Dale make sure that you plug the drive in a SATA controller for running |
| 28 |
the hdparm erase function. It has been reported that doing this using a USB |
| 29 |
port will brick the drive! |
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Mick |
Archives