You are not logged in.

#1 2023-01-02 20:51:09

francesco_dem
Member
From: Napoli - Italy
Registered: 2013-06-16
Posts: 14

[SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

I have a problem at boot with the kernels 6.1.1 and 6.1.2:

Error device dev/sda6/ not found
Skipping fsck

# lsblk -o +uuid

sda    8:0    0 447,1G  0 disk                                
├─sda1
│      8:1    0 199,5G  0 part /mnt/windows                   4FCF3618503B3D85
├─sda2
│      8:2    0   548M  0 part                                B0CC6266CC6226B6
├─sda3
│      8:3    0     1K  0 part                                
├─sda4
│      8:4    0 149,5G  0 part /mnt/manjaro                   81736371-c084-4690-835d-834ea7a9791c
├─sda5
│      8:5    0  46,9G  0 part /home                          bd233066-b082-4656-90d7-7266b37760e8
├─sda6
│      8:6    0  48,8G  0 part /                              ecbb2c5f-30c6-44bd-afb1-1d215061a84d
└─sda7
       8:7    0     2G  0 part [SWAP]                         03cc8d29-4406-403c-99cb-5ecae1a71a7f
sdb    8:16   0 465,8G  0 disk                                
├─sdb1
│      8:17   0   293G  0 part /mnt/Archivio                  0FF77F361C88319F
└─sdb2
       8:18   0 172,8G  0 part /Archivio                      009c41c5-f0bd-4fc0-8121-b7d267cba663
sdc    8:32   0 232,9G  0 disk                                
└─sdc1
       8:33   0 232,9G  0 part /dati                          8f8b637f-a4f5-43c7-8075-72938a641890
sdd    8:48   1     0B  0 disk                                
sde    8:64   1     0B  0 disk                                
sdf    8:80   1     0B  0 disk                                
sdg    8:96   1     0B  0 disk                                
sr0   11:0    1  1024M  0 rom           

sudo blkid

/dev/loop1: TYPE="squashfs"
/dev/sdb2: LABEL="Archivio Linux" UUID="009c41c5-f0bd-4fc0-8121-b7d267cba663" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="343f54a0-02"
/dev/sdb1: LABEL="Archivio Windows" BLOCK_SIZE="512" UUID="0FF77F361C88319F" TYPE="ntfs" PARTUUID="343f54a0-01"
/dev/loop6: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/sdc1: LABEL="Dati" UUID="8f8b637f-a4f5-43c7-8075-72938a641890" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="000e4721-01"
/dev/loop7: TYPE="squashfs"
/dev/sda4: UUID="81736371-c084-4690-835d-834ea7a9791c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="40c4d2f5-04"
/dev/sda2: BLOCK_SIZE="512" UUID="B0CC6266CC6226B6" TYPE="ntfs" PARTUUID="40c4d2f5-02"
/dev/sda7: UUID="03cc8d29-4406-403c-99cb-5ecae1a71a7f" TYPE="swap" PARTUUID="40c4d2f5-07"
/dev/sda5: UUID="bd233066-b082-4656-90d7-7266b37760e8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="40c4d2f5-05"
/dev/sda1: BLOCK_SIZE="512" UUID="4FCF3618503B3D85" TYPE="ntfs" PARTUUID="40c4d2f5-01"
/dev/sda6: UUID="ecbb2c5f-30c6-44bd-afb1-1d215061a84d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="40c4d2f5-06"
/dev/loop5: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"

the grub is installed on other distro (manjaro)
/boot/grub/grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

set menu_color_normal=light-gray/black
set menu_color_highlight=green/black

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
else
  search --no-floppy --fs-uuid --set=root 81736371-c084-4690-835d-834ea7a9791c
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=it_IT
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=hidden
  set timeout=10
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 10 ; then
  set timeout=0
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-81736371-c084-4690-835d-834ea7a9791c' {
	savedefault
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos4'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
	else
	  search --no-floppy --fs-uuid --set=root 81736371-c084-4690-835d-834ea7a9791c
	fi
	linux	/boot/vmlinuz-5.10-x86_64 root=UUID=81736371-c084-4690-835d-834ea7a9791c rw  quiet apparmor=1 security=apparmor udev.log_priority=3
	initrd	/boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
}
submenu 'Advanced options for Manjaro Linux' $menuentry_id_option 'gnulinux-advanced-81736371-c084-4690-835d-834ea7a9791c' {
	menuentry 'Manjaro Linux (Kernel: 5.10.161-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.161-1-MANJARO x64-advanced-81736371-c084-4690-835d-834ea7a9791c' {
	savedefault
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
		else
		  search --no-floppy --fs-uuid --set=root 81736371-c084-4690-835d-834ea7a9791c
		fi
		linux	/boot/vmlinuz-5.10-x86_64 root=UUID=81736371-c084-4690-835d-834ea7a9791c rw  quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd	/boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
	}
	menuentry 'Manjaro Linux (Kernel: 5.10.161-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.161-1-MANJARO x64-fallback-81736371-c084-4690-835d-834ea7a9791c' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
		else
		  search --no-floppy --fs-uuid --set=root 81736371-c084-4690-835d-834ea7a9791c
		fi
		linux	/boot/vmlinuz-5.10-x86_64 root=UUID=81736371-c084-4690-835d-834ea7a9791c rw  quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd	/boot/initramfs-5.10-x86_64-fallback.img
	}
	menuentry 'Manjaro Linux (Kernel: 5.4.228-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.4.228-1-MANJARO x64-advanced-81736371-c084-4690-835d-834ea7a9791c' {
	savedefault
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
		else
		  search --no-floppy --fs-uuid --set=root 81736371-c084-4690-835d-834ea7a9791c
		fi
		linux	/boot/vmlinuz-5.4-x86_64 root=UUID=81736371-c084-4690-835d-834ea7a9791c rw  quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd	/boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
	}
	menuentry 'Manjaro Linux (Kernel: 5.4.228-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.4.228-1-MANJARO x64-fallback-81736371-c084-4690-835d-834ea7a9791c' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
		else
		  search --no-floppy --fs-uuid --set=root 81736371-c084-4690-835d-834ea7a9791c
		fi
		linux	/boot/vmlinuz-5.4-x86_64 root=UUID=81736371-c084-4690-835d-834ea7a9791c rw  quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd	/boot/initramfs-5.4-x86_64-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-4FCF3618503B3D85' {
	savedefault
	insmod part_msdos
	insmod ntfs
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  4FCF3618503B3D85
	else
	  search --no-floppy --fs-uuid --set=root 4FCF3618503B3D85
	fi
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1
}
menuentry 'Arch Linux (on /dev/sda6)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-ecbb2c5f-30c6-44bd-afb1-1d215061a84d' {
	savedefault
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos6'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6  ecbb2c5f-30c6-44bd-afb1-1d215061a84d
	else
	  search --no-floppy --fs-uuid --set=root ecbb2c5f-30c6-44bd-afb1-1d215061a84d
	fi
	linux /boot/vmlinuz-linux-lts root=/dev/sda6
	initrd /boot/initramfs-linux-lts.img
}
submenu 'Advanced options for Arch Linux (on /dev/sda6)' $menuentry_id_option 'osprober-gnulinux-advanced-ecbb2c5f-30c6-44bd-afb1-1d215061a84d' {
	menuentry 'Arch Linux (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux-lts--ecbb2c5f-30c6-44bd-afb1-1d215061a84d' {
		savedefault
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos6'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6  ecbb2c5f-30c6-44bd-afb1-1d215061a84d
		else
		  search --no-floppy --fs-uuid --set=root ecbb2c5f-30c6-44bd-afb1-1d215061a84d
		fi
		linux /boot/vmlinuz-linux-lts root=/dev/sda6
		initrd /boot/initramfs-linux-lts.img
	}
	menuentry 'Arch Linux (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux--ecbb2c5f-30c6-44bd-afb1-1d215061a84d' {
		savedefault
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos6'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6  ecbb2c5f-30c6-44bd-afb1-1d215061a84d
		else
		  search --no-floppy --fs-uuid --set=root ecbb2c5f-30c6-44bd-afb1-1d215061a84d
		fi
		linux /boot/vmlinuz-linux root=/dev/sda6
		initrd /boot/initramfs-linux.img
	}
}

set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/60_memtest86+ ###
if [ "${grub_platform}" == "pc" ]; then
    menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
        search --fs-uuid --no-floppy --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  81736371-c084-4690-835d-834ea7a9791c
        linux16 /boot/memtest86+/memtest.bin 
    }
fi
### END /etc/grub.d/60_memtest86+ ###

kernel Lts works normaly

Last edited by francesco_dem (2023-01-05 14:01:31)

Offline

#2 2023-01-02 21:17:14

mpan
Member
Registered: 2012-08-01
Posts: 1,188
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

I suspect the cause is that your “grub.cfg” uses non-persistent partition references (the “/dev/sdxn” format). Those are not guaranteed to survive beyond a single boot. Use persistent block device naming.

Since you run grub-mkconfig on different distribution (Manjaro), it’s not a problem on Arch’s side. Consider asking Manjaro. Due to of how os-prober works, it may be a sign of deeper misconfiguration: for example persistent naming being missing in the system from which you invoke grub-mkconfig.

Last edited by mpan (2023-01-02 21:29:43)


Sometimes I seem a bit harsh — don’t get offended too easily!

Offline

#3 2023-01-03 06:57:35

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

If you want to use Manjaro's GRUB then add this to /boot/grug/custom.cfg or /etc/grub.d/40_custom in Manjaro:

menuentry 'Arch' {
   search.fs_uuid ecbb2c5f-30c6-44bd-afb1-1d215061a84d
   configfile /boot/grub/grub.cfg
}

Then disable the Arch menuentry created by grub-mkconfig in Manjaro by adding the (filesystem) UUID to GRUB_OS_PROBER_SKIP_LIST in /etc/default/grub in Manjaro and generate /boot/grub/grub.cfg in Arch, which should use the UUID in the linux line.

Offline

#4 2023-01-03 13:03:44

francesco_dem
Member
From: Napoli - Italy
Registered: 2013-06-16
Posts: 14

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

I created a file in /boot/grug/custom.cfg with

menuentry 'Arch' {
   search.fs_uuid ecbb2c5f-30c6-44bd-afb1-1d215061a84d
   configfile /boot/grub/grub.cfg
}

and i added in /etc/default/grub.

GRUB_OS_PROBER_SKIP_LIST="ecbb2c5f-30c6-44bd-afb1-1d215061a84d"

Then i run grub-mkconfig .

So i have a new boot menu with another arch entries but it doesn't work.

For me is not important a grub on manjaro. Can fix the problem  install grub in arch?

Sorry for my english

I tried to start arch with supergrub
I recevied this error: dependency failed for local file Systems

Last edited by francesco_dem (2023-01-03 18:00:57)

Offline

#5 2023-01-04 15:24:42

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

francesco_dem wrote:

So i have a new boot menu with another arch entries but it doesn't work.

Please be more specific. What actually happens when you select the Arch entries? Did you direct the grub-mkconfig output to /boot/grub/grub.cfg in Arch? Have you checked that file? Post it here if you can't make any sense of it.

francesco_dem wrote:

For me is not important a grub on manjaro. Can fix the problem  install grub in arch?

Yes but then the Manjaro entries generated by Arch's grub-mkconfig will use the block device (/dev/sd...) in the linux line so you'll still have the same problem but with Manjaro instead of Arch.

francesco_dem wrote:

Sorry for my english

That's fine, don't worry. It might be easier to get help in your own language though, is that possible?

francesco_dem wrote:

I tried to start arch with supergrub
I recevied this error: dependency failed for local file Systems

I don't even know what "supergrub" is so I can't really help with that. Sorry.

Offline

#6 2023-01-04 18:24:31

francesco_dem
Member
From: Napoli - Italy
Registered: 2013-06-16
Posts: 14

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Please be more specific. What actually happens when you select the Arch entries?.

Arch starts only with kernel lts entries.
When i try The old entries of kernel 6.1.2, i received error device;
with the new entries (kernel 6.1.2 ) created in /boot/grug/custom.cfg, the system doesn't start.

Did you direct the grub-mkconfig output to /boot/grub/grub.cfg in Arch. Have you checked that file? Post it here if you can't make any sense of it

In arch i haven't the file grub.conf. in boot/grub directory. I don't know the way to direct the grub-mkconfig in arch. can you write the command or what i must do it, thanks

Yes but then the Manjaro entries generated by Arch's grub-mkconfig will use the block device (/dev/sd...) in the linux line so you'll still have the same problem but with Manjaro instead of Arch.

Ok

I don't even know what "supergrub" is so I can't really help with that. Sorry.

Super GRUB2 Disk is a live cd that helps you to boot into most any Operating System (OS) even if you cannot boot into it by normal means.

Offline

#7 2023-01-04 19:32:51

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

francesco_dem wrote:

I don't know the way to direct the grub-mkconfig in arch. can you write the command or what i must do it

The command is in the ArchWiki: https://wiki.archlinux.org/title/GRUB#G … ation_file

Offline

#8 2023-01-05 13:56:09

francesco_dem
Member
From: Napoli - Italy
Registered: 2013-06-16
Posts: 14

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

I fixed the problem; in order:
i removed and reinstalled linux kernel;
i canceled file  /boot/grug/custom.cfg;
i used in arch and in manjaro  grub-mkconfig
a curiosity: in arch i have not a file grub.cfg in  /boot/grub/

Offline

#9 2023-01-05 14:17:36

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Run this command in Arch:

# grub-mkconfig -o /boot/grub/grub.cfg

FFS...

Offline

#10 2023-01-05 14:21:49

d.ALT
Member
Registered: 2019-05-10
Posts: 914

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

francesco_dem wrote:

a curiosity: in arch i have not a file grub.cfg in  /boot/grub/

That shouldn't be needed, IIRC. You're using grub.cfg from Manjaro's GRUB and you're using Manjaro's BootLoader (GRUB) to boot your Archlinux's kernel (+ its initramfs).


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#11 2023-01-05 14:27:13

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

d.ALT wrote:

That shouldn't be needed

Have you actually read the other posts in this thread?

The problem is that Manjaro's grub-mkconfig generates an Arch menuentry that uses the block device to identify the root partition in the "linux" line. This would also happen if Arch generated the configuration file but that would use the block device for the Manjaro entry.

The only way to have a menuentry for both systems that uses the (filesystem) UUID for the "linux" line is to have each distribution generate it's own /boot/grub/grub.cfg and call it using the configfile command from the other distribution's grub.cfg.

Offline

#12 2023-01-05 14:35:53

francesco_dem
Member
From: Napoli - Italy
Registered: 2013-06-16
Posts: 14

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Head_on_a_Stick wrote:

Run this command in Arch:

# grub-mkconfig -o /boot/grub/grub.cfg

FFS...


sudo grub-mkconfig -o /boot/grub/grub.cfg:

/usr/bin/grub-mkconfig: riga 265: /boot/grub/grub.cfg.new: File o directory non esistente

Offline

#13 2023-01-05 14:43:18

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Does /boot/grub/ exist?

EDIT: answering myself: no, it won't because you've not used grub-install in Arch.

So

# mkdir -p /boot/grub
# grub-mkconfig -o /boot/grub/grub.cfg

You don't need the modules or any of the other stuff that would normally be under /boot/grub/. Just /boot/grub/grub.cfg is needed.

You could even direct the configuration file to an arbitrary location as long as that location is provided in Manjaro's /boot/grub/custom.cfg.

Last edited by Head_on_a_Stick (2023-01-05 14:45:34)

Offline

#14 2023-01-05 15:18:48

francesco_dem
Member
From: Napoli - Italy
Registered: 2013-06-16
Posts: 14

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Head_on_a_Stick wrote:

Does /boot/grub/ exist?

EDIT: answering myself: no, it won't because you've not used grub-install in Arch.

I had sensed this. :-)

Head_on_a_Stick wrote:

So

# mkdir -p /boot/grub
# grub-mkconfig -o /boot/grub/grub.cfg

You don't need the modules or any of the other stuff that would normally be under /boot/grub/. Just /boot/grub/grub.cfg is needed.

You could even direct the configuration file to an arbitrary location as long as that location is provided in Manjaro's /boot/grub/custom.cfg.

Another question: If the GRUB.cfg file in the /boot/grub/ directory of Arch doesn't exist now and didn't exist before, are we sure that was the problem? Do you think it is necessary to create the directory and the grub file.cfg considering that now the system boots normally?

Thank you

Offline

#15 2023-01-05 15:51:37

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Using my suggested method will be more reliable. It might be that the block devices will be assigned in the order required by Manjaro's grub.cfg from now onwards but if you use Arch's grub.cfg then your system will continue to boot even if the block devices are assigned differently.

Offline

#16 2023-01-05 17:11:04

d.ALT
Member
Registered: 2019-05-10
Posts: 914

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Head_on_a_Stick wrote:
d.ALT wrote:

That shouldn't be needed

Have you actually read the other posts in this thread?

Nope... Damn, sorry!

But... Why on earth Arch's linux-lts was booting fine from /dev/sda6, then?


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#17 2023-01-05 17:17:09

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,680
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

I think it just depends how the block devices are assigned. Sometimes it will work but sometimes they will be assigned differently, breaking things. UUIDs on the "linux" line are the only way to have a consistent experience (or PARTUUIDs, or LABELs).

Offline

#18 2023-01-05 17:26:18

d.ALT
Member
Registered: 2019-05-10
Posts: 914

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

Head_on_a_Stick wrote:

Sometimes it will work but sometimes they will be assigned differently, breaking things

Yeah... It has been no more than a coincidence, right! (I need some rest... big_smile )


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#19 2023-01-05 17:34:07

mpan
Member
Registered: 2012-08-01
Posts: 1,188
Website

Re: [SOLVED] kernels 6.1.1 and 6.1.2 error device - Skipping fsck

d.ALT wrote:

But... Why on earth Arch's linux-lts was booting fine from /dev/sda6, then?

Because it’s a different kernel version: linux-lts is at 5.15 now. Device names in that format are not predictable, but that doesn’t mean they are chaotic. One can not rely on them across boots, but that’s not implying the kernel is tossing devices in a huge bag and pulls them out randomly on each boot. Usually device names change on kernel changes: between either versions or operating systems. Otherwise they appear unexpectedly stable, which leads many people to think everything is right with their configuration. Until one day the system just refuses to boot and spews at you errors that make you think your main drive has died.


Sometimes I seem a bit harsh — don’t get offended too easily!

Offline

Board footer

Powered by FluxBB