You are not logged in.
Hello guys,
First post in the forum and it's to request help with updating Arch after the move to /usr/bin intervention.
I followed the guide at the front page but I have a big problem.
After rebooting (and herein lies my mistake), I understood that at step 5 I should have issued all 3 commands as shown there:
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su
Instead of that I rebooted only after the first command. And sure enough when the updated system boots I get an error and the rootfs prompt:
ERROR: Root device mounted succesfully but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.
sh: Can't access tty: job control turned off
[rootfs/]#
This makes sense to me now that I understand I should have also issued the other 2 commands to let the system know that init moved out of /sbin but well ... I am kind of stuck.
I tried to edit the grub init parameters as detailed in this blog post but it did not help me, the system gets stuck somewhere in the initialization process.
What can I do to fix this? Any and all help would be really appreciated.
Offline
Boot from a live medium, chroot specifying /usr/bin/bash as the shell, then complete the other two commands.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Offline
Hey guys thanks for your replies
I chrooted into the system with an ARCH live USB stick I had lying around.
The commands I issued were:
mkdir mnt
mount /dev/sda3 mnt
chroot mnt /usr/bin/bash
Subsequently I attempted to follow through with the last 2 commands I had not issued before rebooting but I have some problems:
pacman -S bash
error: Could not open file: /etc/mtab: No such file or directory
error: Could not determine filesystem mount points
error: Failed to commit transaction (unexpected error)
Now this must be a mistake with the way I mounted I guess. I don't chroot very often and I must have misunderstood something.
Issuing file /etc/mtab gives me
/etc/mtab: broken symbolic link to /proc/self/mounts
and from a little search I see that mtab is generated by the mount command so I am definitely doing something wrong either when I chroot or when I mount. Any idea what that is?
Offline
Either use pacman from outside the chroot like the link I gave you previously or read up on how to use chroot.
Offline
Did you happen to see this wiki entry
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Thanks Scimmia! Makes sense, needed to specify the location of some specific directories (including proc) for the file system we chroot into.
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
mount -t devpts pts dev/pts/
Thanks! Now I know and I also have my system back. I just needed to upgrade bash and issue a pacman -Su to upgrade the filesystem and all worked smoothly
Offline
You could also use arch-chroot from the Arch live USB which does lots of it automagically.
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
Is it safe to remove this symlinks?
lrwxrwxrwx 1 root root 7 31.05.2013 20:40 bin -> usr/bin/
lrwxrwxrwx 1 root root 7 31.05.2013 20:40 lib -> usr/lib/
lrwxrwxrwx 1 root root 7 31.05.2013 20:40 lib64 -> usr/lib/
lrwxrwxrwx 1 root root 7 31.05.2013 20:40 sbin -> usr/bin/
System works just fine, so no problem. Just wonder if they are needed..?
Offline
No, it's not safe. They're there for a reason. Don't delete things put there by pacman.
Offline
No, it's not safe. They're there for a reason. Don't delete things put there by pacman.
Allright! Thank you. Not that it bother me that much, just the idea to have everything as clean as possible, so not needed folders must die! This makes me happy that I reinstalled Arch from scratch a few days ago, seems like this update caused 1 or 2 problems.
Offline
CaptainKirk wrote:I copied and pasted the second command from the blog post but I get an error:
$ paclist <repo> | awk ' { print $1 } ' | pacman -Ql - | grep ' /s\?bin/\| /usr/sbin/' bash: syntax error near unexpected token `|'
Am I doing something wrong?
replace <repo> with the name of an actual repository and you'll be fine
I did that and I'm still getting the same message. What am I doing wrong?
Offline
What command are you using exactly?
Offline
What command are you using exactly?
# paclist <core> | awk ' { print $1 } ' | pacman -Ql - | grep ' /s\?bin/\| /usr/sbin/'
bash: syntax error near unexpected token `|'
I also tried extra, community and multilib with the same result
Offline
The < and > are not meant to be retained, remove them. You also don't need to check official repositories, all packages in those comply with the new filesystem. That command string is meant to be used to check third-party repositories.
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.
Online
The < and > are not meant to be retained, remove them. You also don't need to check official repositories, all packages in those comply with the new filesystem. That command string is meant to be used to check third-party repositories.
Thank you! I had a dumb moment.
Offline