|
Hi,
My 2c...
Stop using the bad HDD ASAP. Verify you have all your data from your backups first. If you are missing data from the backups, restore from the bad HDD first. This restoration is best left for professionals or a long read-up on ddrescue or there like. You will be advised to go for a fast grab of the most impotent files --via single file or partition acquisition, depending on circumstances, flowed by an obnoxious reread of failing blocks. Once you have verified you have all the data, you can choose: 1. Do a fresh system install and backup restore. It should be the fastest solution. If you have prepared a Bash or Ansible script, or at least an application list, it is a sure bet. Even if not, it may be faster then copying bit by bit the hole file system, but this depends... 2. Go for copping from the bad HDD. As cp, dd or CloneZillaing will fail on bad block reads, and you know you have them, go with ddrescue full oldHDD to newHDD. First a "quick run" get all good block fast. Second retry on bad blocks hopefully you can get it all out. If you are missing a few blocks you can go figure out what files used them, or forget abut them and diff important directories with the backups. You can ddrescue partitions but as the swap is small 'compared' I would go the full disk to disk.
:-) |
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
