|
I've got all the data moved across to a 1 Tb external USB drive so that's not the problem.
The problem is, when it dies, good (expletive) luck getting Windows to recognize its replacement.
I'm going out tonight to buy a new 1 Tb SATA drive.
In UNIX, all I'd have to do is tar the data across to the other drive, umount both filesystems, change the (v)fstab entry, remount the good drive and I'd be good to go. Probably wouldn't even need to reboot.
Windows thinks the existing failing drive is L:. It thinks the USB drive is M: It's going to assign another drive letter to the new drive and be damned if it's going to let me reassign the drive letter (at least any way I've been able to discover).
So I've been trying to run Windows backup on the faulty drive. The only way it will let me do it (that I've been able to discover) is to back up the entire box. I don't need C: drive backed up. It's fine. By the time it gets around to attempt to back up L: drive, either the box has decided it's time to go into sleep mode (despite it being disabled) or the process has run so long, Windows thinks it's failed and stops paying attention to it, or something else. Who knows? Lacking any sort of non-GUI diagnostics, it's impossible to tell.
So, how do I got about swapping out a still-readable hard drive (it just won't write) with a new one without having to manually reassign all the app locations, hack the registry or other completely unecessary voodoo to get this working?
|