Package Details: raid-check-systemd 4.2-5

Git Clone URL: https://aur.archlinux.org/raid-check-systemd.git (read-only, click to copy)
Package Base: raid-check-systemd
Description: Raid data scrubbing script with systemd timer to be used with mdadm.
Upstream URL: https://wiki.archlinux.org/index.php/RAID#Scrubbing
Keywords: mdadm raid scrub systemd
Licenses: GPL
Conflicts: raid-check
Submitter: TheChickenMan
Maintainer: GI_Jack
Last Packager: GI_Jack
Votes: 14
Popularity: 0.000714
First Submitted: 2016-06-07 08:44 (UTC)
Last Updated: 2024-04-23 16:41 (UTC)

Pinned Comments

TheChickenMan commented on 2017-04-30 19:00 (UTC)

You can view the status of the service while it is running in the kernel log with dmesg. You can also review status with the following: $ systemctl status raid-check.service $ systemctl status raid-check.timer $ systemctl list-timers --all

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Ryblade commented on 2017-09-19 10:35 (UTC)

Gah, I've been all over the place with this one. Glad to see you're up as early as I am :). Thanks for getting on this.

TheChickenMan commented on 2017-09-19 10:26 (UTC)

Looks like they updated their source to mdadm-4.0-5.el7.x86_64.rpm

TheChickenMan commented on 2017-09-01 11:27 (UTC)

You are supposed to use: $ sudo systemctl enable raid-check.timer

morosa commented on 2017-09-01 11:17 (UTC)

I have that problem: systemctl enable /usr/lib/systemd/system/raid-check.service The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified.

TheChickenMan commented on 2017-05-02 09:51 (UTC)

Yes, it does say "started" again even though it's actually finished.

ncoder-2 commented on 2017-05-02 01:42 (UTC)

I just did a systemctl status raid-check.service and I get the following: May 01 08:00:15 host1 systemd[1]: Starting raid-check... May 01 08:42:21 host1 systemd[1]: Started raid-check. I'm guessing it started at 08:00:15. Did it finish at 08:42:21 even though it says that it "started"?

TheChickenMan commented on 2017-04-30 19:00 (UTC)

You can view the status of the service while it is running in the kernel log with dmesg. You can also review status with the following: $ systemctl status raid-check.service $ systemctl status raid-check.timer $ systemctl list-timers --all

ncoder-2 commented on 2017-04-30 18:51 (UTC)

Is there a way to confirm that the raid-check was actually performed? When I journalctl -u raid-check.service, I have no entries and when I journalctl -u raid-check.timer, I have the "at boot" load of the timer and "at poweroff" stop. It would be nice to have the start time of the raid-check on schedule and the stop time in the journal.

TheChickenMan commented on 2016-11-22 03:30 (UTC) (edited on 2016-11-22 06:55 (UTC) by TheChickenMan)

Good point, makedepends on rpmextract removed.

« First ‹ Previous 1 2 3 Next › Last »