KS wrote: > Bob Proulx wrote: > > I will second keith's suggestion to use gddrescue which has somewhat > > improved behavior and might work better. I pretty much have switched > > to using it whenever I need to do this. > > Running it now. Waiting to see if it works any better. I should have emphasized that you want to supply a log file as the third parameter. That usage differs from the other ddrescue. But I am sure you read the docs already. :-) > > Partition the new drive with the same sized partition as the previous > > rescue partition. I like using sfdisk for this purpose. > > > > sfdisk -d /dev/sda > sda.partitions # dumps partition table > > Thanks. > Done. And have the file. I just noticed that the other disc I have is > smaller (250GB). So would it work, if I manually edit the "size=" sector > number and then write it to the disk. Sounds good. Also you can edit the file and just set only the partitions you care about. For example if you wanted to only set the first partition or two and leave the rest unallocated. Then allocate the rest later using a different tool. I just like sfdisk due to its ability to write out the previous and read it back in for the new without me needing to know anything about the sizes. > Can I just change the OS partition size in the dump by reducing the > total sector count for the smaller disk by the start sector number of > the third partition of the dying disk partition table? You should be able to do that, yes. You can also simply delete lines from other partitions to leave those unallocated. Then allocate them afterward using parted or whatever other tool you want. > > http://www.supergrubdisk.org/super-grub2-disk/ > > Hmmm... Thanks Bob, never heard of supergrubdisk. Looks like a good tool. It has worked well for me to boot cranky MS-Windows machines with broken MBRs before. > Waiting for gddrescue to finish. Good luck! Bob
Attachment:
signature.asc
Description: Digital signature