Bootloader can't detect separate disk

  • Open
  • quality assurance status badge
Details
2 participants
  • Divya
  • Vincent Legoll
Owner
unassigned
Submitted by
Divya
Severity
normal
D
D
Divya wrote on 7 May 04:04 +0200
(address . bug-guix@gnu.org)
C5389A21-E1A1-4B38-B5E6-0A34F73F6D40@subvertising.org
Hello,

Here is my `bootloader` section of `config.scm`:

```
(bootloader (bootloader-configuration (bootloader grub-bootloader) (targets (list "/dev/sda")) (menu-entries (list (menu-entry (label "Arch Linux") (device (uuid "886fb01f-323f-40ab-9434-9f00feb96446" 'ext4)) (linux "/boot/vmlinuz-linux-rt") (linux-arguments '("root=UUID=886fb01f-323f-40ab-9434-9f00feb96446 rw quiet")) (initrd "/boot/initramfs-linux-rt.img")))) (default-entry 0) (keyboard-layout keyboard-layout)))
```

I am trying to dual boot Guix with Arch, the former resides in `/dev/sda8` and the latter at `/dev/sdb1`. But the aforementioned configuration doesn't load Arch's kernel resulting in a 'kernel not found error' on the GRUB screen.

I have tried to do some troubleshooting by changing the parameters, but nothing seems to be working. And importantly, when I checked at the GRUB cli by doing `ls`, I see `/dev/sdb1` to be `(hd1,msdos1)` but with `ls` it shows that no file system is detected on it, when it has the `ext4` filesystem that I can access by mounting it.

What could be causing this? I checked `/boot/grub/grub.cfg` and it is trying to search the appropriate disk using UUID but because of the filesystem error, it can't access it and thus the kernel doesn't boot.

I'd like some help on this, also `os-prober` correctly identifies the Arch distro. Can I use it with my `config.scm`? Probably not? Is it possible to integrate it? I have some familiarity with bootloaders, I'd like to see if I can contribute here.

Regards,

Divya
Attachment: file
D
D
Divya wrote on 9 May 09:46 +0200
(address . bug-guix@gnu.org)
414B41D2-1969-45FF-9996-484ED7C6EA80@subvertising.org
On 7 May 2024 02:04:44 GMT, Divya <divya@subvertising.org> wrote:
Toggle quote (19 lines)
>Hello,
>
>Here is my `bootloader` section of `config.scm`:
>
>```
>(bootloader (bootloader-configuration (bootloader grub-bootloader) (targets (list "/dev/sda")) (menu-entries (list (menu-entry (label "Arch Linux") (device (uuid "886fb01f-323f-40ab-9434-9f00feb96446" 'ext4)) (linux "/boot/vmlinuz-linux-rt") (linux-arguments '("root=UUID=886fb01f-323f-40ab-9434-9f00feb96446 rw quiet")) (initrd "/boot/initramfs-linux-rt.img")))) (default-entry 0) (keyboard-layout keyboard-layout)))
>```
>
>I am trying to dual boot Guix with Arch, the former resides in `/dev/sda8` and the latter at `/dev/sdb1`. But the aforementioned configuration doesn't load Arch's kernel resulting in a 'kernel not found error' on the GRUB screen.
>
>I have tried to do some troubleshooting by changing the parameters, but nothing seems to be working. And importantly, when I checked at the GRUB cli by doing `ls`, I see `/dev/sdb1` to be `(hd1,msdos1)` but with `ls` it shows that no file system is detected on it, when it has the `ext4` filesystem that I can access by mounting it.
>
>What could be causing this? I checked `/boot/grub/grub.cfg` and it is trying to search the appropriate disk using UUID but because of the filesystem error, it can't access it and thus the kernel doesn't boot.
>
>I'd like some help on this, also `os-prober` correctly identifies the Arch distro. Can I use it with my `config.scm`? Probably not? Is it possible to integrate it? I have some familiarity with bootloaders, I'd like to see if I can contribute here.
>
>Regards,
>
>Divya
Pimg!
Attachment: file
V
V
Vincent Legoll wrote on 19 Jun 23:33 +0200
Bootloader can't detect separate disk
CAEwRq=qEiG9HcO504WcBJCMkZKn7yG+-nui5ijbo1D-92UCpJg@mail.gmail.com
Hello,

couldn't it be a partition type (GPT vs MBR) issue ?

--
Vincent Legoll
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 70808@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70808
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch