Groups | Search | Server Info | Login | Register


Groups > alt.os.linux.mint > #47404

Re: Making a hard drive image

From Paul <nospam@needed.invalid>
Newsgroups alt.os.linux.mint
Subject Re: Making a hard drive image
Date 2026-05-05 18:52 -0400
Organization A noiseless patient Spider
Message-ID <10tdsc7$pj42$1@dont-email.me> (permalink)
References <n5nvjdFs3gU1@mid.individual.net> <n5q5rnFbcjaU1@mid.individual.net> <n5q68iFbcjaU2@mid.individual.net> <n5qbieFcc4aU1@mid.individual.net> <n5r2c8FfdhoU1@mid.individual.net>

Show all headers | View raw


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

Back to alt.os.linux.mint | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Making a hard drive image Axel <none@not.here> - 2026-05-03 14:00 +1000
  Re: Making a hard drive image Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-03 06:19 +0000
    Re: Making a hard drive image Axel <none@not.here> - 2026-05-03 20:20 +1000
      Re: Making a hard drive image George <George@invalid.invalid> - 2026-05-03 14:54 +0100
        Re: Making a hard drive image Mike Easter <MikeE@ster.invalid> - 2026-05-03 09:44 -0700
          Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-03 16:56 -0400
  Re: Making a hard drive image german newsgroups <usualsuspectrider@gmail.com> - 2026-05-03 11:00 +0200
    Re: Making a hard drive image Axel <none@not.here> - 2026-05-03 20:21 +1000
      Re: Making a hard drive image Edmund <nomail@hotmail.com> - 2026-05-03 16:18 +0200
        Re: Making a hard drive image german newsgroups <usualsuspectrider@gmail.com> - 2026-05-04 10:07 +0200
        Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 18:30 +1000
          Re: Making a hard drive image german newsgroups <usualsuspectrider@gmail.com> - 2026-05-04 17:51 +0200
      Re: Making a hard drive image german newsgroups <usualsuspectrider@gmail.com> - 2026-05-04 10:06 +0200
  Re: Making a hard drive image Mike Easter <MikeE@ster.invalid> - 2026-05-03 10:12 -0700
    Re: Making a hard drive image Mike Easter <MikeE@ster.invalid> - 2026-05-03 10:32 -0700
      Re: Making a hard drive image Mike Easter <MikeE@ster.invalid> - 2026-05-03 10:40 -0700
    Re: Making a hard drive image CtrlAltDel <Altie@BHam.com> - 2026-05-04 06:55 +0000
  Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 09:59 +1000
    Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 10:06 +1000
      Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 11:37 +1000
        Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-04 00:04 -0400
          Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 18:26 +1000
          Re: Making a hard drive image Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-04 08:33 +0000
        Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 18:06 +1000
          Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-04 05:18 -0400
          Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-05 18:52 -0400
            Re: Making a hard drive image Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-06 02:55 +0000
              Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-06 01:37 -0400
                Re: Making a hard drive image Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-06 06:48 +0000
    Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-03 20:19 -0400
      Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 11:48 +1000
  Re: Making a hard drive image Gordon <Gordon@leaf.net.nz> - 2026-05-04 00:45 +0000
    Re: Making a hard drive image Axel <none@not.here> - 2026-05-04 11:51 +1000
    Re: Making a hard drive image Paul <nospam@needed.invalid> - 2026-05-04 00:23 -0400

csiph-web