Ive been using arch for approx 6 months as a primary system (total linux experience starts from the early mandrake and slackware days), i love everything about it: the rolling release and bleeding edge software and i cant forget the package management! However it seems like i have perhaps broke something.
I run arch on both my desktop and eeePC 701 (which im writing on just now), my desktop runs xfce4.10 with SLiM login. I use dwm on my eeepc (repo version not abs).
I decided to run DWM on my desktop because quite frankly i think it is a great window manager. I followed the wiki to install via abs and then recompiled after i changed the "tabs" names to 'www' 'mail' 'term' and 'misc' - I recompiled using the instructions on the wiki, killed dmw and restarted to confirm changes and all was well.
This is where the newbish ways started and this is where i think i have killed my system. As root i issued 'reboot' and it sat for approx 10 mins at which point i think it must of hung up. I ctrl+C and it cancelled the command fine, tried issuing 'reboot' again and same thing happened, hung up. With a lack of patience i have hit the hardware reset button on my tower and upon forced reboot I am met with this:
Failed to mount debug file system Failed to mount POSIX message queue file system Failed to mount huge pages file system Failed to mount configuration file system Failed to mount temporary directory <loop> Welcome to emergancy mode! after logging in , type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode" systemd-remount-fs: failed to execute /bin/mount: no such file or direcotry. systemd-remount-fs: /bin/mount for / exited with exit status 1. Welcome to emergancy mode! after logging in , type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode" systemd-fsck: fsck failed with error code 8 systemd-remount-fs[...]: /bin/mount for / exited with exit status 1. systemd-random-seed[...]: Failed to write new random seed file: Bad file descriptor </loop>
It loops like this continually, i don't actually get to the login prompt. I have tried booting from a bootable arch usb drive, i can mount my / , /home points fine and my data is there. I have tried chrooting (mounting / to /mnt/arch and running pacman -Syy && pacman -Syu which gives an error and does not install the upgrade. I have tried pacman -S udev / linux and also tried the mkinitcpio -p linux command.
I don't want to loose my data, and would prefer to avoid reinstalling arch. Can anyone add a little insight into this problem as what i find via archlinux wiki and google doesnt seem to be helping or resolving the issue at least - perhaps im not looking at in the right area ofcourse.
Thanks in advance,
The error given during the chrooted pacman -Syu is as follows:
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) Errors occured, no packages were upgraded
Edited by sean.ferguson, 07 June 2013 - 19:06.