Today was my first go at Mageia's
Next I want to figure out how to have the Mageia
.iso on an SSD and its persistence (I guess in the form of a partition)
on SSD.
It can help if a manual process of the creation of persistence is described >> here.
I've just done it like this:
'Disks' in linux mint
Next I want to figure out how to have the Mageia
.iso on an SSD and its persistence (I guess in the form of a partition)
on SSD.
Next I want to figure out how to have the Mageia .iso on an SSD and
its persistence (I guess in the form of a partition) on SSD.
Use Diskdrake to create an ext4 partition.
Mike Easter wrote:
Next I want to figure out how to have the Mageia .iso on an SSD and
its persistence (I guess in the form of a partition) on SSD.
There's more in the Mag wiki than isodumper:
https://wiki.mageia.org/en/ Persistent_live_systems#Creating_persistence_using_only_Live_itself
Use Diskdrake to create an ext4 partition.
Just checked a usb using isodumper to create the persistence partition.
$ blkid /dev/sda*
/dev/sda: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00" LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda1: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00" LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MGAISO-ESP" LABEL="MGAISO-
ESP" UUID="05BF-07AA" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda3: LABEL="mgalive-persist" UUID="e7e1a551-2d0a-4c96- a240-895de60d6e88" BLOCK_SIZE="4096" TYPE="ext4"
Inside a running live system ...
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz lang= kbd= root=mgalive:LABEL=Mageia-9-Live- Plasma-x86_64 noiswmd audit=0 rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 vga=788 splash quiet noxconf xdriver=free
IIRC, the live system needs both the root=mgalive kernel parameter and
the partition with the
LABEL="mgalive-persist".
The ESP partition on sda2 is only used if booting in efi mode. If
booting in bios mode then it is
ignored.
I don't remember if the persistence partition must be on the same device
as it's being booted from.
Just checked a usb using isodumper to create the persistence partition.
$ blkid /dev/sda*
/dev/sda: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00" LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda1: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00" LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MGAISO-ESP" LABEL="MGAISO-
ESP" UUID="05BF-07AA" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda3: LABEL="mgalive-persist" UUID="e7e1a551-2d0a-4c96- a240-895de60d6e88" BLOCK_SIZE="4096" TYPE="ext4"
David W. Hodgins wrote:
Just checked a usb using isodumper to create the persistence partition.
$ blkid /dev/sda*
/dev/sda: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00"
LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda1: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00"
LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MGAISO-ESP" LABEL="MGAISO-
ESP" UUID="05BF-07AA" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda3: LABEL="mgalive-persist" UUID="e7e1a551-2d0a-4c96-
a240-895de60d6e88" BLOCK_SIZE="4096" TYPE="ext4"
This part is 'unconventional' (well, 'uncommon' at least) in terms of
the writing of an .iso to USB for booting live. I think I've mentioned
here before that if one uses such as Rufus to write the .iso (which
Rufus can do either hybrid or dd style write) Rufus 'complains' that
the .iso isn't going to work out in the Rufus default method, so Rufus
says that it is going to use dd, which of course works.
Rufus 'complains' that the .iso isn't going to work out in the
Rufus default method, so Rufus says that it is going to use dd,
which of course works.
The image you have selected is an ISOHybrid, but its creators have
not made it compatible with ISO/File copy mode. As a result, DD
image writing mode will be enforced.
Note: DD image mode enforced since this ISOHybrid is not ISO mode compatible.
Mike Easter wrote:
David W. Hodgins wrote:Maybe I should clarify; when I'm talking about uncommon, I'm not talking about the 'extras' that isodumper creates at sda2 & sda3; I'm talking
Just checked a usb using isodumper to create the persistence partition.
$ blkid /dev/sda*
/dev/sda: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00"
LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda1: BLOCK_SIZE="2048" UUID="2023-08-20-08-42-55-00"
LABEL="Mageia-9-Live-Plasma-x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MGAISO-ESP" LABEL="MGAISO-
ESP" UUID="05BF-07AA" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda3: LABEL="mgalive-persist" UUID="e7e1a551-2d0a-4c96-
a240-895de60d6e88" BLOCK_SIZE="4096" TYPE="ext4"
This part is 'unconventional' (well, 'uncommon' at least) in terms of
the writing of an .iso to USB for booting live. I think I've mentioned
here before that if one uses such as Rufus to write the .iso (which
Rufus can do either hybrid or dd style write) Rufus 'complains' that
the .iso isn't going to work out in the Rufus default method, so Rufus
says that it is going to use dd, which of course works.
about sda1 being uncommonly iso9660; in fact the device is considered
iso9660 at sda.
When/After Mag boots, it can see the mgalive-persist part, but for
whatever reason it isn't looking for it when it is booting, and so each
boot is 'brand new' for locale etc.
Ventoy was rejected for adding to Mageia
I realize that the wiki didn't 'include' using Ventoy booting and persistence, which is where I'm at.
I gradually came to accept that I wasn't going to be able to use EasyOS
as a Ventoy .iso, and give it its own usb.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 537 |
Nodes: | 16 (2 / 14) |
Uptime: | 136:38:59 |
Calls: | 10,249 |
Calls today: | 1 |
Files: | 13,980 |
Messages: | 6,407,364 |