[opensuse] rebuilding initrd?
![](https://seccdn.libravatar.org/avatar/86d24de0b34455c28aeb1e8d57d05913.jpg?s=120&d=mm&r=g)
Hi all, Having a problem with a system that will not boot. Reason: mainboard broken and disks are now used on another mainboard, with probably another chipset. It contains a /dev/md0 as root-device, but when booting from the new mobo, md0 is not available. Booting with a rescue CD I can see the raid device /dev/md0 When I do these things after booting a rescue system, it seems to me that the system is the way I want it: ==================== mount /dev/md0 /mnt, mount /dev/sda1 /mnt/boot, mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys chroot /mnt ==================== What command do I need to rebuild the initrd with the modules now loaded? In /etc/sysconfig/kernel to me it seems to have the modules for the old mobo? -- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/8434092a3798a0467c3f2371ef030fc6.jpg?s=120&d=mm&r=g)
On 5/24/2010 10:15 AM, Leen de Braal wrote:
Hi all,
Having a problem with a system that will not boot. Reason: mainboard broken and disks are now used on another mainboard, with probably another chipset. It contains a /dev/md0 as root-device, but when booting from the new mobo, md0 is not available.
Booting with a rescue CD I can see the raid device /dev/md0 When I do these things after booting a rescue system, it seems to me that the system is the way I want it: ==================== mount /dev/md0 /mnt, mount /dev/sda1 /mnt/boot, mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys
chroot /mnt ====================
What command do I need to rebuild the initrd with the modules now loaded? In /etc/sysconfig/kernel to me it seems to have the modules for the old mobo?
Seems like you did all the hard stuff already if you got all the way to manually booting an install kernel and setting up that complete of a chroot complete with bind mounts. All I can see that's left is: Within that chroot, Run lsmod |less to see what modules you need for your hd's. Edit /etc/sysconfig/kernel with the new modules. Definitely make sure it includes raid456 or raid10 or whatever raid level you're using. mikinitrd should automatically Possibly edit /etc/fstab if the fs's were mounted by id or uuid and they changed. Then just run mkinitrd. Exit out of chroot & reboot. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/86d24de0b34455c28aeb1e8d57d05913.jpg?s=120&d=mm&r=g)
On 5/24/2010 10:15 AM, Leen de Braal wrote:
Hi all,
Having a problem with a system that will not boot. Reason: mainboard broken and disks are now used on another mainboard, with probably another chipset. It contains a /dev/md0 as root-device, but when booting from the new mobo, md0 is not available.
Booting with a rescue CD I can see the raid device /dev/md0 When I do these things after booting a rescue system, it seems to me that the system is the way I want it: ==================== mount /dev/md0 /mnt, mount /dev/sda1 /mnt/boot, mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys
chroot /mnt ====================
What command do I need to rebuild the initrd with the modules now loaded? In /etc/sysconfig/kernel to me it seems to have the modules for the old mobo?
Seems like you did all the hard stuff already if you got all the way to manually booting an install kernel and setting up that complete of a chroot complete with bind mounts.
All I can see that's left is:
Within that chroot, Run lsmod |less to see what modules you need for your hd's.
sata_via pata_via via82cxxx were the ones that got it booting again. I then had to tweak some stuff (network most importantly) to get up online.
Edit /etc/sysconfig/kernel with the new modules. Definitely make sure it includes raid456 or raid10 or whatever raid level you're using. mikinitrd should automatically Possibly edit /etc/fstab if the fs's were mounted by id or uuid and they changed. Then just run mkinitrd.
Exit out of chroot & reboot.
Thanks for giving me the hints.
-- bkw
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/8434092a3798a0467c3f2371ef030fc6.jpg?s=120&d=mm&r=g)
On 5/24/2010 1:27 PM, Leen de Braal wrote:
On 5/24/2010 10:15 AM, Leen de Braal wrote:
Hi all,
Having a problem with a system that will not boot. Reason: mainboard broken and disks are now used on another mainboard, with probably another chipset. It contains a /dev/md0 as root-device, but when booting from the new mobo, md0 is not available.
Booting with a rescue CD I can see the raid device /dev/md0 When I do these things after booting a rescue system, it seems to me that the system is the way I want it: ==================== mount /dev/md0 /mnt, mount /dev/sda1 /mnt/boot, mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys
chroot /mnt ====================
What command do I need to rebuild the initrd with the modules now loaded? In /etc/sysconfig/kernel to me it seems to have the modules for the old mobo?
Seems like you did all the hard stuff already if you got all the way to manually booting an install kernel and setting up that complete of a chroot complete with bind mounts.
All I can see that's left is:
Within that chroot, Run lsmod |less to see what modules you need for your hd's.
sata_via pata_via via82cxxx were the ones that got it booting again.
I then had to tweak some stuff (network most importantly) to get up online.
Edit /etc/sysconfig/kernel with the new modules. Definitely make sure it includes raid456 or raid10 or whatever raid level you're using. mikinitrd should automatically Possibly edit /etc/fstab if the fs's were mounted by id or uuid and they changed. Then just run mkinitrd.
Exit out of chroot& reboot.
Thanks for giving me the hints.
Blah, glad you figured it out despite my unclear edit. The line "mkinitrd should automatically" was supposed to be deleted. I was starting to say something else and forgot to delete it after I changed my mind. Moot now since you're running. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Brian K. White
-
Leen de Braal