Casper-rw Persistence files not working with 20.04

Bug #1877222 reported by C.S.Cameron
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have just noticed that casper-rw persistent files are not working with Ubuntu 20.04 when booted from an ISO file.

Persistent partitions are working, however persistent partitions do not work with "persistent-path" and only one persistent partition is allowed per USB disk.

This means that a multiboot, multipersistence USB drive is no longer possible using ISO files.

Hopefully someone will point out that I am making an error somewhere.

I have also just tested BIOS boot of a Persistent UNetbootin USB drive and there is no persistence.

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Revision history for this message
C.S.Cameron (cscameron) wrote :

The persistent file/partition name in Ubuntu 20.04 has been officially changed from casper-rw to writable.

On my computer a persistent partition can be named either casper-rw or writable and it will still work.

However a persistent file must now be named writable.

One Live USB expert compared this to America changing the name of the dollar to "valuable".

Revision history for this message
Adam W (lubuntu-tester) wrote :

"The persistent file/partition name in Ubuntu 20.04 has been officially changed from casper-rw to writable."

Could you post a link/reference here?

tags: added: casper-rw persistence persistent
Revision history for this message
C.S.Cameron (cscameron) wrote :
Revision history for this message
Adam W (lubuntu-tester) wrote :

I can confirm using the name "casper-rw"(for a persistence file, not a partition) with cmd args "persistent-path" is broken on 20.04.

Changing the name to "writable" resumes the expected behavior.

@cscameron, Thanks for the link above.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers