CaptTrev said:
"If you want to really gearhead-out, you can download a copy of any of a number of Linux CD bootable OS images (Knoppix or Centos or even the tiny Morphix Base) then use the DD command to do a LBA to LBA copy from D to C. This will leave you with a repairable image of the old drive on the new drive. You will have to do some partition editing by hand later if you want to extend the original partition to the size of the new disk drive."
WOW - I don't know what any of that means - but it sounds really cool. thanks for the cool advice/trick on the WD drive...I'm going try it --right now that drive is a paperweight - so i have nothing to lose.
Can you explain that last part a little bit more?
MY new WD 300 GIGer should be on my doorstep when I get home tonight.
I know I should partition that drive....should i go 100GIG for one and 200 for the other or what ratio do you all recommend?
I don't know how to explain it except in some detail - though it won't be sufficient - you will need to seek a small amount of help from your local Linux user's group.
LBA means Logical Block Address. Each 512 byte chunk of data (sector) is assigned a number from zero to whatever the last sector would be numbered. This is how we got away from cylinder, head, sector (CHS) addressing some years ago.
On the zero-th LBA, the OS stores a small data structure that describes the size of each of up to four partitions. this is true of "most" OS products. Linux includes a utility to edit this "partition descriptor." It will also display the partitions as they are.
After you boot something like Centos on the CD, you can print-out the MANual pages for DD by typing:
MAN dd
You can then tell DD to "disk duplicate" from 0 to whatever. This will copy the old drive to the new drive, including the partition table. after that's done, the OS will think that the new (is it 300gb?) drive is the same size as the old one (was it 100gb?)....so 200 gb will be unaccessable. you fix that by editing the partition table using a utility the name of which I can't remember.
The point of all of this is that (1) the drive is probably recoverable from the paperweigh state, and (2) once recovered, there's a fairly easy way to make a duplicate that's identical at the "physical device" level so it will perform like the old drive, with all the data, etc. once that's done, all you really need to do is to edit the partition table and tell the OS that the drive is a bit larger than once believed...and voila, you're back with all the data and on a 300% larger drive.
bill
* on a clear disk you can seek forever *