> One concern. The reason (even aside from LVM) that /boot usually goes
> into its own partition (here, I expect, hda2) is that some BIOSs have
> problems accessing cylinders beyond a certain number. If your BIOS has
> that problem, and your hda2 is beyond its limit, you could have a
> problem.
>
> If you are currently booting both XP and Linux from grub, then you
> should be fine. If you boot to Windows' ntdetect.com, and use that to
> select between Linux and XP, you may have a problem.
>
> You could, of course, delete hda1, create a new hda1 that duplicates
> your present hda2, copy the contents of hda2 into it, and adjust
> grub.conf suitably. Reboot to test. Then delete the old hda2, create a
> new hda2 occupying the gap between hda1 and hda3, and add it to your
> existing logical volume group. parted and gparted are your friends.
>
> N.B: Back up the whole kazoo first! Also, you may wish to use
> ntfsprogs' ntfsclone to back up the NTFS partition before you toast
> it.
>
ntfsclone looks very cool. I created an image of my ntfs partition using
this command:
ntfsclone --save-image --output ntfs-backup.img /dev/hda1
I have the kernel-module-ntfs installed but when I try to mount the
image like the man file says I get this error:
# mount -t ntfs -o loop ntfs-backup.img /mnt/old_ntfs
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Plus, I can mount the hda1 partition so I know ntfs is working. I
assuming I did something incorrect in creating the backup, maybe missed
a parameter?
Any ideas?
Thanks,
James
