boot error impossible to mount /boot

benoitldr · 2017-09-11 16:01:19

Hello,

Since 2 days, I tried to boot my archlinux on my fixed pc without success... despite looking into forum and wiki...

I really need your help because I use archlinux for work...

Configuration : dual boot windows10/archlinux
archlinux grub, i3

rEFInd
1) Boot vmlinuz-linux from 510 MiB FAT volume
2) Boot EFI\arch_grub\grubx64.efi from 510 MiB FAT volume

I choose the 2)

systemctl status systemd-modules-load.service 

● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-09-11 15:06:07 CEST; 11min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 193 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 193 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

systemctl status boot.mount

boot.mount - /boot
   Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-09-11 15:06:15 CEST; 12min ago
    Where: /boot
     What: /dev/disk/by-uuid/0D1A-E130
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)
  Process: 247 ExecMount=/usr/bin/mount /dev/disk/by-uuid/0D1A-E130 /boot -t vfat -o rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro (code=exited, status=32)

Sep 11 15:06:15 rollo systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
Sep 11 15:06:15 rollo systemd[1]: Mounting /boot...
Sep 11 15:06:15 rollo systemd[1]: boot.mount: Mount process exited, code=exited status=32
Sep 11 15:06:15 rollo systemd[1]: Failed to mount /boot.
Sep 11 15:06:15 rollo systemd[1]: boot.mount: Unit entered failed state.

fdisk -l

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: 5CBCA208-AAF2-46EF-9113-DEB95B5E3D6B

Device       Start       End   Sectors   Size Type
/dev/sda1     2048    923647    921600   450M Windows recovery environment
/dev/sda2   923648   1128447    204800   100M EFI System
/dev/sda3  1128448   1161215     32768    16M Microsoft reserved
/dev/sda4  1161216 976773119 975611904 465.2G Microsoft basic data


Disk /dev/sdb: 298.1 GiB, 320072933376 bytes, 625142448 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: dos
Disk identifier: 0xf7df29c9

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sdb1  *        2048   1050623   1048576   512M ef EFI (FAT-12/16/32)
/dev/sdb2        1050624  74450943  73400320    35G 83 Linux
/dev/sdb3       74450944 625142447 550691504 262.6G 83 Linux
Partition table entries are not in disk order.

lsblk -f

sda
├─sda1 ntfs    Récupération F04A6FDB4A6F9CDA
├─sda2 vfat                 9474-27AD
├─sda3
└─sda4 ntfs                 C646826B46825BD5
sdb
├─sdb1 vfat                 0D1A-E130
├─sdb2 ext4                 5b9bf432-7ce9-43ab-b535-eedd9a0ddd4a /
└─sdb3 ext4                 e5612070-0e00-44a0-b608-ec3f3de90c0d /home
sdc
├─sdc1
├─sdc2 ntfs    DATA_noir    E08462C88462A0B0
└─sdc5 ntfs    ECHANGE      1904ADCF316BF158
sdd    iso9660 ARCH_201709  2017-09-01-02-58-04-00
├─sdd1 iso9660 ARCH_201709  2017-09-01-02-58-04-00
└─sdd2 vfat    ARCHISO_EFI  C954-BB57

/etc/fstab 

# /dev/sdb2
UUID=5b9bf432-7ce9-43ab-b535-eedd9a0ddd4a	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sdb1
UUID=0D1A-E130      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/sdb3
UUID=e5612070-0e00-44a0-b608-ec3f3de90c0d	/home     	ext4      	rw,relatime,data=ordered	0 2

What I've done :

boot on arch-usb UEFI

loadkeys fr
mount /dev/sdb2 /mnt
mount /dev/sdb1 /mnt/boot
mount /dev/sdb3 /mnt/home
genfstab -U /mnt >> /mnt/etc/fstab
# I save the old fstab
arch-chroot /mnt
pacman -Syu linux
exit
reboot

I tried solutions based on these topics and some part of documentation but my knowledge...

https://bbs.archlinux.org/viewtopic.php?id=228145

https://bbs.archlinux.org/viewtopic.php?id=229385

https://bbs.archlinux.org/viewtopic.php?id=167109

Thanks you in advance,

Benoit

Last edited by benoitldr (2017-09-11 16:16:31)

loqs · 2017-09-11 22:31:05

What is the output of the following?

$ journalctl -b 0 -u systemd-modules-load.service
# mount /boot

Why do you have refind chainloading grub?

benoitldr · 2017-09-12 16:28:14

Hello loqs

journalctl -b 0 -u systemd-modules-load.service
--- Logs begin at Wed 2016-08-31 20:43:04 CEST, end at Tue 2017-09-12 16:07:CEST. --
--- No entries ---

So I try :

journalctl -u systemd-modules-load.service
-- Reboot --
Sep 11 15:39:18 rollo systemd[1]: Starting Load Kernel Modules...
Sep 11 15:39:18 rollo systemd-modules-load[302]: Failed to lookup alias 'vboxdrv': Function not implemented
Sep 11 15:39:18 rollo systemd-modules-load[302]: Failed to lookup alias 'vboxpci': Function not implemented
Sep 11 15:39:18 rollo systemd-modules-load[302]: Failed to lookup alias 'vboxnetadp': Function not implemented
Sep 11 15:39:18 rollo systemd-modules-load[302]: Failed to lookup alias 'vboxnetflt': Function not implemented
Sep 11 15:39:18 rollo systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Sep 11 15:39:18 rollo systemd[1]: Failed to start Load Kernel Modules.
Sep 11 15:39:18 rollo systemd[1]: systemd-modules-load.service: Unit entered failed state.
Sep 11 15:39:18 rollo systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

Because I try to install virtualbox (so I uninstall it https://wiki.archlinux.org/index.php/Vi … nux_hosts)

mount /boot

mount: /boot: unknown filesystem type 'vfat'*

And why do I have refind chainloading grub

I've already noticed that's weird and because refind and grub do the same job, but I have made a mistake in dual booting and I didn't know how to fix it because it's dirty but working...

loqs · 2017-09-12 17:20:22

The output of the following please

$ uname -a
$ pacman -Q linux

Fulgen · 2017-09-12 18:08:40

Perhaps you upgraded your kernel without having your /boot partition mounted, which happened to me. If you did a system upgrade before the error occured the first time, downgrade the kernel, boot normally, mount your boot partition and upgrade the kernel.

benoitldr · 2017-09-12 20:02:31

uname -a
Linux rollo 4.12.10-1-ARCH #1 SMP PREEMPT Wed Aug 30 12:18:42 CEST 2017 x86_64 GNU/Linux

pacman -Q linux
linux 4.12.12-1

so effectively, kernel version is different...

how can I properly downgrade the kernel ?

maybe like here : https://wiki.archlinux.org/index.php/Do … g_packages

I downgrade the kernel via live usb and chroot (I had cleaned the cache via pacman -Sc)

pacman -U https://archive.archlinux.org/packages/l/linux/linux-4.12.10-1-86_64.pkg.tar.xz

After that I just reboot ?

Last edited by benoitldr (2017-09-12 20:22:13)

Head_on_a_Stick · 2017-09-12 20:16:29

^ You don't need to downgrade your kernel at all.

Your running kernel is older than your installed kernel so you probably just need to upgrade your system using the live ISO (with your ESP mounted to correctly).

Even that may not be needed if the `uname` & `pacman -Q` output match when the system is booted with rEFInd's first menu option.

benoitldr wrote:

rEFInd
1) Boot vmlinuz-linux from 510 MiB FAT volume
2) Boot EFI\arch_grub\grubx64.efi from 510 MiB FAT volume

I choose the 2)

The second entry is chainloading GRUB's .efi loader (as you have already surmised) and that is what is loading a kernel image that does not match the installed modules.

Can we see GRUB's configuration file?

Have you tried updating it?

It would probably be easier to drop both rEFInd and GRUB and just use systemd's built-in bootmanager instead, this will simplify your system considerably.

Last edited by Head_on_a_Stick (2017-09-12 20:17:30)

benoitldr · 2017-09-12 20:34:24

I am a bit confused and lost on what I have to do...

I know my system is a bit weird (refind + grub)...

In my laptop with only archlinux the booting system is simplier (just grub)

where is the grub config (in /etc/grub.d/) ?

In fact I don't really understand how the booting mechanism is working because I have two ESP... and when I installed this system (long time ago), I have made some mistake...

For me :

/dev/sda2 EFI System with refind for dual boot ?
/dev/sdb1 EFI system for grub and linux
#in chroot I mount boot like this
mount /dev/sdb2 /mnt/boot

Correct ?

Last edited by benoitldr (2017-09-12 20:44:37)

benoitldr · 2017-09-12 20:51:07

Head_on_a_Stick wrote:

with your ESP mounted to correctly
Even that may not be needed if the `uname` & `pacman -Q` output match when the system is booted with rEFInd's first menu option.
benoitldr wrote:
rEFInd
1) Boot vmlinuz-linux from 510 MiB FAT volume
2) Boot EFI\arch_grub\grubx64.efi from 510 MiB FAT volume
I choose the 2)
The second entry is chainloading GRUB's .efi loader (as you have already surmised) and that is what is loading a kernel image that does not match the installed modules.
Can we see GRUB's configuration file?
Have you tried updating it?
It would probably be easier to drop both rEFInd and GRUB and just use systemd's built-in bootmanager instead, this will simplify your system considerably.

ESP mounted correctly (what's mean correctly ?) /dev/sdb2 ?

If I choose first option in rEFind

ERROR: device '' not found. Skipping fsck.
:: mouting '' on real root
mount: /new_root: no filesystem type specified.
You are now being dropped in an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#

jasonwryan · 2017-09-12 20:53:11

How did you install Arch?

loqs · 2017-09-12 20:57:21

benoitldr wrote:

where is the grub config (in /etc/grub.d/) ?

GRUB#Generate_the_main_configuration_file GRUB#Configuration

benoitldr wrote:

In fact I don't really understand how the booting mechanism is working because I have two ESP... and when I installed this system (long time ago), I have made some mistake...
For me :
/dev/sda2 EFI System with refind for dual boot ?
/dev/sdb1 EFI system for grub and linux
#in chroot I mount boot like this
mount /dev/sdb2 /mnt/boot
Correct ?

$ file /boot/vmlinuz-linux

If that version does not match the version returned by pacman -Q linux then both the fstab entry for /boot and /dev/sdb2 when you used chroot were not correct.
Please note /dev/sd* names are not persistent and can change you should always check the contents of such a partition before using it.

Last edited by loqs (2017-09-12 20:58:12)

Head_on_a_Stick · 2017-09-12 20:57:33

benoitldr wrote:

I have two ESP

Yes, sorry, I didn't read your OP carefully enough, please accept my apologies.

It would be simplest to share /dev/sda2 (the Windows ESP) with your Arch system and have that (auto)mounted to /boot

However, GRUB (and rEFInd, I think) can be made to work with separate ESPs.

Please consult the ArchWiki for details and post back if you have any specific questions:

https://wiki.archlinux.org/index.php/GRUB#UEFI_systems

where is the grub config (in /etc/grub.d/) ?

GRUB's configuration file is at /boot/grub/grub.cfg but most people control the configuration via a template at /etc/default/grub, the specifics are in the above link.

benoitldr · 2017-09-12 21:13:28

Thanks you everybody for your help and time...

I have just noticed something (I try to remember the installation of archlinux long time ago on this computer), in fact the /boot is not in separated partition, but there is a physical partition EFI in /dev/sdb which trick me when I see the result of fdisk -l

I have just chroot with only

mount /dev/sdb2 /mnt
arch-chroot /mnt /bin/bash
pacman -S linux

The system warn me that partition /boot seems to not mounted (after pacman -S linux) but it is due to false /etc/fstab (regenerated when I try to fix myself the problem without posting) correct ?

And it's worked with the second option of rEFind, I think I have to think about a cleaner way for this booting mechanism...

Thanks you again for your time and patience...

Last edited by benoitldr (2017-09-12 21:23:23)

loqs · 2017-09-12 22:17:46

benoitldr wrote:

The system warn me that partition /boot seems to not mounted (after pacman -S linux) but it is due to false /etc/fstab (regenerated when I try to fix myself the problem without posting) correct ?

As you have not provided the location refind or grub is loading the kernel from how can anyone answer if that is correct or not?
Usually in an EFI setup the ESP would be mounted at /boot or /boot/efi.

Arch Linux

#1 2017-09-11 16:01:19

boot error impossible to mount /boot

#2 2017-09-11 22:31:05

Re: boot error impossible to mount /boot

#3 2017-09-12 16:28:14

Re: boot error impossible to mount /boot

#4 2017-09-12 17:20:22

Re: boot error impossible to mount /boot

#5 2017-09-12 18:08:40

Re: boot error impossible to mount /boot

#6 2017-09-12 20:02:31

Re: boot error impossible to mount /boot

#7 2017-09-12 20:16:29

Re: boot error impossible to mount /boot

#8 2017-09-12 20:34:24

Re: boot error impossible to mount /boot

#9 2017-09-12 20:51:07

Re: boot error impossible to mount /boot

#10 2017-09-12 20:53:11

Re: boot error impossible to mount /boot

#11 2017-09-12 20:57:21

Re: boot error impossible to mount /boot

#12 2017-09-12 20:57:33

Re: boot error impossible to mount /boot

#13 2017-09-12 21:13:28

Re: boot error impossible to mount /boot

#14 2017-09-12 22:17:46

Re: boot error impossible to mount /boot

Board footer