On Tue, 2005-12-20 at 16:22 +0100, David Härdeman wrote: > Jonathan Brandmeyer wrote: > > So, what do I need to edit to fix this? Alternatively, > > what command should I try to run after modprobing in > > ide-disk and ide-generic? > > The problem is that ide-disk and ide-generic are not loaded when dm-mod is > loaded so when it performs its initial device scan it skips the ide discs.
Using the still-working 32-bit side of the system, I managed to find what the difference is between having and not having ide-disk and ide-generic in /etc/mkinitramfs/modules. Modules in that list are added to /conf/modules in the ramfs image. So, that is what I did to /conf/modules in the 64-bit initramfs image. The boot still fails, but in a different manner. The last few messages includes a modprobe usage error followed by: mount: Cannot read /etc/fstab: No such file or directory Begin: Running /scripts/log-bottom ... Done. Done. Begin Running /scripts/init-bottom mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory (more failures to mount /sys and /proc) Target filesystem doesn't have /sbin/init (enters Busybox ash) mount returns: none on /sys none on /proc udev on /dev /dev/mapper is empty except for control /proc/modules includes forcedeth ehci_hcd ohci_hcd thermal processor fam ide_cd cdrom dm_mod sd_mod ide_generic ide_disk sata_nv libata scsi_mod amd74xx ide_core According to dmesg the IDE cdroms (hdc, hdd) and SATA hard drives (sda, sdb) are all detected before dm_mod is loaded. All of the relevant partitions for the hard drives show up under /dev > The easiest workaround until the bug is properly fixed is the one suggested by > Maximilian (i.e. add the modules to /etc/initramfs/modules and regenerate the > image). The devices should then be present when dm-mod is loaded which should > generate the lvm nodes. Except that I CANNOT DO THIS because the system is unbootable. -Jonathan