Thanks Clive - but I've heard that grub is really bad with LVM2. In fact, the latest Debian Etch installer still explicitly removes the option to install grub when it detects that / is on an LVM2 volume.
I did eventually solve the problem, by starting sshd in the installer shell (chroot /mnt/VG1-Root sshd) and logging into that (a full chroot, as it were). I had to mount -o bind /proc /mnt/VG1-Root to provide access to /proc/devices, and I also had to use mknod to change the major number of /mnt/VG1-Root/dev/mapper/VG1-Root to 254 from 253, but then lilo ran. So I was right - the problem is something to do with the change from 253 to 254 for LVM2 volumes. I missed this, but it makes me very wary of trying to upgrade my system any more! The "don't know how to handle device" problem is simply a lack of access to /proc/devices, which is solved by the double mounting of /proc. CC -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 07/02/2006 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
