The officially official Devuan Forum!

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

[SOLVED][DAEDALUS] EMMC issue (before GRUB)

Hi guys,

I am pretty sure this a bug or a regression, is happened around a couple of week ago, perhaps after an upgrade.

The laptop requires almost a minute to come out with this warning text:

error: no such device: 3ba85e43-bd5b-4a44-9544-41921221101b
error: no server is specified.
error: no server is specified.

After that it goes in grub and the os boot properly after typing the passphrase to unlock luks...

I fsck with a minimal-live iso the whole disk and partitions and nothing came out as issue or was fixed.

Indisputably is related with the storage and therefore with the eMMC drive, since the latter is the main storage for this laptop:

 ls /dev/disk/by-uuid/
3ba85e43-bd5b-4a44-9544-41921221101b@  F447-1A01@
67af2c73-280d-49f1-aef0-5ed416c42ab8@  fa11faec-6990-4e47-b7da-2deba175d392@
d1ad949a-3157-4090-b03f-f8fb51c3816f@

Although nothing wrong was found:

sudo dmesg | grep mmc
[    1.682994] mmc0: CQHCI version 5.10
[    1.684800] mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
[    1.765625] mmc0: Command Queue Engine enabled
[    1.765638] mmc0: new HS400 MMC card at address 0001
[    1.770314] mmcblk0: mmc0:0001 TA2964 58.3 GiB 
[    1.772782]  mmcblk0: p1 p2 p3
[    1.773273] mmcblk0boot0: mmc0:0001 TA2964 4.00 MiB 
[    1.773685] mmcblk0boot1: mmc0:0001 TA2964 4.00 MiB 
[    1.774157] mmcblk0rpmb: mmc0:0001 TA2964 4.00 MiB, chardev (247:0)
[    2.435548] mmc0: Requiring re-tune after rpm resume
[   15.827721] EXT4-fs (mmcblk0p2): mounting ext2 file system using the ext4 subsystem
[   15.829371] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Quota mode: none.

Other info:

whereis runit
runit: /sbin/runit /etc/runit /lib/runit /usr/share/runit /usr/share/man/man8/runit.8.gz

 lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 5 (daedalus/ceres)
Release:	5
Codename:	daedalus ceres

 lsblk
NAME                   MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
mmcblk0                179:0    0 58.3G  0 disk  
├─mmcblk0p1            179:1    0  512M  0 part  /boot/efi
├─mmcblk0p2            179:2    0  488M  0 part  /boot
└─mmcblk0p3            179:3    0 57.3G  0 part  
  └─mmcblk0p3_crypt    254:0    0 57.3G  0 crypt 
    ├─abook--vg-root   254:1    0 56.3G  0 lvm   /
    └─abook--vg-swap_1 254:2    0  976M  0 lvm   [SWAP]
mmcblk0boot0           179:256  0    4M  1 disk  
mmcblk0boot1           179:512  0    4M  1 disk

sudo fdisk -l
Disk /dev/mmcblk0: 58.31 GiB, 62612570112 bytes, 122290176 sectors
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: gpt
Disk identifier: 8CD4F448-B215-4998-9AD2-D77DA4F59F0F

Device           Start       End   Sectors  Size Type
/dev/mmcblk0p1    2048   1050623   1048576  512M EFI System
/dev/mmcblk0p2 1050624   2050047    999424  488M Linux filesystem
/dev/mmcblk0p3 2050048 122288127 120238080 57.3G Linux filesystem

Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/mmcblk0p3_crypt: 57.32 GiB, 61545119744 bytes, 120205312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/abook--vg-root: 56.32 GiB, 60473475072 bytes, 118112256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/abook--vg-swap_1: 976 MiB, 1023410176 bytes, 1998848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Eventually the laptop boot but it is annoying waiting for a minute without understanding what is happening!

Thanks... 🙏

Last edited by Danielsan (2023-04-09 14:14:43)

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,251  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Kind of looks like something pre-grub tries to access the partition while the partition uuid is encypted.

Maybe ls -l /dev/disk/by-uuid or blkid would help identifying which partition it concerns.

rolfie

Member

Registered: 2017-11-25

Posts: 1,171  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Could it be that grub searches for the theme on the encrypted system device? Check /etc/default/grub.

When this is the case you may need to move the theme files to the unencrypted /boot.

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Kind of looks like something pre-grub tries to access the partition while the partition uuid is encypted.

Maybe ls -l /dev/disk/by-uuid or blkid would help identifying which partition it concerns.

Already posted!

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Could it be that grub searches for the theme on the encrypted system device? Check /etc/default/grub.

When this is the case you may need to move the theme files to the unencrypted /boot.

This sound interesting, actually the theme as changed.

However /EFI and /BOOT are over clear partitions...

From /etc/default/grub:

GRUB_THEME=/usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt

Mmm... 🤔

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

A simple sudo update-grub fixed the issue, not sure what happened to corrupt GRUB, perhaps an update... 🤷

Last edited by Danielsan (2023-04-09 14:17:00)

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,251  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Good you fixed it

It doesn't matter now, but I'm not sure what you meant with "Already posted"? Afaict your OP doesn't include output of either ls -l /dev/disk/by-uuid (note the -l) or blkid, which both are ways of seeing the associations between uuids and partitions.

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Good you fixed it

It doesn't matter now, but I'm not sure what you meant with "Already posted"? Afaict your OP doesn't include output of either ls -l /dev/disk/by-uuid (note the -l) or blkid, which both are ways of seeing the associations between uuids and partitions.

I posted the first command but not the second... And actually the partition it was unable to find was the LVM one belonging to root...

/dev/mapper/abook--vg-root: UUID="3ba85e43-bd5b-4a44-9544-41921221101b" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mmcblk0p3: UUID="67af2c73-280d-49f1-aef0-5ed416c42ab8" TYPE="crypto_LUKS" PARTUUID="d37ff9cc-dde0-4633-9a1b-276f81d36161"
/dev/mmcblk0p1: UUID="F447-1A01" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="6391c5b8-f0a0-48f9-bca4-ecbb6a9869de"
/dev/mmcblk0p2: UUID="fa11faec-6990-4e47-b7da-2deba175d392" BLOCK_SIZE="1024" TYPE="ext2" PARTUUID="60c53789-c48d-4052-956d-99a6419a97eb"
/dev/mapper/abook--vg-swap_1: UUID="d1ad949a-3157-4090-b03f-f8fb51c3816f" TYPE="swap"
/dev/mapper/mmcblk0p3_crypt: UUID="SXoUom-lUES-U2K6-Acug-MJDg-1t1P-kudC1C" TYPE="LVM2_member"

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,251  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Well, no @Danielsan, you did not post output of ln -l /dev/disk/by-uuid

rolfie

Member

Registered: 2017-11-25

Posts: 1,171  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

The installation of the clearlooks-phenix-sapphire-theme changed /etc/grub/default back to desktop-base and the themes there. On my encrypted Daedalus this produced the initial error in grub, an update-grub did NOT fix this. I copied clearlooks-phenix-sapphire-theme to /boot/grub/themes and changed the  /etc/grub/default to point to the /boot/grub/themes-directory, and everything is fine again.

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

The installation of the clearlooks-phenix-sapphire-theme changed /etc/grub/default back to desktop-base and the themes there. On my encrypted Daedalus this produced the initial error in grub, an update-grub did NOT fix this. I copied clearlooks-phenix-sapphire-theme to /boot/grub/themes and changed the  /etc/grub/default to point to the /boot/grub/themes-directory, and everything is fine again.

Mi issue came back...

However when I update-grub I don't see any complaining...

sudo update-grub
[sudo] password for freezr: 
Generating grub configuration file ...
Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt
Found background image: splash.png
Found linux image: /boot/vmlinuz-6.1.0-7-amd64
Found initrd image: /boot/initrd.img-6.1.0-7-amd64
Found linux image: /boot/vmlinuz-6.1.0-6-amd64
Found initrd image: /boot/initrd.img-6.1.0-6-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

ufff... 😖

rolfie

Member

Registered: 2017-11-25

Posts: 1,171  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

This line

Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt

indicates that grub wants to read the path /usr/share/desktop-base/grub-themes/desktop-grub-theme. This path is available on an unencrypted system for grub and for the system when running update-grub at any time, no errros.
On an encrypted system, when grub starts, this path isn't available yet until the initramfs has opened the root directory. This is when you get the errors as from the initial post. When running update grub there is no error since then /usr/share.... is available.

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

This line

Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt

indicates that grub wants to read the path /usr/share/desktop-base/grub-themes/desktop-grub-theme. This path is available on an unencrypted system for grub and for the system when running update-grub at any time, no errros.
On an encrypted system, when grub starts, this path isn't available yet until the initramfs has opened the root directory. This is when you get the errors as from the initial post. When running update grub there is no error since then /usr/share.... is available.

Half understood... /boot is actually clear...

Are you tell me to update grub configuration and move the theme into /boot...

I don't need a theme at all how can I remove it? I prefer plain old-style grub perhaps this is even better to solve it... 🤔

rolfie

Member

Registered: 2017-11-25

Posts: 1,171  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Your system is encrypted, so the /usr/share/... path isn't available to grub when booting.

The solution is to copy the /usr/share/desktop-base/grub-themes/desktop-grub-theme-files to /boot/grub/themes. This will provide the default layout in an unencrypted location. Every now and then the /etc/default/grub may get overwritten by updates. Then you have to fiddle again.

I have no idea what will happen if you simply comment the themes-line from /etc/default/grub. That may cause a real hickup...

Last edited by rolfie (2023-04-27 17:03:37)

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

I have no idea what will happen if you simply comment the themes-line from /etc/default/grub. That may cause a real hickup...

Commenting that line simply disables the fancy grub in favor of the always good and old fashioned grub... 😉

I wonder if this should be reported as bug... 🤔

Last edited by Danielsan (2023-04-27 22:52:02)

Danielsan

Member

Registered: 2020-07-14

Posts: 178  

Re: [SOLVED][DAEDALUS] EMMC issue (before GRUB)

Apparently it was a bug, yesterday I got an grub update that fixed the issue, so if grub can't access to / because encrypted simply falls back to regular grub...