Entry tags:
nnngh h8
Macbook dropped off: sucks to be me until next week. Or later. NNngh.
I've been working with kimo trying to get that machine to have a new HD and dual-boot WinXP and Linux. I think, or thought, I had all the partitions set up and the Windows partitions from the old HD copied over, but only one of them mounts properly under Linux and I have no idea what's wrong with the other one but NTFS-fs thinks it's horribly corrupted. In both cases, I made new partitions larger than the originals; the one that worked is FAT32, the one that didn't is NTFS. Would this have fucked things up on NTFS?
Also, and even more annoyingly, I can't write the old MBR onto the new drive, so I thought np, I'll run repair from the WinXP Pro install disc that I of course still have. So I boot off it, and XP checks hardware, and hangs. Hard. No idea why. This is the same install disc I used for this same machine with identical hardware except for the new hard drive, and the new hard drive is just a plain old ATA/EIDE single drive, so I doubt that's it. No error messages, no nothing; black screen and GTFO.
Oh, the linux partition is so I can run ardour. Eventually. I hope. I suppose I could throw out the old media drive (which is dying of plate rot anyway) and make a non-boot NTFS partition on the new drive to replace that, and boot Linux off the second partition on the new drive, but I don't want to keep the original crap drive because it made XP performance a world of pain, and I'd like this 2.7Ghz machine not to be slower and more painful to use than the PIII/550 I'm using right now.
So other than RAGE, anybody got any suggestions?
I've been working with kimo trying to get that machine to have a new HD and dual-boot WinXP and Linux. I think, or thought, I had all the partitions set up and the Windows partitions from the old HD copied over, but only one of them mounts properly under Linux and I have no idea what's wrong with the other one but NTFS-fs thinks it's horribly corrupted. In both cases, I made new partitions larger than the originals; the one that worked is FAT32, the one that didn't is NTFS. Would this have fucked things up on NTFS?
Also, and even more annoyingly, I can't write the old MBR onto the new drive, so I thought np, I'll run repair from the WinXP Pro install disc that I of course still have. So I boot off it, and XP checks hardware, and hangs. Hard. No idea why. This is the same install disc I used for this same machine with identical hardware except for the new hard drive, and the new hard drive is just a plain old ATA/EIDE single drive, so I doubt that's it. No error messages, no nothing; black screen and GTFO.
Oh, the linux partition is so I can run ardour. Eventually. I hope. I suppose I could throw out the old media drive (which is dying of plate rot anyway) and make a non-boot NTFS partition on the new drive to replace that, and boot Linux off the second partition on the new drive, but I don't want to keep the original crap drive because it made XP performance a world of pain, and I'd like this 2.7Ghz machine not to be slower and more painful to use than the PIII/550 I'm using right now.
So other than RAGE, anybody got any suggestions?
no subject
no subject
I'm kind of hoping that the partition is in fact good and NTFS-fs is lying to me or just otherwise confused. But since my XP install DVD has decided to say HA HA FUXX0R J00 I can't run NT diagnostics on it.
no subject
no subject
no subject
Long story short -- you probably know this, but just to be safe -- the problem with NTFS (aka "Not This Fucking System", various other profane acronyms) is exactly that the NTFS format is proprietary. (Short comparison here (http://cquirke.mvps.org/ntfs.htm), in the unlikely event that this is new to you). vfat (aka fat32) and earlier are public domain. So any non-Windows OS that attempts to read or write NTFS is actually based on reverse engineering of the file system. This causes some problems because an NTFS partition apparently can only be booted after a sector copy from a machine with an identical cylinder geometry (http://www.linux-ntfs.org/doku.php?id=ntfsclone). Why this is key is beyond my wife and I...we just know it causes problems.
So it's possible your data is NOT corrupt but you need to sector copy AGAIN, this time back onto the (repaired) old drive. But since you copied onto a disk with different physical parameters NTFS may simply be puking on mount due to sector/cylinder mismatch.
no subject
an NTFS partition apparently can only be booted after a sector copy from a machine with an identical cylinder geometry.
Okay, I was afraid of that, or something like that. So how do you do this, anyway? Given that for whatever reason I can't just reinstall XP and then do it the smart way, I mean.
no subject
FWIW, I hope this works. I've done a lot of fighting with dead drives for data ("oh look, another dead seismometer"), but never on NTFS.