Five-minute freeze after fsck at boot

Hi folks,

11.4 install recently updated to 12.1 (zypper dup).

At boot time, the machine gets to the openSUSE splash screen, then waits five minutes. If I press ESC, it shows the following output:

doing fast boot
Creating device nodes with udev
udevd[248]: failed to execute '/etc/sysconfig/network/scripts/ifup-sysctl' '/etc

Trying manual resume from /dev/disk/by-uuid/2356b97b-4eef-4e30-89c1-2ce733f290f0
Invoking userspace resume from /dev/disk/by-uuid/2356b97b-4eef-4e30-89c1-2ce733f
resume: libgcrypt version: 1.5.0
Trying manual resume from /dev/disk/by-uuid/2356b97b-4eef-4e30-89c1-2ce733f290f0
Invoking in-kernel resume from /dev/disk/by-uuid/2356b97b-4eef-4e30-89c1-2ce733f
Waiting for device /dev/disk/by-uuid/2356b97b-4eef-4e30-89c1-2ce733f290f0 to app
fsck from util-linux 2.20.1
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1: clean, 560652/6553600 files, 5888587/26213888 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-uuid/099db399-9a6f-4a8f-abea-faebfdb287bf
mount -o rw,acl,user_xattr -t ext4 /dev/disk/by-uuid/099db399-9a6f-4a8f-abea-fae
    6.138105] systemd[1]: [/etc/init.d/cups:19] Failed to add LSB Provides name
    9.533172] SP5100 TCO timer: mmio address 0xb8fe00 already in use
systemd-fsck[696]: /dev/sda3: clean, 160137/16769024 files, 61603570/67047277 blocks
systemd-fsck[700]: /dev/sdb1: clean, 183328/91578368 files, 288027080/366282000 blocks

Then it sits there for exactly 300 seconds, and then it continues to the login screen as normal. During the pause, the HDD led is off, and the CPU fan spins down, so it seems that the machine is completely idle and waiting for something to happen.

I’ve run a smartctl --test=long on both hard drives, and they are fine.

Any ideas?

Thanks in advance,
K.

On 02/19/2012 11:16 AM, Kalenz wrote:
>
>
> Then it sits there for -exactly 300 seconds-, and then it continues to
> the login screen as normal. During the pause, the HDD led is off, and
> the CPU fan spins down, so it seems that the machine is completely idle
> and waiting for something to happen.
>
> I’ve run a -smartctl --test=long- on both hard drives, and they are
> fine.

It is likely waiting for network mounts. If you revert to using SystemV rather
than systemd, then you will likely not see the delay. You can do that for a
single boot by using the F5 option in the GRUB screen. If that helps, the
Release Notes for 12.1 will tell you how to change permanently.