[opensuse-factory] Can't Rescue 10.3
Friday I determined that 4096 was an inappropriate blocksize for my non-libata hda19 Factory / partition. I booted 10.1 from hda7 and did a cp -a on that partition to another partition, reformatted to the 1024 blocksize, then did cp -a back to it. I then tried to mount and chroot to it in order to run grub-install. Grub-install failed due to the non-existent target device. Copying the hda19 device file from the 10.1 / and trying again didn't help. I tried to do a rescue installation, but both rescue modes apparently failed for a similar or the same reason. Is it possible in Factory to do a rescue? If so, how? -- "Therefore, if anyone is in Christ, he is a new creation; the old has gone, the new has come!" 2 Corinthians 5:17 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-04-08 at 20:47 -0400, Felix Miata wrote:
I then tried to mount and chroot to it in order to run grub-install. Grub-install failed due to the non-existent target device.
It could be because the /mnt/dev tree is not populated.
Copying the hda19 device file from the 10.1 / and trying again didn't help.
Ah, so you saw that. The trick is this, before chrooting: mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys mount -o bind /dev /proc/dev and then, chroot (as posted here by Anders Johansson about a month ago).
I tried to do a rescue installation, but both rescue modes apparently failed for a similar or the same reason. Is it possible in Factory to do a rescue? If so, how?
This is a problem on the standard distro as well, only you haven't bumped into it before. It is also possible to run grub without chrooting by specifying the real paths in the rescue system. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGGi8dtTMYHG2NR9URAnfHAJ0cAbnoQ5MtvXgNTs9NeIUJ8T5rZQCbBQMP ih/T184nD5DCiGRIRIc2A8c= =QgjH -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2007/04/09 14:18 (GMT+0200) Carlos E. R. apparently typed:
2007-04-08 at 20:47 -0400, Felix Miata wrote:
I then tried to mount and chroot to it in order to run grub-install. Grub-install failed due to the non-existent target device.
It could be because the /mnt/dev tree is not populated.
Copying the hda19 device file from the 10.1 / and trying again didn't help.
Ah, so you saw that. The trick is this, before chrooting:
mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys mount -o bind /dev /proc/dev
and then, chroot (as posted here by Anders Johansson about a month ago).
The man page for mkinitrd is now rather different: 1-mount root device on /mnt 2-mount --bind /dev /mnt/dev 3-chroot /mnt 4-mount /proc 5-mount /sys 6-mkinitrd When I try it this way, I get a lot of Constant & Prototype error messages from line 66 of Exporter.pm. -- "In the beginning was the Word, and the Word was with God, and the Word was God." John 1:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Felix Miata wrote:
On 2007/04/09 14:18 (GMT+0200) Carlos E. R. apparently typed:
2007-04-08 at 20:47 -0400, Felix Miata wrote:
I then tried to mount and chroot to it in order to run grub-install. Grub-install failed due to the non-existent target device.
It could be because the /mnt/dev tree is not populated.
Copying the hda19 device file from the 10.1 / and trying again didn't help.
Ah, so you saw that. The trick is this, before chrooting:
mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys mount -o bind /dev /proc/dev
and then, chroot (as posted here by Anders Johansson about a month ago).
The man page for mkinitrd is now rather different:
1-mount root device on /mnt 2-mount --bind /dev /mnt/dev 3-chroot /mnt 4-mount /proc 5-mount /sys 6-mkinitrd
When I try it this way, I get a lot of Constant & Prototype error messages from line 66 of Exporter.pm.
I have seen these on 2 x86_64 boxes, but the initrd gets built and the kernel boots fine. Still needs fixing though. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Carlos E. R. -
Felix Miata -
Sid Boyce