Re: (current 64) System unbootable after kernel update
Vincent Batts <vbatts <at> gmail.com>
2011-03-21 15:20:00 GMT
and another thing to keep in mind, the usb boot image needs to match
the ARCH of the installed system you are attempting to chroot into.
since you mentioned the installation was 64bit, then make the usb 64bit as well.
Take care,
vb
http://hashbangbash.com/
On Mon, Mar 21, 2011 at 11:18 AM, Vincent Batts <vbatts <at> gmail.com> wrote:
> this kind of recovery is always "exciting" the first couple of times :)
> also, if you are concerned for the future, there is also an option for
> slackpkg in /etc/slackpkg/slackpkg.conf
> DOWNLOAD_ALL=on
> it will cache all the packages before it begins the install/upgrade process.
> OR
> just keep a local rsync mirror ;) (just joking, it just seems that i
> do that on many of my machines)
>
> when mounting a system in recovery, i have and do still use the --root
> type flags, but i *usually* feel more comfortable in a chroot'ed
> environment. So assuming that '/' and '/boot' are different, a common
> series of commands would be
>
> <snip>
> mount /dev/vg0/lvol1 /mnt
> mount /dev/sda1 /mnt/boot
> mount --bind /dev /mnt/dev
> mount --bind /sys /mnt/sys
> mount --bind /proc /mnt/proc
> chroot /mnt
> </snip>
>
> then, in this chroot, go go to where the cached/stored/downloaded
> packages are. and
> #> upgragepkg --install-new *.t?z
>
> it may be clean and necessary to check /var/log/packages/ for a
> mid-state upgrade, like your kernel-firmware, you may find two files.
> One new and the old looking like
> "kernel-firmware-2.6.37.4-noarch-1-upgraded-2011-03-18,10:07:52"
> In this case sometimes i will removepkg both of them, and then
> installpkg that package manually.
>
> also, with this proper chroot, you can then ensure your /etc/lilo.conf
> is correct, and re-run lilo to seat the boot loader for the new kernel
>
> hope this helps.
>
> Take care,
> vb
> http://hashbangbash.com/
>
>
> On Mon, Mar 21, 2011 at 11:04 AM, Ottavio <ottavio <at> bigfoot.com> wrote:
>> Hello, I am (I should say I was) using slackware 64 current.
>>
>> I usually update my installation every morning with:
>>
>> slackpkg update && slackpkg upgrade-all
>>
>> The updates available were:
>>
>> - pkgtools
>> - kernel-huge
>> - kernel-modules
>> - kernel-firmware
>>
>> While installing the kernel-firmware package the installer hung with a
>> "timer interrupt" error.
>>
>> I had already another virtual terminal as root open but I couldn't
>> type anything and I couldn't get to open any other windows. So I had
>> to reboot the system and it was obviously unbootable.
>>
>> So I booted from the usb image (24 mg) and mounted the root partition
>> on /mnt, downloaded the above mentioned packages and installed the
>> packages with the option:
>>
>> installpkg /tmp/* --root /mnt
>>
>> So i rebooted the system and it is still unbootable, it hangs at
>> "loading linux" .
>>
>> Any ideas?
>>
>> --
>> Ottavio
>>
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>> A: Top-posting.
>> Q: What is the most annoying thing in e-mail?
>>
>> _______________________________________________
>> slackware mailing list
>> slackware <at> mailman.lug.org.uk
>> https://mailman.lug.org.uk/mailman/listinfo/slackware
>>
>
RSS Feed