You are not logged in.
I've done everything in the article, and I have no unofficial packages.
However, I do use zsh as my shell, so I thought I might as well ask before doing anything:
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su
Should I replace bash with zsh here? I do have both bash and zsh installed.
EDIT: I did indeed forget to mount /boot. After doing that the update worked perfectly.
Last edited by graph (2013-06-03 19:23:37)
Offline
No, bash is needed because of post install scripts that call bash or sh specifically.
Online
Hmm. I did everything it asked me to do, but now the installation of filesystem is hanging at "Checking available disk space" - Is this to be expected?
$ sudo pacman -Su
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Packages (1): filesystem-2013.05-2
Total Download Size: 0,01 MiB
Total Installed Size: 0,01 MiB
Net Upgrade Size: -0,30 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
filesystem-2013.05-2-i686 8,4 KiB 600K/s 00:00 [############################################################] 100%
(1/1) checking keys in keyring [############################################################] 100%
(1/1) checking package integrity [############################################################] 100%
(1/1) loading package files [############################################################] 100%
(1/1) checking for file conflicts [############################################################] 100%
(1/1) checking available disk space [############################################################] 100%
Last edited by graph (2013-06-03 14:16:16)
Offline
You probably forgot to mount all the autofs partitions.
Offline
No, I don't think so. At least mount reported that /boot, /home and / was mounted, and that's all the partitions I have.
However, if this indeed is the case, do you have any idea how to fix it?
Offline
I don't know about anyone else, but the upgrade step for filesystem just took a little while (a long time for pacman, but not that long in the grand scheme of things).
How long did it hang before you interrupted it?
All the best,
-HG
Offline
How long did it hang before you interrupted it?
-HG
I've left it hanging (and it still hangs) so about 15 minutes now, I would say. There's no disk activity.
Would it be completely stupid to interrupt it? Pacman hasn't written anything about installing yet.
EDIT: All applications appear to be broken - Probably because of the changes in PATH, I assume. Pacman is still hanging. I am left with an unusable root-terminal (with no applications), firefox and libreoffice.
Last edited by graph (2013-06-03 14:46:55)
Offline
So, still hanging. I guess I'm screwed. Where do I go from here? Use a live-cd to try installing filesystem again? Roll back the filesystem package?
My fear is, that a reboot will result in this error, as experienced in this thread.
Error: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good Luck
[rootfs /]#
Last edited by graph (2013-06-03 15:37:46)
Offline
Also use zsh.
Used "pacman -Syu --ignore filesystem,zsh" instead (seemed logical to me, not sure if that is correct way).
All worked fine.
Offline
Also use zsh.
Used "pacman -Syu --ignore filesystem,zsh" instead (seemed logical to me, not sure if that is correct way).
All worked fine.
No. This is not right. bash is not ignored because it is the user's shell; it is ignored for a separate reason. And, it should be mentioned; having done this update without issue, I have had no problems with zsh whatsoever (no extra work required).
All the best,
-HG
Offline
Also use zsh.
Used "pacman -Syu --ignore filesystem,zsh" instead (seemed logical to me, not sure if that is correct way).
All worked fine.
Offline
Thanks for details.
Unfortunately reason was not stated in the update instruction
Offline
Alright, I have one working shell. I have no Ignores but I do have
HoldPkg = pacman glibc
in /etc/pacman.conf - Could this be the culprit?
Also, here are the (missing) output of the commands from the article. I'm quite interested in knowing whether all my autofs-partitions are mounted, which I believe they are.
# pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
# find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null
# mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=1538736k,nr_inodes=216743,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda5 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=33,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /boot type autofs (rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /home type autofs (rw,relatime,fd=37,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
configfs on /sys/kernel/config type configfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
/dev/sda6 on /home type ext4 (rw,noatime,data=ordered)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
Last edited by graph (2013-06-03 18:00:47)
Offline
No, those package in HoldPkg are normal
How about posting your fstab?
Online
How about posting your fstab?
Contents of /etc/fstab:
# /boot
UUID=61fc73d6-c126-44c4-bf45-98ecbe06c96d /boot ext2 defaults,noatime,noauto,comment=systemd.automount 0 2
# /
#UUID=edfcc182-d233-4315-aefd-0c11f80ff4a9 / ext4 defaults,noatime 0 1
# /home
UUID=bc7fda50-ff21-42dd-aba3-f26b3d89ae1c /home ext4 defaults,noatime,noauto,comment=systemd.automount 0 2
Last edited by graph (2013-06-03 18:14:27)
Offline
It doesn't appear that /boot is mounted
Online
It doesn't appear that /boot is mounted
D'oh! I love you - in a geeky way, that is. This solved my problem. So much for my ability to read the output of mount...
Offline
Alright, I have one working shell. ....
It seems to me I have the same problem - how did you get one shell working?
Offline
It seems to me I have the same problem - how did you get one shell working?
CTRL+C'ed a couple of times when it was hanging at "checking available disk-space". Whatever you do after that, do NOT close that terminal. Beware that this worked for me, I can't tell if it will work for you too.
Offline
It worked. Thanks a lot!
Offline