Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 507396 - sys-fs/mdadm - systemd[1]: mdadm.service operation timed out. Terminating.
Summary: sys-fs/mdadm - systemd[1]: mdadm.service operation timed out. Terminating.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-11 09:56 UTC by Szymon Jaranowski
Modified: 2014-04-13 08:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Jaranowski 2014-04-11 09:56:33 UTC
I'm trying to set up software RAID-1 on systemd-based Gentoo. I'm using tutorial http://wiki.gentoo.org/wiki/Complete_Handbook/Software_RAID. There is only a note on OpenRC service "mdraid"; I'd expect the same, or very similar, name of systemd service. The is no service of the same name "mdraid". There is a service called "mdadm", but it doesn't start.

Reproducible: Always

Steps to Reproduce:
# systemctl start mdraid

or:

# systemctl start mdadm

Actual Results:  
# systemctl start mdraid
Failed to issue method call: Unit mdraid.service failed to load: No such file or directory.

or:

# systemctl start mdadm
Job for mdadm.service failed. See 'systemctl status mdadm.service' and 'journalctl -xn' for details.

Expected Results:  
The start of the service.

I'm using sys-fs/mdadm-3.2.6-r1. "systemctl start mdadm" suggested to see following:

# systemctl status mdadm.service
mdadm.service - Software RAID monitoring and management
   Loaded: loaded (/usr/lib64/systemd/system/mdadm.service; disabled)
   Active: failed (Result: timeout) since Fri 2014-04-11 10:37:27 CEST; 51s ago
  Process: 15082 ExecStart=/sbin/mdadm --monitor --scan -f --pid-file=/run/mdadm/mdadm.pid $MDADM_OPTS (code=exited, status=0/SUCCESS)

Apr 11 10:35:57 ws-spj systemd[1]: PID file /run/mdadm/mdadm.pid not readable (yet?) after start.
Apr 11 10:37:27 ws-spj systemd[1]: mdadm.service operation timed out. Terminating.
Apr 11 10:37:27 ws-spj systemd[1]: Failed to start Software RAID monitoring and management.
Apr 11 10:37:27 ws-spj systemd[1]: Unit mdadm.service entered failed state.

# journalctl -xn
-- Logs begin at Sat 2014-03-29 13:57:33 CET, end at Fri 2014-04-11 10:37:27 CEST. --
Apr 11 10:36:48 ws-spj kernel: usb 1-5: SerialNumber: 0badece7
Apr 11 10:36:48 ws-spj kernel: usb 1-5: usb_probe_device
Apr 11 10:36:48 ws-spj kernel: usb 1-5: configuration #1 chosen from 1 choice
Apr 11 10:36:48 ws-spj kernel: usb 1-5: adding 1-5:1.0 (config #1, interface 0)
Apr 11 10:36:48 ws-spj kernel: usb 1-5: adding 1-5:1.1 (config #1, interface 1)
Apr 11 10:36:48 ws-spj kernel: usb 1-5: adding 1-5:1.2 (config #1, interface 2)
Apr 11 10:36:48 ws-spj kernel: hub 1-0:1.0: state 7 ports 10 chg 0000 evt 0020
Apr 11 10:37:27 ws-spj systemd[1]: mdadm.service operation timed out. Terminating.
Apr 11 10:37:27 ws-spj systemd[1]: Failed to start Software RAID monitoring and management.
-- Subject: Unit mdadm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f0
-- 
-- Unit mdadm.service has failed.
-- 
-- The result is failed.
Apr 11 10:37:27 ws-spj systemd[1]: Unit mdadm.service entered failed state.

RAID kernel modules seems OK:

# lsmod
Module                  Size  Used by
raid1                  26360  0 
md_mod                 98708  1 raid1
...
Comment 1 Pacho Ramos gentoo-dev 2014-04-13 08:42:32 UTC
+*mdadm-3.3-r3 (13 Apr 2014)
+
+  13 Apr 2014; Pacho Ramos <pacho@gentoo.org> +files/mdadm.service-r1,
+  +mdadm-3.3-r3.ebuild:
+  Fix unit file following policy and solving bug #507396 by Szymon Jaranowski
+