On Monday 21 December 2015 14:53:16 Stephen Powell wrote: > On Mon, 21 Dec 2015 10:36:48 -0500 (EST), David Baron wrote: > > On Monday 21 December 2015 10:25:15 Stephen Powell wrote: > >> Obviously, the LILO map file is on the IDE drive. Is your /boot > >> partition > >> on the IDE drive? If so, you cannot remove it. The /boot partition must > >> be a partition on a physical drive, but obviously it cannot be on the > >> drive > >> that you want to remove. > > > > The boot is not a separate partition but is a directory on the root so > > travels with it. Copy on both old and new directories. > > No, that won't work. If the root filesystem is an LVM2 logical volume, then > /boot *cannot* be part of the root filesystem. To be more rigorous, there > will be a /boot directory in the / filesystem, but it must be an *empty* > directory, so that another filesystem can be mounted on that directory. > Another filesystem must get mounted on the /boot directory in the root > filesystem, and that filesystem must be made on a partition of a *real* > disk which is accessible via the BIOS. It cannot be an LVM2 logical > volume. The boot partition contains the LILO map file (by default, > /boot/map) as well as the kernel image file and the initial RAM filesystem > image file. LILO reads these files at boot time via BIOS calls, and the > BIOS does not support LVM2 logical volumes. You can have a physical disk > with two partitions on it, one partition of which is an LVM2 physical > volume which is part of an LVM2 logical volume, and the other one of which > is a stand-alone partition which is mounted on /boot. But the filesystem > which gets mounted on /boot must *not* be an LVM2 logical volume. I > thought I made that clear before. Also, the LILO boot sector must be > either on the MBR of a *real* disk, or the first sector of a partition on a > *real* disk. > > > The loop that I get is something more problematic. > > Agreed. As I said before, there is probably something missing from the > initial RAM file system that needs to be there for the kernel to mount an > LVM2 logical volume.
> =========================== > > Could he not dd them onto another drive? > ... >He can copy the /boot data to another drive, not necessarily >with dd. In fact, if he wants to be able to remove the >existing IDE drive, he must. But he cannot copy it to an >LVM2 logical volume. The data in /boot (after copying) >must be on a partition on a physical disk which is accessible >via the BIOS and not on the old IDE drive which he wishes >to remove. The / filesystem can be an LVM2 logical volume, >provided the initial RAM filesystem contains sufficient files >to mount an LVM2 logical volume, but the filesystem which >gets mounted on /boot must be made on a partition of a *real* >disk which is not scheduled to be removed from the system. Repeat: NO LV's