--- Bob Miller <[EMAIL PROTECTED]> wrote: > Larry Price wrote: > > This is kind of a borderline question; > > A disk was intentionally zero'd out using > > dd if=/dev/zero of=/dev/hda > > however the DOS fdisk utility couldn't rebuild the partition > table > > afterwards.
This is shifting the subject a bit, but worth knowing: When I do: dd bs=100k count=1 if=/dev/hda of=hda_100k.dd dd bs=100k count=1 if=/dev/hda1 of=hda1_100k.dd (same for hdb and hdb1) and then use mc in hex mode to look at the four .dd files. I find that the hdX and hdX1 match at an offset of 7E00 hex (both drives are of different size and geometry) I see LILO in the MBR 0-1FF, then a few bits and lots of zeros in the range up to 7E00 hex. Q1: is the stuff after the MBR and below 7E00 hex the partition table ? Q2: if I'd just have a dd dump of some partition hdXN (like hdb1) how useful would this be if I try to restore it to another device? (assuming that one has enough space) Or in other words, is the stuff below 7E00 just 'metadata' concerning the organization of the drive as a whole with no relationship to the data that are on the individual partitions? In the past I have only used dd in the context of same_device <-> file transfer, but never across devices. Currently I have not enough room to test this in a safe way. Any feedback ? ....................... Horst _______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
