slow boot on 11.3 m7

hello, i’ve experienced many time a slow boot probleme on a dell laptop d430 with an opensuse 11.3 m7 (updated from m6, m5 and so on)

i saw the probleme the first time on m6.
i did a zypper dup up to m7. and the problem is still here.

the booting process work fine from grub to the kernel
but, when it comes to launching services, the load average goes up.
i found many errors due to the facts that no network was available : wifi or wired.

when i kill the dhclient6 and dhcpcd, everything return to normal.

is it due to the many updates ?
or is it something new ?

i think, to reproduce the problem, simply boot without any network responding to dhcp request, maybe.

anyone confirm ?

by the way, great job to all the opensuse team.

RC1 is due today - you might update and see if you still see the slowness
once it’s available (may already be, I haven’t looked myself yet).

Jim


Jim Henderson
openSUSE Forums Administrator

I can confirm this.
After a fresh install of opensuse, sometimes booting takes forever. I also suspected networking to be the problem: at work I work wired, at home I work wireless. I’ll try killing DHCP if the machine seems overly busy. But still.

BTW: I use a HP Compaq 6710b laptop.

I have experienced the same with a toshiba laptop.

Are you using any NFS connections? It seems for me that booting almost stops searching NFS folders…

P.S. with the final version of 11.3 teal 2.6.34

Robert

On 08/17/2010 03:36 PM, jjanarnava wrote:
>
> I have experienced the same with a toshiba laptop.
>
> Are you using any NFS connections? It seems for me that booting almost
> stops searching NFS folders…

If you are mounting an NFS volume, look in /etc/init.d/nfs and find the section
that looks like


if test -n "$mnt" ; then
# If network devices are not yet discovered, mounts
# might fail, so we might need to 'udevadm settle' to
# wait for the interfaces.
# We cannot try the mount and on failure: 'settle' and try again
# as if there are 'bg' mounts, we could get multiple copies
# of them.  So always 'settle' if there is any mounting to do.
udevadm settle
mount -at nfs,nfs4 > /dev/null 2>&1 &

Your file will not have that & at the end of the mount line. Put it there and
NFS mounts will not delay the boot, yet the volumes will be mounted when the
network comes up.

It works!!!

Thank you very much and sorry for the very late reply! :shame:

I found another solution editing /etc/nfsmount.conf changing Defaultvers=4 to =3 this worked too. What would be the better solution? Adding the &, what was missing or nfsmount.conf.

Thanks again!