Bug 728543 - systemd failed to mount /home when home is raid1 partition
Summary: systemd failed to mount /home when home is raid1 partition
Status: RESOLVED DUPLICATE of bug 724912
Alias: None
Product: openSUSE 12.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: RC 2
Hardware: x86-64 Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Frederic Crozat
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-05 16:39 UTC by Olivier Nicolas
Modified: 2011-11-07 14:31 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
dmesg (160.38 KB, text/plain)
2011-11-05 16:39 UTC, Olivier Nicolas 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Nicolas 2011-11-05 16:39:14 UTC 
Created attachment 460613 [details]
dmesg

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

/home is mounted form /dev/md2

Most of the time, systemd start fsck on /dev/md2 but raid is not yet assembled.

[   13.704299] systemd-fsck[845]: fsck.ext3: Invalid argument while trying to open /dev/md2
[   13.704367] systemd-fsck[845]: /dev/md2:
[   13.704391] systemd-fsck[845]: The superblock could not be read or does not describe a correct ext2

[   14.166607] md: bind<sda5>
[   14.220503] md: raid1 personality registered for level 1
[   14.220733] bio: create slab <bio-1> at 1
[   14.220815] md/raid1:md2: active with 2 out of 2 mirrors
[   14.220839] md2: detected capacity change from 0 to 33295826944


Problem does not happen when SysV init is used.

Reproducible: Sometimes

Steps to Reproduce:
1. boot using systemd 
2. enter emergency mode 
3. manually mount the /home filesystem "systemctl restart home.mount"
4.
Comment 1 Frederic Crozat 2011-11-07 14:31:55 UTC 
looks like a dup of bnc#724912 (you might not be using crypto, but the bug is really about systemd not waiting enough for md to be "ready")

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