You are not logged in.
Hello guys,
I did not update my system for the last 4 weeks because I was on holiday. Yesterday then I ran pacman -Syu as the last news on the change of filesystem suggests.
During the update process I received the first errors such as /usr/bin/foo cannot be found.
I was not even able to open a new shell. I thought it's wise to restart the system but now I cannot even boot into my system. After the GRUB start menu I receive the following error before I am dropped to the recovery shell.
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
No volume groups found
ERROR: resume: hibernation device '/dev/mapper/VolGroup00-Swap' not found
ERROR: device '/dev/mapper/VolGroup00-Arch' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/mapper/VolGroup00-Arch'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
Can I somehow rescue my system?
Last edited by orschiro (2013-02-07 19:04:39)
Offline
Hi
Not sure if this will get you any further, but in your error it says
Type 'exit' to try and continue booting
, what happens if you do so ?
And there was this thread about the update, you probably saw it already: https://bbs.archlinux.org/viewtopic.php?pid=1226064
As far as I understood, if you could get to that point.
All Arch Linux packages that had files in this directory have been updated, so update these individually first.
$ pacman -Qo /usr/lib64/{foo,bar}
/usr/lib64/foo is owned by foopkg
/usr/lib64/bar is owned by barpkg
$ sudo pacman -S foopkg barpkg
Regards
Personal website: reboot.li
GitHub: github.com/rebootl
Offline
, what happens if you do so ?
I get the message:
mount: you must specify the filesystem type
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
My filesystem is ext4. I guess I will have to mount the volume group manually. Is this possible from the recovery shell?
Refering to your advice to update the packages manually. Through pacman -Syu I already updated them but probably filesystem before the others.
I would really like to understand what has caused this complete crash now.
Offline
There are a few topics on this already. The one I mentioned above.
Then this one
https://bbs.archlinux.org/viewtopic.php?id=156942
and https://bbs.archlinux.org/viewtopic.php?id=156821
In the last one is a reference to:
https://wiki.archlinux.org/index.php/Pa … onger_boot
That might help for your case.
Last edited by rebootl (2013-02-02 21:42:54)
Personal website: reboot.li
GitHub: github.com/rebootl
Offline
So I went into this further.
Since I am using a volume group I did the following:
# vgchange -ay
# mount /dev/VolGroup00/Arch /mnt
# arch-chroot /mnt
chroot: failed to run command /bin/sh: No such file or directory
Ideas?
What the hell happened to my /bin directory?
Last edited by orschiro (2013-02-07 13:50:45)
Offline
I suspect your /bin directory is fine, and you just need to complete the glibc/filesystem update. From a live environment, with your root partition mounted to /mnt and your network up and running, run
# pacman -r /mnt -Syu filesystem glibc
Any problems, check the links rebootl posted for solutions.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thanks a lot WorMzy!
This finally solved the problem. Indeed there must have gone something wrong during the original update procedure. Very nice. I did not know about the pacman -r /mnt way.
After running your command I was able to use arch-chroot and to rebuild the boot image.
Now I am writing to you from my restored system.
Regards from a very happy
Robert
Offline