Jammy Jellyfish.Jammy Jellyfish DEV loop: unable to read RDB boot failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
After Kernel linux-image-
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/
/dev/loop8 0 0 1 1 /var/lib/
/dev/loop6 0 0 1 1 /var/lib/
/dev/loop4 0 0 1 1 /var/lib/
/dev/loop11 0 0 1 1 /var/lib/
/dev/loop2 0 0 1 1 /var/lib/
/dev/loop0 0 0 1 1 /var/lib/
/dev/loop9 0 0 1 1 /var/lib/
/dev/loop7 0 0 1 1 /var/lib/
/dev/loop5 0 0 1 1 /var/lib/
/dev/loop12 0 0 1 1 /var/lib/
/dev/loop3 0 0 1 1 /var/lib/
/dev/loop10 0 0 1 1 /var/lib/
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
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/ FindRightPackag e. 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.]