You are not logged in.
I recently (earlier today) performed a full system update in the usual way ("sudo pacman -Syu") but unfortunately my laptop crashed after the packages were updated but before the post-transaction hooks were run.
So after restarting I am faced with (apologies for any typos, I'm copying this out manually, hence why I truncated the UUID):
Warning: /lib/modules/4.10.11-1-ARCH/modules.devname not found - ignoring
starting version 232
ERROR: device 'UUID=5e583dbe-[etc.]' not found. Skipping fsck.
mount: can't find UUID=5e583dbe-[etc.]
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]# And while the cursor blinks, the keyboard is not responsive.
I'm trying to fix this by using chroot from an installation/recovery distro (e.g. the Arch Linux 2017-04-01 ISO).
However, while it appears to arch-chroot in OK, any command involving pacman does not return anything, so my console looks something like:
[root@archiso ~]# pacman -Syu
[root@archiso ~]# pacman -Syy
[root@archiso ~]# pacman -Syu --debug
[root@archiso ~]# pacman -Syy --debug
[root@archiso ~]# It appears to find pacman it as there is no "command not found" error which I get if I misspell it:
[root@archiso ~]# pacma -Syu
bash: pacma: command not found
[root@archiso ~]# Similarly I can run mkinitcpio (e.g. "mkinitcpio -p linux") but it returns a lot of "module not found" errors and a warning that "No modules were added to the image. This is probably not what you want.", which is consistent with the boot error.
Any ideas on how to complete/rollback my failed update and get the system booting again?
Offline
Boot from the installation media, mount your root partition, and then run a full upgrade from outside the chroot using pacmans --root switch.
pacman --root=/mnt -SyuLast edited by Slithery (2017-04-30 19:42:35)
Offline
Offline
The chroot presents the same environment as the system. If the system is broken, then so is the chroot. As suggested above, you need to fix it from the installation medium directly. Once you have done that then you can chroot into the system to test it before rebooting into it.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
Thanks everyone for the fast responses. ![]()
Boot from the installation media, mount your root partition, and then run a full upgrade from outside the chroot using pacmans --root switch.
pacman --root=/mnt -Syu
Thanks - just tried this and get a message about the disk being full:
error: Partition / too full: 81866 blocks needed, 65468 blocks free
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.According to "df -h" I have 150G available in "/mnt" (the broken Arch system), but perhaps it's referring to "/" (the live media) which only has 195M available.
Anyway, following the link provided by loqs (thanks), using "find /mnt/usr/lib -size 0" suggests I have quite a few broken packages, and similarly if I try to just reinstall the linux package it gives me a lot of 'ldconfig File is empty, not checked' messages.
I'm starting to think it wasn't a coincidence that it crashed when updating and there was already something more wrong with this system - it's running on an old Dell laptop from 2008, but with a recently installed new SSD and Arch installed from scratch a couple of months ago, but I wonder if there are some hardware issues showing up...
Offline
S.M.A.R.T. to check the SSD also did you fsck the filesystems?
# du -hs /mnt/*Should tell you how much space each entry in / of the system is using ( assuming it is mounted at /mnt from the live media ) but it seems there are other issues to address first.
pacman -Qkk again use from live media with --root argument will detect changes to files metadata that pacman tracks but if the file has all the same attributes only its contents is corrupted it will not detect that.
Edit:
spelling each entry not eachentry
Edit2:
In case it is a more serious issue you have a backup of all files you can not replace?
Edit3:
Remove -x option from du ( so it will cross filesystems if they are mounted )
Last edited by loqs (2017-04-30 21:22:00)
Offline
S.M.A.R.T. to check the SSD also did you fsck the filesystems?
# du -hs /mnt/*Should tell you how much space each entry in / of the system is using ( assuming it is mounted at /mnt from the live media ) but it seems there are other issues to address first.
pacman -Qkk again use from live media with --root argument will detect changes to files metadata that pacman tracks but if the file has all the same attributes only its contents is corrupted it will not detect that.
Edit:
spelling each entry not eachentry
Edit2:
In case it is a more serious issue you have a backup of all files you can not replace?
Edit3:
Remove -x option from du ( so it will cross filesystems if they are mounted )
Thanks, loqs.
Just ran some smartctl commands as described in the Wiki link and everything seems to be OK - it returns 'PASSED' for the general health and the 'short' test also didn't return any errors. I doubt the SSD is the issue is that is more or less brand new (at least compared to the rest of the laptop!). fsck returns clean for the ext4 partition (which has /, /boot and /home - I didn't bother splitting these out for this install). And the du lines add up to the 15G or so out of the 170G partition.
Yes - I have backups of everything so can wipe and start again if necessary, which is looking more and more like the easiest option unfortunately.
And I think there are probably underlying hardware issues, as I have a Windows partition that randomly BSODs (yes, I know, not unusual for Windows
, but still...). I tried using memtest but that didn't return any errors but I haven't tried anything else (e.g. to test the motherboard / integrated chips).
Offline
Do the Block count and Free blocks values from the following seem reasonable?
# dumpe2fs -h /dev/whateverOffline
Do the Block count and Free blocks values from the following seem reasonable?
# dumpe2fs -h /dev/whatever
Yes, the outputs (47492608 block count, 42425624 free blocks) look reasonable and consistent with du and lsblk.
Offline