(it's highly recommended to use a good quality pen)
* Method 1 (beginner, simple persistence):
# Assuming that your usb drive is /dev/sdc
$ USB_DEV=/dev/sdc
$ cp io-live--2016.04--e21-k4.6.3-rt-amd64 ${USB_DEV}
# !!! Be careful that it will erase all contents in your usb drive
(an alternate way to copy the iso to the USB flash drive is to use dd.. use this in case of problem with cp)
$ sudo dd io-live--2016.04--e21-k4.6.3-rt-amd64 ${USB_DEV}
When the copy has finished, create an ext4 partition in the free space of the drive with label: persistence
Finally, copy the persistence.conf in this partition and you're done... you can now reboot a enjoy the full persistence :o)
* Method 2 (advanced, encrypted persistence):
It consists of making an ext4 partition (4Go) in the beginning of the drive, extract the iso in it, install extlinux and make it bootable
In the free space, create an encrypted (LUKS) partition with label persistence that contains a persistence.conf file.
Also, as this is my first time really delving into linux, I do not have a linux, or the technical know-how to follow these steps in windows to create my own live persistent version. (I believe this requires... terminal?) Please help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there! Desperately trying to make a working USB with Win10 to switch to the latest release of io.GNU... But all I get is can not mount /dev/loop0
because of filesystem.squashfs
The file just seems doesn't fit FAT32 that can be obtained from Win software to make a bootable USB drive.
Any ideas?
Last edit: Volodymyr 2019-04-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First considering the ISO I downloaded is OK ... But I encounter the same problem as Volodymyr .
The USB device is a 32Go SD card adapted on an USB stick ...
I firsts tried to flash directly to the SD card, with same results as Volodymyr : "(initsram) : no aufs found", then "can not mount /dev/loop0, etc ... " all with a command-line looking bootloader ....
Finally, after unsuccessfull tries on the USB stick adaptation, I could obtain the "splash" bootloader : but if trying to boot any one option seem to run correctly, the boot abort on a blank screen without any possible control ... Only an hard reset is efficient ...
But I'm in doubt the ISO is corrupted . I think your méthod to create Flash drive isn't detailed enought ... For example, I got different results if I format Vfat first or not, or ext4 ... The best result ( splash bootloader ) were obtained in erasing all partition table on the stick ... But Gparted don't reconize any partition table after flashing the stick . So I wasn't able to create a new "persistence" one ... Gparted only found errors GPT signature . Here is the message : > /dev/sdc contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?
So how the USB device have to be formated, partitonned, etc, before flashing it ? Great thanks in advance : 2 days of big crisis ....
Edit : a try with the "dd" method don't work :
" dd: opérande « io-live--2019.01--full-k4.19.20-k4.19.20-rt12-i386 » non reconnu
Saisissez « dd --help » pour plus d'informations."
Last edit: phil gay 2019-06-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
if going from SD card to using a USB stick gave you a marginal increase in what could be seen, it may not be a filesystem issue with grub but that your BIOS is buggy and can't properly handle large drives ( http://tldp.org/HOWTO/Large-Disk-HOWTO-4.html ).
This translates into the BIOS being unable to read blocks past a certain point in the drive, and so if your root filesystem starts before that limit, but ends after that limit, then some files will be accessible at boot through the BIOS and others won't.
The standard way to work around this problem is to create a small /boot/ partition near the beginning of the drive, to ensure that everything that needs to be read through the BIOS, can be.
Regarding Gparted's error message, the fake msdos partition table refers to the MBR format, which could have been changed while you were erasiing the other partitions and not doing a complete flash. When formatting, make sure not to do a quick format and make sure whatever program you're using actually goes through the memory slots and changes each bit to 0 for a non-recoverable type of wipe.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey Clivus, did ou get past all the mentioned issues with the latest 2019 (io-live--2019.01--full-k4.19.20-k4.19.20-rt12-amd64) version using Unetbootin? I've been having to using the 2017-03 version because I couldn't seem to get it to work.
Tried all the various noacpi acpi=none nvidia.modeset=0 nomodeset tricks one would normally do when using a later nvidia card but continue to run into the aforementioned issue of
(initsram) : no aufs found.
Just wondering if you had no issues with the latest version as I wouldn't expect you to be able to help with the inistram issue
Side note: hitting 'exit' command would just eventuall lead to beig unable to mount aufs and filesystem.squashfs.
Last edit: David Do 2020-05-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You mean for posts from @nemyrnyi (Volodymyr) and @louphil (AKA Phil Gay)? Seems to be in the right place.
As for exFat I was using Rufus but after overcoming other issues ran into their issue this morning. So thanks for posting, I'll give it a try if the progress I was attempting by switching over to using a linux system to make the USB drive doesnt work.
I had started to think it was maybe because I was using a USB 3.0 Thumb drive as I recall having issues in the past with other distros but not sure if anyone else has any input on that?
Last edit: David Do 2020-05-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After using either a cp or dd command, even followed by a sync command and even unplug / replug the USB-stick, I don't have the same results than on your capture of GParted :
- no 1st partition, it's all the 16 Go USB-stick that seemed to be used by IO
- file system is "iso9660" instead of "unknown"
- no flags / can't change them
- no "unallocated" entry to make the 2nd partition for "persistence" data
Where did I go wrong?
Last edit: zebulon-1st 2021-10-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You've got to create a new partition table for the drive before copying files so then you need to create a partition that is large enough for the .iso while leaving enough unused space for your desired persistent disk space. So before you even mount the drive for copying, you need to make the separate partitions first. otherwise, you can try shrinking your current partition that has the OS and then create a new partition in the unallocated space if gparted lets you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You've got to create a new partition table for the drive before copying
files so then you need to create a partition that is large enough for the
.iso while leaving enough unused space for your desired persistent disk
space. So before you even mount the drive for copying, you need to make the
separate partitions first. otherwise, you can try shrinking your current
partition that has the OS and then create a new partition in the
unallocated space if gparted lets you.
Preparing an USB flash drive (with persistence)
(it's highly recommended to use a good quality pen)
* Method 1 (beginner, simple persistence):
When the copy has finished, create an ext4 partition in the free space of the drive with label: persistence
Finally, copy the persistence.conf in this partition and you're done... you can now reboot a enjoy the full persistence :o)
* Method 2 (advanced, encrypted persistence):
It consists of making an ext4 partition (4Go) in the beginning of the drive, extract the iso in it, install extlinux and make it bootable
In the free space, create an encrypted (LUKS) partition with label persistence that contains a persistence.conf file.
That's it... enjoy :)
Last edit: Manu Kebab 2016-07-16
Hi, for ease of usb creation on Windows, would you please send in a request to add this to their supported list? :
http://www.linuxliveusb.com/en/submit-a-linux
Also, as this is my first time really delving into linux, I do not have a linux, or the technical know-how to follow these steps in windows to create my own live persistent version. (I believe this requires... terminal?) Please help!
Hi, Thanks for your interest and link... I will send them a request. :)
Done ;)
Hi there! Desperately trying to make a working USB with Win10 to switch to the latest release of io.GNU... But all I get is
can not mount /dev/loop0
because of filesystem.squashfs
The file just seems doesn't fit FAT32 that can be obtained from Win software to make a bootable USB drive.
Any ideas?
Last edit: Volodymyr 2019-04-03
You can try to format it using extFat format?
Last edit: David Do 2020-05-22
Hi :) I'll upload another iso as soon as possible... I think it's a bug related to the iso file size
First considering the ISO I downloaded is OK ... But I encounter the same problem as Volodymyr .
The USB device is a 32Go SD card adapted on an USB stick ...
I firsts tried to flash directly to the SD card, with same results as Volodymyr : "(initsram) : no aufs found", then "can not mount /dev/loop0, etc ... " all with a command-line looking bootloader ....
Finally, after unsuccessfull tries on the USB stick adaptation, I could obtain the "splash" bootloader : but if trying to boot any one option seem to run correctly, the boot abort on a blank screen without any possible control ... Only an hard reset is efficient ...
But I'm in doubt the ISO is corrupted . I think your méthod to create Flash drive isn't detailed enought ... For example, I got different results if I format Vfat first or not, or ext4 ... The best result ( splash bootloader ) were obtained in erasing all partition table on the stick ... But Gparted don't reconize any partition table after flashing the stick . So I wasn't able to create a new "persistence" one ... Gparted only found errors GPT signature . Here is the message :
> /dev/sdc contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?
So how the USB device have to be formated, partitonned, etc, before flashing it ? Great thanks in advance : 2 days of big crisis ....
Last edit: phil gay 2019-06-06
if going from SD card to using a USB stick gave you a marginal increase in what could be seen, it may not be a filesystem issue with grub but that your BIOS is buggy and can't properly handle large drives ( http://tldp.org/HOWTO/Large-Disk-HOWTO-4.html ).
This translates into the BIOS being unable to read blocks past a certain point in the drive, and so if your root filesystem starts before that limit, but ends after that limit, then some files will be accessible at boot through the BIOS and others won't.
The standard way to work around this problem is to create a small /boot/ partition near the beginning of the drive, to ensure that everything that needs to be read through the BIOS, can be.
Regarding Gparted's error message, the fake msdos partition table refers to the MBR format, which could have been changed while you were erasiing the other partitions and not doing a complete flash. When formatting, make sure not to do a quick format and make sure whatever program you're using actually goes through the memory slots and changes each bit to 0 for a non-recoverable type of wipe.
I had this problem. Eventually realised it was the 4Gb limit on Fat32. Unetbootin doesn't know exfat. Ext4 worked eventually.
Hey Clivus, did ou get past all the mentioned issues with the latest 2019 (io-live--2019.01--full-k4.19.20-k4.19.20-rt12-amd64) version using Unetbootin? I've been having to using the 2017-03 version because I couldn't seem to get it to work.
Tried all the various noacpi acpi=none nvidia.modeset=0 nomodeset tricks one would normally do when using a later nvidia card but continue to run into the aforementioned issue of
(initsram) : no aufs found.Just wondering if you had no issues with the latest version as I wouldn't expect you to be able to help with the inistram issue
Side note: hitting 'exit' command would just eventuall lead to beig unable to mount aufs and filesystem.squashfs.
Last edit: David Do 2020-05-29
opps! That was for another thread. Doh!
You mean for posts from @nemyrnyi (Volodymyr) and @louphil (AKA Phil Gay)? Seems to be in the right place.
As for exFat I was using Rufus but after overcoming other issues ran into their issue this morning. So thanks for posting, I'll give it a try if the progress I was attempting by switching over to using a linux system to make the USB drive doesnt work.
I had started to think it was maybe because I was using a USB 3.0 Thumb drive as I recall having issues in the past with other distros but not sure if anyone else has any input on that?
Last edit: David Do 2020-05-23
After using either a
cporddcommand, even followed by asynccommand and even unplug / replug the USB-stick, I don't have the same results than on your capture of GParted :- no 1st partition, it's all the 16 Go USB-stick that seemed to be used by IO
- file system is "iso9660" instead of "unknown"
- no flags / can't change them
- no "unallocated" entry to make the 2nd partition for "persistence" data
Where did I go wrong?
Last edit: zebulon-1st 2021-10-10
You've got to create a new partition table for the drive before copying files so then you need to create a partition that is large enough for the .iso while leaving enough unused space for your desired persistent disk space. So before you even mount the drive for copying, you need to make the separate partitions first. otherwise, you can try shrinking your current partition that has the OS and then create a new partition in the unallocated space if gparted lets you.
Oh. Ok. I will do all of these when I will be back. I'm away for a few days.
Thanks for your help, anyway.
Le 14 oct. 2021 06:36, "David Do" defordo@users.sourceforge.net a écrit :