[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Looking for a "Sanity Check"



Greetings.
 
   While attempting to "zero in" on the cause of a problem while partitioning a laptop
hdd (described in bug#284996) I put a copy of hexdump on a floppy, booted from a Sarge
RC-2 CD, and once the install progressed to the point where it looks for network
hardware, stopped, went to the 2nd console window and tried;
 
    cat /dev/ide/host0/bus0/target0/lun0/disc | /floppy/hexdump -C | more
 
Which appears to work, but generated unexpected results (appeared to show that cfdisk 2.2
corrupted the partition table of the hard drive, by repeatedly writing the function names
'GreyString' and oregroundWindow'?) This begs the question; Am I seeing what I think I'm
seeing?
 
  If I do the same thing starting with a single Win98 partition, the same area of the disk
(judging from the addresses displayed by hexdump) appear far less suspicious, and include
'55AA' (which I believe marks the end of the partition table for a bootable partition).
 
  So my question to the list is; Is it OK to use the above-mentioned cat-hexdump-more
command, or am I deceiving myself somehow? TIA,
 
                          Steve Kleiser

Reply to: