Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Wed, 5 Mar 2008 09:36:40 -0800 "Kristian Erik Hermansen" <[hidden email]> wrote: > Actually, I would have backed up before performing the fdisk. Doing > the fdisk operation is destructive. You lose information that might > have been helpful to recovery in the future. Just my two cents. I > have hosed a few file systems in weird ways by just naively "fixing" > the corruption... That would probably be wise, but not easy. The best way is to boot from a standalone Linux system, and copy the partitions that way, but you still run the risk of a damaged backup if a read fails as it might terminate the backup, but the advice is certainly good advice. Additionally, there is a Linux badblocks(8) command whose job it is is to remap badblocks. I was in a hurry earlier and forgot about it. -- -- Jerry Feldman <[hidden email]> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846 _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |