NOBLE 24.04 Persistence is not enabled

Bug #2065315 reported by geole0
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I'm trying to make persistence work in an installation boot without success.

I suspect that the "persistence" parameter which is no longer recognized may be the cause.
However, it is possible that with this version there is a new technique to enable persistence. But I can't find how to do it.
Thank you for your reply

May 09 13:42:42 ubuntu kernel: Kernel command line: BOOT_IMAGE=/casper/vmlinuz quiet persistent splash
May 09 13:42:42 ubuntu kernel: Unknown kernel command line parameters "persistent splash BOOT_IMAGE=/casper/vmlinuz", will be passed to user space.
May 09 13:42:42 ubuntu kernel: persistent

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CasperVersion: 1.498
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Thu May 9 14:31:58 2024
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
summary: - NOBLE 20.04 Persistence is not enabled
+ NOBLE 24.04 Persistence is not enabled
affects: grub2 (Ubuntu) → casper (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

Your report shows you booted with 'persistent' as the parameter, which is correct and is still supported. Why do you claim that it is "no longer recognized"?

> LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)

This seems reasonable.

What media are you booting from, how did you prepare it? Persistence only works if the boot medium is writable and has room for the addition of a persistence partition.

Changed in casper (Ubuntu):
status: New → Incomplete
Revision history for this message
geole0 (geole0) wrote :

Good morning
I was worried because I read

 Unknown kernel command line parameters "persistent splash BOOT_IMAGE=/casper/vmlinuz", will be passed to user space.
May 09 13:42:42 ubuntu kernel: persistent

My live USB is like that

a@b:~$ lsblk -fe7 /dev/sdd
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sdd
├─sdd1 vfat FAT32 USBUNET 72EE-4CCC 219,9M 96% /media/a/USBUNET
├─sdd2 ext4 1.0 casper-rw 06f20fd7-c411-4aa5-be02-7b11934f71b9 7,1G 4% /media/a/casper-rw
└─sdd3 exfat 1.0 USBEXFAT F6BD-F745 660,9M 0% /media/a/USBEXFAT
a@b:~$

I don't know if this partition should mount automatically or if it's up to me to mount it. If yes, how?

The DF command did not list this partition as mounted.

THANKS

Revision history for this message
geole0 (geole0) wrote :

Hello
It is now good with this order.
ubuntu@ubuntu:~$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 14.65 GiB, 15728640000 bytes, 30720000 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc4d3df7d

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 16779263 16777216 8G 83 Linux
/dev/sdb2 * 16779264 29362175 12582912 6G b W95 FAT32
/dev/sdb3 29362176 30719999 1357824 663M 7 HPFS/NTFS/exFAT
ubuntu@ubuntu:~$

Revision history for this message
geole0 (geole0) wrote :

Good morning.
During the first try, I made a mistake in using it.
I just started again under the same conditions and persistence works well.
With my regrets.

df -htext4
Filesystem Size Used Avail Use% Mounted on
/dev/disk/by-label/casper-rw 636M 4.8M 585M 1% /var/log

sudo lsblk /dev/sdd
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sdd 8:48 1 14.6G 0 disk
├─sdd1 8:49 1 8G 0 part
├─sdd2 8:50 1 6G 0 part /cdrom
└─sdd3 8:51 1 663M 0 part /var/crash
                                /var/log

sudo blkid | grep sdd
/dev/sdd1: LABEL="COW" UUID="1519dfcc-0e04-4290-9c39-590b4270305f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c4d3df7d-01"
/dev/sdd2: LABEL_FATBOOT="USBUNET" LABEL="USBUNET" UUID="72EE-4CCC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="c4d3df7d-02"
/dev/sdd3: LABEL="casper-rw" UUID="771a5628-7772-40d4-b5f3-929476b5a1b7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c4d3df7d-03"

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for casper (Ubuntu) because there has been no activity for 60 days.]

Changed in casper (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.