You are not logged in.
I have just upgraded to the latest arch kernel and somehow it always hangs while booting.
This is what happens:
During the boot process, I get a couple of errors about the mount point not being able to be found, and one of them being "/dev/pts" if I remember correctly (my computer screen displays the lines very fast, so I cannot read/remember everything). Then, there are many many lines about not being able to mount something. However, it continues until it goes through all my daemons, before stopping.
On a maybe related note, I have also seen the "libdbus-1.so.3: cannot open shared object file" error when hal or fam are loading from my daemons, but I have tried to solve that problem by copying the libdbus shared library from my other linux installation to it. I still got an error that said "/etc/rc.d/dbus" not found, and I have tried disabling hal and fam from the daemons in my /etc/rc.conf without any luck.
I am currently on another linux distribution with which I dual boot.
I know this is pretty vague, but does anyone have any clues on what might be happening? Thank you so much!
Last edited by sausagepotato (2008-11-29 00:02:19)
Offline
/usr/lib/libdbus-1.so.3 and /etc/rc.d/dbus are owned by the dbus-core package so it looks like you have somehow removed dbus from your system, try re-installing the dbus-core package (and maybe the dbus package aswell).
I'm not sure about the /dev/pts issue, do the messages occur before you get the coloured 'welcome to arch' text (where the daemons etc are started) or during the coloured text?
Offline
thanks for the reply!
Hm, I'll try reinstalling dbus. I remember when I was upgrading my system with pacman -Syu, I did see some errors with dbus, but I kind of ignored them.
Is there any way to install dbus with pacman into my archlinux distro using a different distro, possibly using chroot or something? (I'm still a beginner at this)
the mount points errors occured after the welcome to arch text, and were after the loading udev part too. I think it started in the "checking filesystems" stage.
Thanks again!
Offline
Yes, you should be able to install via a chroot, in your running distribution make a temporary place to mount your arch system,, then mount the arch partition and bind-mount some additional ramfs areas e.g.
mkdir /mnt/arch
mount /dev/sdXX /mnt/arch
mount /dev/ /mnt/arch/dev/ --bind
mount /sys/ /mnt/arch/sys/ --bind
mount /proc/ /mnt/arch/proc/ --bind
You should then be able to chroot into your arch system,
chroot /mnt/arch
You should now be logged into your arch system as root and can run pacman.
If the mount errors are occuring after the welcome to arch text you might want to check you have the latest initscripts package..
Last edited by ghostHack (2008-11-27 21:25:01)
Offline
It said dbus-core was already installed, so I reinstalled it. I'll go reboot now...
EDIT:
Thanks so much, there are no more dbus errors anymore!
but it still hangs...it still had the "/dev/pts does not exist" errors
One thing that I did notice though was that after the "welcome to arch" starting message, the first line while booting was something about "using the static /dev filesystem".
I'm wondering if this (http://bbs.archlinux.org/viewtopic.php?id=56604) is something similar...
EDIT AGAIN:
Yes! It was the initscripts that was causing me the trouble! I just did pacman -S initscripts, and everything was okay! Thanks
Last edited by sausagepotato (2008-11-27 22:56:25)
Offline
Glad I could help you fix things
You might want to mark the topic as [SOLVED] to help anyone else searching with similar problems.
Offline
okay, done!
Offline