[SOLVED] Mount /boot/efi fails after linux-....pkg.tar.xz upgrade

Can anyone help with this please? Sorry if it's a well known issue and I have just failed to find the solution, but I have searched for one.
I use yaourt -Syu regularly, and generally it's great.
BUT - every time linux-3.17...-x86_64.pkg.tar.xz is upgraded the system fails to reboot! Throwing something like:
Nov 17 16:09:49 cart systemd[1]: boot-efi.mount mount process exited, code=exited status=32
Nov 17 16:09:49 cart systemd[1]: Failed to mount /boot/efi.
Nov 17 16:09:49 cart systemd[1]: Unit boot-efi.mount entered failed state.
Nov 17 16:09:49 cart mount[232]: mount: unknown filesystem type 'vfat'
After much struggling I have discovered a workaround, but I don't understand it - or like it. This is what I do:
1. Boot from an archiso image cd in UEFI mode
2. Mount the correct partitions on / /home and /boot
3. # arch-chroot /mnt /bin/bash
4. # cd /var/cache/pacman/pkg
5. # pacman -U linux-3.16.3-1-x86_64.pkg.tar.xz (or whatever is the latest upgrade)
Then, when I exit and reboot all is well again.
I use the rEFInd boot manager to choose between ArchLinux and ,reluctantly, Windows 8.1 - I suspect that might have something to do with my problem but I don't know what.
If anyone can tell what I am doing wrong, please explain.
Thanks
John
Last edited by JohnColeman (2014-11-18 15:58:51)

Hi Matt,
I think you've done it - thanks a lot.
I changed this line in my /etc/fstab :
UUID=0E51-F605 /boot/efi vfat ...
to
UUID=0E51-F605 /boot vfat ...
and I think that's done the trick.
I did pacman -U linux-3.16.3-1-x86_64.pkg.tar.xz again without booting from an archiso image cd in UEFI mode, which would previously have failed - and it didn't.
I look forward to the next actual upgrade of linux-3...
Thanks again, I can't remember how, or why, I went wrong in fstab but I won't do it again.
John

Similar Messages

[Solved] Failed to mount /boot/efi

Hi,
Recently I've been having a lot of trouble starting Arch Linux. As in I can't. It starts off fine, but then whike it tries to mount my disks I get this problem:
systemd-fsck[159]: fsck.fat 3.0.23 (2013-10-15)
systemd-fsck[159]: /dev/sda5: 111 files, 6783/130048 clusters
[ OK ] Started File System Check on /dev/disk/by-uuid/6AE1-65C8.
Mounting /boot/efi...
[ FAILED ] Failed to mount /boot/efi.
See 'systemctl status boot-efi.mount' for details.
[ DEPEND ] Dependency failed for Local File Systems.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
This is the output of systemctl status boot-efi.mount:
boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Sun 2013-12-01 17:40:58 EST; 4min 16s ago
Where: /boot/efi
What: /dev/disk/by-uuid/6AE1-65C8
Process: 179 ExecMount=/bin/mount /dev/disk/by-uuid/6AE1-65C8 /boot/efi -t vfat -o rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro (code=exited, status=32)
Dec 01 17:40:58 jay-archlinux systemd[1]: boot-efi.mount mount process exited, code=exited status=32
Dec 01 17:40:58 jay-archlinux systemd[1]: Failed to mount /boot/efi
Dec 01 17:40:58 jay-archlinux systemd[1]: Unit boot-efi.mount entered failed state.
The output of mount /dev/disk/by-uuid/6AE1-65C8 /boot/efi -t vfat:
mount: unknown filesystem type: 'vfat'
(When I first started getting this it told me dosfstools wasn't installed. However I've since installed the latest version and it's made no difference.
I dual boot Arch Linux and Windows 8 on a laptop under UEFI, and have had this setup for about a year now. This problem seems like it may be associated with recent problems I've been having with windows 8 (Spontaneously restarting itself 2 or 3 times a day with a BSoD and "Kernel Data Inpage Error".) One time after such a restart I went to boot Arch Linux after the restart rather than Windows and got errors similar to the one I first posted, except that they were occurring with my Windows NTFS partitions which I mount in Arch Linux. After booting into Windows and restarting manually, the error just became what it is now. However I'm not sure if this was where the problem first began or not as I haven't used Arch Linux very often over the past few months.
Does anyone have any idea what's going on or how to fix it?
Thanks.
Last edited by jdgordon01 (2013-12-01 14:05:59)

pacman -Q linux
linux 3.11.6-1
uname -a
3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:45:16 CEST 2013 x86_64 GNU/Linux
No idea how that's happened... I initially tried 'mkinitcpio -p linux' but it also did nothing.
EDIT: Turns out I must have updated at some point and forgotten a crucial step in manually copying the new files in /boot/ to /boot/efi/EFI/arch/ which is necessary when updating under UEFI systems. I updated again using the live USB/chrooting, manually copied everything that was needed and everything's working again!
Last edited by jdgordon01 (2013-12-01 14:05:35)

Boot-up fails after pacman update

Recent update of many pkgs failed to load after downloading.
The boot stops at :
Archlinux 0.7 (wombat) [(none)] (vc/1)
(none) login:
Attempts to login fail (probably because I don't know what should go for login)
The hdd can be addressed from another hdd boot-up and all partitions accessed.
It just won't finish boot. :cry:

As posted previously, a recent upgrade was followed by a failure to load the downloaded packages. None of these packages were kernel upgrades and lilo run would not be necessary thereafter.
My fstab and rc.conf follow:#
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
#/dev/#EXT2FS_BOOT# /boot ext2 defaults 0 1
#/dev/#REISERFS_ROOT# / reiserfs defaults 0 0
#/dev/#EXT2FS_ROOT# / ext2 defaults 0 1
#/dev/#SWAP# swap swap defaults 0 0
#/dev/#REISERFS_HOME# /home reiserfs defaults 0 0
#/dev/#EXT2FS_HOME# /home ext2 defaults 0 2
/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd iso9660 rw,user,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat user,noauto,unhide 0 0
none /dev/pts devpts defaults 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs size=2G,nr_inodes=10k 0 0
/dev/discs/disc0/part3 / ext3 rw,users,exec 0 0
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
/dev/discs/disc1/part3 /mnt/drive ext3 rw,users,exec 0 0
/dev/discs/disc1/part1 /mnt/fat1 vfat defaults 0 0
/dev/sdb1 /mnt/fat3 vfat defaults 0 0
/dev/sda1 /mnt/fat2 vfat defaults 0 0
/dev/sda3 /mnt/drive ext3 defaults 0 0
# /etc/rc.conf - Main Configuration for Arch Linux
# Localization
# Note: HARDWARECLOCK is either "UTC" or "localtime"
KEYMAP=us
TIMEZONE=Canada/Pacific
HARDWARECLOCK="localtime"
# Networking
HOSTNAME="n6re"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(!usbserial !ide-scsi ne2k-pci snd-cmipci
usb-storage sd_mod sr_mod)
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="eth0 216.86.214.121 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 216.86.214.1"
ROUTES=(gateway)
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(!pcmcia network crond syslogd klogd kdm)
# End of file
The above files are from the affected HDD.
I note that (none)login: appears with an ID name in place of (none) in this clone HDD when opting for console login from the kde window options, so that element is missing in the other hard drive.
How to replace (none) with the right ID is the problem solution.

[SOLVED] Font render/refresh fail after upgrade

After upgrading last Thursday some applications have trouble rendering or refreshing text.
LibreOffice
Claws-Mail
In claws-mail, I do see some of the text re-appear after scrolling. For LibreOffice the problem only manifests itself in the menu bar, not in the document contents.
I don't think it's related to the OpenJDK bug mentioned on this board since claws-mail doesn't depend on OpenJDK.
Can anyone give pointers on where to investigate the cause of this problem?
Update: problem seems xrandr/dual-screen related, see my later comment.
Final update: xf86-video-intel was the culprit, see my steps for downgrading.
Last edited by wlen (2014-06-23 12:29:43)

Hooray, managed to find the cause.
Looked through all the packages that were upgraded on that day, you can find these in: /var/log/pacman.log
Then proceeded to downgrade all the packages related to video/fonts things that I recognised; 'intel-dri', all the '*mesa*' packages, 'wxgtk' and 'xf86-video-intel'. Tested after every downgrade, and it turned out only 'xf86-video-intel' caused the font render bug.
The upgrade in the log:
/var/log/pacman.log
[2014-06-18 02:21] [PACMAN] upgraded xf86-video-intel (2.99.911-2 -> 2.99.912-1)
The downgrade:
wget http://seblu.net/a/arm/packages/x/xf86-video-intel/xf86-video-intel-2.99.911-2-x86_64.pkg.tar.xz
sudo pacman -U xf86-video-intel-2.99.911-2-x86_64.pkg.tar.xz

[SOLVED]UEFI boot gives 'failed to install override security policy'

Hi, newb here who has hit a dead end quite early in the process of installing Arch.
When trying to boot Arch into EFI mode, it says
'failed to install override security policy'
Of course I did my research and it seems that only three other people on this planet have had the same problem, and their solutions do not work for me.
http://superuser.com/questions/615142/u … ity-policy
Overwriting EFI/boot/bootx64.efi with loader.efi enables me to see a menu where I can choose from booting Arch, UEFI shell v1 or UEFI shell v2. Still, selecting Arch results in a blank screen with two grey bars at the top and bottom of the screen, so not really not much help.
I'm not a UNIX nor an EFI wizard, so please bear with me. I'm a Windows user with some anecdotal Linux knowledge (I have installed Ubuntu countless times, wanted a bit of a challenge this time) who wanted to make the switch to the Linux ecosystem, but this error prevents me from doing so. I also tried to install rEFInd as suggested here: https://bbs.archlinux.org/viewtopic.php?id=174734
But I seem to be unable to boot into any UEFI shell v2, it's also printing the errors:
ASSERT_EFI_ERROR (Status = Not Found)
ASSERT C:\svn_code...and so on )
My Windows installation is on BIOS/MBR, so I cannot install rEFInd manually using Windows, and I also cannot use the v1 UEFI shell because of the lacking bcfg command. I don't know how to procede from here. My board is an AsRock P67 Extreme4 Rev 09 with a 2.10 EFI. This board doesn't even have Secure Boot if I'm correct, I also searched every possible submenu of the EFI for an option to disable Secure Boot, but haven't found anything.
Last edited by 0x33 (2015-03-11 17:35:56)

I presume you are trying to use gummiboot?
Please post the contents of /boot/loader/loader.conf and also your gummiboot configuration file for your Arch system (if you are not using gummiboot post the config. files for whichever boot loader/manager you are using).
Load the Arch live ISO, mount all your partitions and `arch-chroot` into your system and then post the output of:
lsblk -f
# parted -l
# efibootmgr -v
Last edited by Head_on_a_Stick (2015-03-10 21:05:43)

[SOLVED] KVM and Qemu fail after installation

I tried installing Windows 7 and Vista with both Qemu and KVM.
Installation goes fine but after Windows reboots during the installation I only get a strange screen after the bios. It shows some random characters, as shown in the image. I tried varying the filesystem (raw, qcow and qcow) and the memory size, etc. but nothing works, not even the standalone kvm project. Any suggestions?
I used the following code to install the OS:
qemu-img create -f qcow2 windows7.img 20G
qemu -enable-kvm -boot d -m 1500 -hda windows7.img -cdrom win7.iso
Last edited by Wilco (2009-11-29 08:26:59)

I had the same problem. i have tried many things (even -vga std) but that screen always appear at reboot. because i really wanted to give w7 a try i have tested another windows 7 iso. VERDICT : IT WORKS PERFECTLY. so, just try with another iso.

[SOLVED] Cannot boot from raid1 after upgrade

My system cannot boot from software raid(1) after upgrading the kernel to version 3.2.13-1. I realized then, that mkinitcpio.conf was overwritten (probably missed that in a previous upgrade). So I put back "mdadm" to HOOKS and "raid1" to MODULES. Unfortunately it didn't help. This is the boot-up screen:
Any ideas?
Last edited by dito (2012-03-28 13:10:52)

Thank you for your answer. I replaced the mdadm hook with mdadm_udev and updated my mdadm.conf. Removing the hd configuration stuff from grub then finally did the trick. Works again!

[SOLVED]wlanwep encryption is failing after system update(pacman -Syu)

After a system update with "pacman -Syu" my wlan encryption does not work anymore.
If I switch off encryption on my access point, I can communicate without any problems.
I have currently two wlans active, one with encryption, one without. I use the following iwconfig settings
iwconfig wlan0 essid my_open_wlan
iwconfig wlan0 essid my_wep_wlan key s:my_wep_password
In the first case I get the connection, in the second I cannot transmit over the network(Destination Host Unreachable).
lspci:
07:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
iwconfig:
wlan0 IEEE 802.11bgn ESSID:"wlan_2012"
Mode:Managed Frequency:2.437 GHz Access Point: 00:04:0E:57:4E:27
Bit Rate=1 Mb/s Tx-Power=13 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=39/70 Signal level=-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:44 Invalid misc:43 Missed beacon:0
ip addr:
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether ec:55:f9:1d:bf:41 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.11/24 brd 192.168.1.255 scope global wlan0
inet6 fe80::ee55:f9ff:fe1d:bf41/64 scope link
valid_lft forever preferred_lft forever
This is the output for the open wlan. If I try to connect to the encrypted wlan with "iwconfig wlan0 essid "my_encr_wlan" key s:my_wep_password", the iwconfig command gives me:
wlan0 IEEE 802.11bgn ESSID:"wlan_2007"
Mode:Managed Frequency:2.452 GHz Access Point: D8:5D:4C:FA:24:0D
Bit Rate=5.5 Mb/s Tx-Power=13 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=33/70 Signal level=-77 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:2 Invalid misc:1 Missed beacon:0
I have tried wpa_supplicant as well with the same result.
Can anybody give me hint?
Regards
Helmut
Last edited by helmut (2012-03-05 16:31:25)

Wep and ath9k has been buggy for me for a long time now - sometimes it works, sometimes it doesn't. Never got around it, adding "options ath9k nohwcrypt=1" into /etc/modprobe.d/ath9k.conf seemed to work for some time. You could give it a try. The network I have problems with is at the university, they use wep + vpn to connect. I can connect fine (like in your last iwconfig), but dhcpd times out.
If you have control over the network, you could just switch to wpa - safer anyway. Or search the forum for "atheros wep", it is a somewhat common problem I think.
P.S.: please use code tags when posting console output.
Last edited by hokasch (2012-02-18 14:48:24)

[SOLVED]mounting webdav share fails, cadaver works?

cadaver http://localhost/dav
dav:/dav/> mkcol test
Creating `test': succeeded.
dav:/dav/> ls
Listing collection `/dav/': succeeded.
Coll: test 0 Mar 8 16:59
mount -t davfs http://localhost:80/dav /tmp/test2
Please enter the username to authenticate with proxy
http or hit enter for none.
Username:
Please enter the username to authenticate with server
http://localhost:80/dav or hit enter for none.
Username:
/sbin/mount.davfs: connection timed out two times;
trying one last time
/sbin/mount.davfs: server temporarily unreachable;
mounting anyway
WTF?
ive used the webdav howto from archs wiki.
greets
Last edited by metalfan (2008-03-21 14:09:41)

works with davfs-1.3, ive filled a bug report.

IPhone 5S fingerprint reader fails after iOS 7.0.3 upgrade

Hi all.
I recently updated my iPhone 5S to IOS 7.0.3 and ever since then, I am struggling to unlock my phone every time. I press the home button and then I used to just leave my finger on the button and it would unlock. Now it just doesn't seem to recognise my finger is even there.
I lift my finger off and put it on again and nothing. I lift my finger off and actually press the button again and leave my finger there and sometime it unlocks, sometimes it doesn't. It doesn't even say "try again" it simply doesn't recognise I'm trying to unlock it. I'm ready to chuck the bloody thing at the wall!!
Has anybody else experienced this problem since updating to IOS 7.0.3?

I bought my iPhone 5s a few days ago. It came with 7.0.3. It works 100% of the time, but people were having trouble with it when they went from 7.0.2 to 7.0.3. A lot of times, when doing an upgrade, the fingerprint scanner problem can be solved with some simple troubleshooting skills:
Troubleshooting steps:
First, if you have never rebooted your phone after the update, it helps to reset your phone. This is just pressing and holding the home button + power button until the apple logo comes on the screen (the phone will power off and then on. When Apple logo appears, you can let go of both buttons).
If fingerprint scanner is still hit and miss, you should redo your finger prints by go to settings->general->touch id & passcode->touch id. Delete all saved fingerprints (swipe to the left and press delete). Add fingerprints again.
If it still doesn't work or still hit and miss, you can always reinstall the ios. This can be googled. For me, it is too much trouble, so I go to the next step..
Finally, if that's still no good, you can always take it back to the apple store. The warranty on it is a full year so it is free for them to just look at it and tell you if it's a hardware problem. I know cuz I have replaced my iPad, iPhone, and even my macbook this way. No, I don't do it on purpose, but apple products has flaws too. Especially if it is a hardware problem, I need it replaced - and since it is still under warranty, it is replaced for free. So I don't hesitate to stick it in their face. Well, don't be mean about it though. Just say it like it is without the attitude and they will do what they can to help you fix it.
Tips: when you replace your phone, they may or may not give you a "refurbished" phone. That's the only thing I don't like about replacing my apple things. BUT since iPhone 5s is so new, the chances of you receiving a refurbished phone is quite slim... Or so I was told. So don't wait.

R3trans Failing after SSFS Implementation during EHP Upgrade

Hi Experts,
I would need your urgent support and advice on my current issue.
I am upgrading my ECC 6 EHP6 to EHP7. In the extraction phase the SUM stopped and asked for a manual action, where it said oracle tools are unable to connect to database and i need to implement SSFS mechanism as per note 1622837. Please find my below system details.
SAP Version : EHP 6 NW 7.3
Database : Oracle 11G
OS : Windows
I have implemented SSFS as per 1622837 and 11639578. Now my R3trans is failing i.e R3trans -d is failing but R3trans -x is success.
Somewhere i smell that it could be an authorization issue but not sure. Kindly check my attached R3trans log and dev_wo log and advice a solution ASAP. Because of this the upgrade is stuck.
Thanks in advance
Regards,
Prithivi Raj

Hi Prithvi Raj,
Check the permissions of the SSFS direcotries it should be readable by your sidadm
check the key and data file in directories
. usr\sap\<SID>\SYS\global\security\rsecssfs\data
usr\sap\<SID>\SYS\global\security\rsecssfs\key
and has below environment parameters
Profile parameter : rsdb/ssfs_connect = 1
Environment variable: rsdb_ssfs_connect 1
Check this thread for reference.
http://scn.sap.com/community/oracle/blog/2013/07/23/ssfs-secure-storage-in-file-system-configuration-in-oracle-db-for-sap
Let us know the outcome of same.
Regards,
Ram

[Solved]dual boot windows 7 and arch linux

I have successfully installed arch linux dual boot with the original win7 on my PC. If I only use linux, then the system works well. The problem is that once I boot into Win7 then after reboot, the linux boot manager will stop working and the system always boots into windows automatically. My guess is Win7 automatically repair the boot loader.
My current solution is whenever I have finished using Windows, I'll boot with my linux USB installation, and run "gummiboot --path=/boot install". Afterwards, linux will work fine. But I believe there must be a better solution. Any help will be appreciated.
I have UEFI board by the way.
Last edited by jl2014 (2015-04-19 17:35:57)

Thanks for all your help first! I have tried Head_on_a_Stick's suggestions as the first step. Here is what I did. I have created :
$ cat /boot/loader/entries/windows.conf
title Windows
efi /EFI/hidden/Boot/bootmgfw.efi
The window boot path was :
/boot/EFI/Microsoft/Boot/bootmgfw.efi
and I changed
/boot/EFI/Microsoft
to
/boot/EFI/hidden
After reboot, I clicked 'Windows' option on the linux boot manager. Below are the error messages:
Windows failed to start.
File: \EFI\Microsoft/Boot/BCD
Info: An error occurred while attempting to read the boot configuration data.
Any idea what goes wrong?
I'll try other suggestions soon. Thanks all of you again.
Last edited by jl2014 (2015-04-19 00:03:33)

[solved] AMD Radeon - strange behaviour after mesa-update

Good afternoon Ladies and Gentlemen,
This is my first posting, I will try to give as much as detailed information refering to my problem as possible. Please be patient if I ask for solutions which for you all seem easy and logical, I am a Newbie.
The details: I am running a HP Pavilion 17 " AMD Quadcore laptop, 8gb Ram, Arch Linux 32bit Kernel 3.17.1 XFCE desktop with an AMD Radeon graphic card for about a few weeks now. Everything went fine so far, but last Saturday I did an update via pacman-Syu, the update included a mesa package. All went smooth as ever. Then after a reboot the XFCE desktop had stripes across the laptop screen, the mouse cursor had disappeared, also letters of the icon descriptions and the menus were missing, some strange "hieroglyphics" appeared instead of them. I wasn't able to downgrade the mesa-package as I nearly wasn't able to open the terminal because of the missing mouse cursor, then I managed somehow to get into the terminal and gave in the commands but the writing was incomplete and/or did not work because of these strange and missing letters.
No problem, I thought to myself, a fresh install will do the work, so I wipped my hard drive using Parted Magic, then I did a fresh Arch install (Netinstall), this time using LXDE instead of XFCE as my desktop environment. When I booted into the login screen first, it looked fine but after logging into the desktop all the stripes, the missing mouse cursor and the strange letters appeared again. So is there any solution to that strange behaviour ? Before the Saturday-update everything worked without any problems for weeks. BTW other OS work without these problems, I tried Macpup just for fun, no messing-up with my Radeon graphics card happened.
Sorry for my piss poor English I am Austrian. Sorry for eventually causing any inconvenience asking this question. Regards, Fladi.
Last edited by fladi (2014-11-04 05:01:28)

fafik1234 wrote:
I have the same problem, free drivers, xfce4, procesor AMD5350(Kabini), vga radeon R3 (8400)
downgrade linux kernel to linux-3.16.4
download: http://seblu.net/a/arm/packages/l/linux … pkg.tar.xz
pacma -U linux-3.16.4-1-i686.pkg.tar.xz
edit /etc/pacman.conf
IgnorePkg = linux linux-headers
screenshot
linux 3.17 xfce http://pics.tinypic.pl/i/00592/ek3z3ip81ky2.png
linux 3.17 compiz http://pics.tinypic.pl/i/00592/bddprwn4tey8.png
linux 3.16 compiz http://pics.tinypic.pl/i/00592/ja5ma8c7rdgl.png
On a laptop, free drivers, linux 3.17.1-pae, openbox, procesor core i5, vga integrated card - everything OK
The screenshots you posted match exactly to my problem ! Are you really sure the bug is coming from Kernel 3.17 ? I had this kernel running for about a week without any problems, the problems came when updating mesa.

[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] Arch failed to mount /boot

Hey there,
after my btrfs filesystem somehow got corrupted, so it would only mount my "/"-filesystem as read-only, I backed it up with rsync, recreated the partition and then transfered the data back. After that, I was unable to boot anymore with this error:
[1.593560] systemd-fsck[306]: fsck.fat 3.0.27 (2014-11-12)
[1.594292] systemd-fsck[306] /dev/sda1: 98 files, 43105/98304 clusters
Mounting boot...
[FAILED]Failed to mount /boot.
See "systemctl status boot.mount" for details
SystemD the prompted me with it's emergency mode, but this didn't react to any keyboard presses, so I couldn't check the exact error with sth. like journalctl -xb. I then booted a, today downloaded, Arch Live-CD and tried to access the logs via journalctl -b -D /var/log/journal/ didn't work out: It only had the logs from before the boot problem.
With a bit of googling I figured a way of fixing this could be chrooting in and reinstalling initramfs, typing chroot errored out with:
chroot: failed to run command /usr/bin/zsh: No such file or directory
I tried commenting out /boot in fstab, but at booting something [FAILED] with Load Kernel Modules and I instantly got prompted with a blank, black screen with a "_" blinking in the top left corner, like a normal console, expect any prompt of any kind was missing and it didn't react to my keystrokes, similiar to SystemD's emergency mode
So essentially two smaller problems with few google results are hindering me from solving my big problem.
Thanks for any help in advance,
Quanttek
Last edited by Quanttek (2015-05-26 09:48:21)

Head_on_a_Stick wrote:
Quanttek wrote:I use plain "chroot". "chroot --help" works, but not chroot itself. I also tried to rebuild the symbolic link from the normal lib -> /usr/lib to /lib/* -> /usr/lib/* and it didnt work
https://wiki.archlinux.org/index.php/Ch … ing_chroot
Probably easier to use `arch-chroot` though:
https://wiki.archlinux.org/index.php/Ch … rch-chroot
Thanks. Using arch-chroot worked out. It is/was certainly no environment issue, I even tested it with both i386 and x86_64.
I used it to reinstall mkinitcpio and to update my system, so now on boot I dont get a failure on mounting /boot anymore, but I still have problems with Load Kernel Modules.
My screen now looks something like this: http://m.imgur.com/ATWHJoq
Again it's not reacting to any keystrokes. I'll get some sleep now and will look tomorrow into getting some information from the journal logs.

[SOLVED] Mount /boot/efi fails after linux-....pkg.tar.xz upgrade

Similar Messages

Maybe you are looking for