You are not logged in.
First off my system seems to now work fine . I'm curious to where I messed up tho so I'll try to briefly tell you about my update this morning.
It's been 2 month since I last updated I followed the news.
pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
Resulted in grub-common from what I could google that should not matter.
[2013-07-12 07:04] [PACMAN] Running 'pacman -Syu --ignore filesystem,bash'
[2013-07-12 07:04] [PACMAN] synchronizing package lists
[2013-07-12 07:04] [PACMAN] starting full system upgradeDuring the update X (I assume) crashed I still had sound but the system was frozen while flickering between a black and white screen. I had to cool boot.
On startup I got sent to busy box. I did a chroot into the system.
chroot /mnt/arch /usr/bin/bash
Cannot chroot '/bin/bash': No such file or directoryNot sure if it's related.
https://mailman.archlinux.org/pipermail … 33049.html
[2013-07-12 10:18] [PACMAN] Running 'pacman -Syu'
[2013-07-12 10:18] [PACMAN] synchronizing package lists
[2013-07-12 10:18] [PACMAN] starting full system upgrade
[2013-07-12 10:19] [PACMAN] Running 'pacman -S bash'
[2013-07-12 10:20] [PACMAN] upgraded bash (4.2.045-1 -> 4.2.045-4)
[2013-07-12 10:20] [PACMAN] Running 'pacman -Su'
[2013-07-12 10:20] [PACMAN] starting full system upgrade
[2013-07-12 10:20] [PACMAN] upgraded filesystem (2013.03-2 -> 2013.05-2)
[2013-07-12 10:20] [PACMAN] Running 'pacman -Syu'
[2013-07-12 10:20] [PACMAN] synchronizing package lists
[2013-07-12 10:20] [PACMAN] starting full system upgradeI rebuild the kernel then for some reason I decided to reinstalled grub too.
Now the system boots. As I started out I am wondering why this happened?
edit; was never able to find a useful clue and it has not repeated itself thanks for trying to help btw. ![]()
Last edited by cell (2013-10-21 17:51:59)
Offline
Are you wondering why X crashed or why X's crashing followed by reboot resulted in being dumped into the busybox shell?
I have no idea about the first.
Regarding the second, as I understand it, you rebooted before updating bash or filesystem, correct? So basically, anything looking for commands under /bin, /sbin or /usr/sbin would have drawn a blank because the upgrades you'd completed would have correctly moved everything to /usr/bin leaving those directories empty (except for bash etc.). The final upgrade of filesystem removes those empty directories and replaces them with symbolic links to /usr/bin which ensures that anything looking for stuff in /bin etc. will continue to find it. If you look in /etc/shells, for example, you will see that most shells are still specified as /bin/<shell> just for instance.
I'm not sure why X crashing prevented you from completing the upgrade. Did you try switching to another tty and just continuing at the command line? (Or restartintg X?)
Last edited by cfr (2013-07-13 01:23:52)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline