What I did several times: I used the Fedora installation routine with an USB stick or an USB attached portable NVMe drive as installation target. So I could boot the machine from USB leaving the internal disk untouched. I think that is what you mean with „making up a USB flash drive…“ Later I used dd to copy everything to the internal disk and was able to boot. Then I used gparted or cfdisk to adjust/enlarge the partitions. I never used safe boot. That may be a problem. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast

On Mon, Apr 29, 2024 at 8:27 PM ToddAndMargo via users <users(a)lists.fedoraproject.org&gt; wrote: Can you? Probably yes. But it would probably be quicker and easier to do a fresh install. As discussed in a recent thread after cloning you would have to make sure all the grub bits are updated with correct UUIDs. You would also have to rebuild initramfs, etc. If you are wanting to preserve user data, just re-create the user making sure the uid:gid are the same, and then mount the home directory from the USB drive under /mnt and then (as root) copy to the NVMe drive. If you are worried about missing a software package, you can make a list of installed rpms on the USB drive and use it to confirm the new install isn't missing anything that was on the USB.

On Tue, 2024-04-30 at 12:17 +0930, Tim via users wrote: I usually use 'sudo -i' when I need that. poc

On 29 Apr 2024 at 17:27, ToddAndMargo via users wrote: Date sent: Mon, 29 Apr 2024 17:27:23 -0700 To: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; Subject: can I clone from a usb flash drive to an NVMe drive? Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; From: ToddAndMargo via users <users(a)lists.fedoraproject.org&gt; Copies to: ToddAndMargo <ToddAndMargo(a)zoho.com&gt; Couple comments from maintainer of the g4l disk imaging project. Cloning the image would not be a problem with a bit level imaging program. I once did an image from an HDD disk to an SDD disk, and the image was perfect, but it didn't work exactly. Wouldn't boot since the boot kernel and init files didn't inclued the SSD setup. Back then had to build a new kernel on the HDD disk that included the support modules. Prograble would be a good ideal to create a new rescue kernel, which is generally much larger, and includes extra info. On my system I have the initramfs for rescue is much larger. ls -l | grep "6.8.7\|rescue" -rw------- 1 root root 119750715 Jan 9 12:07 initramfs-0-rescue-189711f94e78436d9618b891a8fce70e.img -rw------- 1 root root 39933046 Apr 23 14:44 initramfs-6.8.7-200.fc39.x86_64.img -rwxr-xr-x 1 root root 14666984 Jan 9 12:05 vmlinuz-0-rescue-189711f94e78436d9618b891a8fce70e -rwxr-xr-x 1 root root 14864200 Apr 17 10:00 vmlinuz-6.8.7-200.fc39.x86_64 Would probable be able to image that, and then boot system using the rescue image instead of latest default. Then after boot do a dnf reinstall kernel-core and it might install the latest kernel with the correct setup? Seemed to work with hdd to ssd, but not 100% sure with nvme? Sometime I just do a clean install but save the rpms from the old system, and then reinstall them. Create list of rpms of system using. #!/usr/bin/bash rpm --qf "%{NAME}.%{ARCH}\n" -qa | sort | grep -v gpg-pubkey Then do an install of files from file on the clean build. Usually, might have some packages that are missing, so use --skip-broken. So, just some info. May or may not be helpful. +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com mailto:msetzerii@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+

On 5/2/24 23:34, Todd Chester via users wrote: Here is the weird thing. I created a full install of FC40 MATE on a 32 GB stick. Put a bunch of cool programs on it. Went to boot it on the customer's machine and oh holy ... The bios was so screwed up that I could only get it to boot once. After that, if the stick was at the top of the boot order, I just got a flashing cursor. If I removed the stick, got a blank screen. It did not roll over to the next in boot order (W11). AAAAHHHHH!!!! The customer came up with an idea. He has a laptop from his business that was given to him when he retired. He wanted nothing on the laptop. So in with the stick and perfect boot. NO fussing with the BIOS. Then back down and in with Clonzilla. Did a clone over with k2 fill space and rescue option. And a perfect clone and all the space was used with the primary partition. Will wonder ever cease. -T