[ please keep the bug report on cc, this is _not_ private mail, cool thanks ]
On Tue, 05 Jun 2007, Peter Wood wrote: > Hi, > recreating the initrd and booting with the bootdelay parameter set gets > me into the rescue console after an error message that the > rootfilesystme could not be found ok usually mkinitramfs gives you info on what to check, the rescue shell is there for purpose. did you check if you passed correct root bootarg a) cat /proc/cmdline checked if the device was there b) ls /dev/[hs]daX checked if the fs on it is recognised c) fstype /dev/[hs]daX /lib/udev/vol_id -t /dev/[hs]daX checked if the correct kernel modules are loaded d) dmesg cat /proc/modules this bug report needs the info from above otherwise is unreproducible. > Below is the /proc/modules output and /dev for the mkinitrd image and > for the yaird image. I hope this helps. woow, again mkinitrd does not exist. > All the best, > > Peter > > /proc/modules (mkinitrd): > ide_generic [permanent] > sg > sr_mod > cdrom > sd_mod > generic > sis5513 > ide_core > sis900 > mii > ehci_hcd > ohci_hcd > usb_core > pata_sis ^^^^^^^^^^ hmmm so it looks like your kernel is not up2date, this got disabled. please update to 2.6.21 from sid. the generated image should boot without trouble > ata_generic > libata > scsi_mod > thermal > processor > fan if you had followed the advice of the initramfs to check your devices and cmdline you'd had noticed that your root dev changed from /dev/hda to /dev/sda. in grub it is very easy to pass the corrected one. i'll close that bug report, as persistent root devices are not an initramfs or kernel trouble. search UUID for a fine way to boot across device renaming. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
