Jammy Jellyfish.Jammy Jellyfish DEV loop: unable to read RDB boot failure

[Christophe Rigaud]

After Kernel linux-image-5.17.0-1020-oem upgrade, a DEV loop13: unable to read RDB block message is displayed at boot sequence. The boot sequence is then stopped -> system fails to load. Rebooting in safe mode allows an access to the system. The following command returns :

systemctl status dev-loop13.device
○ dev-loop13.device - /dev/loop13
     Loaded: loaded
     Active: inactive (dead)

losetup:

NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC
/dev/loop1 0 0 1 1 /var/lib/snapd/snaps/core_13886.snap 0 512
/dev/loop8 0 0 1 1 /var/lib/snapd/snaps/snapd_17336.snap 0 512
/dev/loop6 0 0 1 1 /var/lib/snapd/snaps/hunspell-dictionaries-1-7-2004_2.snap 0 512
/dev/loop4 0 0 1 1 /var/lib/snapd/snaps/firefox_1993.snap 0 512
/dev/loop11 0 0 1 1 /var/lib/snapd/snaps/bare_5.snap 0 512
/dev/loop2 0 0 1 1 /var/lib/snapd/snaps/core18_2566.snap 0 512
/dev/loop0 0 0 1 1 /var/lib/snapd/snaps/code_111.snap 0 512
/dev/loop9 0 0 1 1 /var/lib/snapd/snaps/warzone2100_5456.snap 0 512
/dev/loop7 0 0 1 1 /var/lib/snapd/snaps/pycharm-community_302.snap 0 512
/dev/loop5 0 0 1 1 /var/lib/snapd/snaps/gnome-3-38-2004_119.snap 0 512
/dev/loop12 0 0 1 1 /var/lib/snapd/snaps/gtk-common-themes_1535.snap 0 512
/dev/loop3 0 0 1 1 /var/lib/snapd/snaps/core20_1623.snap 0 512
/dev/loop10 0 0 1 1 /var/lib/snapd/snaps/warzone2100-videos_2.snap 0 512

All loops belong to snap. /dev/loop13 is not listed -> I removed it, but it didn't fix the issue. The boot failed once again with 5.17. In checking through safe mode, /dev/loop13 was created again.

To note: there is not issue booting with 5.15.0.52-generic

Regards
Christophe

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1994062/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Christophe Rigaud (crigaud)]

1. Package not mentioned because not identified.
2. I made a thorough analysis of the issue and it seems to be something different:
- NVIDIA proprietary drivers (version 515) are not loaded with linux-image-5.17.0-1020-oem at boot sequence, while they are loaded with 5.15.0.52-generic (see file enclosed for details).
- Drivers available :
 driver : nvidia-driver-515 - distro non-free
 driver : nvidia-driver-515-open - distro non-free
- apt-update downloaded both 5.17 & a new version of NVIDIA drivers.

[Dominik S (dominiktoja)]

I have a similar problem, recently I tested several linux distributions and I have this problem only on ubuntu 22.10 and ubuntu 23.04 beta. During system startup, I get messages popping up and the screen has weird discoloration at the bottom.

Errors:
kernel: Dev loop0: unable to read RDB block 8
kernel: Dev loop17: unable to read RDB block 8

Ubuntu 23.04

uname --kernel-release
5.19.0-21-generic

It seems to affect the kernel but on arch linux with kernel 5.19 there was no such problem
Unfortunately, I don't know how to provide more relevant information :(

[Christophe Rigaud (crigaud)]

Hello,

Apparently getting whose errors at setup doesn't seem to be an real issue : the system only warns that the files do not have the proper size.

In my case the true issue was at Kernel upgrade level: one of the new Kernel component was missing preventing the setup to succeed. The fix was to reboot relying on the legacy Kernel, remove the upgraded Kernel then installing again manually.

If I were you I would check the logs in either /var/log, /var/log/messages or /var/log/syslog
Another thing to check: if your current video driver is compatible with Kernel 5.19.0-21-generic ?

Chris.