Re: filesystem Update Error /bin exists in filesystem

I didnt update my system for like 7 months, for college assignments sake, and now i was having a hard time updating but i did it. Unfortunally i cant boot now and im going to emergency shell.

What i did was update everything exept filesystem, then removing tlp because it had somthing in sbin, then update the filesystem. I forgot to ignore bash, so i only had 1 shell but after filesystem update shell was working again, so i tought i could reboot but as it turns out i cant

I know i shouldnt let arch get 7 months outdated but i dont really want to make a fresh install.

Re: filesystem Update Error /bin exists in filesystem

You can't boot now because your initial ramdisk (initrd) doesn't have the modules for your current kernel. This is because, by not holding back the bash package during the main part of the update, various packages were unable to execute their .install scripts -- one of these was the linux package which uses this script to generate a new initrd.

The solution, which is documented multiple times in this thread, is to boot a liveCD, chroot into your installation, and manually run the mkinitcpio script. Alternatively chroot in and reinstall the linux package, which will trigger a re-run of the install script.

Re: filesystem Update Error /bin exists in filesystem

Scimmia wrote:

FIX GUIDE: For those that screwed up the filesystem update and can't boot anymore because it can't find /sbin/init(since I don't like coellobranco's, I figured I should post my own)

1) Boot an Arch Install Disk. Set up your network if you need to (see Beginner's Guide).2) Mount all of the partitions you use to /mnt. This includes not only the root partition, but /usr, /var, etc (to /mnt/usr, /mnt/var/, etc).3) Run "pacman --root /mnt -Qo /mnt/bin /mnt/sbin /mnt/usr/sbin". Ideally, it should tell you that /mnt/bin and /mnt/sbin don't exist and that /mnt/usr/sbin is owned by "filesytem". If you get any other packages listed, they need to be fixed or uninstalled! If they're packages from the official repos, upgrade them with "pacman --root /mnt -S <pkgname>. If they're packages you don't need, you can uninstall them with "pacman --root /mnt -Rs <pkgname>". Remember, if they're not critical for your system, you can always reinstall them later once you get back up and going.4) Run "find /mnt/bin /mnt/sbin /mnt/usr/sbin -exec pacman --root /mnt -Qo -- {} + >/dev/null" This will tell you of any untracked files in the relevant directories. Any files it finds need to be deleted or moved. I suggest putting any scripts you made in /usr/local/bin so they don't get in the way. If you removed any files from /mnt/bin or /mnt/sbin, check these dirs afterwards to see if they're empty. If they are, delete them.5) Run "ls -l /mnt /mnt/usr/sbin". At this point /mnt/bin and /mnt/sbin shouldn't exist and /mnt/usr/sbin should be empty. If that's not the case, stop. Come back here and ask for help.6) Run "pacman --root /mnt -Su". This should install the filesystem package without any errors. Once that is done, your system should be functional again.

I'm really sorry to post here for help, but I have run into the "can't find /sbin/init, bailing out error" after trying to follow the home page instructions. I had to first replace grub-common with grub (2.00-1) before upgrading the remaining packages (ignoring filesystem and bash). In looking at pacman.log, I only received these warnings during the the kernel build:

I didn't think these modules needed to be dealt with at this point. I also got a message about SNA being used in the xf86-input-evdev package.

I then upgraded bash without any problems (at least according to pacman.log) and the next entry is "Running 'pacman -Su' but there are no additional errors or messages. At this point I think I tried to restart the system and I am not sure if filesystem was fully upgraded properly or not.

Now, on boot I get:

*** Warning ***
* The root device is not configured to be mounted *
* read-write@ It may be fsck'd again later. *
***
ERROR: Root device mounted successfully, 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 /]#

In following Scimmia's instructions above, I booted using an archiso USB (with filesystem 2012.10-1) and mounted the root and var partitions to /mnt and /mnt/var, respectively, and at step 3 I get:

Re: filesystem Update Error /bin exists in filesystem

By the looks of things, your problem is two-fold: 1) you haven't upgraded the filesystem package, and 2) the existing filesystem package installed on your system is in an inconsistent state.

I expect that 2) is the reason for 1), as when you try to install the update, you will recieve "exists in filesystem" errors for any number of directories. Try running the final step of the upgrade again from the liveCD:

pacman -r /mnt -Syu

Make a note of which files are conflicting, and report back (full output in [ code ] tags is preferable, you can use sprunge or similar utility to upload output from a tty).

You can ignore the firmware errors mkinitcpio spits out, chances are you don't need them.

The instructions say to "fix" them. What exactly does this entail? I'm reading about people manually copying/moving files, but I have more than three or four files here... And do the errors at the top of that list mean anything important?

Second, I tried the command to check files from non-official repos (I have some stuff installed from archlinuxfr), but `paclist` just tells me "command not found." What do I need to do to get paclist installed?

It also wants me to update pacman, but of course I can't because the new version depends on things that won't update due to the above issues...

I've been trying to get this working for a while now, and I'm wondering if nuking and starting over might be the best option! But then I'd lose all of the time I spent getting things set up just how I like them...

Re: filesystem Update Error /bin exists in filesystem

mjohnson, I think that reinstalling and keeping your Arch up to date from now on will be faster and easier.

[sigh] I thought that might be the case.

karol wrote:

mjohnson wrote:

I'd lose all of the time I spent getting things set up just how I like them...

If you like it so much, why haven't you kept it updated? :-)

I have Arch on a desktop which used to be my primary machine, but about a year go I got a new, fast laptop that became my primary machine. But even though I don't use my desktop much these days, I still like it to be customized just the way I have it for when I do use it. I started using Arch about four years ago and really like its customizability and bleeding-edge updates.

Is Arch not meant to be usable/recoverable if you don't update it every couple of months? (I'm just surprised that by letting it sit for a little while there's no good way to get back up to speed.) If that's the case, maybe it's just not the right fit for a lesser-used, secondary/backup machine...as much as I hate the idea of switching to something else!

Re: filesystem Update Error /bin exists in filesystem

mjohnson wrote:

I have Arch on a desktop which used to be my primary machine, but about a year go I got a new, fast laptop that became my primary machine.

The same thing happened to me. I switched my desktop (which is used less) to Fedora, and I've been quite pleased. Fairly easy to maintain, recent packages, delta-RPMs (fast update downloads), similar configs to Arch (systemd). I keep Arch on my laptop, which is used day to day.

Re: filesystem Update Error /bin exists in filesystem

Pse wrote:

mjohnson wrote:

I have Arch on a desktop which used to be my primary machine, but about a year go I got a new, fast laptop that became my primary machine.

The same thing happened to me. I switched my desktop (which is used less) to Fedora, and I've been quite pleased. Fairly easy to maintain, recent packages, delta-RPMs (fast update downloads), similar configs to Arch (systemd). I keep Arch on my laptop, which is used day to day.

Thanks for the suggestion! I haven't tried Fedora out yet, but that's something to keep in mind. (I've done more with Debian and Ubuntu, personally.) I ended up reinstalling Arch; I have dmcrypt + LVM set up, and I wasn't sure how easy it would be to configure the same setup in another distro. Even in Arch it took me a while to remember how I had it set up, but after that point reinstalling Arch wasn't bad, and I'm back up and running!

Re: filesystem Update Error /bin exists in filesystem

I've configured lvm-on-luks on a machine running Fedora, as well as on my Arch laptop. (Again, not needing to keep up with updates was the key reason to go Fedora - though selinux was also a consideration for that machine.) The biggest hassle is fighting the installer but it may be easier if you don't go with the KDE spin but the standard one - I'm not sure.