Re: migrate / to new partition; wants to use old mount points
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ric Otte wrote:
> I wanted to migrate a sid install from a partition on a sata drive to a
> partition on another ide drive. I used dd to copy the partion, changed
> fstab, and tried to boot into the system on the ide drive. Grub recognizes
> the ide drive, begins to boot, but after several (maybe 7 or 8 screens) of
> data, the boot halts because it is trying to mount the old sata drive (which
> is not now connected to the machine). I originally thought this was a grub
> problem (see thread "moved system do different partition; grub boot
> problem"), but now think that the kernel on the new partition is booting, but
> at some point in the boot process it begins to use all of the mount points on
> the sata drive. It is almost as if it is using the old fstab is being used
> instead of the new one. I then erased the new partition, and copied over the
> old / using 'cp -a', which had the same result. I then tried rsync, with the
> same effect.
>
> The message on the screen when the boot process stops reads something like:
> waiting 7 seconds for /sys/block/sda/sda10/dev to show up
> /bin/cat /sys/block/sda/sda10/dev: No such file or Directory
> I cannot figure out why it is looking for sda10, which is where the original
> / was located on the sata drive, instead of looking at hdc2, which is where
> the new / is located and is what it booted off of.
>
> Is there any place besides /etc/fstab that indicates what partitions to
> mount? I changed /etc/mtab, but that didn't help, and can't find any other
> places that might be diverting the boot process to the old drive.
>
> Any advice would be appreciated. Thanks.
> Ric
Well, since we already went through this, I will paste my original reply
here and see what others think.
You could have sent this to the list, but it really doesn't matter.
I have 2 different Linux distributions, and a Windows XP that I never
use anymore and will likely be wiping soon. Here's my menu.lst (the
relevant part)
> > title Debian GNU/Linux, kernel 2.6.20.7-slh-up-1
> > root (hd1,6)
> > kernel /boot/vmlinuz-2.6.20.7-slh-up-1 root=/dev/sda7 ro
vga=791 resume=/dev/sda5 vga=791 resume=/dev/sda5
> > initrd /boot/initrd.img-2.6.20.7-slh-up-1
> >
> > title Debian GNU/Linux, kernel 2.6.20.6-slh-up-1
> > root (hd1,6)
> > kernel /boot/vmlinuz-2.6.20.6-slh-up-1 root=/dev/sda7 ro
vga=791 resume=/dev/sda5 vga=791 resume=/dev/sda5
> > initrd /boot/initrd.img-2.6.20.6-slh-up-1
> >
> > title Debian GNU/Linux, kernel memtest86+
> > root (hd1,6)
> > kernel /boot/memtest86+.bin
> >
> > ### END DEBIAN AUTOMAGIC KERNELS LIST
> > title Windows XP (hda1)
> > root (hd0,0)
> > chainloader +1
> > makeactive
> >
> > title Kubuntu, kernel 2.6.20-15-generic
> > root (hd1,1)
> > kernel /boot/vmlinuz-2.6.20-15-generic
root=UUID=b914bced-6e30-4e34-a2af-8107b407207d ro quiet splash
> > initrd /boot/initrd.img-2.6.20-15-generic
The windows drive is IDE, and the damn UUID's I will be changing to
LABELs soon, because I hate UUID.
I have never experienced the type of problem you seem to be having. It
does seem rather strange. Is perhaps your MBR not correct?
What happens if you do something like this:
grub
root (hd0,1)
setup (hd0)
quit
That should rewrite your MBR and tell it to look at your IDE Sid system
first to find the information to boot. So you'll have to use that
systems menu.lst to boot the other one. Alternatively, you could have a
sparate /boot partition that is irrelevant to all systems, and use that
to boot them all and ignore the /boot anywhere else, but then whenever
the kernel gets updated, you have to manually copy things to your own
boot partition.
Joe
- --
Registerd Linux user #443289 at http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGMMHziXBCVWpc5J4RArF1AJ0VZd+5NipaAa6BX5J0h05WqpXliQCfcqyQ
vPLj4BN6bgEpauTWP9hEtjw=
=f9hN
-----END PGP SIGNATURE-----
Reply to: