Conversation

Notices

1. Embed this notice
   T man :sex: :puffgiga: :puffpowerroll: (theorytoe@ak.kyaruc.moe)'s status on Thursday, 10-Apr-2025 23:47:00 JST T man :sex: :puffgiga: :puffpowerroll:
   main rig still takes forever to boot
   dont have time to dedicate to fixing it but hopefully when I get back home I can actually put effort into doing a sysclone
   • Embed this notice
     Lina Inver?e (lina@eientei.org)'s status on Thursday, 10-Apr-2025 23:49:59 JST Lina Inver?e

     in reply to
     @theorytoe try a big rig, over the road
   • Embed this notice
     T man :sex: :puffgiga: :puffpowerroll: (theorytoe@ak.kyaruc.moe)'s status on Thursday, 10-Apr-2025 23:55:35 JST T man :sex: :puffgiga: :puffpowerroll:

     in reply to

     • djsumdog
     cc @djsumdog I remember you writing about how you do system clones on most of your machines here https://battlepenguin.com/tech/copying-linux-between-machines/
     
     I would assume the process is similar for a regular disk; Just creating the partitions on the new disk, then copying from the old disk to the new disk, then setting up fstab. Unless im perhaps mistaken?
   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Friday, 11-Apr-2025 00:06:25 JST djsumdog

     in reply to
     If the new drive is the same size or bigger, you could also use `dd` to clone the entire disk, then use `efibootmgr` to setup the bootloader either from a recovery image or after booting using UEFI Shell. Then just expand the partition/filesystem.
     
     I've been meaning to post an update to that guide for ZFS, which I've been using on my systems recently. With ZFS I can take a snapshot and send it to a new drive.
     T man :sex: :puffgiga: :puffpowerroll: likes this.
   • Embed this notice
     T man :sex: :puffgiga: :puffpowerroll: (theorytoe@ak.kyaruc.moe)'s status on Friday, 11-Apr-2025 00:14:14 JST T man :sex: :puffgiga: :puffpowerroll:

     in reply to

     • djsumdog
     @djsumdog
     oh cool, didnt know I could use diskdestroyer to do that
     
     i assume that setting up the bootloader happens from the usb live environment? Ive only ever done clean installs so im not super knowledgeable in ways of cloning systems
   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Friday, 11-Apr-2025 00:33:33 JST djsumdog

     in reply to

     Back in the Master Boot Record (MBR) days, the boot loader was just in the boot sector of a partition and you could mark it as active with fdisk. So you could move a disk and it would "just work." But now with UEFI and GUID Partition Tables (GPT), the BIOS has to be told: add a boot entry labeled Linux that points to (hdx,x)/EFI/Grub.uefi or whatever. You'll see that at the bottom of my guide.

     If your motherboard supports UEFI shell (there's usually a "Start UEFI shell" option. Sometimes its built in to the BIOS, sometimes you have to put the shell on a USB stick), you can use that to navigate to the UEFI executable. The command syntax is similar to MSDOS. You type fd0: <enter> dir / cd.... You can find your bootloader and start it, then use efibootmgr after you're booted to add the entry permanently.

     Some BIOS setup screens let you configure the UEFI menu (Dell, Framework, etc.) It's a nice feature but not very common.

     T man :sex: :puffgiga: :puffpowerroll: likes this.
   • Embed this notice
     T man :sex: :puffgiga: :puffpowerroll: (theorytoe@ak.kyaruc.moe)'s status on Friday, 11-Apr-2025 00:47:33 JST T man :sex: :puffgiga: :puffpowerroll:

     in reply to

     • djsumdog
     • mangeurdenuage :gnu: :trisquel: :gondola_head: 🌿 :abeshinzo: :ignucius:
     @mangeurdenuage @djsumdog yes however I have had mixed results with that...
   • Embed this notice
     mangeurdenuage :gnu: :trisquel: :gondola_head: 🌿 :abeshinzo: :ignucius: (mangeurdenuage@shitposter.world)'s status on Friday, 11-Apr-2025 00:47:34 JST mangeurdenuage :gnu: :trisquel: :gondola_head: 🌿 :abeshinzo: :ignucius:

     in reply to

     • djsumdog
     @theorytoe @djsumdog
     >I remember you writing about how you do system clones on most of your machines here
     If you aren't aware a dedicated bootable distro exist for that clonezilla.org
   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Friday, 11-Apr-2025 05:49:58 JST djsumdog

     in reply to

     • :gnu:+bonifartius 𒂼𒄄

     Yes. \efi\BOOT\BOOTX64 will boot without needing to be set in the BIOS. (x64 can be replaced for different architecture) That's how bootable USB sticks work.

   • Embed this notice
     :gnu:+bonifartius 𒂼𒄄 (bonifartius@qoto.org)'s status on Friday, 11-Apr-2025 05:50:00 JST :gnu:+bonifartius 𒂼𒄄

     in reply to

     • djsumdog

     @djsumdog @theorytoe there is a default loader file name that is tried with UEFI as well

   • Embed this notice
     Jolly Rancher (not_br549@jollyville.net)'s status on Friday, 11-Apr-2025 05:50:03 JST Jolly Rancher

     in reply to

     • djsumdog
     good stuff to know.
     I miss the days when a disk partition could simply be marked bootable. And I don't think UEFI has made the process any more secure. If anything, it has enlarged the attack surface.
     
     Infuriatingly, on my Acer notebook I must hit F12 right after powering on, and select the GRUB entry, otherwise it just boots Win10. I admit that I have not done much research on it, but have failed to find a way to edit the UEFI boot order.
     djsumdog likes this.