[SOLVED] linux: /boot/vmlinuz-linux exists in filesystem

I have had this issue for a while now. I ignored it but now I'd like to be able to upgrade. Pacman throws this error:
error: failed to commit transaction (conflicting files)
linux: /boot/vmlinuz-linux exists in filesystem
Errors occurred, no packages were upgraded.
There are now news at archlinux.org, and I'm hesitant to use the --force flag. What do you suggest? Also, I have linux-ck-kernel, if that's relevant to the issue.
Last edited by rubik (2015-01-21 14:19:37)

I don't know how I installed linux-ck-kernel, it's been a while. I probably followed the wiki.
@a821: Here are the commands' outputs:
$ pacman -Qo /boot/vmlinuz-linux
error: No package owns /boot/vmlinuz-linux
$ uname -a
Linux miki-laptop 3.17.5-1-ck #1 SMP PREEMPT Sun Dec 7 07:23:18 EST 2014 x86_64 GNU/Linux
I'm puzzled! Why would pacman care about that file if no package owns it?! The wiki says that in this case I should rename it and update again. I'll try and see what happens.
Last edited by rubik (2015-01-21 13:24:47)

Similar Messages

[SOLVED] Cannot boot with linux-3.5.3

Edit: Solved, as explained here.
Hello,
after upgrading to linux-3.5.3-1 my boot stopped at
:: running early hook [udev]
I tried upgrading to grub-bios-2.00, removing any customization I had in modprobe.conf and /etc/modules-load.d as well as removing the only module (radeon) from /etc/mkinitcpio.conf (obviously followed by mkinitcpio -p linux), which made me go on to
:: waiting for udev uevents to be processed [BUSY]
I'm not sure it's an actual progress.
My /etc/udev/rules.d is empty and /usr/lib/udev/rules.d only contains pacman-tracked stuff.
I enabled some debugging as described here but couldn't get anything useful - is there any way for such messages to be logged somewhere, so they can be pasted here?
I ended up downgrading to linux-3.4.9, which boots fine.
Any idea to troubleshoot this?
cat /etc/rc.conf
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond dbus @networkmanager kdm @cpufreq sshd @cups @supervisor)
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=
# address=
# netmask=
# gateway=
cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
pacman -Qo /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/10-dm.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/10-vboxdrv.rules is owned by virtualbox 4.1.20-2
/usr/lib/udev/rules.d/11-dm-lvm.rules is owned by lvm2 2.02.97-1
/usr/lib/udev/rules.d/13-dm-disk.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/40-gphoto.rules is owned by libgphoto2 2.4.14-1
/usr/lib/udev/rules.d/40-hpet-permissions.rules is owned by jack2 1.9.8-2
/usr/lib/udev/rules.d/40-usb-media-players.rules is owned by media-player-info 17-1
/usr/lib/udev/rules.d/42-usb-hid-pm.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/50-udev-default.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/53-sane.rules is owned by sane 1.0.23-1
/usr/lib/udev/rules.d/60-cdrom_id.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-pcmcia.rules is owned by pcmciautils 018-4
/usr/lib/udev/rules.d/60-persistent-alsa.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-input.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-serial.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-v4l.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-rfkill.rules is owned by rfkill 0.4-5
/usr/lib/udev/rules.d/61-accelerometer.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules is owned by gnome-bluetooth 3.4.2-1
/usr/lib/udev/rules.d/64-md-raid.rules is owned by mdadm 3.2.5-2
/usr/lib/udev/rules.d/65-kvm.rules is owned by qemu 1.1.1-1
/usr/lib/udev/rules.d/69-cd-sensors.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/69-libmtp.rules is owned by libmtp 1.1.4-1
/usr/lib/udev/rules.d/70-infrared.rules is owned by v4l-utils 0.8.8-1
/usr/lib/udev/rules.d/70-power-switch.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-uaccess.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-udev-acl.rules is owned by consolekit 0.4.6-4
/usr/lib/udev/rules.d/71-seat.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/73-seat-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-net-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-probe_mtd.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-tty-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/77-nm-olpc-mesh.rules is owned by networkmanager 0.9.4.0-6
/usr/lib/udev/rules.d/78-sound-card.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-drivers.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-udisks.rules is owned by udisks 1.0.4-5
/usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 1.94.0-2
/usr/lib/udev/rules.d/85-usbmuxd.rules is owned by usbmuxd 1.0.8-1
/usr/lib/udev/rules.d/90-alsa-restore.rules is owned by alsa-utils 1.0.25-3
/usr/lib/udev/rules.d/90-libgpod.rules is owned by libgpod 0.8.2-6
/usr/lib/udev/rules.d/90-pulseaudio.rules is owned by pulseaudio 2.1-1
/usr/lib/udev/rules.d/95-cd-devices.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/95-dm-notify.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/95-keyboard-force-release.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-keymap.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-udev-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-csr.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-hid.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-wup.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules is owned by bluez 4.101-1
/usr/lib/udev/rules.d/99-systemd.rules is owned by systemd-tools 188-2
cat /var/log/pacman.log
[2012-08-28 12:27] Running 'pacman -Sy'
[2012-08-28 12:27] synchronizing package lists
[2012-08-28 14:51] Running 'pacman -S -u'
[2012-08-28 14:51] starting full system upgrade
[2012-08-28 14:53] upgraded gc (7.2.c-1 -> 7.2.d-1)
[2012-08-28 14:53] >>> Updating module dependencies. Please wait ...
[2012-08-28 14:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-28 14:53] ==> Building image from preset: 'default'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [autodetect]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] ==> Building image from preset: 'fallback'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-28 14:53] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-28 14:53] In order to use the new version, reload all virtualbox modules manually.
[2012-08-28 14:53] upgraded virtualbox-modules (4.1.20-1 -> 4.1.20-3)
[2012-08-28 14:59] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.3fb/google-chrome-21.0.1180.81-1-x86_64.pkg.tar.xz'
[2012-08-28 14:59] upgraded google-chrome (21.0.1180.57-1 -> 21.0.1180.81-1)
[2012-08-28 15:00] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.MgI/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:00] Running 'pacman -Sy'
[2012-08-28 15:00] synchronizing package lists
[2012-08-28 15:01] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.Vic/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:01] upgraded tunlr (0.1.4-1 -> 0.1.5-1)
[2012-08-28 17:34] Running 'pacman -S extra/kdeedu-kmplot'
[2012-08-28 17:34] installed kdeedu-kmplot (4.9.0-1)
[2012-08-29 10:20] Running 'pacman -Syu'
[2012-08-29 10:20] synchronizing package lists
[2012-08-29 10:20] starting full system upgrade
[2012-08-29 11:07] Running 'pacman -S grub-bios'
[2012-08-29 11:07] removed grub (0.97-21)
[2012-08-29 11:07] Generating grub.cfg.example config file...
[2012-08-29 11:07] This may fail on some machines running a custom kernel.
[2012-08-29 11:08] done.
[2012-08-29 11:08] installed grub-common (2.00-1)
[2012-08-29 11:08] installed grub-bios (2.00-1)
[2012-08-29 11:48] Running 'pacman -Sy'
[2012-08-29 11:48] synchronizing package lists
[2012-08-29 11:48] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -Sy'
[2012-08-29 12:11] synchronizing package lists
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -S -u'
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:15] upgraded firefox (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded firefox-i18n-it (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded gsmartcontrol (0.8.7-1 -> 0.8.7-2)
[2012-08-29 12:15] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded samba (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 12:15] upgraded syslinux (4.05-6 -> 4.05-7)
[2012-08-29 12:15] upgraded thunderbird (14.0-1 -> 15.0-1)
[2012-08-29 12:15] upgraded thunderbird-i18n-it (14.0-1 -> 15.0-1)
[2012-08-29 12:15] -> You can now set custom file descriptor ulimits for Tor in
[2012-08-29 12:15] -> "/etc/conf.d/tor" using the "TOR_MAX_FD" variable.
[2012-08-29 12:15] upgraded tor (0.2.2.37-1 -> 0.2.2.38-1)
[2012-08-29 12:56] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.K10/downgrade-3.0-1-any.pkg.tar.xz'
[2012-08-29 12:56] installed downgrade (3.0-1)
[2012-08-29 12:57] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:04] Running 'pacman -U /var/cache/pacman/pkg/virtualbox-modules-4.1.20-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -R virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rd virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rdd virtualbox-modules'
[2012-08-29 13:06] removed virtualbox-modules (4.1.20-3)
[2012-08-29 13:06] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:06] >>> Updating module dependencies. Please wait ...
[2012-08-29 13:06] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-29 13:06] ==> Building image from preset: 'default'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [autodetect]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:06] -> Running build hook: [sata]
[2012-08-29 13:06] -> Running build hook: [resume]
[2012-08-29 13:06] -> Running build hook: [filesystems]
[2012-08-29 13:06] -> Running build hook: [usbinput]
[2012-08-29 13:06] -> Running build hook: [fsck]
[2012-08-29 13:06] ==> Generating module dependencies
[2012-08-29 13:06] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Image generation successful
[2012-08-29 13:06] ==> Building image from preset: 'fallback'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:07] -> Running build hook: [sata]
[2012-08-29 13:07] -> Running build hook: [resume]
[2012-08-29 13:07] -> Running build hook: [filesystems]
[2012-08-29 13:07] -> Running build hook: [usbinput]
[2012-08-29 13:07] -> Running build hook: [fsck]
[2012-08-29 13:07] ==> Generating module dependencies
[2012-08-29 13:07] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-29 13:07] ==> Image generation successful
[2012-08-29 13:07] upgraded linux (3.5.3-1 -> 3.4.9-1)
[2012-08-29 14:47] Running 'pacman -Sy'
[2012-08-29 14:47] synchronizing package lists
[2012-08-29 14:49] Running 'pacman -S -u'
[2012-08-29 14:49] starting full system upgrade
Last edited by thujone (2012-09-19 12:18:51)

because the report opener said that those freezes fixed with the 'futex' patch (included in 3.14-5).
As he says:
for those who have again problems despite the patch it means probably that there are another bugs further in the source code of kernel 3.14, bugs who are not necessarily related to the "futex problem"
i will try a clean profile, thanks.
Last edited by tritonas00 (2014-04-16 13:22:51)

[Solved]Wont boot after installing syslinux; unknown filesystem 'swap'

After installing syslinux to be my boot manager I can no longer boot into Arch, I can however boot into Windows 7. When I try to boot into Arch I get the following error.
Loading ../vmlinuz-linux......
Loading ../initramfs-linux.img......ready.
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda3'
fsck: fsck.swap: not found
fsck: error 2 while executing fsck.swap for /dev/sda3
ERROR: fsck failed on 'dev/sda3'
:: mounting '/dev/sda3' on real root
mount: unknown filesystem type 'swap'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs /]#
What's going on?
Last edited by slughappy1 (2012-07-05 22:50:35)

loafer wrote:Can you post your syslinux.cfg please.
Surely
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
LABEL windows
MENU LABEL Windows7
COM32 chain.c32
APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com

[SOLVED] Update fails ("/usr/lib64 exists in filesystem")

Hi,
today I wanted to update my arch linux. I selected all packages:
bash-4.2.042-2 filesystem-2013.01-1 gcc-4.7.2-4 gcc-libs-4.7.2-4 glibc-2.17-2 linux-api-headers-3.7.4-1 mkinitcpio-0.12.0-3 sudo-1.8.6.p5-1 transmission-gtk-2.76-2
But then I've got following error (translated from German to English)
Error: Could not complete procedure (conflicts in files)
filesystem: /usr/lib64 exists in filesystem
Any idea?
Best regards
Steffo
Last edited by Steffo (2013-01-27 12:42:45)

swordfish wrote:
Please have a look at this:
https://wiki.archlinux.org/index.php/De … i%3Ausrlib
This doesn't work:
sudo pacman -U -d http://pkgbuild.com/~allan/glibc-2.16.0-1-x86_64.pkg.tar.xz
I get following error:
error: failed to commit transaction (conflicting files)
glibc: /lib/ld-linux-x86-64.so.2 exists in filesystem
glibc: /lib/libBrokenLocale.so.1 exists in filesystem
glibc: /lib/libanl.so.1 exists in filesystem
glibc: /lib/libc.so.6 exists in filesystem
glibc: /lib/libcidn.so.1 exists in filesystem
glibc: /lib/libcrypt.so.1 exists in filesystem
glibc: /lib/libdl.so.2 exists in filesystem
glibc: /lib/libm.so.6 exists in filesystem
glibc: /lib/libnsl.so.1 exists in filesystem
glibc: /lib/libnss_compat.so.2 exists in filesystem
glibc: /lib/libnss_db.so.2 exists in filesystem
glibc: /lib/libnss_dns.so.2 exists in filesystem
glibc: /lib/libnss_files.so.2 exists in filesystem
glibc: /lib/libnss_hesiod.so.2 exists in filesystem
glibc: /lib/libnss_nis.so.2 exists in filesystem
glibc: /lib/libnss_nisplus.so.2 exists in filesystem
glibc: /lib/libpthread.so.0 exists in filesystem
glibc: /lib/libresolv.so.2 exists in filesystem
glibc: /lib/librt.so.1 exists in filesystem
glibc: /lib/libthread_db.so.1 exists in filesystem
glibc: /lib/libutil.so.1 exists in filesystem
Errors occurred, no packages were upgraded.

[solved] mesa-dri: /etc/drirc exists in filesystem

EDIT: The following problem was solved by upgrading the system using `pacman -Suy` instead of `yaourt -Suy`
The problem was:
I'm trying to install mesa-dri, because my system refuses to upgrade. However, it gives me this error.
(1/1) checking for file conflicts [########################################################] 100%
error: failed to commit transaction (conflicting files)
mesa-dri: /etc/drirc exists in filesystem
mesa-dri: /usr/lib/xorg/modules/dri/swrast_dri.so exists in filesystem
Errors occurred, no packages were upgraded.
I tried to see what ows those files and install mesa, but
➜ ~ pacman -Qo /etc/drirc
/etc/drirc is owned by mesa 10.2.8-1
➜ ~ pacman -Qo /usr/lib/xorg/modules/dri/swrast_dri.so
/usr/lib/xorg/modules/dri/swrast_dri.so is owned by mesa 10.2.8-1
➜ ~ yaourt -S mesa
[sudo] password for steve:
resolving dependencies...
looking for inter-conflicts...
:: mesa-dri and ati-dri are in conflict. Remove ati-dri? [y/N] y
:: mesa-dri and intel-dri are in conflict. Remove intel-dri? [y/N] y
:: mesa-dri and nouveau-dri are in conflict. Remove nouveau-dri? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: mesa-libgl: requires mesa=10.2.8
I'm not sure where I should look for a solution to this problem and what should I do. I don't want to force anything if it can make my system unusable. Can anybody point me in the right direction to do this safely?
mesa-libgl is required by
➜ ~ pacman -Qi mesa-libgl
Required By : ati-dri bumblebee cairo compton-git freeglut glu intel-dri libva mesa-demos mplayer mpv nouveau-dri qt4 qt5-base sdl2
simplescreenrecorder webkitgtk2 xorg-server xorg-xdriinfo
Last edited by SteveSapolsky (2014-10-23 12:46:11)

WorMzy wrote:
Can you post the full output of
# pacman -Syu
A rookie mistake on my part. I was assuming that if `yaourt -Suy` gave this message then pacman would as well. I tried
pacman -Suy
And pacman upgraded my system without problems.
FTR, here is what `yaourt -Suy` was giving me:
➜ ~ yaourt -Suy
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: failed to prepare transaction (could not satisfy dependencies)
:: Starting full system upgrade...
:: ati-dri: requires mesa=10.2.8
:: intel-dri: requires mesa=10.2.8
:: lib32-intel-dri: requires lib32-mesa=10.2.8
:: nouveau-dri: requires mesa=10.2.8

[Solved] KDE 4.7: nepomukcontroller exists in filesystem

When upgrading, after downloading everything, I get the following:
checking for file conflicts [################################################################] 100%
error: failed to commit transaction (conflicting files)
kdebase-runtime: /usr/bin/nepomukcontroller exists in filesystem
kdebase-runtime: /usr/share/applications/kde4/nepomukcontroller.desktop exists in filesystem
Errors occurred, no packages were upgraded.
The only other reference I've found to this issue is this post on the Chackra forums, but without replies. I've also checked the public dev mailing list, but no mention of the issue there, either. Can anyone help? Thanks in advance.
Last edited by gauthma (2011-07-30 10:28:34)

sumski wrote:
pacman -Qo /usr/bin/nepomukcontroller
https://bbs.archlinux.org/viewtopic.php?id=56373
Yep, that's what I should have done. But I somehow convinced myself that this was a problem with the update itself, and so my perspective narrowed... Anyway problem solved now (thanks for the reply nonetheless!)

[SOLVED] libido3 preventing pacman update exists in filesystem

After running pacman -Syu, I receive the infamous .../exists in filesystem
I read the wiki and pacman -Qo on each of the trouble files results in the owner being libido3 12.10.2-100
I do have unity installed through the arch repositories.
If there was no owner, I would remove them, however since the files are owned by something, I don't know what to do next.
Thanks
Last edited by glenn69 (2013-01-29 23:48:42)

I can't seem to find much about the file online either. I'm not sure if ido is the same file as libido?
... but the result of pacman -Qo on a problem file results in
/usr/include/libido3-0.1/libido/idoentrymenuitem.h is owned by libido3 12.10.2-100
then I searched for libido with this result:
[root@Arch-Home_x86_64 ~]# find / -name libido3*
/var/cache/pacman/pkg/libido3-12.10.2-100-x86_64.pkg.tar.xz
/var/lib/pacman/local/libido3-12.10.2-100
/usr/include/libido3-0.1
/usr/lib/pkgconfig/libido3-0.1.pc
/usr/lib/libido3-0.1.so.0.0.0
/usr/lib/libido3-0.1.so
/usr/lib/libido3-0.1.so.0

[SOLVED] Triple Boot Arch Linux, Windows 7 + Windows 8 on second disk

Hi,
I have installed Arch Linux and Windows 7 on my primary disk. Everything's perfect. I want to install Windows 8 on my second disk. My only problem is how do I make grub2 recognize Windows 8 on the second disk and add it to the grub file, so i can boot Arch, Windows 7 and Windows 8.
Thank you for your time,
Deadvi
Last edited by Deadvi (2012-08-29 21:24:00)

It overwrote the MBR from the first disk, even though you installed Windows 8 on the second disk? That's odd... Make sure that the boot order in the BIOS is right (that the drive with Arch Linux is the first to boot) and from a 2012 Arch Linux install media run:
# mount /dev/sdxY /mnt #Your root partition.
# mount /dev/sdxZ /mnt/boot #Your boot partition (if you have one).
# arch-chroot /mnt
And continue with the instructions from here. If you don't have a 2012 Arch Linux install media (or you only have some other "live" Linux distribution), use the old chroot way.

[Solved] Error when updating: file exists in filesystem

Hello all,
While updating with pacman my laptop overheated and turned off.
After rebooting I removed /var/lib/pacman/db.lck.
When I resume pacman -Syu I get:
http://pastebin.com/7c1iTgWG
Is there any way to fix this or is a fresh install in order?
Thank you very much for your help
Last edited by vidar-mud (2012-11-21 18:50:29)

Welcome to the boards. Please read our Forum Etiquette https://wiki.archlinux.org/index.php/Forum_Etiquette
You should also read the stickies in Newbie Corner, notably the Common Problems and Issues one, where yours is described.

[SOLVED]dual boot-Failed to mount real root device

Hello,
Here is my drives partition info:
/dev/sda1 2,949,122,048 3,907,028,991 957,906,944 7 NTFS / exFAT / HPFS
/dev/sda2 2,048 901,117,951 901,115,904 83 Linux
/dev/sda3 * 901,117,952 1,925,115,903 1,023,997,952 f W95 Extended (LBA)
/dev/sda5 901,120,000 901,439,487 319,488 83 Linux
/dev/sda6 901,441,536 905,648,127 4,206,592 82 Linux swap / Solaris
/dev/sda7 905,650,176 1,925,115,903 1,019,465,728 83 Linux
/dev/sda4 1,925,115,904 2,949,122,047 1,024,006,144 7 NTFS / exFAT / HPFS
/dev/sdb1 2,048 2,099,199 2,097,152 83 Linux
/dev/sdb2 2,099,200 53,299,199 51,200,000 83 Linux
/dev/sdb3 53,299,200 73,779,199 20,480,000 83 Linux
/dev/sdb4 73,779,200 224,673,791 150,894,592 7 NTFS / exFAT / HPFS
I installed Opensuse 12.1 on /dev/sda5. It is booting with Grub, working with no problems. The computer boots directly to Grub menu.
THEN, I installed Arch linux (last release) on both sda and sdb following these mounting points:
/dev/sdb1 mounted as /boot Ext2
/dev/sdb2 mounted as / BTRFS
/dev/sdb3 mounted as /usr BTRFS
/dev/sda2 mounted as /home BTRFS
Intstallation went smooth until the end. Installed the bootloader.
Now, I am trying to configure GRUB to boot Arch.
Here is what I added on /boot/grub/menu.lst, in sda5 under Opensuse:
title Arch Linux [/boot/vmlinuz-linux]
root (hd1,0)
kernel /vmlinuz-linux root=/dev/sdb1 ro
initrd /initramfs-linux.img
In Opensuse, i can check that vmlinux and grub/menu.lst are indeed in /dev/sdb1
My /etc/fstab is on /dev/sdb2
=============================== sdb2/etc/fstab: ==========
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda2 /home btrfs defaults 0 1
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb2 / btrfs defaults 0 1
/dev/sdb3 /usr btrfs defaults 0 1
With this parameters, i got an message error when booting Arch:
Mounting /dev/sdb1 on /new_root failed: no such device.
Error : failed to mount the real root device.
So, at busybox prompt, I tried this command line :
ramfs # mount -t ext2 /dev/sdb1
Got an error : Can't read /etc/fstab
I tried too to give a uuid adress to sdb1 in my menu.lst file, but it didn't change anything, so I am sure partition number is correct.
It seems to me in fact that GRUB can't find fstab.
Two questions :
-Would it be better in fact to use only 1 GRUB file for both systems? If yes, shall I keep only the grub config from Opensuse?
-What do I wrong with Arch booting? Why can't I boot Arch?
EDIT :1- just realised there is no BOOT flag in my partiton table on /dev/sdb.
2- root is on /dev/sdb2, not sdb1.
1-I toggled my first partition bootable using fdisk
2-changed root to point to /dev/sdb2
Now booting into Arch login
Last edited by gabx (2011-11-22 22:33:09)

It was a very simple problem. I used the wrong uuid for my /
Correct entry in 40_custom is:
#!/bin/sh
exec tail -n +3 $0
# 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.
menuentry "Arch Linux uuid" {
insmod part_msdos
insmod ext2
search --fs-uuid --no-floppy --set=root 8516fa60-0d45-4f33-b269-817c5290f6cc
linux /vmlinuz26 root=/dev/disk/by-uuid/9f32e668-2548-4ed4-a10b-3fbea66a6d95 ro vga=775
initrd /kernel26.img
Now the boot is working great. Next thing was that my /home and swap was not detected.
That was simply because /etc/fstab was still using /dev/sda etc naming. changing that to uuid solved that part as well.
To use uuid all the way and of cause the correct one solved everything
/Christer
Last edited by agkbill (2011-07-15 16:00:30)

[SOLVED]Dual boot Grub2 : file not found

here is my config :
Ubuntu 11.1 installed on sd1. It is my default system, and where the GRUB2 config is.
I installed Archlinux on sd2, with /boot on (hd1,1) and / on (hd1,2).
I want to set up GRUB to boot both systems.
here is my /etc/grub.d/11_linux_arch, in the Ubuntu system :
#!/bin/sh -e
echo "Adding Archlinux"
cat << EOF
menuentry "ArchLinux" {
set root=(hd1,2)
linux /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
EOF
vmlinux-linux and initramfs-linux.img are well in my /boot folder on (hd1,1)
At grub prompt, I can see Archlinux as an option. When I select it, I get an error message, "file not found".
I can't see where is an error.
TY for any help.
Last edited by gabx (2011-11-29 22:41:11)

Here is what I added to /etc/grub.d/40_custom
# Arch Linux
menuentry "Arch Linux" {
set root=(hd1,1)
linux /vmlinuz-linux root=/dev/disk/by-uuid/38616db1-366f-40f4-a728-1230e81abb21 ro
initrd /initramfs-linux.img
I think telling the uuid is better but /dev/sdb2 (my / partition) works too.
Then :
#sudo update-grub
and I have been able to dual boot Archlinux and Ubuntu 11.10.
The resolution is bad, so I will add a line about it, but I guess it is not diificult.

[Solved again] Updated to linux-3.10.8; Can no longer boot

Hey everyone.
So, linux-3.10.2-1 just dropped to the [testing] repos, and I got it through a standard -Syu. Along with it were upgraded libxfont, linux-headers, lirc-utils (and I installed extundelete during the same command).
Here's the relevant bit of /var/log/pacman.log:
[2013-07-22 11:03] [PACMAN] Running 'pacman --color=always -Syu extundelete'
[2013-07-22 11:03] [PACMAN] synchronizing package lists
[2013-07-22 11:03] [PACMAN] starting full system upgrade
[2013-07-22 11:06] [PACMAN] installed extundelete (0.2.4-1)
[2013-07-22 11:06] [PACMAN] upgraded libxfont (1.4.5-1 -> 1.4.6-1)
[2013-07-22 11:07] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-07-22 11:07] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Starting build: 3.10.2-1-ARCH
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Starting build: 3.10.2-1-ARCH
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-07-22 11:07] [PACMAN] upgraded linux (3.10.1-1 -> 3.10.2-1)
[2013-07-22 11:07] [PACMAN] upgraded linux-headers (3.10.1-1 -> 3.10.2-1)
[2013-07-22 11:07] [PACMAN] upgraded lirc-utils (1:0.9.0-51 -> 1:0.9.0-52)
Then, because I am on a UEFI system, I copied the initrd images and the vmlinuz image over to my ESP (just like I've done many a time before), and now the system won't boot. It doesn't throw any errors; rather, as soon as UEFI selects the entry to run, the computer just sits there (there is nothing in the logs so far as I can find).
I've booted with a live medium and I've tried regenerating the images and recopying them (the checksums of the images changed, so I figured that might do the trick), but it's still a no-go. Is there something obvious that I'm missing? Has anyone else run into this problem?
[Edit]: Though this appeared to be solved with 3.10.3, the problem appears to have returned with 3.10.8. No actual solution has been found. As with before, a new kernel has been released (3.10.9) with which this issue does not exist…
All the best,
-HG
Last edited by HalosGhost (2013-08-21 17:01:46)

So I added /boot to my fstab with option "auto" to not rely on the systemd-efi-generator and /boot was mounted just fine. Then I set noauto,x-systemd.automount and the autofs mount point was created as expected. Then I removed the /boot entry in fstab again and the systemd-efi-generator seems to work fine again...
I'm seriously confused right now...
btw, I did all of this mit kernel 3.9.9 booted. 3.10.2 doesn't boot on my system, it's the famous ""EFI machine randomly hangs while loading kernel" bug again. But this shouldn't have anything to do with the kernel install problem...
edit: I just realized that my "btw" is actually what OP describes. I should have read the thread completely, sorry
Either way, as far as I can see these are two separate issues. The EFI bug with the long thread that I mentioned above and the fact that /boot seems to not mount in some cases. I did some more testing regarding this, but I still have no idea what is happening. I could have sworn there was no automount point set up by systemd at some point, which would have made sense. But I can't reproduce it anymore...
Last edited by 65kid (2013-07-23 21:54:55)

[SOLVED] [GRUB error] "no such device" "vmlinuz-linux not found"

SOLUTION AT POST #11
I just completed the install process onto a new machine. Grub starts but then returns these error messages.
Booting 'Arch GNU/Linux, with Linux core repo kernel'
error: no such device: ad4103fa-d940-47ca-8506-301d8071d467.
Loading Linux core repo kernel ...
error: file '/boot/vmlinuz-linux' not found.
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue...
I installed Arch via a flashdrive (sdb), onto SATA port 1 (sda). SDA has a fresh MBR. Unfortunately, I have no way to post my grub config files. What files must I modify to get GRUB to work properly?
fstab: http://sprunge.us/SVMi
grub.cfg: http://sprunge.us/hQCB
Edit: Thread solved.
Last edited by qKUqm3wtY4 (2013-01-31 03:36:43)

SOLUTION
by: jynnantonix
Step 1: Start Arch via boot disc.
Step 2: Connect to internet.
Step 3: Mount partitions.
# swapon dev/sdX
# mount /dev/sdX /mnt
# mount /dev/sdX /mnt/home
# mount /dev/sdX /mnt/boot
Step 4: Chroot
# arch-chroot /mnt
Step 5: Remake grub.conf
# grub-mkconfig -o /boot/grub/grub.cfg
Another Notable Tip by: jynnantonix
If you need to post information from terminal to the internet, use the following:
[insert command here] | curl -F 'sprunge=<-' http://sprunge.us
example: ls -l /dev/disk/by-uuid/ | curl -F 'sprunge=<-' http://sprunge.us
example: cat /boot/grub/grub.cfg | curl -F 'sprunge=<-' http://sprunge.us
Last edited by qKUqm3wtY4 (2013-01-31 04:04:49)

[SOLVED] rEFInd -- Error: Not Found while loading vmlinuz-linux

System Info:
3.14.1-1-ARCH
refind-efi-0.7.8-1
Problem: rEFInd does not boot arch linux.
When booting the machine, rEFInd's gui selection menu presents options for windows or linux.
Upon selecting linux, the following is displayed:
rEFInd - Booting OS
Starting vmlinuz-linux
Using load options 'ro root=UUID=bd6b3352-1b79-4c70-a061-21ff87ff0772 initrd=\boot\initramfs-linux.img'
Invalid loader file!
Error: Not Found while loading vmlinuz-linux
* Hit any key to continue *
Below are the outputs of blkid, lsblk -f, the structure of /boot and cats of /boot/efi/EFI/refind/refind.conf and /boot/refind_linux.conf
blkid
/dev/sda1: UUID="2014-05-01-05-20-54-00" LABEL="ARCH_201405" TYPE="iso9660" PTUUID="1535e446" PTTYPE="dos" PARTUUID="1535e446-01"
/dev/sda2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="96ED-5DA9" TYPE="vfat" PARTUUID="1535e446-02"
/dev/sdb1: LABEL="Recovery" UUID="E63202B832028E2D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e3729f62-9c32-4ac9-a9dd-56a9c073e7e5"
/dev/sdb2: UUID="9C03-552D" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9bcdb083-82e9-49e6-b03d-fd376585d633"
/dev/sdb4: UUID="B2161962161928BD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6de10de9-3322-486c-8108-bf14f5a7bcb6"
/dev/sdb5: UUID="bd6b3352-1b79-4c70-a061-21ff87ff0772" TYPE="ext4" PARTLABEL="root" PARTUUID="699115b1-1413-42b3-9fd7-a80a8a51b6fa"
/dev/sdb6: UUID="e71e6a25-913a-4932-9fc9-81942a5dab2e" TYPE="ext4" PARTLABEL="home" PARTUUID="1fc33e24-4c26-459c-a80a-9440e1f4e683"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="f07bfb26-3377-487a-a022-efd840614a0d" TYPE="ext4"
/dev/loop2: UUID="f07bfb26-3377-487a-a022-efd840614a0d" TYPE="ext4"
/dev/mapper/arch_root-image: UUID="f07bfb26-3377-487a-a022-efd840614a0d" TYPE="ext4"
/dev/sdb3: PARTLABEL="Microsoft reserved partition" PARTUUID="fa94c812-e1ff-4603-ba97-be7f155f12c8"
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sdb
├─sdb1
├─sdb2 /boot/efi
├─sdb3
├─sdb4
├─sdb5 /
└─sdb6 /home
sdc
├─sdc1
└─sdc2
loop0
loop1
└─arch_root-image /etc/resolv.conf
loop2
└─arch_root-image /etc/resolv.conf
Structure of /boot
*note: /boot is really the original microsoft efi system partition (in my case, /dev/sda2) that I mounted to /boot/efi and whose structure is shown below:
/boot
├── efi
│ ├── EFI
│ │ ├── Boot
│ │ │ └── bootx64.efi
│ │ ├── Microsoft
│ │ │ └── Boot
│ │ │ ├── BCD
│ │ │ ├── BCD.LOG
│ │ │ ├── BCD.LOG1
│ │ │ ├── BCD.LOG2
│ │ │ ├── bg-BG
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── bootmgfw.efi
│ │ │ ├── bootmgr.efi
│ │ │ ├── BOOTSTAT.DAT
│ │ │ ├── boot.stl
│ │ │ ├── en-US
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── Fonts
│ │ │ │ ├── {{FONTS REMOVED FOR BREVITY}}
│ │ │ ├── Resources
│ │ │ │ ├── bootres.dll
│ │ │ │ └── en-US
│ │ │ │ └── bootres.dll.mui
│ │ ├── refind
│ │ │ ├── drivers_x64
│ │ │ │ └── ext4_x64.efi
│ │ │ ├── icons
│ │ │ │ ├── {{ICONS REMOVED FOR BREVITY}}
│ │ │ ├── keys
│ │ │ │ ├── altlinux.cer
│ │ │ │ ├── canonical-uefi-ca.der
│ │ │ │ ├── fedora-ca.cer
│ │ │ │ ├── openSUSE-UEFI-CA-Certificate.cer
│ │ │ │ ├── refind.cer
│ │ │ │ └── SLES-UEFI-CA-Certificate.cer
│ │ │ ├── refind.conf <=================== http://ix.io/cFy
│ │ │ └── refind_x64.efi
│ │ └── tools
│ ├── initramfs-linux-fallback.img
│ ├── initramfs-linux.img
│ └── vmlinuz-linux
└── refind_linux.conf <===================== http://ix.io/cFw
49 directories, 190 files
Excerpt of /boot/efi/EFI/refind/refind.conf
(full file available here: http://ix.io/cFy)
menuentry Linux {
icon EFI/refind/icons/os_arch.icns
volume "EFI system partition"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "ro root=UUID=bd6b3352-1b79-4c70-a061-21ff87ff0772"
cat /boot/refind_linux.conf
"Boot with standard options" "ro root=UUID=bd6b3352-1b79-4c70-a061-21ff87ff0772 "
"Boot to single-user mode" "ro root=UUID=bd6b3352-1b79-4c70-a061-21ff87ff0772 single"
"Boot with minimal options" "ro root=UUID=bd6b3352-1b79-4c70-a061-21ff87ff0772"
Last edited by dk0r (2014-05-28 01:36:16)

A couple of things that are important:
refind_linux.conf should be in the same directory as vmlinuz-linux and the initrd so it should be in /boot/ since that is where your kernel is.
In your refind.conf stanza you have the line volume "EFI system partition" which tells rEFInd that the loader is in that partition whereas the kernel and initrd files seem to be in /boot/ which is not the EFI System Partition. Hence the volume line needs to specify the filesystem where /boot is which in your case appears to be /dev/sdb5 so the volume line in that case should be volume "root" since root is the filesystem label for sdb5? Note that if you update to rEFInd version 0.8.0 or later then you can use the partuuid value to specify the volume but in the version you are using that token for the volume was not yet implemented.
In the stanza you quoted there was no terminating } but maybe you just didn't copy it to your post.
Making these changes may let the system boot to the arch kernel.
Last edited by mcloaked (2014-05-27 20:21:16)

[Solved] Error boot after upgrading and util-linux-tools and sysvinit

Hi all ...
This morning I did a sudo pacman -Syu to update my laptop which packs sysvinit-tools 2.88-8 and 2.22-6 util-linux packages including ...
My surprise that I take is that a few hours ago after starting my laptop again I come across a series of error messages which do not allow me log into the laptop. catches of messages are these:
Picture 1
Picture 2
The log of pacman to upgrade is:
[09.24.2012 9:01] Running 'pacman-Syu'
[09.24.2012 9:01] synchronizing package lists
[09.24.2012 9:03] starting full system upgrade
[09.24.2012 9:21] removed eject (2.1.5-7)
[09.24.2012 9:22] upgraded coreutils (8.17-3 -> 8.19-1)
[09.24.2012 9:22] upgraded libmtp (1.1.4-1 -> 1.1.5-1)
[09.24.2012 9:22] upgraded mlocate (0.25-2 -> 0.26 to 1)
[09.24.2012 9:22] upgraded procps-ng (3.3.3-3 -> 3.3.3-6)
[09.24.2012 9:22] upgraded qt (4.8.3-2 -> 4.8.3-3)
[09.24.2012 9:22] upgraded util-linux (2.21.2-5 -> 2.22-6)
[09.24.2012 9:22] upgraded sysvinit-tools (2.88-7 -> 2.88-8)
[09.24.2012 9:22] upgraded transmission-gtk (2.61-3 -> 2.61-4)
[09.24.2012 9:22] upgraded whois (5.0.18-1 -> 5.0.19-1)
In making this latest update pacman eject told me that was going to be replaced by util-linux ... before answering affirmatively check the official website of ArchLinux to see if there were any announcement about this change ... I assumed there was none like it was nothing critical and permitted the installation of this patch ....
At the end of the error message you see in the pictures I show that I can run a command or shortcut systemctl keyboard to enter the "default mode" but I have no way to give commands and keyboard shortcut does not work.
No I could do to recover the system (other than reinstalling ArchLinux with new. Iso) ...
Someone has spent the same??? found a solution???
Greetings and thanks in advance!
Sorry my bad English!
Last edited by jesusangelm (2012-09-25 18:12:20)

in another forum recommended me to downgrade the updated packages to restore the system and use it.
but installing the updated packages I get this error
If I try the downgrade util-linux gives me:
pacman -U /var/cache/pacman/pkg/util-linux-2.21.2-5-x86_64.pkg.tar.xz
loading packages...
warning: downgrading package util-linux (2.22-6 => 2.21.2-5)
resolving dependencies...
looking for inter-conflicts...
Targets (1): util-linux-2.21.2-5
Total Installed Size: 7.45 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [############################################] 100%
(1/1) loading package files [############################################] 100%
(1/1) checking for file conflicts [############################################] 100%
error: failed to commit transaction (conflicting files)
util-linux: /bin/dmesg exists in filesystem
util-linux: /bin/findmnt exists in filesystem
util-linux: /bin/login exists in filesystem
util-linux: /bin/lsblk exists in filesystem
util-linux: /bin/more exists in filesystem
util-linux: /bin/mount exists in filesystem
util-linux: /bin/mountpoint exists in filesystem
util-linux: /bin/umount exists in filesystem
util-linux: /sbin/agetty exists in filesystem
util-linux: /sbin/blkid exists in filesystem
util-linux: /sbin/blockdev exists in filesystem
util-linux: /sbin/cfdisk exists in filesystem
util-linux: /sbin/chcpu exists in filesystem
util-linux: /sbin/ctrlaltdel exists in filesystem
util-linux: /sbin/fdisk exists in filesystem
util-linux: /sbin/findfs exists in filesystem
util-linux: /sbin/fsck exists in filesystem
util-linux: /sbin/fsck.cramfs exists in filesystem
util-linux: /sbin/fsck.minix exists in filesystem
util-linux: /sbin/fsfreeze exists in filesystem
util-linux: /sbin/fstrim exists in filesystem
util-linux: /sbin/hwclock exists in filesystem
util-linux: /sbin/losetup exists in filesystem
util-linux: /sbin/mkfs exists in filesystem
util-linux: /sbin/mkfs.bfs exists in filesystem
util-linux: /sbin/mkfs.cramfs exists in filesystem
util-linux: /sbin/mkfs.minix exists in filesystem
util-linux: /sbin/mkswap exists in filesystem
util-linux: /sbin/pivot_root exists in filesystem
util-linux: /sbin/raw exists in filesystem
util-linux: /sbin/sfdisk exists in filesystem
util-linux: /sbin/swaplabel exists in filesystem
util-linux: /sbin/swapoff exists in filesystem
util-linux: /sbin/swapon exists in filesystem
util-linux: /sbin/switch_root exists in filesystem
util-linux: /sbin/wipefs exists in filesystem
util-linux: /usr/bin/cal exists in filesystem
util-linux: /usr/bin/chfn exists in filesystem
util-linux: /usr/bin/chrt exists in filesystem
util-linux: /usr/bin/chsh exists in filesystem
util-linux: /usr/bin/col exists in filesystem
util-linux: /usr/bin/colcrt exists in filesystem
util-linux: /usr/bin/colrm exists in filesystem
util-linux: /usr/bin/column exists in filesystem
util-linux: /usr/bin/cytune exists in filesystem
util-linux: /usr/bin/fallocate exists in filesystem
util-linux: /usr/bin/flock exists in filesystem
util-linux: /usr/bin/getopt exists in filesystem
util-linux: /usr/bin/hexdump exists in filesystem
util-linux: /usr/bin/i386 exists in filesystem
util-linux: /usr/bin/ionice exists in filesystem
util-linux: /usr/bin/ipcmk exists in filesystem
util-linux: /usr/bin/ipcrm exists in filesystem
util-linux: /usr/bin/ipcs exists in filesystem
util-linux: /usr/bin/isosize exists in filesystem
util-linux: /usr/bin/linux32 exists in filesystem
util-linux: /usr/bin/linux64 exists in filesystem
util-linux: /usr/bin/logger exists in filesystem
util-linux: /usr/bin/look exists in filesystem
util-linux: /usr/bin/lscpu exists in filesystem
util-linux: /usr/bin/mcookie exists in filesystem
util-linux: /usr/bin/namei exists in filesystem
util-linux: /usr/bin/newgrp exists in filesystem
util-linux: /usr/bin/pg exists in filesystem
util-linux: /usr/bin/prlimit exists in filesystem
util-linux: /usr/bin/rename exists in filesystem
util-linux: /usr/bin/renice exists in filesystem
util-linux: /usr/bin/rev exists in filesystem
util-linux: /usr/bin/script exists in filesystem
util-linux: /usr/bin/scriptreplay exists in filesystem
util-linux: /usr/bin/setarch exists in filesystem
util-linux: /usr/bin/setsid exists in filesystem
util-linux: /usr/bin/setterm exists in filesystem
util-linux: /usr/bin/tailf exists in filesystem
util-linux: /usr/bin/taskset exists in filesystem
util-linux: /usr/bin/ul exists in filesystem
util-linux: /usr/bin/unshare exists in filesystem
util-linux: /usr/bin/uuidgen exists in filesystem
util-linux: /usr/bin/whereis exists in filesystem
util-linux: /usr/bin/write exists in filesystem
util-linux: /usr/bin/x86_64 exists in filesystem
util-linux: /usr/include/blkid/blkid.h exists in filesystem
util-linux: /usr/include/libmount/libmount.h exists in filesystem
util-linux: /usr/include/uuid/uuid.h exists in filesystem
util-linux: /usr/lib/libblkid.a exists in filesystem
util-linux: /usr/lib/libblkid.so exists in filesystem
util-linux: /usr/lib/libblkid.so.1 exists in filesystem
util-linux: /usr/lib/libblkid.so.1.1.0 exists in filesystem
util-linux: /usr/lib/libmount.a exists in filesystem
util-linux: /usr/lib/libmount.so exists in filesystem
util-linux: /usr/lib/libmount.so.1 exists in filesystem
util-linux: /usr/lib/libmount.so.1.1.0 exists in filesystem
util-linux: /usr/lib/libuuid.a exists in filesystem
util-linux: /usr/lib/libuuid.so exists in filesystem
util-linux: /usr/lib/libuuid.so.1 exists in filesystem
util-linux: /usr/lib/libuuid.so.1.3.0 exists in filesystem
util-linux: /usr/lib/pkgconfig/blkid.pc exists in filesystem
util-linux: /usr/lib/pkgconfig/mount.pc exists in filesystem
util-linux: /usr/lib/pkgconfig/uuid.pc exists in filesystem
util-linux: /usr/sbin/addpart exists in filesystem
util-linux: /usr/sbin/delpart exists in filesystem
util-linux: /usr/sbin/fdformat exists in filesystem
util-linux: /usr/sbin/ldattach exists in filesystem
util-linux: /usr/sbin/partx exists in filesystem
util-linux: /usr/sbin/readprofile exists in filesystem
util-linux: /usr/sbin/rtcwake exists in filesystem
util-linux: /usr/sbin/tunelp exists in filesystem
util-linux: /usr/sbin/uuidd exists in filesystem
util-linux: /usr/sbin/vigr exists in filesystem
util-linux: /usr/sbin/vipw exists in filesystem
util-linux: /usr/share/getopt/getopt-parse.bash exists in filesystem
util-linux: /usr/share/getopt/getopt-parse.tcsh exists in filesystem
util-linux: /usr/share/locale/ca/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/cs/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/da/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/de/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/es/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/et/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/eu/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/fi/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/fr/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/gl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/hu/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/id/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/it/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/ja/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/nl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/pl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/pt_BR/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/ru/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/sl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/sv/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/tr/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/uk/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/vi/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/zh_CN/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/zh_TW/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/man/man1/cal.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chrt.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
util-linux: /usr/share/man/man1/col.1.gz exists in filesystem
util-linux: /usr/share/man/man1/colcrt.1.gz exists in filesystem
util-linux: /usr/share/man/man1/colrm.1.gz exists in filesystem
util-linux: /usr/share/man/man1/column.1.gz exists in filesystem
util-linux: /usr/share/man/man1/dmesg.1.gz exists in filesystem
util-linux: /usr/share/man/man1/fallocate.1.gz exists in filesystem
util-linux: /usr/share/man/man1/flock.1.gz exists in filesystem
util-linux: /usr/share/man/man1/getopt.1.gz exists in filesystem
util-linux: /usr/share/man/man1/hexdump.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ionice.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ipcmk.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ipcrm.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ipcs.1.gz exists in filesystem
util-linux: /usr/share/man/man1/logger.1.gz exists in filesystem
util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
util-linux: /usr/share/man/man1/look.1.gz exists in filesystem
util-linux: /usr/share/man/man1/lscpu.1.gz exists in filesystem
util-linux: /usr/share/man/man1/mcookie.1.gz exists in filesystem
util-linux: /usr/share/man/man1/more.1.gz exists in filesystem
util-linux: /usr/share/man/man1/mountpoint.1.gz exists in filesystem
util-linux: /usr/share/man/man1/namei.1.gz exists in filesystem
util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
util-linux: /usr/share/man/man1/pg.1.gz exists in filesystem
util-linux: /usr/share/man/man1/prlimit.1.gz exists in filesystem
util-linux: /usr/share/man/man1/rename.1.gz exists in filesystem
util-linux: /usr/share/man/man1/renice.1.gz exists in filesystem
util-linux: /usr/share/man/man1/rev.1.gz exists in filesystem
util-linux: /usr/share/man/man1/script.1.gz exists in filesystem
util-linux: /usr/share/man/man1/scriptreplay.1.gz exists in filesystem
util-linux: /usr/share/man/man1/setsid.1.gz exists in filesystem
util-linux: /usr/share/man/man1/setterm.1.gz exists in filesystem
util-linux: /usr/share/man/man1/tailf.1.gz exists in filesystem
util-linux: /usr/share/man/man1/taskset.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ul.1.gz exists in filesystem
util-linux: /usr/share/man/man1/unshare.1.gz exists in filesystem
util-linux: /usr/share/man/man1/uuidgen.1.gz exists in filesystem
util-linux: /usr/share/man/man1/whereis.1.gz exists in filesystem
util-linux: /usr/share/man/man1/write.1.gz exists in filesystem
util-linux: /usr/share/man/man3/libblkid.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_clear.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_compare.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_copy.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate_random.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate_time.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate_time_safe.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_is_null.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_parse.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_time.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_unparse.3.gz exists in filesystem
util-linux: /usr/share/man/man5/fstab.5.gz exists in filesystem
util-linux: /usr/share/man/man8/addpart.8.gz exists in filesystem
util-linux: /usr/share/man/man8/agetty.8.gz exists in filesystem
util-linux: /usr/share/man/man8/blkid.8.gz exists in filesystem
util-linux: /usr/share/man/man8/blockdev.8.gz exists in filesystem
util-linux: /usr/share/man/man8/cfdisk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/chcpu.8.gz exists in filesystem
util-linux: /usr/share/man/man8/ctrlaltdel.8.gz exists in filesystem
util-linux: /usr/share/man/man8/cytune.8.gz exists in filesystem
util-linux: /usr/share/man/man8/delpart.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fdformat.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fdisk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/findfs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/findmnt.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fsck.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fsck.minix.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fsfreeze.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fstrim.8.gz exists in filesystem
util-linux: /usr/share/man/man8/hwclock.8.gz exists in filesystem
util-linux: /usr/share/man/man8/i386.8.gz exists in filesystem
util-linux: /usr/share/man/man8/isosize.8.gz exists in filesystem
util-linux: /usr/share/man/man8/ldattach.8.gz exists in filesystem
util-linux: /usr/share/man/man8/linux32.8.gz exists in filesystem
util-linux: /usr/share/man/man8/linux64.8.gz exists in filesystem
util-linux: /usr/share/man/man8/losetup.8.gz exists in filesystem
util-linux: /usr/share/man/man8/lsblk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkfs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkfs.bfs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkfs.minix.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkswap.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mount.8.gz exists in filesystem
util-linux: /usr/share/man/man8/partx.8.gz exists in filesystem
util-linux: /usr/share/man/man8/pivot_root.8.gz exists in filesystem
util-linux: /usr/share/man/man8/raw.8.gz exists in filesystem
util-linux: /usr/share/man/man8/readprofile.8.gz exists in filesystem
util-linux: /usr/share/man/man8/rtcwake.8.gz exists in filesystem
util-linux: /usr/share/man/man8/setarch.8.gz exists in filesystem
util-linux: /usr/share/man/man8/sfdisk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/swaplabel.8.gz exists in filesystem
util-linux: /usr/share/man/man8/swapoff.8.gz exists in filesystem
util-linux: /usr/share/man/man8/swapon.8.gz exists in filesystem
util-linux: /usr/share/man/man8/switch_root.8.gz exists in filesystem
util-linux: /usr/share/man/man8/tunelp.8.gz exists in filesystem
util-linux: /usr/share/man/man8/umount.8.gz exists in filesystem
util-linux: /usr/share/man/man8/uuidd.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
util-linux: /usr/share/man/man8/wipefs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/x86_64.8.gz exists in filesystem
Errors occurred, no packages were upgraded.
If I try the downgrade sysvinit-tool gives me:
pacman -U /var/cache/pacman/pkg/sysvinit-tools-2.88-7-x86_64.pkg.tar.xz
loading packages...
warning: downgrading package sysvinit-tools (2.88-8 => 2.88-7)
resolving dependencies...
looking for inter-conflicts...
Targets (1): sysvinit-tools-2.88-7
Total Installed Size: 0.17 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [############################################] 100%
(1/1) loading package files [############################################] 100%
(1/1) checking for file conflicts [############################################] 100%
error: failed to commit transaction (conflicting files)
sysvinit-tools: /bin/pidof exists in filesystem
sysvinit-tools: /sbin/bootlogd exists in filesystem
sysvinit-tools: /sbin/fstab-decode exists in filesystem
sysvinit-tools: /sbin/killall5 exists in filesystem
sysvinit-tools: /sbin/sulogin exists in filesystem
sysvinit-tools: /usr/bin/last exists in filesystem
sysvinit-tools: /usr/bin/lastb exists in filesystem
sysvinit-tools: /usr/bin/mesg exists in filesystem
sysvinit-tools: /usr/bin/utmpdump exists in filesystem
sysvinit-tools: /usr/bin/wall exists in filesystem
sysvinit-tools: /usr/include/initreq.h exists in filesystem
sysvinit-tools: /usr/share/man/man1/last.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/lastb.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/mesg.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/utmpdump.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/wall.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/bootlogd.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/fstab-decode.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/killall5.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/pidof.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/sulogin.8.gz exists in filesystem
Errors occurred, no packages were upgraded.
If I try the downgrade eject gives me:
pacman -U /var/cache/pacman/pkg/eject-2.1.5-7-x86_64.pkg.tar.xz
loading packages...
resolving dependencies...
looking for inter-conflicts...
Targets (1): eject-2.1.5-7
Total Installed Size: 0.14 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [############################################] 100%
(1/1) loading package files [############################################] 100%
(1/1) checking for file conflicts [############################################] 100%
error: failed to commit transaction (conflicting files)
eject: /usr/bin/eject exists in filesystem
eject: /usr/share/man/man1/eject.1.gz exists in filesystem
Errors occurred, no packages were upgraded.

[SOLVED] linux: /boot/vmlinuz-linux exists in filesystem

Similar Messages

Maybe you are looking for