| Summary: | systemd 2.16.x on archlinux :[ OK ] / [ FAILED ] messages are no more showed during boot | ||
|---|---|---|---|
| Product: | systemd | Reporter: | a.antolini |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED NOTOURBUG | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
boot screenshot
boot sequence |
||
|
Description
a.antolini
2014-09-03 12:18:54 UTC
Same problem with version 2.16 on my system. No messages show on startup. Messages show on shutdown. System still works fine though. I had started a hread at this location (https://bbs.archlinux.org/viewtopic.php?id=186603), before finding this bug report. I discovered that the root cause ( at least for me) could be that the /usr dir is mounted on separated partition! I did some test with an old laptop which have installed a minimal Archlinux always updated (then with systemd 216-3) with no /usr or /var mounted on separated partition With this configuration [ OK ] messages are... OK! I can see them during startup as usual.. Then I tried to replicated on this laptop, the disk partitioning similar to my main desktop where I noticed the issue and where I have /var and /usr mounted on separated partition since I started with Archlinux On laptop, using sysrescuecd and gparted, at first I moved /var on separated partition but nothing changed ( OK messages was visible at startup as usual) then I also moved /usr on separated partition and... BINGO! : All OK messages are not visible at startup and I see only messages related to fsck check like on main desktop. I hope this could help for the issue resolution.. Thanks Andrea Andrea - Good info on testing usr on separate partition. My usr is on a separate/dedicated partition also. This never affected these OK/FAILED boot messages from appearing before. So did something change to require the usr directory not be on a separate partition from now on? ...probably yes ;-) but I'm not a developer; I just only verified that systemd 216 and /usr mounted on separated partition produce this collateral effect, while, as you already told, with all previous version of systemd OK/FAILED messages appeared as expected. maybe nowadays having /usr on separated partition doesn't make sense, but I used to have this config since I started with Linux (not only with Arch) and I would like to continue with that ;) I hope that systemd developers will be able to reproduced the issue then fix it sooner or later :) Andrea Whether /usr is separate or not should not matter for this. What happens if you include 'systemd.show_status=1' on the kernel command line? Created attachment 108429 [details]
boot screenshot
Added the suggested command to the kernel cmdline but unfortunately nothing changed
Attached a captured boot sequence if it can be useful
thanks
Andrea
Created attachment 108430 [details]
boot sequence
/usr must be pre-mounted from the initrd, if it is split off. We don't really support systems where that's not the case. The code short work to a certain level, but you are basically on your own if you mount /usr after boot. Sorry, |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.