Bug 428108

Summary: openSUSE 11.1 Beta 1 first-boot error : Failed to connect socket /var/run/dbus/system_bus_socket: No such file or directory
Product: [openSUSE] openSUSE 11.1 Reporter: Jags FL <Jags_FL>
Component: InstallationAssignee: Timo Hoenig <thoenig>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P2 - High CC: Jags_FL, rwooninck
Version: Beta 1   
Target Milestone: Beta 2   
Hardware: i686   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jags FL 2008-09-20 09:39:28 UTC
openSUSE 11.1 Beta 1 will not boot.

First-boot error :

:::::
Failed to connect socket /var/run/dbus/system_bus_socket: No such file or directory     Failed

Bootsplash: Status on console 0 changed to on
blogd: no message logging because /var file system is not accessible

fsck failed: Please repair manually & reboot. The root file system is currently mounted read-only. To remount it read-write do:

bash# mount -n o remount, rw /

Attention: Only CONTROL-D will reboot the system in this maintanance mode. Shutdown or reboot will not work.

Give root password for login:
:::::

Installed from ' openSUSE-11.1-Beta1-DVD-i386.iso ' on a HP desktop.
Partitioning:

hdb1 /home  (encrypted)
hdb2 /      (not encrypted)


- Jags  / Sept 20, 2:39 AM PT
Comment 1 Timo Hoenig 2008-09-25 10:55:06 UTC
Jags, is this a stock installation or some special setup?
Comment 2 Jags FL 2008-09-25 15:45:51 UTC
hi Timo

Its a regular/stock installation. I've installed openSUSE 11 and openSUSE 11.1 Factory on the same machine many times previously. 

Sept 25 / 8:45 AM
Comment 3 Timo Hoenig 2008-09-25 16:38:59 UTC
Thanks for getting back, Jags.

This message sounds bogus to me:

blogd: no message logging because /var file system is not accessible

If /var isn't accessible you'll get a whole lot of errors, not just that D-Bus is not able to start :)

Are you sure that /var is OK on your machine?
Comment 4 Jags FL 2008-09-25 17:12:42 UTC
Timo

yes, I can confirm thats the message I got on a first boot... I had it wrote down on a paper. But by now I've formatted the partition.

Let me know if you want me to recreate the error, I can reinstall it with same settings & partitioning as earlier.

Sept 25, 10:12 AM PT
Comment 5 Timo Hoenig 2008-09-25 17:21:42 UTC
Jags, if you could try to reproduce the bug would be great.  Maybe that will give us a hint what is going wrong.  If you run into the same bug again, it would be interesting if /var exists and if it is writable.

Thank you!
Comment 6 Jags FL 2008-09-26 09:22:59 UTC
hi Timo

After reading following notes, I've decided to wait till openSUSE 11.1 Beta 2 or till 2.6.28 release before installing any alpha/beta versions. Thanks.

 - jags / Sept 26 / 2:22 AM PT



(1) at __ http://news.opensuse.org/2008/09/22/serious-e1000e-driver-issue-in-sle-11-beta-1-and-opensuse-111-beta-1/ __ 

:::
The Intel e1000e driver on openSUSE 11.1 Beta 1 and SUSE Linux Enterprise 11 Beta 1 might have a serious issue with the potential to damage the network card in a way that it cannot be used any longer.

Intel and Novell are currently working to analyze and solve the issue.

For the time being:

Please do NOT USE:

openSUSE 11.1 Beta 1
or
SUSE Linux Enterprise 11 Beta 1

on systems with Intel e1000e hardware.
:::

and

(2) at __ http://wiki.mandriva.com/en/2009.0_Errata __

:::
EEPROM corruption on Intel 82566 and 82567 network chipsets (ICH8 and ICH9)

A serious bug exists in version 2.6.27 of the Linux kernel (all pre-releases up to and including 2.6.27rc7) which can result in the EEPROM on Intel 82566 and 82567 network chipsets becoming corrupted, rendering the adapter unusable in all operating systems. This issue affects all Mandriva Linux 2009 kernels between from 2.6.27-0.rc5.1mnb to 2.6.27-0.rc6.5.1mnb. It is worked around (by entirely removing the offending e1000e driver) in kernel 2.6.27-0.rc7.1.1mnb.
:::
Comment 7 Timo Hoenig 2008-09-26 09:52:15 UTC
Jags, of course, I understand.  Just post your updates whenever you find time to give one of the next betas a try.  Thanks!
Comment 8 Raymond Wooninck 2008-09-30 16:54:46 UTC
I do not believe that the topic of this bug is related to the disappearance of the /var filesystem and not being able to boot. 

I have an up-to-date Factory installation and I receive during the boot process the following error :

Starting udevd: done
Loading required kernel modules   done
Activating swap-devices in /etc/fstab... done
error: libhal_ctx_set_dbus_connection: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Setting up the hardware clock   done
udevadm[1417]: the program '/bin/bash' called '/sbin/udevsettle', it should use'udevadm settle <options>', this will stop working in a future release

Nevertheless my system will boot normally and everything seems to be working fine. I have already tried to update hal and dbus-1, but this does not seem to help. 

g24504@hqvm000261:/var/log> rpm -q hal
hal-0.5.11_git20080828-12.8
g24504@hqvm000261:/var/log> rpm -q dbus-1
dbus-1-1.2.3-16.10

I got this error after the upgrade to Beta-1 and I can't seem to get ride of it. 

Strangely enough the file is being generated as that it is there after the boot process completed :

24504@hqvm000261:/var/run/dbus> ls -l
total 8
drwxr-xr-x 2 root root 4096 2008-09-29 22:33 at_console
-rw-r--r-- 1 root root    5 2008-09-30 18:09 pid
srwxrwxrwx 1 root root    0 2008-09-30 18:09 system_bus_socket
g24504@hqvm000261:/var/run/dbus>

Maybe this is a sequencing error between hal and dbus ??

Regards

Raymond
Comment 9 Jags FL 2008-10-04 03:10:15 UTC
hi Timo

Just installed openSUSE 11.1 Beta 2 from 'openSUSE-11.1-Beta2-DVD-i386' successfully on the same machine and it boots just fine.

Partitioning:

hdb1 /      (not encrypted)
hdb2 /home  (encrypted)
Comment 10 Timo Hoenig 2008-10-04 09:04:27 UTC
Thanks for getting back, Jags.

It seems that bug 428371 was the root cause.  Closing as duplicate.

*** This bug has been marked as a duplicate of bug 428371 ***