|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd failed to mount /home when home is raid1 partition | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Olivier Nicolas <o.nicolas> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | RC 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | dmesg | ||
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 *** |
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.