On Thu, Apr 26, 2007 at 07:40:02PM +0200, Florian Kulzer wrote: [...] > Are you sure you made the necessary changes to /etc/yaird/Default.cfg > and /etc/fstab before calling yaird? > > You can extract the relevant file, "init", from the new initrd like this: > > zcat new-initrd-name | cpio -i init > > Then you can check if these lines in "init" specify the correct device: > > mkbdev '/dev/sda' 'sda' > mkbdev '/dev/sda6' 'sda/sda6' > > /bin/mount -n \ > $ro \ > -t ext3 \ > -o 'errors=remount-ro' \ > '/dev/sda6' \ > '/mnt' > > You could also try to chroot into the new root partition and build the > initrd from there. > > -- > Regards, | http://users.icfo.es/Florian.Kulzer > Florian |
I think I made the right changes to /etc/yaird/Default.cfg,and when I followed your directions, I got the right lines in init. So I chroot into the new partition and made a new initrd.img. But I still couldn't boot. Here are some of the last lines on the screen before it hangs on boot: hdc: hdc1 hdc2 hdc3 hdc4 Attempting manual resume umount: devfs: not mounted mount: unknown filesystem type 'devfs' kjournald Starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode umount: devfs not mounted /sbin/init: 432: cannot create /dev/null: Read only filesystem /sbin/init: 433: cannot open dev/console: No such file Kernel panic - not syncing: Attempted to kill init I am not sure what all of this means. Thanks, Ric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]