pacman -Syu cause startup to fail after HAL...

lang2 · 2006-10-25 11:55:11

Hello there,

I just did a pacman -Syu and the box refuses to start. I said yes to the mkcpio question and changed /boot/grub/menu.lst (though I actually use grub from Kubuntu installed on another root partition). The init process will go OK until it finishes bring up the HAL, where it just hangs.

Anyone had similiar problem before?

Snowman · 2006-10-25 21:38:06

Try commenting out the hal daemon in rc.conf to see if your system will start. If you got to the part where daemons are loaded, your switch to mkinitcpio was successfull. There's probably a problem with hal.

lang2 · 2006-10-25 22:06:40

Thanks snowman. But HAL wasn't my problem. I tried to comment out hal from rc.conf and this time the system hang after finishing the previous daemon. I then added httpd after HAL, the system then hang after finished loading the http daemon.

What normally happens after loading the daemon? Starting the shell? /bin/bash is there and the permission looks OK.

Snowman · 2006-10-25 22:32:40

I think it starts the login app. login belongs to the shadow package wich was recently updated. Maybe there's a problem with the package. Try downgrading it.

lang2 · 2006-10-25 22:57:55

hmmm.
How do I downgrade a package when I can't login to the system?

entvex · 2006-10-26 17:58:25

can't you use the install cd to boot into your system ?

lang2 · 2006-10-26 22:16:31

I downgraded the shadow package and the problem is still there.

I waited for a longer time and eventually init said that there is nothing more to be done for that run level......

Lone_Wolf · 2006-10-27 11:45:05

please post your daemons line , there may be a problem with another daemon.

Are you starting in runlevel 3 (console login) or runlevel 5 (graphical login) ?

Does it make any difference if you start with the fallback image ?
(probably not, as your problem is after mkinitcpio finishes, but it doesn't hurt to test it.)

lang2 · 2006-10-28 08:40:06

My daemon line is:

DAEMONS=(!syslog-ng !hotplug !pcmcia network netfs crond sshd samba alsa dbus hal httpd)

I haven't changed it except for experimenting with httpd.

I am using runlevel 3 for startup. I checked inittab and found the following lines:

c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty 38400 vc/6 linux

and remembered that before init print out "no more tasks for this runlevel" it also complained about disabling c1-16 for 5 min because they were too slow. Is it a clue?

Lone_Wolf · 2006-10-28 10:03:47

Are you mounting network drives at boot time ?

Try removing sshd, samba and httpd from the daemons line to check if the problem is network related.

1 minor comment : you can remove !hotplug and !pcmcia from the daemons line. Those 2 no longer exist in archlinux.

PavelZh · 2006-10-28 10:31:43

lang2 wrote:

My daemon line is:
DAEMONS=(!syslog-ng !hotplug !pcmcia network netfs crond sshd samba alsa dbus hal httpd)

May be, is offtopic: but why syslog disabled?

lang2 · 2006-10-28 15:33:53

Tried disabling sshd, samba and httpd, and enabled syslog-ng, but still have the same problem. sigh.

I edited the initab so that I can login into single user mode. Then 'telinit 3' gave the same result.

init complained about

c[1-6] respwaning too fast, disabled for 5 minutes.

Please help. Its been a week since I login into Arch and I want to get back!

Lone_Wolf · 2006-10-28 21:08:35

If you boot with an arch install cd, and let it boot your installed system , can you login then ?

tpowa's new ftp-iso http://www.archlinux.org/~tpowa/newisos … 5-i686.iso is probably the best choice.

lang2 · 2006-10-29 10:27:09

I tried the bootcd and the fallback kernel. The same thing......
Please don't tell me I need to reinstall the system....

Lone_Wolf · 2006-10-29 11:55:06

Maybe re-installing is not necessary. i just noticed this in one of your posts :

I edited the initab so that I can login into single user mode. Then 'telinit 3' gave the same result.

IF runlevel 1 works, but runlevel 3 doesn't , we finally have a clue where to look for the problem.

Both runlevel 1 & 3 start rc.sysinit and the 6 consoles.
In runlevel 1 sysinit is followed by rc.single, while in runlevel 3 sysinit is followed by rc.multi which in turn starts rc.local
something is probably wrong with one of them.

try the following from single user mode :

cp /etc/rc.conf     /etc/rc.conf.problem
cp /etc/rc.multi    /etc/rc.multi.problem
cp /etc/rc.local    /etc/rc.local.problem
/etc/rc.d/network start
pacman -Sy

IF "pacman -Sy" = SUCCESS
THEN

pacman -Sf initscripts

This will overwrite the startupscripts with the latest version of the default startscripts for archlinux.
ELSE
below are the original versions of rc.conf , rc.multi and rc.local (initscripts 0.7.2-9) : just copy them to your /etc folder , as it's possible the local version of initscripts is corrupt.

ENDIF

Now try telinit 3 again and report back.

If this works , you can customize the rc.conf to your liking again.
The .problem files may help to determine the root cause of your problem.

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="myhost"
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)


# End of file

rc.multi

#!/bin/bash
#
# /etc/rc.multi
#

. /etc/rc.conf
. /etc/rc.d/functions

# Load sysctl variables if sysctl.conf is present
[ -r /etc/sysctl.conf ] && /sbin/sysctl -q -p &>/dev/null

# Start daemons
for daemon in "${DAEMONS[@]}"; do
    if [ "$daemon" = "${daemon#!}" ]; then
        if [ "$daemon" = "${daemon#@}" ]; then
            /etc/rc.d/$daemon start
        else
            stat_bkgd "Starting ${daemon:1}"
            (/etc/rc.d/${daemon:1} start) &>/dev/null &
        fi
    fi
done

if [ -x /etc/rc.local ]; then
    /etc/rc.local
fi

# vim: set ts=2 noet:

rc.local

#!/bin/bash
#
# /etc/rc.local: Local multi-user startup script.
#

lang2 · 2006-10-30 10:40:09

Thanks for not giving me up. I tried but it is the same. The initscripts from repo is the same as my local ones. But I tried telinit 3 anyway and it has the same problem.

I took a look at rc.multi and it is actually quite simple:

#!/bin/bash
#
# /etc/rc.multi
#

echo "Processing rc.multi"
. /etc/rc.conf
. /etc/rc.d/functions

# Load sysctl variables if sysctl.conf is present
[ -r /etc/sysctl.conf ] && /sbin/sysctl -q -p &>/dev/null

# Start daemons
for daemon in "${DAEMONS[@]}"; do
	if [ "$daemon" = "${daemon#!}" ]; then
		if [ "$daemon" = "${daemon#@}" ]; then
			/etc/rc.d/$daemon start
		else
			stat_bkgd "Starting ${daemon:1}"
			(/etc/rc.d/${daemon:1} start) &>/dev/null &
		fi
	fi
done

if [ -x /etc/rc.local ]; then
	/etc/rc.local
fi

I can see the rc.local been process if I insert echo "Processing rc.local" into it. But the system just wounldn't give a login shell. I think it must be a problem with agetty.....[/code]

lang2 · 2006-10-30 12:27:58

I logged in from single user mode and execute the agetty line manually and indeed it take a quite long (30sec - 1 min) to come back. And it doesn't seem to invoke the /bin/login program

I then changed inittab to do:

 /sbin/agetty -n -l /bin/login 38400 vc/1 linux

I.e. invoke /bin/login explicitly but init behaves the same.

It has to be agetty but I don't know how to fix it.

Snowman · 2006-10-30 16:14:28

$ pacman -Qo /sbin/agetty
/sbin/agetty is owned by util-linux 2.12-9

Try reinstalling util-linux

lang2 · 2006-10-30 16:57:02

Snowman: tried that already。

Snowman · 2006-10-30 17:04:57

You could also try to reinstall all the other packages in base. Maybe one of them is broke. Just a guess...

django · 2006-10-30 19:48:18

lang2 wrote:

Hello there,
I just did a pacman -Syu and the box refuses to start. I said yes to the mkcpio question and changed /boot/grub/menu.lst (though I actually use grub from Kubuntu installed on another root partition). The init process will go OK until it finishes bring up the HAL, where it just hangs.
Anyone had similiar problem before?

Just to be sure, you changed /boot/grub/menu.lst in your kubuntu partition, didn´t you?

lang2 · 2006-10-31 09:51:32

django wrote:

lang2 wrote:
Hello there,
I just did a pacman -Syu and the box refuses to start. I said yes to the mkcpio question and changed /boot/grub/menu.lst (though I actually use grub from Kubuntu installed on another root partition). The init process will go OK until it finishes bring up the HAL, where it just hangs.
Anyone had similiar problem before?

Just to be sure, you changed /boot/grub/menu.lst in your kubuntu partition, didn´t you?

Yes. I was able to boot into single user mode.

Maybe I will do a re-install.......

Lone_Wolf · 2006-10-31 19:48:42

Lang2 , let's try 1 other thing :

single user mode , start network, pacman -Syu

Since your problem started new versions of Gnome and Kde and many other packages have been put in the repos.
Sometimes a problem automagically goes away when a newer version of a package is installed.

lang2 · 2006-11-01 20:25:00

Thanks guys for not giving me up. I tried pacman -Syu one last time and didn't work. So I have the system reintalled.

Arch Linux

#1 2006-10-25 11:55:11

pacman -Syu cause startup to fail after HAL...

#2 2006-10-25 21:38:06

Re: pacman -Syu cause startup to fail after HAL...

#3 2006-10-25 22:06:40

Re: pacman -Syu cause startup to fail after HAL...

#4 2006-10-25 22:32:40

Re: pacman -Syu cause startup to fail after HAL...

#5 2006-10-25 22:57:55

Re: pacman -Syu cause startup to fail after HAL...

#6 2006-10-26 17:58:25

Re: pacman -Syu cause startup to fail after HAL...

#7 2006-10-26 22:16:31

Re: pacman -Syu cause startup to fail after HAL...

#8 2006-10-27 11:45:05

Re: pacman -Syu cause startup to fail after HAL...

#9 2006-10-28 08:40:06

Re: pacman -Syu cause startup to fail after HAL...

#10 2006-10-28 10:03:47

Re: pacman -Syu cause startup to fail after HAL...

#11 2006-10-28 10:31:43

Re: pacman -Syu cause startup to fail after HAL...

#12 2006-10-28 15:33:53

Re: pacman -Syu cause startup to fail after HAL...

#13 2006-10-28 21:08:35

Re: pacman -Syu cause startup to fail after HAL...

#14 2006-10-29 10:27:09

Re: pacman -Syu cause startup to fail after HAL...

#15 2006-10-29 11:55:06

Re: pacman -Syu cause startup to fail after HAL...

#16 2006-10-30 10:40:09

Re: pacman -Syu cause startup to fail after HAL...

#17 2006-10-30 12:27:58

Re: pacman -Syu cause startup to fail after HAL...

#18 2006-10-30 16:14:28

Re: pacman -Syu cause startup to fail after HAL...

#19 2006-10-30 16:57:02

Re: pacman -Syu cause startup to fail after HAL...

#20 2006-10-30 17:04:57

Re: pacman -Syu cause startup to fail after HAL...

#21 2006-10-30 19:48:18

Re: pacman -Syu cause startup to fail after HAL...

#22 2006-10-31 09:51:32

Re: pacman -Syu cause startup to fail after HAL...

#23 2006-10-31 19:48:42

Re: pacman -Syu cause startup to fail after HAL...

#24 2006-11-01 20:25:00

Re: pacman -Syu cause startup to fail after HAL...

Board footer