[SOLVED] Boot Crash F17

business_kid · 09-12-2012, 04:26 AM

I'm annoyed about this as I've just installed the Electronic Spin and updated it and I haven't had time to break it yet. I gather the updates have done that for me :-(. Here's what I get before I'm thrown into maintenance (From dmesg).

Quote:

[ 15.627616] systemd[1]: Job graphical.target/start failed with result 'dependency'.
[ 15.634382] systemd[1]: Job abrt-vmcore.service/start failed with result 'dependency'.
[ 15.640749] systemd[1]: Job multipathd.service/start failed with result 'dependency'.
[ 15.640876] systemd[1]: Job ksmtuned.service/start failed with result 'dependency'.
[ 15.640896] systemd[1]: Job ksm.service/start failed with result 'dependency'.
[ 15.640973] systemd[1]: Job mcelog.service/start failed with result 'dependency'.
[ 15.641131] systemd[1]: Job sm-client.service/start failed with result 'dependency'.
[ 15.641152] systemd[1]: Job sendmail.service/start failed with result 'dependency'.
[ 15.641248] systemd[1]: Job xinetd.service/start failed with result 'dependency'.
[ 15.641327] systemd[1]: Job atd.service/start failed with result 'dependency'.
[ 15.641405] systemd[1]: Job irqbalance.service/start failed with result 'dependency'.
[ 15.641481] systemd[1]: Job crond.service/start failed with result 'dependency'.
[ 15.641559] systemd[1]: Job arp-ethers.service/start failed with result 'dependency'.
[ 15.641637] systemd[1]: Job mdmonitor.service/start failed with result 'dependency'.
[ 15.641717] systemd[1]: Job auditd.service/start failed with result 'dependency'.
[ 15.641823] systemd[1]: Job systemd-user-sessions.service/start failed with result 'dependency'.
[ 15.641926] systemd[1]: Job ip6tables.service/start failed with result 'dependency'.
[ 15.642023] systemd[1]: Job iptables.service/start failed with result 'dependency'.
[ 15.642104] systemd[1]: Job livesys.service/start failed with result 'dependency'.
[ 15.642206] systemd[1]: Job livesys-late.service/start failed with result 'dependency'.
[ 15.642286] systemd[1]: Job spice-vdagentd.service/start failed with result 'dependency'.
[ 15.642367] systemd[1]: Job tcsd.service/start failed with result 'dependency'.
[ 15.642389] systemd[1]: Job basic.target/start failed with result 'dependency'.
[ 15.642427] systemd[1]: Job systemd-tmpfiles-clean.timer/start failed with result 'dependency'.
[ 15.643212] systemd[1]: Unit slack.mount entered failed state.
[ 15.752674] Adding 4176864k swap on /dev/sda9. Priority:0 extents:1 across:4176864k
[ 15.800110] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 15.800421] Registered led device: b43-phy0::tx
[ 15.800444] Registered led device: b43-phy0::rx
[ 15.800468] Registered led device: b43-phy0::radio
[ 15.641717] systemd[1]: Job auditd.service/start failed with result 'dependency'.
[ 15.641823] systemd[1]: Job systemd-user-sessions.service/start failed with result 'dependency'.
[ 15.641926] systemd[1]: Job ip6tables.service/start failed with result 'dependency'.
[ 15.642023] systemd[1]: Job iptables.service/start failed with result 'dependency'.
[ 15.642104] systemd[1]: Job livesys.service/start failed with result 'dependency'.
[ 15.642206] systemd[1]: Job livesys-late.service/start failed with result 'dependency'.
[ 15.642286] systemd[1]: Job spice-vdagentd.service/start failed with result 'dependency'.
[ 15.642367] systemd[1]: Job tcsd.service/start failed with result 'dependency'.
[ 15.642389] systemd[1]: Job basic.target/start failed with result 'dependency'.
[ 15.642427] systemd[1]: Job systemd-tmpfiles-clean.timer/start failed with result 'dependency'.
[ 15.643212] systemd[1]: Unit slack.mount entered failed state.
[ 15.752674] Adding 4176864k swap on /dev/sda9. Priority:0 extents:1 across:4176864k
[ 15.800110] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 15.800421] Registered led device: b43-phy0::tx
[ 15.800444] Registered led device: b43-phy0::rx
[ 15.800468] Registered led device: b43-phy0::radio
[ 15.858616] systemd-journald[519]: Fixed max_use=145.2M max_size=18.1M min_size=64.0K keep_free=72.6M
[ 15.862693] systemd-journald[519]: Vacuuming...
[ 36.488930] EXT4-fs (sda10): re-mounted. Opts: (null)
[ 36.521529] udevd[539]: starting version 182
[ 36.579826] systemd[1]: Job rsyslog.service/start failed with result 'dependency'.
[ 36.583656] systemd[1]: Job abrtd.service/start failed with result 'dependency'.
[ 36.589347] systemd[1]: Job sendmail.service/start failed with result 'dependency'.
[ 36.594969] systemd[1]: Job auditd.service/start failed with result 'dependency'.
[ 36.598349] systemd[1]: Job systemd-user-sessions.service/start failed with result 'dependency'.
[ 36.650221] systemd-journald[602]: Fixed max_use=145.2M max_size=18.1M min_size=64.0K keep_free=72.6M
[ 36.654119] systemd-journald[602]: Vacuuming...
[ 88.065978] EXT4-fs (sda8): mounting ext3 file system using the ext4 subsystem
[ 88.120347] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
[ 88.125948] SELinux: initialized (dev sda8, type ext3), uses xattr

Where is it getting that stuff from? grep in /etc/rc.d/init.d is pretty unresponsive, I don't see an rc.sysinit, and the install (from a live cd) seems to have very few init scripts.

EDIT: Forgot to mention - I did get in there and basic libraries and modules.dep all seem present & accounted for.

business_kid · 09-12-2012, 12:22 PM

It's objecting to some ext3 partition I wanted available :-O.

Maybe SELinux shafting the poor old user again. All the waffle from the kernel and the init has changed teetotally :-/. Very Strange.

eskimojoy · 10-19-2012, 12:08 AM

How exactly did you solve the problem?

I ran into the same issue just by changing /etc/pam.d/system-auth and /etc/nsswitch.conf for LDAP configuration. I have no clue why this caused booting errors.

business_kid · 10-19-2012, 09:58 AM

I'm banging my head off the wall trying to think... I THINK I grabbed the dmesg (from slackware) and started at the first error (from the boot parameters or init scripts) and fixed it. I changed kernel parameters and updated BIOS. The rest of the crap vanished and I was slightly amazed.

I was booting with pcie_aspm=force. That threw the ACPI interrupts big time. So then I added pci_no_crs or the like. ACPI was basically haywire with kernels 3.2x and above. So I updated the BIOS (2008-->2011), and dropped all the nutty kernel parameters, and things work smoother. How I'm doing with power consumption I don't know. The power supply goes off and the laptop starts running on battery any time the sun goes behind a cloud. Pulling the battery usually sorts it. It's a hardware issue, I think.

EDIT: I had the exact fault in the thread:

Quote:

It's objecting to some ext3 partition I wanted available

Some init script was barfing over that. I think I just took it out and mounted it manually once I had logged in.

eskimojoy · 10-19-2012, 03:38 PM

Thanks ....

I found the problem yesterday that my case was caused by incorrect settings of LDAP authentication.
After emergency mode log in as root I disabled LDAP and boot was back to normal. Now I am searching to correctly set up LDAP client... I can't understand why it is so difficult on Fedora 17 to get LDAP working....