From Newsgroup: alt.os.linux.mint

On 03/05/2026 11:20, Axel wrote:

Lawrence DrCOOliveiro wrote:

On Sun, 3 May 2026 14:00:45 +1000, Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the
NVME drive I can use on any disk to create a working drive.

Use rsync.

<https://manpages.debian.org/rsync(1)>

I don't want to use the terminal. I won't know what I'm doing

You could try Clonezilla, or ask Windows users to provide an Acronis or Macrium ISO. These ISOs can be booted with Ventoy, and both Acronis and Macrium will allow you to create an exact replica of your hard disk.


--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On 5/3/26 12:21 PM, Axel wrote:

german newsgroups wrote:

Le 03/05/2026 |a 06:00, Axel a |-crit-a:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the
NVME drive I can use on any disk to create a working drive. I tried
the Disks app, and discovered it doesn't compress the image, and
since the image created is a bit over 500 Gb, I can only write it to
a drive larger than 500Gb. (sigh) I think the problem is that the
NVME drive is actually a fraction over 500Gb, since if I try to clone
it to a 500Gb drive I get a message that the receptor drive is too
small. I was told I can reduce the partition on the NVME drive to
make a smaller image, but I'm afraid to do that in case I lose data.
I will try Rescuezilla, but if that doesn't compress the image
there's no gain from that. Does anyone have any better suggestions
for what I can do? thanks to all. :)

why this image ?

when you install...the time stamps is correct ! the time stamps
software install too !

so, after what we need ? a skeleton about yours folder with the config
files ? yes, the name user is not the sometimes...

what is your feel ?

Je ne comprends pas votre anglais

Ignore this idiot.
Clonezilla will work fine for you.
--
Once an organization gains any influence, it will be corrupted from both within and without.

Edmund
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 5/3/2026 12:44 PM, Mike Easter wrote:

George wrote:

You could try Clonezilla, or ask Windows users to provide an Acronis or
Macrium ISO. These ISOs can be booted with Ventoy, and both Acronis and
Macrium will allow you to create an exact replica of your hard disk.

Hiren's PE (the W11 one) has Macrium Reflect v7.3.5925 which isn't quite as new as the one at Macrium which free trial has limitations.

Also some older Hiren's have old Acronis.

Those Hiren's .iso/s do fine w/ Ventoy.-a I used to keep a USB Ventoy stick w/ the Hiren's from Win XP to W10 & W11.-a The XP Hiren's also has linux tools.

Macrium works for things like the following.

FAT32 NTFS ExFAT EXTn <=== done via a smart copy (similar to partclone smart copy)

SWAP <=== done via a "dd" run

Microsoft-Reserved <=== a small partition with NoFS, gets done via a "dd" run (Gparted won't touch this)

BTRFS... <=== Anything that is not recognized, gets the "dd" treatment, not efficient.

That means a wide range of other Linux filesystems,
might well receive the "dd" treatment per partition,
which is not particularly efficient if the partition
is only partially full. If you were BTRFS, then that
would not be a candidate for Macrium at least.

The Macrium staff are not oblivious to Linux, as at
one time, the Macrium Rescue CD was Linux based. And somehow
Microsoft convinced them to take the WinPE path (even though
that takes quite a bit more downloads).

If your workflow uses EXT3 or EXT4 and nothing else,
then you can work your project through Macrium Rescue CD
(for both Backup and Restore of a disk image). This would
be suited to disaster recovery applications.

There is a Windows application "img2vhd.exe" provided with
earlier versions of the software, that works with later
versions of backup images (Full Images at least). The application
itself is no longer supported, or available in Macrium 8+ .This
allows converting the MRIMG proprietary format, into
a VHD, and from there, various other converters can
convert to other containers as you wish. This is an alternative
path if you aren't running Windows and using the MRIMG mounter
that Windows has. You could for example, run img2vhd.exe under
WINE and do conversions as needed. It's just an alternative
path for acquiring single-file copy/paste.

Since it involved a VHD container, that workflow cannot handle
items bigger than 2.2TB. It's a fine workflow for a person with
a 512GB NVMe drive as the source of the backups. Not a good
workflow for a Linux user with a 24TB boot drive...

While Rescuezilla 2.6.1 Oracular Image.Explorer is not working,
maybe at some point it will get fixed. It's not clear where this
Image Explorer code is coming from. It appears to be a mounter
of some sort, it seems intent on ingesting a Partclone file,
but it is not working at the moment. Whoever wrote that code
or forked it, it's likely to be a bit on the raw side. Maybe
AndyMH knows more about the status of such things. It could
be that the /dev/nbd device in the kernel, is the part
that is actually at fault. But I cannot be sure about that.

No tool, seems to be unambigiously capable of restoring a
1TB NVMe to a 512GB NVMe at the moment. (Clonezilla has some
parameters you can add, but while the backup runs to completion,
there is something still wrong with the restore to the smaller item.)
While there is a special condition a person could use, to make it
possible to do such restorations, the requirements on partition
size are absurd, and nobody is going to configure their
tres-expensive hardware device in such a manner. And you still have
to do backup/restore testing, to verify this even works on the
tools you test this on (Clonezilla, Foxclone, maybe not RescueZilla).

I just checked the prices of local NVMe drives here, and it's
unlikely anyone in the audience can afford one anyway. So if your NVMe is dying, you're looking an an Ebay HDD as a replacement <whimper>.
You can't buy 1TB and 2TB HDD at my computer store, they
don't exist. Occasionally, 8TB or 10TB drives show up,
at inflated prices. This week is hardly the right week
to be having a hardware failure. Whatever crap you've collected
to date, that's what you've got to work with, basically.
Nobody else can bail you out.

One thing that is interesting, is the most expensive NVMe you could
consider buying, is missing from my computer store listing. The
staff then, can "sense" the audience for extravagantly expensive
storage is "strictly limited" and not worth wasting the time of
day on. My computer store allows you to "special order" items, which is
basic drop-shipping in action, but they couldn't even be bothered
to do that, suggesting there isn't even a supply of the item to be had.

As a result of these observations, if you're restoring your NVMe,
there's a good chance there is a (larger) HDD in your future. It will be
the "cheaper, if I can find one" option. I have plenty of HDD here,
but they're slow and not exactly my go-to solution for a boot drive.
That would be a special kind of torture, to be replacing a flash device
with something like that.

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the NVME
drive I can use on any disk to create a working drive. I tried the
Disks app, and discovered it doesn't compress the image, and since the
image created is a bit over 500 Gb, I can only write it to a drive
larger than 500Gb. (sigh) I think the problem is that the NVME drive
is actually a fraction over 500Gb, since if I try to clone it to a
500Gb drive I get a message that the receptor drive is too small. I
was told I can reduce the partition on the NVME drive to make a
smaller image, but I'm afraid to do that in case I lose data. I will
try Rescuezilla, but if that doesn't compress the image there's no
gain from that. Does anyone have any better suggestions for what I can
do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I
have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows
there are no files in the main partition:
https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???
--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On 2026-05-03, Axel <none@not.here> wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness.

To be correct the image neds to be written to the same size or larger disk/partition, and yes down to the byte.

I want an image of the NVME
drive I can use on any disk to create a working drive.

If you accept the size limitation then you will get a working drive after
the copy is done.

Bork your HD and you can install the backup image and be away right from the reboot after the copy.

You need to understand the tool(s). It is some what frustrating the the copy partition/disk needs to be larger(or the exact size) than the backup.

I tried the Disks
app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce
the partition on the NVME drive to make a smaller image, but I'm afraid
to do that in case I lose data.

Well, have about you do an image backup of the disk before you try reducing
the NVMe partition? then if you lose data all you need to do is to restore
the NVMe partition from the backup and try again.

Just keep in mind that a partion is not the whole disk in some cases.

I will try Rescuezilla, but if that
doesn't compress the image there's no gain from that. Does anyone have
any better suggestions for what I can do? thanks to all. :)

Clonezilla, and others use partclone as the engine.

Regarding compression. Clonezilla does not copy the unused space on the orginal, it then compresses the copied parts. The issue is that clonezilla *demands* that it needs a space as large as the orginal to copy it back to.

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the
NVME drive I can use on any disk to create a working drive. I tried
the Disks app, and discovered it doesn't compress the image, and
since the image created is a bit over 500 Gb, I can only write it to
a drive larger than 500Gb. (sigh) I think the problem is that the
NVME drive is actually a fraction over 500Gb, since if I try to clone
it to a 500Gb drive I get a message that the receptor drive is too
small. I was told I can reduce the partition on the NVME drive to
make a smaller image, but I'm afraid to do that in case I lose data.
I will try Rescuezilla, but if that doesn't compress the image
there's no gain from that. Does anyone have any better suggestions
for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what
I have done. successfully created an image of the NVME using
rescuezilla. successfully wrote that to a 500Gb SSD, but it won't
boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps? https://auslink.info/linux/image.png
--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 5/3/2026 7:59 PM, Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I found that the image can only be written back to the original drive, which pretty much negates it's usefulness. I want an image of the NVME drive I can use on any disk to create a working drive. I tried the Disks app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce the partition on the NVME drive to make a smaller image, but I'm afraid to do that in case I lose data. I will try Rescuezilla, but if that doesn't compress the image there's no gain from that. Does anyone have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

Directory: 2026-05-03-1942-img-rescuezilla # This is a backup of a 200GB LLM223 UEFI/GPT install
# sda1 = ESP, sda2 = main ext4, sda3 = swap

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- Sun, 5, 3, 2026 3:43 PM 233 blkdev.list
-a---- Sun, 5, 3, 2026 3:43 PM 632 blkid.list
-a---- Sun, 5, 3, 2026 3:45 PM 51220 clonezilla-img
-a---- Sun, 5, 3, 2026 3:43 PM 198 dev-fs.list
-a---- Sun, 5, 3, 2026 3:43 PM 4 disk
-a---- Sun, 5, 3, 2026 3:43 PM 1894 Info-dmi.txt
-a---- Sun, 5, 3, 2026 3:45 PM 235 Info-img-id.txt
-a---- Sun, 5, 3, 2026 3:43 PM 14682 Info-lshw.txt
-a---- Sun, 5, 3, 2026 3:43 PM 1288 Info-lspci.txt
-a---- Sun, 5, 3, 2026 3:43 PM 912 Info-OS-prober.txt
-a---- Sun, 5, 3, 2026 3:43 PM 182 Info-packages.txt
-a---- Sun, 5, 3, 2026 3:43 PM 868 Info-smart.txt
-a---- Sun, 5, 3, 2026 3:43 PM 11 parts
-a---- Sun, 5, 3, 2026 3:43 PM 37 sda-chs.sf
-a---- Sun, 5, 3, 2026 3:43 PM 17408 sda-gpt-1st
-a---- Sun, 5, 3, 2026 3:43 PM 16384 sda-gpt-2nd
-a---- Sun, 5, 3, 2026 3:43 PM 17920 sda-gpt.gdisk
-a---- Sun, 5, 3, 2026 3:43 PM 676 sda-gpt.sgdisk
-a---- Sun, 5, 3, 2026 3:43 PM 512 sda-mbr
-a---- Sun, 5, 3, 2026 3:43 PM 392 sda-pt.parted
-a---- Sun, 5, 3, 2026 3:43 PM 351 sda-pt.parted.compact
-a---- Sun, 5, 3, 2026 3:43 PM 549 sda-pt.sf
-a---- Sun, 5, 3, 2026 3:43 PM 7118216 sda1.vfat-ptcl-img.uncomp.aa -a---- Sun, 5, 3, 2026 3:44 PM 4000000000 sda2.ext4-ptcl-img.uncomp.aa -a---- Sun, 5, 3, 2026 3:44 PM 4000000000 sda2.ext4-ptcl-img.uncomp.ab -a---- Sun, 5, 3, 2026 3:44 PM 762122082 sda2.ext4-ptcl-img.uncomp.ac -a---- Sun, 5, 3, 2026 3:45 PM 53 swappt-sda3.info

The swap info file says:

UUID="d87e9ab3-7db2-4bfd-87ae-016f1a3fd208"
LABEL=""

so no space is used backing up swap.

Does your backup resemble that ? The sda2.ext4-ptcl files are PartClone files so
only the used portion of the partition is stored in there. I specifically turned
off compression, as I was expecting to be able to use Image Explorer.

*******

For any data-full partitions, you can use the fsarchiver program to back
up the partitions. If RescueZilla seems incapable of populating your main partition properly, you can overwrite your main partition with an fsarchiver run.

I was hoping to build my own backup solution, if I could find a "skeletal" backup function
for the non-partition parts. The sda-mbr file, the sda-gpt-1st and sda-gpt-2nd files, are
items to be restored via "dd". Booting is via sda1.vfat-ptcl (which is the ESP partition).
Those would all be examples of skeletal bits. Macrium would have backed up my SWAP
as a 2GB "dd" file, whereas RescueZilla just creates a new SWAP using the appropriate
GPT GUID-type for the job. And maybe a mkswap for the filesystem part.

If the main partition part does not work, you can attempt to use fsarchiver in its
place (to fill the partition manually after RescueZilla is "finished").

At this point, it's all experiments. The RescueZilla really should have worked.

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Gordon wrote:

On 2026-05-03, Axel <none@not.here> wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness.

To be correct the image needs to be written to the same size or larger disk/partition, and yes down to the byte.

Ok

I want an image of the NVME
drive I can use on any disk to create a working drive.

If you accept the size limitation then you will get a working drive after
the copy is done.

Bork your HD and you can install the backup image and be away right from the reboot after the copy.

You need to understand the tool(s). It is somewhat frustrating the the copy partition/disk needs to be larger(or the exact size) than the backup.

I will use Rescuezilla in future

I tried the Disks
app, and discovered it doesn't compress the image, and since the image
created is a bit over 500 Gb, I can only write it to a drive larger than
500Gb. (sigh) I think the problem is that the NVME drive is actually a
fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a
message that the receptor drive is too small. I was told I can reduce
the partition on the NVME drive to make a smaller image, but I'm afraid
to do that in case I lose data.

Well, have about you do an image backup of the disk before you try reducing the NVMe partition? then if you lose data all you need to do is to restore the NVMe partition from the backup and try again.

yes, good idea

Just keep in mind that a partion is not the whole disk in some cases.

I will try Rescuezilla, but if that
doesn't compress the image there's no gain from that. Does anyone have
any better suggestions for what I can do? thanks to all. :)

Clonezilla, and others use partclone as the engine.

Regarding compression. Clonezilla does not copy the unused space on the orginal, it then compresses the copied parts. The issue is that clonezilla *demands* that it needs a space as large as the orginal to copy it back to.

Ok
--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Axel wrote:

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the
NVME drive I can use on any disk to create a working drive. I tried
the Disks app, and discovered it doesn't compress the image, and
since the image created is a bit over 500 Gb, I can only write it to
a drive larger than 500Gb. (sigh) I think the problem is that the
NVME drive is actually a fraction over 500Gb, since if I try to
clone it to a 500Gb drive I get a message that the receptor drive is
too small. I was told I can reduce the partition on the NVME drive
to make a smaller image, but I'm afraid to do that in case I lose
data. I will try Rescuezilla, but if that doesn't compress the image
there's no gain from that. Does anyone have any better suggestions
for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is
what I have done. successfully created an image of the NVME using
rescuezilla. successfully wrote that to a 500Gb SSD, but it won't
boot. Disks shows there are no files in the main partition:
https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps? https://auslink.info/linux/image.png

solved! I mounted the 'empty' partition using Disks and the files are
all there https://auslink.info/linux/mounted.png, so I tried the disk in
a different PC, and it works perfectly. issue was the first PC I tried
was using legacy bios. thanks everyone,
--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Paul wrote:

On Sun, 5/3/2026 7:59 PM, Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I found that the image can only be written back to the original drive, which pretty much negates it's usefulness. I want an image of the NVME drive I can use on any disk to create a working drive. I tried the Disks app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce the partition on the NVME drive to make a smaller image, but I'm afraid to do that in case I lose data. I will try Rescuezilla, but if that doesn't compress the image there's no gain from that. Does anyone have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

Directory: 2026-05-03-1942-img-rescuezilla # This is a backup of a 200GB LLM223 UEFI/GPT install
# sda1 = ESP, sda2 = main ext4, sda3 = swap

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- Sun, 5, 3, 2026 3:43 PM 233 blkdev.list
-a---- Sun, 5, 3, 2026 3:43 PM 632 blkid.list
-a---- Sun, 5, 3, 2026 3:45 PM 51220 clonezilla-img
-a---- Sun, 5, 3, 2026 3:43 PM 198 dev-fs.list
-a---- Sun, 5, 3, 2026 3:43 PM 4 disk
-a---- Sun, 5, 3, 2026 3:43 PM 1894 Info-dmi.txt
-a---- Sun, 5, 3, 2026 3:45 PM 235 Info-img-id.txt
-a---- Sun, 5, 3, 2026 3:43 PM 14682 Info-lshw.txt
-a---- Sun, 5, 3, 2026 3:43 PM 1288 Info-lspci.txt
-a---- Sun, 5, 3, 2026 3:43 PM 912 Info-OS-prober.txt
-a---- Sun, 5, 3, 2026 3:43 PM 182 Info-packages.txt
-a---- Sun, 5, 3, 2026 3:43 PM 868 Info-smart.txt
-a---- Sun, 5, 3, 2026 3:43 PM 11 parts
-a---- Sun, 5, 3, 2026 3:43 PM 37 sda-chs.sf
-a---- Sun, 5, 3, 2026 3:43 PM 17408 sda-gpt-1st
-a---- Sun, 5, 3, 2026 3:43 PM 16384 sda-gpt-2nd
-a---- Sun, 5, 3, 2026 3:43 PM 17920 sda-gpt.gdisk
-a---- Sun, 5, 3, 2026 3:43 PM 676 sda-gpt.sgdisk
-a---- Sun, 5, 3, 2026 3:43 PM 512 sda-mbr
-a---- Sun, 5, 3, 2026 3:43 PM 392 sda-pt.parted
-a---- Sun, 5, 3, 2026 3:43 PM 351 sda-pt.parted.compact -a---- Sun, 5, 3, 2026 3:43 PM 549 sda-pt.sf
-a---- Sun, 5, 3, 2026 3:43 PM 7118216 sda1.vfat-ptcl-img.uncomp.aa
-a---- Sun, 5, 3, 2026 3:44 PM 4000000000 sda2.ext4-ptcl-img.uncomp.aa
-a---- Sun, 5, 3, 2026 3:44 PM 4000000000 sda2.ext4-ptcl-img.uncomp.ab
-a---- Sun, 5, 3, 2026 3:44 PM 762122082 sda2.ext4-ptcl-img.uncomp.ac
-a---- Sun, 5, 3, 2026 3:45 PM 53 swappt-sda3.info

The swap info file says:

UUID="d87e9ab3-7db2-4bfd-87ae-016f1a3fd208"
LABEL=""

so no space is used backing up swap.

Does your backup resemble that ? The sda2.ext4-ptcl files are PartClone files so
only the used portion of the partition is stored in there. I specifically turned
off compression, as I was expecting to be able to use Image Explorer.

*******

For any data-full partitions, you can use the fsarchiver program to back
up the partitions. If RescueZilla seems incapable of populating your main partition properly, you can overwrite your main partition with an fsarchiver run.

I was hoping to build my own backup solution, if I could find a "skeletal" backup function
for the non-partition parts. The sda-mbr file, the sda-gpt-1st and sda-gpt-2nd files, are
items to be restored via "dd". Booting is via sda1.vfat-ptcl (which is the ESP partition).
Those would all be examples of skeletal bits. Macrium would have backed up my SWAP
as a 2GB "dd" file, whereas RescueZilla just creates a new SWAP using the appropriate
GPT GUID-type for the job. And maybe a mkswap for the filesystem part.

If the main partition part does not work, you can attempt to use fsarchiver in its
place (to fill the partition manually after RescueZilla is "finished").

At this point, it's all experiments. The RescueZilla really should have worked.

it did. I was copying the LM disk from a machine with UEFI bios, and
trying to use the copy in a PC with legacy bios. so booting was the
problem. (see my latest post)

Paul

--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 5/3/2026 9:37 PM, Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I found that the image can only be written back to the original drive, which pretty much negates it's usefulness. I want an image of the NVME drive I can use on any disk to create a working drive. I tried the Disks app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce the partition on the NVME drive to make a smaller image, but I'm afraid to do that in case I lose data. I will try Rescuezilla, but if that doesn't compress the image there's no gain from that. Does anyone have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps? https://auslink.info/linux/image.png

solved! I mounted the 'empty' partition using Disks and the files are all there https://auslink.info/linux/mounted.png, so I tried the disk in a different PC, and it works perfectly. issue was the first PC I tried was using legacy bios. thanks everyone,

One thing to be aware of, is the GUID of the two EXT4 partitions are the same. This could cause problems with attempting to mount the item. I don't
know if I've ever tested that (what happens when the two partitions
are exactly the same, being on the machine at the same time).

A legacy BIOS would certainly cause no end of problems, such as having
no NVMe driver. But then, you would be less likely to have a slot
for the NVMe drive to plug into.

Another weirdness I notice, is the CT500BX500SSD1 has the same "title string" on its ESP partition, as the Team Group drive is using. Is that title
string the actual volume name of the ESP ? If the volumes in GRUB are identified by the GUID, there could be a wee bit of confusion there too.
I've had trouble in the past, just with two Windows Boot Managers interacting, and selecting one thing and "something else boots". I haven't seen one of
those incidents in some time. It tends to happen when I have two identical brand and size drives, like two WD Black 1TB in the machine at the same time, one on Port 2, the other on Port 4. And the content on the drives, consisted
of separate installs and no copying involved.

But at least you're finally seeing a backup and restore that seems to have worked.
You're now the expert on backup and restore :-)

Paul

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 5/3/2026 8:45 PM, Gordon wrote:

On 2026-05-03, Axel <none@not.here> wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness.

To be correct the image neds to be written to the same size or larger disk/partition, and yes down to the byte.

I want an image of the NVME
drive I can use on any disk to create a working drive.

If you accept the size limitation then you will get a working drive after
the copy is done.

Bork your HD and you can install the backup image and be away right from the reboot after the copy.

You need to understand the tool(s). It is some what frustrating the the copy partition/disk needs to be larger(or the exact size) than the backup.

I tried the Disks
app, and discovered it doesn't compress the image, and since the image
created is a bit over 500 Gb, I can only write it to a drive larger than
500Gb. (sigh) I think the problem is that the NVME drive is actually a
fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a
message that the receptor drive is too small. I was told I can reduce
the partition on the NVME drive to make a smaller image, but I'm afraid
to do that in case I lose data.

Well, have about you do an image backup of the disk before you try reducing the NVMe partition? then if you lose data all you need to do is to restore the NVMe partition from the backup and try again.

Just keep in mind that a partion is not the whole disk in some cases.

I will try Rescuezilla, but if that
doesn't compress the image there's no gain from that. Does anyone have
any better suggestions for what I can do? thanks to all. :)

Clonezilla, and others use partclone as the engine.

Regarding compression. Clonezilla does not copy the unused space on the orginal, it then compresses the copied parts. The issue is that clonezilla *demands* that it needs a space as large as the orginal to copy it back to.

Clonezilla actually has an option to support restore to a smaller partition.
In one thread, someone claimed to have got that to work, but they did
not elaborate, which is a bit suspicious. I don't know what these switches
do right off hand. The Clonezilla mechanism of summarizing the command it
is about to launch, is a great way to capture stuff like this, if the operator has an opportunity to do so. This is the reference to some part of this.

"Why does not Clonezilla respect the -icds setting and does not run
Partclone with the -C switch?
"

But if something is that twitchy, it's going to take a bit of test to be "comfortable" with using it.

*******

And this is cool. This describes part of what Image Explorer on RescueZilla
is (attempting) to do. (Image Explorer is an icon on the main control panel)

https://blog.hiebl.cc/qa/create-mount-restore-partclone-images/

"Requirements

partclone (pacman): for backup and restore
partclone-utils (AUR): for mounting the image for reading files
"

"Mounting a partclone Image

The imagemount binary in the partclone-utils uses the network block devices API to
provide access to the backups through a standard filesystem interface. This is done
transparently, no further nbd utilities are required.

First we load the network block devices driver to create the devices
/dev/nbd0, /dev/nbd1, rCa, which imagemount needs in order to mount the backup.

sudo modprobe nbd

Next, mount the actual image.

sudo imagemount\
-v 3\ # verbosity level 3
-d /dev/nbd0\ # use the first network block device
-f ./rootfs.pcl\ # our backup image
-t ext4\ # our image contains a ext4 filesystem
-m /media/imagemount\ # mount it here
-D\ # do not daemonize, keep in foreground
-r # mount read only (write does not work anyways)

Now the filesystem contained in the backup should be accessible at the specified
mountpoint as long as the imagemount process is active. To unmount the filesystem,
simply terminate the [imagemount] process.
"

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 3 May 2026 10:12:17 -0700, Mike Easter wrote:

And bravo to Cherie DeVaux; first woman trainer to win the Kentucky
Derby.

Cherie didn't just fall off the training turnip truck; she spent 14 y
working for other trainers and has had her own training biz for 8 more.

Congrats to her. Her vagina makes it more special than a man winning it,
for sure. Her winning is still not as good as a black person winning the
Kentucky Derby though, or a handicapped person.

Sadly, there are many handicapped or even paralyzed people that could
actually win the Derby if just given a chance and strapped onto a horse.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Edmund wrote:

On 5/3/26 12:21 PM, Axel wrote:

german newsgroups wrote:

Le 03/05/2026 |a 06:00, Axel a |-crit-a:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but
I found that the image can only be written back to the original
drive, which pretty much negates it's usefulness. I want an image
of the NVME drive I can use on any disk to create a working drive.
I tried the Disks app, and discovered it doesn't compress the
image, and since the image created is a bit over 500 Gb, I can only
write it to a drive larger than 500Gb. (sigh) I think the problem
is that the NVME drive is actually a fraction over 500Gb, since if
I try to clone it to a 500Gb drive I get a message that the
receptor drive is too small. I was told I can reduce the partition
on the NVME drive to make a smaller image, but I'm afraid to do
that in case I lose data. I will try Rescuezilla, but if that
doesn't compress the image there's no gain from that. Does anyone
have any better suggestions for what I can do? thanks to all. :)

why this image ?

when you install...the time stamps is correct ! the time stamps
software install too !

so, after what we need ? a skeleton about yours folder with the
config files ? yes, the name user is not the sometimes...

what is your feel ?

Je ne comprends pas votre anglais

Ignore this idiot.

sound advice

Clonezilla will work fine for you.

It did!
--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Mon, 4 May 2026 00:04:49 -0400, Paul wrote:

One thing to be aware of, is the GUID of the two EXT4 partitions are
the same. This could cause problems with attempting to mount the
item.

Yet another reason to avoid rCLimagerCY backups.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but
I found that the image can only be written back to the original
drive, which pretty much negates it's usefulness. I want an image
of the NVME drive I can use on any disk to create a working drive.
I tried the Disks app, and discovered it doesn't compress the
image, and since the image created is a bit over 500 Gb, I can only
write it to a drive larger than 500Gb. (sigh) I think the problem
is that the NVME drive is actually a fraction over 500Gb, since if
I try to clone it to a 500Gb drive I get a message that the
receptor drive is too small. I was told I can reduce the partition
on the NVME drive to make a smaller image, but I'm afraid to do
that in case I lose data. I will try Rescuezilla, but if that
doesn't compress the image there's no gain from that. Does anyone
have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is
what I have done. successfully created an image of the NVME using
rescuezilla. successfully wrote that to a 500Gb SSD, but it won't
boot. Disks shows there are no files in the main partition:
https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps?
https://auslink.info/linux/image.png

solved! I mounted the 'empty' partition using Disks and the files are
all there https://auslink.info/linux/mounted.png, so I tried the disk
in a different PC, and it works perfectly. issue was the first PC I
tried was using legacy bios. thanks everyone,

I still have a problem. :( The PC I want to use the copy drive in has
only legacy bios. is there anyway I can make this disk boot in that PC? thanks,
--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Le 03/05/2026 |a 16:18, Edmund a |-crit-a:

On 5/3/26 12:21 PM, Axel wrote:

german newsgroups wrote:

Le 03/05/2026 |a 06:00, Axel a |-crit-a:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the
NVME drive I can use on any disk to create a working drive. I tried
the Disks app, and discovered it doesn't compress the image, and
since the image created is a bit over 500 Gb, I can only write it to
a drive larger than 500Gb. (sigh) I think the problem is that the
NVME drive is actually a fraction over 500Gb, since if I try to
clone it to a 500Gb drive I get a message that the receptor drive is
too small. I was told I can reduce the partition on the NVME drive
to make a smaller image, but I'm afraid to do that in case I lose
data. I will try Rescuezilla, but if that doesn't compress the image
there's no gain from that. Does anyone have any better suggestions
for what I can do? thanks to all. :)

why this image ?

when you install...the time stamps is correct ! the time stamps
software install too !

so, after what we need ? a skeleton about yours folder with the
config files ? yes, the name user is not the sometimes...

what is your feel ?

Je ne comprends pas votre anglais

Ignore this idiot.
Clonezilla will work fine for you.

why idiot ? you are bipolaire we know it !
--
Amicalement,

Frenchy Friendly, & French touch !

german
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Le 03/05/2026 |a 12:21, Axel a |-crit-a:

german newsgroups wrote:

Le 03/05/2026 |a 06:00, Axel a |-crit-a:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I
found that the image can only be written back to the original drive,
which pretty much negates it's usefulness. I want an image of the
NVME drive I can use on any disk to create a working drive. I tried
the Disks app, and discovered it doesn't compress the image, and
since the image created is a bit over 500 Gb, I can only write it to
a drive larger than 500Gb. (sigh) I think the problem is that the
NVME drive is actually a fraction over 500Gb, since if I try to clone
it to a 500Gb drive I get a message that the receptor drive is too
small. I was told I can reduce the partition on the NVME drive to
make a smaller image, but I'm afraid to do that in case I lose data.
I will try Rescuezilla, but if that doesn't compress the image
there's no gain from that. Does anyone have any better suggestions
for what I can do? thanks to all. :)

why this image ?

when you install...the time stamps is correct ! the time stamps
software install too !

so, after what we need ? a skeleton about yours folder with the config
files ? yes, the name user is not the sometimes...

what is your feel ?

Je ne comprends pas votre anglais

c'est pas grave tout le monde comprend ton sac |a merdes.
--
Amicalement,

Frenchy Friendly, & French touch !

german
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Paul wrote:

On Sun, 5/3/2026 9:37 PM, Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I found that the image can only be written back to the original drive, which pretty much negates it's usefulness. I want an image of the NVME drive I can use on any disk to create a working drive. I tried the Disks app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce the partition on the NVME drive to make a smaller image, but I'm afraid to do that in case I lose data. I will try Rescuezilla, but if that doesn't compress the image there's no gain from that. Does anyone have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps? https://auslink.info/linux/image.png

solved! I mounted the 'empty' partition using Disks and the files are all there https://auslink.info/linux/mounted.png, so I tried the disk in a different PC, and it works perfectly. issue was the first PC I tried was using legacy bios. thanks everyone,

One thing to be aware of, is the GUID of the two EXT4 partitions the same.

yes

This could cause problems with attempting to mount the item. I don't
know if I've ever tested that (what happens when the two partitions
are exactly the same, being on the machine at the same time).

A legacy BIOS would certainly cause no end of problems, such as having
no NVMe driver. But then, you would be less likely to have a slot
for the NVMe drive to plug into.

Another weirdness I notice, is the CT500BX500SSD1 has the same "title string" on its ESP partition, as the Team Group drive is using.

because it's a copy of it?

Is that title
string the actual volume name of the ESP ?

yes. they both have UUID COBC-1FD9

If the volumes in GRUB are
identified by the GUID, there could be a wee bit of confusion there too.

the copy drive would only be connected to the nvme machine via USB, if ever

I've had trouble in the past, just with two Windows Boot Managers interacting,
and selecting one thing and "something else boots". I haven't seen one of those incidents in some time. It tends to happen when I have two identical brand and size drives, like two WD Black 1TB in the machine at the same time, one on Port 2, the other on Port 4. And the content on the drives, consisted of separate installs and no copying involved.

But at least you're finally seeing a backup and restore that seems to have worked.
You're now the expert on backup and restore :-)

I wish

Paul

--
Linux Mint 22.3

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Mon, 5/4/2026 4:06 AM, Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I found that the image can only be written back to the original drive, which pretty much negates it's usefulness. I want an image of the NVME drive I can use on any disk to create a working drive. I tried the Disks app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce the partition on the NVME drive to make a smaller image, but I'm afraid to do that in case I lose data. I will try Rescuezilla, but if that doesn't compress the image there's no gain from that. Does anyone have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps? https://auslink.info/linux/image.png

solved! I mounted the 'empty' partition using Disks and the files are all there https://auslink.info/linux/mounted.png, so I tried the disk in a different PC, and it works perfectly. issue was the first PC I tried was using legacy bios. thanks everyone,

I still have a problem. :( The PC I want to use the copy drive in has only legacy bios. is there anyway I can make this disk boot in that PC? thanks,

Wouldn't that require a BIOS boot partition, plus the Boot Repair DVD ?

The BIOS boot partition, I think that's part of getting a legacy BIOS
to boot a GPT disk. And it does not necessarily work with all legacy machines (my year 2000 machine is pretty cranky).

https://sourceforge.net/projects/boot-repair-cd/files/

boot-repair-disk-64bit.iso 2023-12-23 2.6 GB

if your machine is old enough, it might have a 32-bit only CPU in it.
And that DVD is 64-bit materials.

The DVD response style varies.

It can do Boot Repair all by itself, without you having to use the Terminal.

In "tough" cases, it gives Terminal commands to use (it makes you chroot in
for example).

In any case, it should give some indication what kind of repair is required.
As a lazy person, that DVD is in my "pile of current DVDs", just because
it gets enough occasional usage to stay in that pile. It's for Debian/Ubuntu/LinuxMint/Zoran, but for some reason does not seem
to work with Fedora.

I think you could make a GPT BIOS Boot partition in

sudo gdisk /dev/sda

as gdisk has a list of partition types, and one of the
partition types it would have, is the BIOS Boot type. it
has a specific GUID that must be applied. The GPT partition
table has room for 128 entries, so you won't run out of
partitions to create (not like the four primary partition
limit on an MSDOS disk).

I think I had to do one of these once, and it worked OK.

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Le 04/05/2026 |a 10:30, Axel a |-crit-a:

Edmund wrote:

On 5/3/26 12:21 PM, Axel wrote:

german newsgroups wrote:

Le 03/05/2026 |a 06:00, Axel a |-crit-a:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but
I found that the image can only be written back to the original
drive, which pretty much negates it's usefulness. I want an image
of the NVME drive I can use on any disk to create a working drive.
I tried the Disks app, and discovered it doesn't compress the
image, and since the image created is a bit over 500 Gb, I can only >>>>> write it to a drive larger than 500Gb. (sigh) I think the problem
is that the NVME drive is actually a fraction over 500Gb, since if
I try to clone it to a 500Gb drive I get a message that the
receptor drive is too small. I was told I can reduce the partition
on the NVME drive to make a smaller image, but I'm afraid to do
that in case I lose data. I will try Rescuezilla, but if that
doesn't compress the image there's no gain from that. Does anyone
have any better suggestions for what I can do? thanks to all. :)

why this image ?

when you install...the time stamps is correct ! the time stamps
software install too !

so, after what we need ? a skeleton about yours folder with the
config files ? yes, the name user is not the sometimes...

what is your feel ?

Je ne comprends pas votre anglais

Ignore this idiot.

sound advice

Clonezilla will work fine for you.

It did!

it's fun the politic.
--
Amicalement,

Frenchy Friendly, & French touch !

german
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Mon, 5/4/2026 4:06 AM, Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

Axel wrote:

I want a full back up of my 500Gb NVME disk. I tried Foxclone, but I found that the image can only be written back to the original drive, which pretty much negates it's usefulness. I want an image of the NVME drive I can use on any disk to create a working drive. I tried the Disks app, and discovered it doesn't compress the image, and since the image created is a bit over 500 Gb, I can only write it to a drive larger than 500Gb. (sigh) I think the problem is that the NVME drive is actually a fraction over 500Gb, since if I try to clone it to a 500Gb drive I get a message that the receptor drive is too small. I was told I can reduce the partition on the NVME drive to make a smaller image, but I'm afraid to do that in case I lose data. I will try Rescuezilla, but if that doesn't compress the image there's no gain from that. Does anyone have any better suggestions for what I can do? thanks to all. :)

thanks for all replies, I will investigate them. for now, this is what I have done. successfully created an image of the NVME using rescuezilla. successfully wrote that to a 500Gb SSD, but it won't boot. Disks shows there are no files in the main partition: https://auslink.info/linux/copy.png
this is the nvme i copied from: https://auslink.info/linux/nvme.png
???

p.s. this is the image I made. if that helps? https://auslink.info/linux/image.png

solved! I mounted the 'empty' partition using Disks and the files are all there

https://auslink.info/linux/mounted.png>>
so I tried the disk in a different PC, and it works perfectly. issue was the first
PC I tried was using legacy bios. thanks everyone,

I still have a problem. :( The PC I want to use the copy drive in has only legacy bios.
is there anyway I can make this disk boot in that PC? thanks,

For this setup, I did the following.

1) Install LM223 UEFI/GPT on NVMe (512GB)
Custom install: ESP first, BIOS-GRUB second (10MB, maybe only needs 1MB?), EXT4 slash, small swap
As near as I can tell, the BIOS-GRUB was not populated by GRUB during install.
As it is a NoFS partition, I like to keep those towards the left if possible.
(Like, to the left of Microsoft Reserved, which is another NoFS partition, on dual boots.)
The BIOS-GRUB partition is my "escape clause" :-)

2) Backup with Rescuezilla to 256GB scratch.

3) Restore to 1TB HDD. Put the drive into Legacy-only machine (Optiplex 780 E8400 Core2Duo)

4) Didn't boot. Blinking underline-cursor.

5) Tried Boot Repair DVD. Didn't work. Whined about either booting as UEFI (cannot do
on Legacy computer) or it was complaining it did not have the BIOS-GRUB files like the
LM223 DVD should have. At this point, I added a second EXT4 for a second OS install.
I installed LM223 from the DVD, and the DVD would boot in Legacy Mode.
There was some GRUB activity, so it did seem to try installing (in more than one place).

6) This time, my pair of OSes are now booting in the Legacy Machine, using their newly installed GRUB.

[Picture] LM223-BIOS-GRUB-legacy-BIOS-fix.gif

https://imgur.com/a/2HgqMoh

So my "extra partition" did the trick, by providing a storage place
for the GRUB .img file. There is still No_FS in the BIOS-GRUB partition,
it is a .img file "dd" transferred into the start of the partition. That's
what the label in GParted shows.

Summary: You can get there. It's the usual amount of annoyance.

And the Image-Explorer in RescueZilla works. I did a fresh boot of the RescueZilla USB stick (Rufus) and if you do Image-Explorer first thing,
it seems to work. The PartClone (...ptcl) should not be compressed if you plan on doing that.

Paul

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Tue, 5 May 2026 18:52:56 -0400, Paul wrote:

Summary: You can get there. It's the usual amount of annoyance.

Would be a lot simpler if you had done a file copy onto a new volume.

The rCLamount of annoyancerCY is only rCLusualrCY if you donrCOt know any better
...
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Tue, 5/5/2026 10:55 PM, Lawrence DrCOOliveiro wrote:

On Tue, 5 May 2026 18:52:56 -0400, Paul wrote:

Summary: You can get there. It's the usual amount of annoyance.

Would be a lot simpler if you had done a file copy onto a new volume.

The rCLamount of annoyancerCY is only rCLusualrCY if you donrCOt know any better
...

You also do these things when you move a UEFI boot drive to
a Legacy machine. That's what it is about. The OP asked about
it, and I demonstrated it can be fixed.

The actual backup and restore was trivial. I tested that.
The UEFI NVMe image booted just fine on the UEFI 1TB HDD.
Both were tested on the same computer, and they both worked.
They just were not plugged in at the same time (I unplugged
the NVMe module, before attempting to boot up the 1TB
prepared HDD).

It is when you move a UEFI-prepared storage device to a
Legacy machine (Optiplex 780 E8400), you have to fix up GRUB for that.
When I first plugged it in, I got a flashing underline, implying
nothing bootable was being found. On another situation (my VM setup),
that situation shows "No boot materials found" when there is that
sort of mismatch. While Boot Repair fixes some things, there
are bound to be the odd combination that has rough edges. And
I've used the "side by side" install methods multiple
times, and also on more than one platform. I was using that,
as a means to get UEFI certificates injected for Windows
(something that now comes with manual commands so you
don't have to do that any more).

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Wed, 6 May 2026 01:37:25 -0400, Paul wrote:

You also do these things when you move a UEFI boot drive to a Legacy
machine.

That just involves fixing up the bootloader. No need to touch the user
files at all.
--- Synchronet 3.21f-Linux NewsLink 1.2