a new hard-drive in a 2y/o laptop

Chris Brennan xaero at xaerolimit.net
Wed Jan 5 18:26:24 UTC 2011


On Wed, Jan 5, 2011 at 12:44 AM, Ian Smith <smithi at nimnet.asn.au> wrote:

>
> Saw Chris' later message that -F isn't there for him, but here's what
> should be, on the data, the sure-fire way to clobber that last sector:
>
>  dd if=/dev/zero of=/dev/ad4 oseek=1465149167
>
> which command SHOULD report just 512 bytes written (we're sure it can't
> write past the end of the disk with no count specified), after which:
>
>  dd if=/dev/ad4 iseek=1465149167 | hd
>
> SHOULD show zeroes from 00000000 to 000001ff (ie next block 00000200)
> If not, there really must be some hardware issue with writing?
>
> Hopefully getting there!
>
> cheers, Ian
>

[..]
Fixit# sysctrl kern.geom.debugflags=16
kern.geom.debugflags: 0 -> 16
Fixit# dd if=/dev/zero of=/dev/ad4 oseek=1465149167
dd: /dev/ad4: end of device
2+0 records in
1+0 records out
512 bytes transferred in 0.0100001 secs (51195 bytes/sec)
Fixit# dd if=/dev/ad4 iseek=1465149167 | hd
1+0 records in
1+0 records out
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
|................|
512 bytes transferred om 0.009863 secs (51912 bytes/sec)
*
00000200
Fixit#
[..]

restarting and back to sysinstall from BETA1 is nice dice ... same original
error ... can I just zero the whole drive?


More information about the freebsd-questions mailing list