USB thumb stick with live Ubuntu 18.04 and persistence has stopped working after out of memory error and shutdown
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
1
down vote
favorite
My USB which had worked OK for a week or so suddenly no longer works.
It boots up to the Ubuntu logo showing the blinking progress spots until the screen suddenly goes dark and a scrolling text message is displayed. It scrolls so fast I have great difficulty reading it. I tried the advice of one of the subscribers and tried typing ESC and also pressing the ESC key. This did produce some text but I couldn't read it all as it kept scrolling so fast.
After much concentration I think I managed to get one line read verbatim. It appeared after a lot of entries which seem to be OK'd and reads as follows:
[157.187130] [drm:intel-enable-lvds [i915]<ERROR>timed out waiting for panel to power on
The above line is replicated repeatedly but each starts with a different ref #.
I was installing a program when I got a message that I was out of memory and the installation couldn't proceed. I shut down thinking that I would gain memory space since the installation hadn't completed. I thought I would then be able to reboot and once up and running delete some programs to free up space. Unfortunately I wasn't able to boot up properly again.
I would be grateful if anyone could enlighten me as to what, if anything, I can do to rectify this.
Obviously, I could just build another USB live boot but I had quite a number of programs installed and I had problems with every one of them struggling to install them (which wasn't the case when using Knoppix 8.1 live USB where it worked right from the start and all Linux and Wine programs installed easily and worked perfectly).
boot live-usb
add a comment |Â
up vote
1
down vote
favorite
My USB which had worked OK for a week or so suddenly no longer works.
It boots up to the Ubuntu logo showing the blinking progress spots until the screen suddenly goes dark and a scrolling text message is displayed. It scrolls so fast I have great difficulty reading it. I tried the advice of one of the subscribers and tried typing ESC and also pressing the ESC key. This did produce some text but I couldn't read it all as it kept scrolling so fast.
After much concentration I think I managed to get one line read verbatim. It appeared after a lot of entries which seem to be OK'd and reads as follows:
[157.187130] [drm:intel-enable-lvds [i915]<ERROR>timed out waiting for panel to power on
The above line is replicated repeatedly but each starts with a different ref #.
I was installing a program when I got a message that I was out of memory and the installation couldn't proceed. I shut down thinking that I would gain memory space since the installation hadn't completed. I thought I would then be able to reboot and once up and running delete some programs to free up space. Unfortunately I wasn't able to boot up properly again.
I would be grateful if anyone could enlighten me as to what, if anything, I can do to rectify this.
Obviously, I could just build another USB live boot but I had quite a number of programs installed and I had problems with every one of them struggling to install them (which wasn't the case when using Knoppix 8.1 live USB where it worked right from the start and all Linux and Wine programs installed easily and worked perfectly).
boot live-usb
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My USB which had worked OK for a week or so suddenly no longer works.
It boots up to the Ubuntu logo showing the blinking progress spots until the screen suddenly goes dark and a scrolling text message is displayed. It scrolls so fast I have great difficulty reading it. I tried the advice of one of the subscribers and tried typing ESC and also pressing the ESC key. This did produce some text but I couldn't read it all as it kept scrolling so fast.
After much concentration I think I managed to get one line read verbatim. It appeared after a lot of entries which seem to be OK'd and reads as follows:
[157.187130] [drm:intel-enable-lvds [i915]<ERROR>timed out waiting for panel to power on
The above line is replicated repeatedly but each starts with a different ref #.
I was installing a program when I got a message that I was out of memory and the installation couldn't proceed. I shut down thinking that I would gain memory space since the installation hadn't completed. I thought I would then be able to reboot and once up and running delete some programs to free up space. Unfortunately I wasn't able to boot up properly again.
I would be grateful if anyone could enlighten me as to what, if anything, I can do to rectify this.
Obviously, I could just build another USB live boot but I had quite a number of programs installed and I had problems with every one of them struggling to install them (which wasn't the case when using Knoppix 8.1 live USB where it worked right from the start and all Linux and Wine programs installed easily and worked perfectly).
boot live-usb
My USB which had worked OK for a week or so suddenly no longer works.
It boots up to the Ubuntu logo showing the blinking progress spots until the screen suddenly goes dark and a scrolling text message is displayed. It scrolls so fast I have great difficulty reading it. I tried the advice of one of the subscribers and tried typing ESC and also pressing the ESC key. This did produce some text but I couldn't read it all as it kept scrolling so fast.
After much concentration I think I managed to get one line read verbatim. It appeared after a lot of entries which seem to be OK'd and reads as follows:
[157.187130] [drm:intel-enable-lvds [i915]<ERROR>timed out waiting for panel to power on
The above line is replicated repeatedly but each starts with a different ref #.
I was installing a program when I got a message that I was out of memory and the installation couldn't proceed. I shut down thinking that I would gain memory space since the installation hadn't completed. I thought I would then be able to reboot and once up and running delete some programs to free up space. Unfortunately I wasn't able to boot up properly again.
I would be grateful if anyone could enlighten me as to what, if anything, I can do to rectify this.
Obviously, I could just build another USB live boot but I had quite a number of programs installed and I had problems with every one of them struggling to install them (which wasn't the case when using Knoppix 8.1 live USB where it worked right from the start and all Linux and Wine programs installed easily and worked perfectly).
boot live-usb
edited May 28 at 20:03
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
Zanna
47.8k13116226
47.8k13116226
asked May 28 at 16:00
Col
61
61
add a comment |Â
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
1
down vote
Before putting a lot of effort into fixing the persistent USB, consider a full install to a USB instead. Persistent installs lack certain important things, like kernel security updates.
There are lots of suggestions from a Google search on:
free up space on an Ubuntu persistent USB
Your options:
- Use a bigger persistent file if less than 4G.
- Use a Persistent partition for larger than 4G storage.
- Use a home-rw file for up to 4G more storage,
- Cleanup the existing persistent storage.
The persistent storge file just contains a ext filesystem, which may be mounted with the loop option. Remove things like /var/log files, /var/cache/apt/archives deb files, etc. A new (larger?) file may be created (empty), moutned, then filled with the old information.
add a comment |Â
up vote
1
down vote
A Persistent install uses a file or partition named casper-rw, (or home-rw).
A casper-rw file is usually located on a FAT32 partition, and is limited to 4GB by the file system, however YUMI can make larger casper-rw files on a NTFS partition. Persistent partitions are only limited in size by disk size and are generally on an ext2 or ext4 file system.
If casper-rw becomes full the persistent drive will not boot.
A casper-rw file can be mounted and data removed to make the drive bootable again.
To mount casper-rw file, (booting from a second drive).
Create directory:
sudo mkdir /media/casper
Then mount drive:
sudo mount -o loop casper-rw /media/casper/
After a few files are removed the Persistent drive should boot.
If you need more persistence space, you can create a home-rw persistence file up to 4GB, (by copying and renaming a fresh casper-rw file). It will contain all your home folder data, or you can make the boot drive using YUMI to make a large NTFS casper-rw file, or use mkusb to make an unlimited casper-rw partition.
If you will be needing to update or upgrade your boot drive it is probably best to do a Full install to the drive.
Nowadays with large USB3 flash drives, Full installs are quite practical. A Full install is more secure, can use encrypted home directory, is updateable, upgradeable, boots faster, makes better use of disk space, can use proprietary drivers, etc, However a Full install is not much use for installing Ubuntu, and takes longer to make.
Home can be moved from casper-rw to home-rw using rsync, (I prefer grsync for the GUI).
add a comment |Â
up vote
0
down vote
Backup and restore a persistent live drive
Persistent live drives are sensitive to corruption. So it is a good idea to have a good backup routine.
Backup the content of the
casper-rw
file/partition often. Make it a routine. See this link,Backup and restore of persistent overlay data
There are reasons to backup 'only' the
/home
directory (inside thecasper-rw
file/partition. See this link,How do I upgrade a mkusb Persistent Live system from 16.04 to 18.04
If there is a
home-rw
file/partition, back it up too.Test that you can restore from the backup to create a working persistent live drive. (Test it before you have problems.)
Repair a persistent live drive
Even when the file system of the
casper-rw
file/partition is healthy, there are problems, when it is full.- boot from another drive or boot live-only (without the boot option
persistent
) into the persistent live drive - create directories to be mountpoints
mount the
casper-rw
file system (loop mount if in a file)sudo mount /dev/sdxn mountpoint # casper-rw partition
sudo mount /dev/sdxn mountpoint1 # casper-rw file
sudo mount -o loop mountpoint1/casper-rw mountpoint2remove some files that are not necessary
- unmount and reboot, and persistence will work again, if the only problem was that it was full.
- boot from another drive or boot live-only (without the boot option
If the file system of the
casper-rw
file/partition is damaged you can repair it according to the following link,Repair the partition table and file system of a pendrive
sudo e2fsck -f /dev/sdxn # casper-rw partition
sudo e2fsck -f mountpoint/casper-rw # casper-rw filewhere x is the drive letter and n is the partition number.
If the damage is too severe, repairing the file system may not help, and the only options are to
- restore from a backup
- try to recover the most valuable files with recovery tools, for example
testdisk
orphotorec
from cgsecurity.org
Install Ubuntu into a USB pendrive
It can be a good alternative to create an installed Ubuntu system in a fast USB 3 pendrive. This is described with many details in the following link,
Boot Ubuntu from external drive
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Before putting a lot of effort into fixing the persistent USB, consider a full install to a USB instead. Persistent installs lack certain important things, like kernel security updates.
There are lots of suggestions from a Google search on:
free up space on an Ubuntu persistent USB
Your options:
- Use a bigger persistent file if less than 4G.
- Use a Persistent partition for larger than 4G storage.
- Use a home-rw file for up to 4G more storage,
- Cleanup the existing persistent storage.
The persistent storge file just contains a ext filesystem, which may be mounted with the loop option. Remove things like /var/log files, /var/cache/apt/archives deb files, etc. A new (larger?) file may be created (empty), moutned, then filled with the old information.
add a comment |Â
up vote
1
down vote
Before putting a lot of effort into fixing the persistent USB, consider a full install to a USB instead. Persistent installs lack certain important things, like kernel security updates.
There are lots of suggestions from a Google search on:
free up space on an Ubuntu persistent USB
Your options:
- Use a bigger persistent file if less than 4G.
- Use a Persistent partition for larger than 4G storage.
- Use a home-rw file for up to 4G more storage,
- Cleanup the existing persistent storage.
The persistent storge file just contains a ext filesystem, which may be mounted with the loop option. Remove things like /var/log files, /var/cache/apt/archives deb files, etc. A new (larger?) file may be created (empty), moutned, then filled with the old information.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Before putting a lot of effort into fixing the persistent USB, consider a full install to a USB instead. Persistent installs lack certain important things, like kernel security updates.
There are lots of suggestions from a Google search on:
free up space on an Ubuntu persistent USB
Your options:
- Use a bigger persistent file if less than 4G.
- Use a Persistent partition for larger than 4G storage.
- Use a home-rw file for up to 4G more storage,
- Cleanup the existing persistent storage.
The persistent storge file just contains a ext filesystem, which may be mounted with the loop option. Remove things like /var/log files, /var/cache/apt/archives deb files, etc. A new (larger?) file may be created (empty), moutned, then filled with the old information.
Before putting a lot of effort into fixing the persistent USB, consider a full install to a USB instead. Persistent installs lack certain important things, like kernel security updates.
There are lots of suggestions from a Google search on:
free up space on an Ubuntu persistent USB
Your options:
- Use a bigger persistent file if less than 4G.
- Use a Persistent partition for larger than 4G storage.
- Use a home-rw file for up to 4G more storage,
- Cleanup the existing persistent storage.
The persistent storge file just contains a ext filesystem, which may be mounted with the loop option. Remove things like /var/log files, /var/cache/apt/archives deb files, etc. A new (larger?) file may be created (empty), moutned, then filled with the old information.
answered May 28 at 22:21
ubfan1
8,56631527
8,56631527
add a comment |Â
add a comment |Â
up vote
1
down vote
A Persistent install uses a file or partition named casper-rw, (or home-rw).
A casper-rw file is usually located on a FAT32 partition, and is limited to 4GB by the file system, however YUMI can make larger casper-rw files on a NTFS partition. Persistent partitions are only limited in size by disk size and are generally on an ext2 or ext4 file system.
If casper-rw becomes full the persistent drive will not boot.
A casper-rw file can be mounted and data removed to make the drive bootable again.
To mount casper-rw file, (booting from a second drive).
Create directory:
sudo mkdir /media/casper
Then mount drive:
sudo mount -o loop casper-rw /media/casper/
After a few files are removed the Persistent drive should boot.
If you need more persistence space, you can create a home-rw persistence file up to 4GB, (by copying and renaming a fresh casper-rw file). It will contain all your home folder data, or you can make the boot drive using YUMI to make a large NTFS casper-rw file, or use mkusb to make an unlimited casper-rw partition.
If you will be needing to update or upgrade your boot drive it is probably best to do a Full install to the drive.
Nowadays with large USB3 flash drives, Full installs are quite practical. A Full install is more secure, can use encrypted home directory, is updateable, upgradeable, boots faster, makes better use of disk space, can use proprietary drivers, etc, However a Full install is not much use for installing Ubuntu, and takes longer to make.
Home can be moved from casper-rw to home-rw using rsync, (I prefer grsync for the GUI).
add a comment |Â
up vote
1
down vote
A Persistent install uses a file or partition named casper-rw, (or home-rw).
A casper-rw file is usually located on a FAT32 partition, and is limited to 4GB by the file system, however YUMI can make larger casper-rw files on a NTFS partition. Persistent partitions are only limited in size by disk size and are generally on an ext2 or ext4 file system.
If casper-rw becomes full the persistent drive will not boot.
A casper-rw file can be mounted and data removed to make the drive bootable again.
To mount casper-rw file, (booting from a second drive).
Create directory:
sudo mkdir /media/casper
Then mount drive:
sudo mount -o loop casper-rw /media/casper/
After a few files are removed the Persistent drive should boot.
If you need more persistence space, you can create a home-rw persistence file up to 4GB, (by copying and renaming a fresh casper-rw file). It will contain all your home folder data, or you can make the boot drive using YUMI to make a large NTFS casper-rw file, or use mkusb to make an unlimited casper-rw partition.
If you will be needing to update or upgrade your boot drive it is probably best to do a Full install to the drive.
Nowadays with large USB3 flash drives, Full installs are quite practical. A Full install is more secure, can use encrypted home directory, is updateable, upgradeable, boots faster, makes better use of disk space, can use proprietary drivers, etc, However a Full install is not much use for installing Ubuntu, and takes longer to make.
Home can be moved from casper-rw to home-rw using rsync, (I prefer grsync for the GUI).
add a comment |Â
up vote
1
down vote
up vote
1
down vote
A Persistent install uses a file or partition named casper-rw, (or home-rw).
A casper-rw file is usually located on a FAT32 partition, and is limited to 4GB by the file system, however YUMI can make larger casper-rw files on a NTFS partition. Persistent partitions are only limited in size by disk size and are generally on an ext2 or ext4 file system.
If casper-rw becomes full the persistent drive will not boot.
A casper-rw file can be mounted and data removed to make the drive bootable again.
To mount casper-rw file, (booting from a second drive).
Create directory:
sudo mkdir /media/casper
Then mount drive:
sudo mount -o loop casper-rw /media/casper/
After a few files are removed the Persistent drive should boot.
If you need more persistence space, you can create a home-rw persistence file up to 4GB, (by copying and renaming a fresh casper-rw file). It will contain all your home folder data, or you can make the boot drive using YUMI to make a large NTFS casper-rw file, or use mkusb to make an unlimited casper-rw partition.
If you will be needing to update or upgrade your boot drive it is probably best to do a Full install to the drive.
Nowadays with large USB3 flash drives, Full installs are quite practical. A Full install is more secure, can use encrypted home directory, is updateable, upgradeable, boots faster, makes better use of disk space, can use proprietary drivers, etc, However a Full install is not much use for installing Ubuntu, and takes longer to make.
Home can be moved from casper-rw to home-rw using rsync, (I prefer grsync for the GUI).
A Persistent install uses a file or partition named casper-rw, (or home-rw).
A casper-rw file is usually located on a FAT32 partition, and is limited to 4GB by the file system, however YUMI can make larger casper-rw files on a NTFS partition. Persistent partitions are only limited in size by disk size and are generally on an ext2 or ext4 file system.
If casper-rw becomes full the persistent drive will not boot.
A casper-rw file can be mounted and data removed to make the drive bootable again.
To mount casper-rw file, (booting from a second drive).
Create directory:
sudo mkdir /media/casper
Then mount drive:
sudo mount -o loop casper-rw /media/casper/
After a few files are removed the Persistent drive should boot.
If you need more persistence space, you can create a home-rw persistence file up to 4GB, (by copying and renaming a fresh casper-rw file). It will contain all your home folder data, or you can make the boot drive using YUMI to make a large NTFS casper-rw file, or use mkusb to make an unlimited casper-rw partition.
If you will be needing to update or upgrade your boot drive it is probably best to do a Full install to the drive.
Nowadays with large USB3 flash drives, Full installs are quite practical. A Full install is more secure, can use encrypted home directory, is updateable, upgradeable, boots faster, makes better use of disk space, can use proprietary drivers, etc, However a Full install is not much use for installing Ubuntu, and takes longer to make.
Home can be moved from casper-rw to home-rw using rsync, (I prefer grsync for the GUI).
edited Jun 3 at 16:21
answered Jun 3 at 15:51
C.S.Cameron
3,7741924
3,7741924
add a comment |Â
add a comment |Â
up vote
0
down vote
Backup and restore a persistent live drive
Persistent live drives are sensitive to corruption. So it is a good idea to have a good backup routine.
Backup the content of the
casper-rw
file/partition often. Make it a routine. See this link,Backup and restore of persistent overlay data
There are reasons to backup 'only' the
/home
directory (inside thecasper-rw
file/partition. See this link,How do I upgrade a mkusb Persistent Live system from 16.04 to 18.04
If there is a
home-rw
file/partition, back it up too.Test that you can restore from the backup to create a working persistent live drive. (Test it before you have problems.)
Repair a persistent live drive
Even when the file system of the
casper-rw
file/partition is healthy, there are problems, when it is full.- boot from another drive or boot live-only (without the boot option
persistent
) into the persistent live drive - create directories to be mountpoints
mount the
casper-rw
file system (loop mount if in a file)sudo mount /dev/sdxn mountpoint # casper-rw partition
sudo mount /dev/sdxn mountpoint1 # casper-rw file
sudo mount -o loop mountpoint1/casper-rw mountpoint2remove some files that are not necessary
- unmount and reboot, and persistence will work again, if the only problem was that it was full.
- boot from another drive or boot live-only (without the boot option
If the file system of the
casper-rw
file/partition is damaged you can repair it according to the following link,Repair the partition table and file system of a pendrive
sudo e2fsck -f /dev/sdxn # casper-rw partition
sudo e2fsck -f mountpoint/casper-rw # casper-rw filewhere x is the drive letter and n is the partition number.
If the damage is too severe, repairing the file system may not help, and the only options are to
- restore from a backup
- try to recover the most valuable files with recovery tools, for example
testdisk
orphotorec
from cgsecurity.org
Install Ubuntu into a USB pendrive
It can be a good alternative to create an installed Ubuntu system in a fast USB 3 pendrive. This is described with many details in the following link,
Boot Ubuntu from external drive
add a comment |Â
up vote
0
down vote
Backup and restore a persistent live drive
Persistent live drives are sensitive to corruption. So it is a good idea to have a good backup routine.
Backup the content of the
casper-rw
file/partition often. Make it a routine. See this link,Backup and restore of persistent overlay data
There are reasons to backup 'only' the
/home
directory (inside thecasper-rw
file/partition. See this link,How do I upgrade a mkusb Persistent Live system from 16.04 to 18.04
If there is a
home-rw
file/partition, back it up too.Test that you can restore from the backup to create a working persistent live drive. (Test it before you have problems.)
Repair a persistent live drive
Even when the file system of the
casper-rw
file/partition is healthy, there are problems, when it is full.- boot from another drive or boot live-only (without the boot option
persistent
) into the persistent live drive - create directories to be mountpoints
mount the
casper-rw
file system (loop mount if in a file)sudo mount /dev/sdxn mountpoint # casper-rw partition
sudo mount /dev/sdxn mountpoint1 # casper-rw file
sudo mount -o loop mountpoint1/casper-rw mountpoint2remove some files that are not necessary
- unmount and reboot, and persistence will work again, if the only problem was that it was full.
- boot from another drive or boot live-only (without the boot option
If the file system of the
casper-rw
file/partition is damaged you can repair it according to the following link,Repair the partition table and file system of a pendrive
sudo e2fsck -f /dev/sdxn # casper-rw partition
sudo e2fsck -f mountpoint/casper-rw # casper-rw filewhere x is the drive letter and n is the partition number.
If the damage is too severe, repairing the file system may not help, and the only options are to
- restore from a backup
- try to recover the most valuable files with recovery tools, for example
testdisk
orphotorec
from cgsecurity.org
Install Ubuntu into a USB pendrive
It can be a good alternative to create an installed Ubuntu system in a fast USB 3 pendrive. This is described with many details in the following link,
Boot Ubuntu from external drive
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Backup and restore a persistent live drive
Persistent live drives are sensitive to corruption. So it is a good idea to have a good backup routine.
Backup the content of the
casper-rw
file/partition often. Make it a routine. See this link,Backup and restore of persistent overlay data
There are reasons to backup 'only' the
/home
directory (inside thecasper-rw
file/partition. See this link,How do I upgrade a mkusb Persistent Live system from 16.04 to 18.04
If there is a
home-rw
file/partition, back it up too.Test that you can restore from the backup to create a working persistent live drive. (Test it before you have problems.)
Repair a persistent live drive
Even when the file system of the
casper-rw
file/partition is healthy, there are problems, when it is full.- boot from another drive or boot live-only (without the boot option
persistent
) into the persistent live drive - create directories to be mountpoints
mount the
casper-rw
file system (loop mount if in a file)sudo mount /dev/sdxn mountpoint # casper-rw partition
sudo mount /dev/sdxn mountpoint1 # casper-rw file
sudo mount -o loop mountpoint1/casper-rw mountpoint2remove some files that are not necessary
- unmount and reboot, and persistence will work again, if the only problem was that it was full.
- boot from another drive or boot live-only (without the boot option
If the file system of the
casper-rw
file/partition is damaged you can repair it according to the following link,Repair the partition table and file system of a pendrive
sudo e2fsck -f /dev/sdxn # casper-rw partition
sudo e2fsck -f mountpoint/casper-rw # casper-rw filewhere x is the drive letter and n is the partition number.
If the damage is too severe, repairing the file system may not help, and the only options are to
- restore from a backup
- try to recover the most valuable files with recovery tools, for example
testdisk
orphotorec
from cgsecurity.org
Install Ubuntu into a USB pendrive
It can be a good alternative to create an installed Ubuntu system in a fast USB 3 pendrive. This is described with many details in the following link,
Boot Ubuntu from external drive
Backup and restore a persistent live drive
Persistent live drives are sensitive to corruption. So it is a good idea to have a good backup routine.
Backup the content of the
casper-rw
file/partition often. Make it a routine. See this link,Backup and restore of persistent overlay data
There are reasons to backup 'only' the
/home
directory (inside thecasper-rw
file/partition. See this link,How do I upgrade a mkusb Persistent Live system from 16.04 to 18.04
If there is a
home-rw
file/partition, back it up too.Test that you can restore from the backup to create a working persistent live drive. (Test it before you have problems.)
Repair a persistent live drive
Even when the file system of the
casper-rw
file/partition is healthy, there are problems, when it is full.- boot from another drive or boot live-only (without the boot option
persistent
) into the persistent live drive - create directories to be mountpoints
mount the
casper-rw
file system (loop mount if in a file)sudo mount /dev/sdxn mountpoint # casper-rw partition
sudo mount /dev/sdxn mountpoint1 # casper-rw file
sudo mount -o loop mountpoint1/casper-rw mountpoint2remove some files that are not necessary
- unmount and reboot, and persistence will work again, if the only problem was that it was full.
- boot from another drive or boot live-only (without the boot option
If the file system of the
casper-rw
file/partition is damaged you can repair it according to the following link,Repair the partition table and file system of a pendrive
sudo e2fsck -f /dev/sdxn # casper-rw partition
sudo e2fsck -f mountpoint/casper-rw # casper-rw filewhere x is the drive letter and n is the partition number.
If the damage is too severe, repairing the file system may not help, and the only options are to
- restore from a backup
- try to recover the most valuable files with recovery tools, for example
testdisk
orphotorec
from cgsecurity.org
Install Ubuntu into a USB pendrive
It can be a good alternative to create an installed Ubuntu system in a fast USB 3 pendrive. This is described with many details in the following link,
Boot Ubuntu from external drive
edited Jun 4 at 6:50
answered Jun 4 at 6:44
![](https://i.stack.imgur.com/lcww5.png?s=32&g=1)
![](https://i.stack.imgur.com/lcww5.png?s=32&g=1)
sudodus
19.8k32666
19.8k32666
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1041251%2fusb-thumb-stick-with-live-ubuntu-18-04-and-persistence-has-stopped-working-after%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password