Bug 744378

Summary:	systemd got stuck after fsck-ing my raid-1 root filesystem
Product:	[openSUSE] openSUSE 12.1	Reporter:	Tazio Ceri <praise.tazio>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED NORESPONSE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	fcrozat
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	My fstab My /var/log/messages

Description Tazio Ceri 2012-01-31 19:43:11 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

Everytime I boot with systemd, the system got stuck. Pressing ESC in the boot screen makes me see that systemd has stopped after fscking my / filesystem, which is under software RAID-1.
I have to press control + alt + canc repeatedly to reboot the system with system V init.
That did not happen when I first installed OpenSUSE 12.1.

Reproducible: Always

Steps to Reproduce:
1.Update your OpenSUSE 12.1
2.Boot with the default init system.
3.Verify that it hangs on your RAID-1 root filesystems.
Actual Results:  
The system is stuck, but it still reacts to control+alt+canc keys.

Expected Results:  
Booting should work flawlessly

Comment 1 Frederic Crozat 2012-02-02 15:20:43 UTC

Does it fallback to emergency mode after a timeout of 5min ?

Could you try booting with systemd.log_level=debug systemd.log_target=kmsg and attach dmesg output ?

You might also try to install systemd package from http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12.1/ it contains additional fixes (but I'm not sure it will fix your issue).

Your bug sounds similar to bnc#743717

Could you describe your partitions and mount point in details so I try to duplicate it in a VM ? 

Thanks.

Comment 2 Tazio Ceri 2012-02-03 00:11:57 UTC

Created attachment 474174 [details]
My fstab

This is my fstab. It's generated by YaST (no manual editing)

Comment 3 Tazio Ceri 2012-02-03 00:13:53 UTC

I am using systemd from fcrosat: repository. No improvement.

My bug is different from #743717 because it always happens, and fsck does not fail.

I will try to boot with those options as soon as possible ( tomorrow in the evening).
I don't think I have been waiting for 5 minutes, I will do that as well.

Comment 4 Frederic Crozat 2012-02-03 11:59:28 UTC

Tazio, I' reproduced your setup in a VM, with for 12.1 install (no updates) and all updates installed and I can't reproduce the problem.

if you can't get a emergency shell after waiting for 5 minutes, boot with systemd.log_level=debug systemd.log_target=syslog

then reboot under sysvinit and attach /var/log/messages, it should contain systemd debug trace.

Comment 5 Frederic Crozat 2012-02-03 13:55:17 UTC

If you can boot under systemd, I'm also interested into output of :
systemctl status md.service

Comment 6 Tazio Ceri 2012-02-04 14:30:00 UTC

(In reply to comment #5)
> If you can boot under systemd, I'm also interested into output of :
> systemctl status md.service

md.service - LSB: Multiple Device RAID
          Loaded: loaded (/etc/init.d/boot.md)
          Active: active (exited) since Fri, 03 Feb 2012 19:02:25 +0100; 11min ago
         Process: 720 ExecStart=/etc/init.d/boot.md start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/md.service

Comment 7 Tazio Ceri 2012-02-04 14:55:11 UTC

Created attachment 474447 [details]
My /var/log/messages

Comment 8 Frederic Crozat 2012-02-06 10:39:07 UTC

Why do you think it is related to RAID1 ?

I see network.service is failing, could you update sysconfig and dhcp package from http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/openSUSE:/12.1:/Update:/Test/openSUSE_12.1/ and see if it helps ?

If it doesn't, try the following :
ln -s /lib/systemd/system/rescue.target /etc/systemd/system/kbrequest.target
and reboot with systemd.log_level=debug systemd.log_target=kmsg

then, when everything seems stuck, press alt-up : it should ask you for root password, then get "dmesg" output and attach it to this bug report (/var/log/messages was unfortunately incomplete).

Comment 9 Kun Kun Zhang 2012-03-09 12:28:31 UTC

Long time no response.So closed.Feel free to reopen it.Thanks.