Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34906 - [pacman] Upgrading kernel with boot partition not mounted

Attached to Project: Arch Linux
Opened by Salvatore (Salvatore) - Tuesday, 23 April 2013, 08:37 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 23 April 2013, 09:33 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Since I have a separate boot partition and I decided not to have it mounted automatically adding the flag 'noauto' in /etc/fstab file, when I upgrade the package core/linux pacman notices that boot partition is not mounted and it prints a warning message but copies anyway kernel and initramfs images to /boot without boot partition being mounted, so at the next reboot is still loaded the old kernel form the boot paritition that was not modified during upgrades and obviously it can't load all the modules that were associated to the new kernel. I would like to know if there is a reason for pacman not mounting /boot when upgrading kernel and if there is not, if you can add this feature to the software since I am not able to do that.

Additional info:

This is the version of pacman I have installed:

core/pacman 4.1.0-2 (base base-devel) [installed]
A library-based package manager with dependency support

.--. Pacman v4.1.0 - libalpm v8.0.0
/ _.-' .-. .-. .-. Copyright (C) 2006-2013 Pacman Development Team
\ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet
'--'
This program may be freely redistributed under
the terms of the GNU General Public License.

This is my /etc/fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda3 LABEL=Root
UUID=bc73b939-0fd9-487e-8be8-4eeaa3be169f / ext4 defaults,noatime,discard 0 1

# /dev/sda4 LABEL=Home
UUID=542af04a-2cae-4270-8a20-5d4a918ad685 /home ext4 defaults,noatime,discard 0 0

# /dev/sda2 LABEL=Boot
UUID=faaf0bf8-ec77-41ae-a92a-d3d9ea62844c /boot ext2 noauto,noatime 0 0

# tmpfs
tmpfs /tmp tmpfs noatime,nodev,nosuid,nodiratime,size=4G 0 0


This is what pacman writes when upgrading core/linux with boot partition unmounted:
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Packages (1): linux-3.8.8-1

Total Installed Size: 62.90 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [##################################################################################] 100%
(1/1) checking package integrity [##################################################################################] 100%
(1/1) loading package files [##################################################################################] 100%
(1/1) checking for file conflicts [##################################################################################] 100%
(1/1) checking available disk space [##################################################################################] 100%
(1/1) reinstalling linux [##################################################################################] 100%
WARNING: /boot appears to be a separate partition but is not mounted.
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.8.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.8.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful




Steps to reproduce:

Upgrade the kernel with pacman having separate boot partition not mounted.

Thanks in advance,
Salvatore
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 23 April 2013, 09:33 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Technically we could just mount your boot partition from pre_install or from mkinitcpio, but we don't. If we start implementing this, we have to tackle all corner cases from readonly boot volumes to unmounted boot volumes. The warning indicates you're doing something that will probably break, so it's up to you to fix it.

Loading...