Can't boot Clonezilla image from Surface Go 1 to Acer Apire 5737z
from Dariusmiles2123@sh.itjust.works to linux@lemmy.ml on 30 Sep 2024 12:44
https://sh.itjust.works/post/25963065

Hi everyone,

I have a finely tuned Fedora 40 image that I cloned using Clonezilla (see: sh.itjust.works/post/25762756)

I wanted to deploy it on my old Acer Aspire 5737z but it won’t boot. It’s just displaying a — on a black screen for hours.

I’m not so knowledgeable but I guess it means I would have to reinstall the GRUB or whatever.

I’ve booted into my Fedora Live USB and tried the lsblk command people were talking about on the web (I don’t understand the terminal). Here’s the result.

I think the SDA disk is the one I would like to boot from.

Can anyone help me understand what I have to do 😇🙏

#linux

threaded - newest

alphapuggle@programming.dev on 30 Sep 2024 13:33 next collapse

I’m doing my morning scroll before I start my day, so I can’t delve too deep, but this is the article I always reference when I have to do repairs

askubuntu.com/a/831241

#1 thing I noticed in your image is that lsblk only shows you partitions, and doesn’t mount them. You probably want /dev/sda3 mounted at /mnt

The only thing from the article you want to modify is using mount -B /sys/firmware/efi/efivars /mnt/sys/efi/efivars, I believe the functionality changed since that article was written and that’s what worked for me

Additionally, if you drive is formatted as btrfs instead of ext4, once you mount your drive your root will most likely be at /mnt/admin or similar. Mount subdirectories to that folder instead of /mnt

If you have questions lmk and I’ll get back to you at some point today

Dariusmiles2123@sh.itjust.works on 30 Sep 2024 14:40 collapse

Thanks for the help but I don’t understand anything from the message on askubuntu.

I’ve tried the sudo mount/dev/sda3 /mnt part though…

Sorry for my lack of terminal skills

alphapuggle@programming.dev on 30 Sep 2024 15:16 collapse

That’s alright, I’ll do my best to walk you through it.

Your drive contains multiple partitions (/dev/sda1 through /dev/sda3).
One of these drives is going to be your EFI partition. This is what your system can read before linux boots, your BIOS can’t understand ext4 / btrfs / etc, but it can understand fat32.
If you run lsblk -no FSTYPE /dev/sda1 it should return vfat if that’s your EFI partition. That’s what we’re going to mount to /mnt/boot/efi

I’m assuming that /dev/sda3 is your data partition, e.g. where your linux install is. You can find the filesystem format the same way as your EFI partition. Edit: After determining which partition is which, you’re going to want to mount the root partition, and then the EFI partition
mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot/efi

Unix systems have theology of “everything is a file”, all devices and system interfaces are mounted as files. As such, to be able to properly chroot into an offline install, we need to make binds from our running system to the offline system. That’s what’s achieved by running for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
This is just a simple loop that mounts /dev, /dev/pts, /proc, /sys, and /run to your offline install. You’re going to want to either add /sys/firmware/efi/efivars to that list, or mount it (with -B, which is shorthand for --bind, not a normal mount).

Once you’ve done this, you should be able to successfully chroot into /mnt (or /mnt/root if running btrfs)
At this point, you should be able to run your grub repair commands.

Dariusmiles2123@sh.itjust.works on 30 Sep 2024 15:43 collapse

<img alt="" src="https://sh.itjust.works/pictrs/image/602d1b3d-500c-405d-b7cb-81abcd60248c.png">

Here is what I’m getting after running through the steps you kindly gave me. The second part is the part where I’m probably not doing right…

alphapuggle@programming.dev on 30 Sep 2024 16:14 collapse

Apologies, I think I got a bit ahead of myself in the description.
Once you’ve determined which partition is which (in your case, /dev/sda1 does appear to be the EFI partition, and /dev/sda3 appears to be your root partition), you need to mount them in this order

mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot/efi

Dariusmiles2123@sh.itjust.works on 30 Sep 2024 16:47 collapse

Here’s what I’m getting: <img alt="" src="https://sh.itjust.works/pictrs/image/4507dc12-8a9f-4c9d-b6d3-6092dd6dc4a7.png">

alphapuggle@programming.dev on 30 Sep 2024 17:17 collapse

Could you send me the output of lsblk -no FSTYPE /dev/sda3 and ll /mnt?

[deleted] on 30 Sep 2024 17:32 next collapse

.

Dariusmiles2123@sh.itjust.works on 02 Oct 2024 10:33 collapse

Hi again. Here is what it gave me:

<img alt="" src="https://sh.itjust.works/pictrs/image/6c495621-dc76-4ab2-86bf-5743309a3a03.png">

alphapuggle@programming.dev on 02 Oct 2024 15:32 collapse

Since you’re using btrfs, there is likely another subfolder under /mnt. ll /mnt will tell you this, but the drive isn’t still mounted from the other day. When you’re mounting the EFI partition, you’re going to want to mount it to that folder, and not /mnt itself (/mnt/root/boot/efi, instead of /mnt/boot/efi) same for the binds (/dev, /proc, /run, etc)

Dariusmiles2123@sh.itjust.works on 02 Oct 2024 20:30 collapse

Here is what I’m getting.

<img alt="" src="https://sh.itjust.works/pictrs/image/16079af3-3dda-4732-95df-482317383e04.png">

I’m almost ready to give up on my dream of establishing a perfectly tuned version of Fedora that I can deploy on all my computer just through Clonezilla…

alphapuggle@programming.dev on 03 Oct 2024 02:31 collapse

Interesting, both of my F40 installs with btrfs only have a root folder, but it looks like yours has created separate ones for /, /home, and /boot. run ll /mnt/boot; ll /mnt/home; ll /mnt/root so I can take a quick look at where things are located. My best guess is that sda1 gets mounted to /mnt/boot, while everything else (/dev, /sys, etc) gets mounted to /mnt/root

Dariusmiles2123@sh.itjust.works on 03 Oct 2024 05:54 collapse

Here’s what I’m getting:

<img alt="" src="https://sh.itjust.works/pictrs/image/de558759-1fa9-4f50-8268-f99f6241f1fc.png">

I don’t think I’ve set up anything particular, so I guess my install is different than yours because Fedora changed something. But clearly that change doesn’t help me;-)

hohoho@lemmy.world on 30 Sep 2024 13:34 next collapse

Did you mount the partition to /mnt/sysimage before attempting to chroot it? You can use the ‘mount’ command to see what’s mounted where.

bigsailboat@r.nf on 30 Sep 2024 13:38 collapse

Hey there!

It sounds like you’re on the right track! The black screen with a dash usually means the bootloader (GRUB in this case) might need some love. So, you’ll likely need to reinstall GRUB on your old Acer.

Here’s a simple way to do it from your Fedora Live USB:

  1. Open a terminal (if it’s not already).
  2. Run lsblk to confirm that your old Acer’s drive is /dev/sda.
  3. Mount the Fedora partition with something like:
    sudo mount /dev/sda1 /mnt
    (Make sure /dev/sda1 is the correct partition; adjust if needed).
  4. Install GRUB by running:
    sudo grub2-install --boot-directory=/mnt/boot /dev/sda
  5. Then create a new GRUB config with:
    sudo grub2-mkconfig -o /mnt/boot/grub2/grub.cfg
  6. Reboot and fingers crossed, it should work!

It sounds a bit like magic (or some weird old ritual), but it should help your Acer find its way. Give it a shot! If it doesn’t work, let us know exactly what you see. We’ve got your back!

Dariusmiles2123@sh.itjust.works on 30 Sep 2024 14:19 next collapse

<img alt="" src="https://sh.itjust.works/pictrs/image/4961f6ca-1ddb-4f75-9680-6e78f18429af.png"> <img alt="" src="https://sh.itjust.works/pictrs/image/70eb8695-f01e-4422-80a0-7459d1fe9a05.png"> <img alt="" src="https://sh.itjust.works/pictrs/image/b10d0db7-843b-4319-bc62-664ea5e0acb6.png">

Thanks for the precise answer adapted to a rookie like me😇😅

Sadly it ain’t working. I guess the GRUB installing part which is problematic.

hinterlufer@lemmy.world on 30 Sep 2024 17:54 collapse

Take that as you will, but you sound like ChatGPT.

gigachad@sh.itjust.works on 30 Sep 2024 18:36 collapse

I get these vibes too, their other comment are in the same style.

hinterlufer@lemmy.world on 30 Sep 2024 21:53 collapse

Yep, the other comment is even more ChatGPT-ish. And the account was created today. Guess that’s a bot.