GNU bug report logs - #70808
Bootloader can't detect separate disk

Previous Next

Package: guix;

Reported by: Divya <divya <at> subvertising.org>

Date: Tue, 7 May 2024 02:07:02 UTC

Severity: normal

To reply to this bug, email your comments to 70808 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#70808; Package guix. (Tue, 07 May 2024 02:07:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Divya <divya <at> subvertising.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 07 May 2024 02:07:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Divya <divya <at> subvertising.org>
To: bug-guix <at> gnu.org
Subject: Bootloader can't detect separate disk
Date: Tue, 07 May 2024 02:04:44 +0000
[Message part 1 (text/plain, inline)]
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
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#70808; Package guix. (Thu, 09 May 2024 07:49:01 GMT) Full text and rfc822 format available.

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Divya <divya <at> subvertising.org>
To: bug-guix <at> gnu.org
Subject: Re: Bootloader can't detect separate disk
Date: Thu, 09 May 2024 07:46:21 +0000
[Message part 1 (text/plain, inline)]
On 7 May 2024 02:04:44 GMT, Divya <divya <at> subvertising.org> wrote:
>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!
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#70808; Package guix. (Wed, 19 Jun 2024 21:36:02 GMT) Full text and rfc822 format available.

Message #11 received at 70808 <at> debbugs.gnu.org (full text, mbox):

From: Vincent Legoll <vincent.legoll <at> gmail.com>
To: 70808 <at> debbugs.gnu.org, Divya <divya <at> subvertising.org>
Subject: Bootloader can't detect separate disk
Date: Wed, 19 Jun 2024 21:33:47 +0000
Hello,

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

-- 
Vincent Legoll




This bug report was last modified 120 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.