unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: William <willbilly@fedora.email>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org
Subject: Re: Adding a menu entry on GRUB.
Date: Sun, 21 Apr 2024 17:48:15 +0200	[thread overview]
Message-ID: <20240421174815.79c610cd@fedora.email> (raw)
In-Reply-To: <875xwm2uxr.fsf@lease-up.com>

On Fri, 12 Apr 2024 13:21:52 -0700
Felix Lechner <felix.lechner@lease-up.com> wrote:

> Hi William,
> 
> On Fri, Apr 12 2024, William wrote:
> 
> > What could be causing this behavior?  
> 
> Maybe the GRUB module for that particular file system was not loaded
> (or was not found).  Please have a look at the documentation for
> 'insmod'.
> 
> Kind regards
> Felix

Hello. 

The SSD partition table is MBR, and all three partitions contain an
ext4 filesystem. I don't see how it could be a missing module issue,
and even if it was I'm not sure which module would I have to choose
since Guix is already installed on an MBR partition table with ext4
filesystem and it boots just fine.

This looks like some sort of obscure and bizarre bug, as
everything I'm seeing tells me that the SSD filesystems should be
recognized without any issue by Guix GRUB, but they aren't.

I ran e2fsck, lsblk, blkid and fdisk on a booted system to verify
that everything is fine with these partitions, no sign of anything
unusal...


fdisk:

Disk /dev/nvme0n1: 232,89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: KINGSTON SNV2S250G                      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xcd98d418

Device         Boot     Start       End   Sectors   Size Id Type
/dev/nvme0n1p1 *         2048   2097151   2095104  1023M 83 Linux
/dev/nvme0n1p2        2097152 197408767 195311616  93,1G 83 Linux
/dev/nvme0n1p3      197408768 488396799 290988032 138,8G 83 Linux




lsblk:

nvme1n1 
├─nvme1n1p1 ext4   1.0 d757ca6e-ae43-41b7-bc73-7e80cd270e05 
├─nvme1n1p2 ext4   1.0 da4c92d2-099f-4046-ab1d-1695860f33f0 
└─nvme1n1p3 ext4   1.0 d4fd6b3f-c46f-4ce0-9ad4-cb0b32f9b23e




blkid:

/dev/nvme1n1: PTUUID="2717697f" PTTYPE="dos"


/dev/nvme1n1p2: UUID="da4c92d2-099f-4046-ab1d-1695860f33f0"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2717697f-02"


/dev/nvme1n1p3: UUID="d4fd6b3f-c46f-4ce0-9ad4-cb0b32f9b23e"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2717697f-03"

/dev/nvme1n1p1: UUID="d757ca6e-ae43-41b7-bc73-7e80cd270e05"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2717697f-01"




e2fsck:

nvme1n1p1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

         389 inodes used (0.61%, out of 64000)
           2 non-contiguous files (0.5%)
           1 non-contiguous directory (0.3%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 381
       28616 blocks used (11.18%, out of 256000)
           0 bad blocks
           1 large file

         370 regular files
           9 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
         379 files

nvme1n1p2
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

      238335 inodes used (12.00%, out of 1986768)
         266 non-contiguous files (0.1%)
         217 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 209222/63
     3819800 blocks used (48.13%, out of 7936000)
           0 bad blocks
           2 large files

      194070 regular files
       14662 directories
           0 character device files
           0 block device files
           0 fifos
        2320 links
       29593 symbolic links (29042 fast symbolic links)
           0 sockets
------------
      240645 files

nvme1n1p3
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

       40577 inodes used (0.31%, out of 13221888)
         241 non-contiguous files (0.6%)
          47 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 40446/32
     2101091 blocks used (3.98%, out of 52856752)
           0 bad blocks
           1 large file

       36603 regular files
        3715 directories
           0 character device files
           0 block device files
           0 fifos
          12 links
         249 symbolic links (91 fast symbolic links)
           0 sockets
------------
       40579 files


  reply	other threads:[~2024-04-21 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 21:18 Adding a menu entry on GRUB William
2024-04-12 11:04 ` 宋文武
2024-04-12 15:37   ` William
2024-04-12 20:21     ` Felix Lechner via
2024-04-21 15:48       ` William [this message]
2024-04-22  0:53         ` Felix Lechner via
2024-04-22 19:37           ` William

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240421174815.79c610cd@fedora.email \
    --to=willbilly@fedora.email \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).