1. Forum
  2. Usenet
  3. ALT.OS.LINUX.UBUNTU

  • failed upgrade

    From philo@21:1/5 to All on Wed May 25 17:38:32 2022
    I attempted to upgrade my Ubuntu 20.04 to 22.04 and on reboot am faced
    with Kernel Panic not syncing VFS: Unable to mount root fs on
    unknown block


    It has the 5.4.0-110-generic kernel and it looks like the upgrade has
    removed all previous kernels.


    I thankfully have Mint on another drive and can dual boot so I can
    access the failed Linux system.


    Help would very much be appreciated. Thanks


    If I can't get this solved, about all I can think of is to try a fresh
    install on another drive and copy my data back. That alternative might
    not be all that bad as I can move from a mechanical drive to SSD but
    still I'd like to get this fixed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter@21:1/5 to philo on Sat May 28 09:02:26 2022
    On 26.05.2022 00:38, philo wrote:
    I attempted to upgrade my Ubuntu 20.04  to 22.04 and on reboot am faced
    with Kernel Panic    not syncing   VFS: Unable to mount root fs on unknown block


    It has the 5.4.0-110-generic kernel and it looks like the upgrade has
    removed all previous kernels.


    I thankfully have Mint on another drive and can dual boot so I can
    access the failed Linux system.


    Help would very much be appreciated. Thanks


    If I can't get this solved, about all I can think of is to try a fresh install on another drive and copy my data back.  That alternative might
    not be all that bad as I can move from a mechanical drive to SSD but
    still I'd like to get this fixed.

    Are you sure about that kernel version?
    My 20.04.4 has kernel 5.13.0-44-generic, and a quick search say 22.04
    will ship with 5.15

    Peter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From philo@21:1/5 to Peter on Sat May 28 16:57:10 2022
    On 5/28/22 2:02 AM, Peter wrote:
    On 26.05.2022 00:38, philo wrote:
    I attempted to upgrade my Ubuntu 20.04  to 22.04 and on reboot am
    faced with Kernel Panic    not syncing   VFS: Unable to mount root fs >> on unknown block


    It has the 5.4.0-110-generic kernel and it looks like the upgrade has
    removed all previous kernels.


    I thankfully have Mint on another drive and can dual boot so I can
    access the failed Linux system.


    Help would very much be appreciated. Thanks


    If I can't get this solved, about all I can think of is to try a fresh
    install on another drive and copy my data back.  That alternative
    might not be all that bad as I can move from a mechanical drive to SSD
    but still I'd like to get this fixed.

    Are you sure about that kernel version?
    My 20.04.4 has kernel 5.13.0-44-generic, and a quick search say 22.04
    will ship with 5.15

    Peter



    You are correct. Now that I have updated GRUB things are sorted out I
    see I am running Kernel 5.15.0-33

    The reason it did not boot was GRUB was pointing to a kernel which had
    been removed.


    As long as I am here, I might as make one more comment.

    Even though I had 5 gigs of free space on my root partition, from time
    to time during the upgrade I received a message of low disk space.

    I did a check at the time to confirm disk space was not low. Anyway the upgrade did not fail.


    As a precaution though I ran Bleach Bit as Administrator and dumped
    about 2 gigs worth of junk.

    Since this installation started out as 12.04 many years ago, clearing
    junk was something I should have done a few years ago.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From stepore@21:1/5 to philo on Sat May 28 23:01:51 2022
    On 5/28/22 14:57, philo wrote:

    Even though I had 5 gigs of free space on my root partition, from time
    to time during the upgrade I received a message of low disk space.

    I did a check at the time to confirm disk space was not low. Anyway the upgrade did not fail.


    As a precaution though I ran Bleach Bit as Administrator and dumped
    about 2 gigs worth of junk.

    Since this installation started out as 12.04 many years ago, clearing
    junk was something I should have done a few years ago.

    If your actual free space on your disk was fine, then it was most likely exhausted inodes. Since you upgraded from 12.04 then that would explain
    it. Had you done: df -i , that would have shown you inode use rather
    than disk space use. Exhausted inodes does show up sometimes as a 'low
    disk space' error.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From philo@21:1/5 to All on Sun May 29 08:53:53 2022
    Too many inodes makes sense.
    I never thought of that...thank you.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)