Bug 4510 - mdadm.service is launched and during boot (I don't use mdadm on my laptop)
Summary: mdadm.service is launched and during boot (I don't use mdadm on my laptop)
Status: RESOLVED DUPLICATE of bug 37
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120
  Show dependency treegraph
 
Reported: 2012-02-13 16:16 CET by Damien Lallement
Modified: 2012-03-24 23:34 CET (History)
1 user (show)

See Also:
Source RPM: mdadm
CVE:
Status comment:


Attachments
systemd-analyze blame (1.67 KB, text/plain)
2012-02-13 16:17 CET, Damien Lallement
Details
systemd-analyze plot (435.75 KB, image/svg+xml)
2012-02-13 16:17 CET, Damien Lallement
Details
systemd-analyze time (91 bytes, text/plain)
2012-02-13 16:17 CET, Damien Lallement
Details

Description Damien Lallement 2012-02-13 16:16:57 CET
Description of problem: I was in Mageia 1 and upgraded my laptop to cauldron. So, I'm know using systemd. I was booting in less than 1 minute before and know, it take 5 minutes to my laptop to boot. If I check with systemd-analyze blame, I can see that it take 6712ms for my laptop to boot. mdadm service is launched but I don't understand why, as I don't use mdadm on my laptop.


Version-Release number of selected component (if applicable):
systemd-40-2.mga2.src.rpm
Comment 1 Damien Lallement 2012-02-13 16:17:14 CET
Created attachment 1548 [details]
systemd-analyze blame
Comment 2 Damien Lallement 2012-02-13 16:17:30 CET
Created attachment 1549 [details]
systemd-analyze plot
Comment 3 Damien Lallement 2012-02-13 16:17:45 CET
Created attachment 1550 [details]
systemd-analyze time
Comment 4 Manuel Hiebel 2012-02-14 00:07:15 CET
it was fixed with a new install https://bugs.mageia.org/show_bug.cgi?id=37

Blocks: (none) => 2120
Source RPM: systemd-40-2.mga2.src.rpm => mdadm

Comment 5 Colin Guthrie 2012-03-24 23:34:08 CET
I'm surprised it takes nearly 7 seconds for mdadm to run (takes only 1s here although it is equally superfluous - /me is disabling it as we speak!). It's also important to remember that this time is not sequential... the plot is good for seeing that.

Also in difference to when that plot was generated, prefdm now loads after network-auth, not network-up. If network-auth is disabled, it'll come up way faster.

As bug #37 is fixed, I think this particular bug can be closed.

I'll mark it as a dupe as that seems most appropriate.

To disable mdadm, just do: systemctl disable mdadm.service (it'll just forward it to chkconfig tho')

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

Status: NEW => RESOLVED
CC: (none) => mageia
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.