Mailinglist Archive: opensuse-factory (528 mails)
| < Previous | Next > |
Re: [opensuse-factory] Fixing the machine after kernel 2.6.21-10
- From: Andreas Vetter <vetter@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 May 2007 08:25:14 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0705250821530.13051@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Fri, 25 May 2007, Silviu Marin-Caea wrote:
> I have updated my installation with this kernel from factory and it didn't
> boot anymore (it didn't see the hard-disk).
>
> The problem that I'm most concerned about is not this. What is much more
> serious is that I haven't been able to fix it to boot again. Perhaps I
> didn't do the right things. I'm gonna describe what I've tried, and if
> there's something more that could be done, please tell me.
>
> 1. Update the kernel 2.6.21-8 to 2.6.21-10, along with a good number of other
> packages (including hal)
>
> 2. Reboot, see that it doesn't work (it doesn't see the storage)
>
> 3. Look if the old kernel is still on disk. It isn't. Perhaps it should do a
> backup called vmlinuz-backup that gets overwritten at each update, so the
> directory doesn't become full of backups.
>
> 4. Decided to install back the old kernel with rpm --upgrade --force
>
> 5. boot the alpha4 DVD in rescue mode
>
> 6.
> mkdir /tmp/local
> mount /dev/sda4 /tmp/local
> cp [...]/kernel-2.6.21-10[...].rpm /tmp/local
Seems you forgot the 3 bind mounts before chrooting?
mount --bind /proc /tmp/local/proc
mount --bind /dev /tmp/local/dev
mount --bind /sys /tmp/local/sys
> chroot /tmp/local
> rpm --upgrade --force kernel-2.6.21-8[...].rpm
> At which point I got a lot of errors, probably from the mkinitrd script that
> didn't see the hard-disk, because the device it's created dynamically at
> runtime, if I'm correct.
>
> 7. I have corrected grub/menu.lst by editing it and tried booting, but it gave
> the same error (not seeing the disk), probably because the initrd image is
> invalid.
>
> I ended up doing a fresh reinstall. This is not good. Someone with enough
> knowledge should be able to fix this situation without reinstallation.
>
> So either I don't have sufficient knowledge (easily fixable and not a
> distribution problem) or it can't be done--quite bad.
>
> Which one is it?
--
Mit freundlichen Gruessen,
Andreas Vetter
Fakultaet fuer Physik und Astronomie Tel: +49 (0)931 888-5890
Universitaet Wuerzburg Fax: +49 (0)931 888-5508
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
> I have updated my installation with this kernel from factory and it didn't
> boot anymore (it didn't see the hard-disk).
>
> The problem that I'm most concerned about is not this. What is much more
> serious is that I haven't been able to fix it to boot again. Perhaps I
> didn't do the right things. I'm gonna describe what I've tried, and if
> there's something more that could be done, please tell me.
>
> 1. Update the kernel 2.6.21-8 to 2.6.21-10, along with a good number of other
> packages (including hal)
>
> 2. Reboot, see that it doesn't work (it doesn't see the storage)
>
> 3. Look if the old kernel is still on disk. It isn't. Perhaps it should do a
> backup called vmlinuz-backup that gets overwritten at each update, so the
> directory doesn't become full of backups.
>
> 4. Decided to install back the old kernel with rpm --upgrade --force
>
> 5. boot the alpha4 DVD in rescue mode
>
> 6.
> mkdir /tmp/local
> mount /dev/sda4 /tmp/local
> cp [...]/kernel-2.6.21-10[...].rpm /tmp/local
Seems you forgot the 3 bind mounts before chrooting?
mount --bind /proc /tmp/local/proc
mount --bind /dev /tmp/local/dev
mount --bind /sys /tmp/local/sys
> chroot /tmp/local
> rpm --upgrade --force kernel-2.6.21-8[...].rpm
> At which point I got a lot of errors, probably from the mkinitrd script that
> didn't see the hard-disk, because the device it's created dynamically at
> runtime, if I'm correct.
>
> 7. I have corrected grub/menu.lst by editing it and tried booting, but it gave
> the same error (not seeing the disk), probably because the initrd image is
> invalid.
>
> I ended up doing a fresh reinstall. This is not good. Someone with enough
> knowledge should be able to fix this situation without reinstallation.
>
> So either I don't have sufficient knowledge (easily fixable and not a
> distribution problem) or it can't be done--quite bad.
>
> Which one is it?
--
Mit freundlichen Gruessen,
Andreas Vetter
Fakultaet fuer Physik und Astronomie Tel: +49 (0)931 888-5890
Universitaet Wuerzburg Fax: +49 (0)931 888-5508
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |