Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Spindown every minute

pfp
in unRAID Server 4.4 [No new topics]

Featured Replies

This goes on for hours.  Is this actually doing something or just a logging problem?  Could this possibly be harming my drives?

My spindown delay is set for 4 hours. 

 

Mar 9 23:53:14 Ruprecht kernel: mdcmd (6764): spindown 0
Mar 9 23:54:02 Ruprecht kernel: mdcmd (6770): spindown 0
Mar 9 23:54:12 Ruprecht kernel: mdcmd (6773): spindown 0
Mar 9 23:54:33 Ruprecht kernel: mdcmd (6776): spindown 1
Mar 9 23:54:34 Ruprecht kernel: mdcmd (6777): spindown 2
Mar 9 23:55:16 Ruprecht kernel: mdcmd (6782): spindown 0
Mar 9 23:55:45 Ruprecht kernel: mdcmd (6784): spindown 0
Mar 9 23:55:45 Ruprecht kernel: mdcmd (6786): spindown 1
Mar 9 23:55:47 Ruprecht kernel: mdcmd (6787): spindown 2
Mar 9 23:56:58 Ruprecht kernel: mdcmd (6795): spindown 0
Mar 9 23:57:24 Ruprecht kernel: mdcmd (6797): spindown 0
Mar 9 23:57:24 Ruprecht kernel: mdcmd (6799): spindown 1
Mar 9 23:57:25 Ruprecht kernel: mdcmd (6800): spindown 2
Mar 9 23:58:37 Ruprecht kernel: mdcmd (6808): spindown 0
Mar 9 23:58:50 Ruprecht kernel: mdcmd (6811): spindown 0
Mar 9 23:58:50 Ruprecht kernel: mdcmd (6812): spindown 1
Mar 9 23:58:55 Ruprecht kernel: mdcmd (6813): spindown 2
Mar 9 23:59:53 Ruprecht kernel: mdcmd (6820): spindown 0
Mar 10 00:00:18 Ruprecht kernel: mdcmd (6822): spindown 0
Mar 10 00:00:18 Ruprecht kernel: mdcmd (6823): spindown 1
Mar 10 00:00:20 Ruprecht kernel: mdcmd (6824): spindown 2
Mar 10 00:02:01 Ruprecht kernel: mdcmd (6836): spindown 0
Mar 10 00:02:23 Ruprecht kernel: mdcmd (6838): spindown 0
Mar 10 00:02:24 Ruprecht kernel: mdcmd (6839): spindown 1
Mar 10 00:02:27 Ruprecht kernel: mdcmd (6840): spindown 2
Mar 10 00:04:11 Ruprecht kernel: mdcmd (6852): spindown 0
Mar 10 00:04:25 Ruprecht kernel: mdcmd (6855): spindown 0
Mar 10 00:04:26 Ruprecht kernel: mdcmd (6856): spindown 1
Mar 10 00:04:30 Ruprecht kernel: mdcmd (6857): spindown 2
Mar 10 00:05:29 Ruprecht kernel: mdcmd (6864): spindown 0
Mar 10 00:05:49 Ruprecht kernel: mdcmd (6866): spindown 0
Mar 10 00:05:50 Ruprecht kernel: mdcmd (6867): spindown 1
Mar 10 00:05:51 Ruprecht kernel: mdcmd (6869): spindown 2
Mar 10 00:07:03 Ruprecht kernel: mdcmd (6877): spindown 0
Mar 10 00:07:29 Ruprecht kernel: mdcmd (6879): spindown 0
Mar 10 00:07:29 Ruprecht kernel: mdcmd (6880): spindown 1
Mar 10 00:07:31 Ruprecht kernel: mdcmd (6881): spindown 2
Mar 10 00:09:26 Ruprecht kernel: mdcmd (6893): spindown 0
Mar 10 00:09:43 Ruprecht kernel: mdcmd (6896): spindown 0
Mar 10 00:09:43 Ruprecht kernel: mdcmd (6897): spindown 1
Mar 10 00:09:47 Ruprecht kernel: mdcmd (6898): spindown 2
Mar 10 00:10:38 Ruprecht kernel: mdcmd (6904): spindown 4
Mar 10 00:10:52 Ruprecht kernel: mdcmd (6907): spindown 0
Mar 10 00:11:05 Ruprecht kernel: mdcmd (6910): spindown 0
Mar 10 00:11:06 Ruprecht kernel: mdcmd (6911): spindown 1
Mar 10 00:11:12 Ruprecht kernel: mdcmd (6912): spindown 2
Mar 10 00:11:21 Ruprecht kernel: mdcmd (6913): spindown 4
Mar 10 00:11:32 Ruprecht kernel: mdcmd (6915): spindown 4
Mar 10 00:12:17 Ruprecht kernel: mdcmd (6921): spindown 0
Mar 10 00:12:31 Ruprecht kernel: mdcmd (6924): spindown 0
Mar 10 00:12:32 Ruprecht kernel: mdcmd (6925): spindown 1
Mar 10 00:12:35 Ruprecht kernel: mdcmd (6926): spindown 2
Mar 10 00:12:44 Ruprecht kernel: mdcmd (6927): spindown 4
Mar 10 00:12:55 Ruprecht kernel: mdcmd (6929): spindown 4
Mar 10 00:13:35 Ruprecht kernel: mdcmd (6934): spindown 0
Mar 10 00:14:00 Ruprecht kernel: mdcmd (6936): spindown 0
Mar 10 00:14:00 Ruprecht kernel: mdcmd (6937): spindown 1
Mar 10 00:14:03 Ruprecht kernel: mdcmd (6938): spindown 2
Mar 10 00:14:12 Ruprecht kernel: mdcmd (6939): spindown 4
Mar 10 00:14:32 Ruprecht kernel: mdcmd (6941): spindown 4
Mar 10 00:15:45 Ruprecht kernel: mdcmd (6950): spindown 0
Mar 10 00:16:01 Ruprecht kernel: mdcmd (6952): spindown 0
Mar 10 00:16:02 Ruprecht kernel: mdcmd (6953): spindown 1
Mar 10 00:16:14 Ruprecht kernel: mdcmd (6956): spindown 2
Mar 10 00:16:21 Ruprecht kernel: mdcmd (6957): spindown 4
Mar 10 00:16:32 Ruprecht kernel: mdcmd (6959): spindown 4
Mar 10 00:17:17 Ruprecht kernel: mdcmd (6965): spindown 0
Mar 10 00:17:33 Ruprecht kernel: mdcmd (6968): spindown 0
Mar 10 00:17:34 Ruprecht kernel: mdcmd (6969): spindown 1
Mar 10 00:17:36 Ruprecht kernel: mdcmd (6970): spindown 2
Mar 10 00:17:45 Ruprecht kernel: mdcmd (6971): spindown 4
Mar 10 00:17:59 Ruprecht kernel: mdcmd (6973): spindown 4
Mar 10 00:18:40 Ruprecht kernel: mdcmd (6978): spindown 0
Mar 10 00:18:51 Ruprecht kernel: mdcmd (6981): spindown 0
Mar 10 00:18:52 Ruprecht kernel: mdcmd (6982): spindown 1
Mar 10 00:18:58 Ruprecht kernel: mdcmd (6983): spindown 2
Mar 10 00:19:07 Ruprecht kernel: mdcmd (6984): spindown 4
Mar 10 00:19:18 Ruprecht kernel: mdcmd (6986): spindown 4
Mar 10 00:19:59 Ruprecht kernel: mdcmd (6991): spindown 0
Mar 10 00:20:19 Ruprecht kernel: mdcmd (6993): spindown 0
Mar 10 00:20:19 Ruprecht kernel: mdcmd (6994): spindown 1
Mar 10 00:20:20 Ruprecht kernel: mdcmd (6996): spindown 2
Mar 10 00:20:27 Ruprecht kernel: mdcmd (6997): spindown 4
Mar 10 00:20:38 Ruprecht kernel: mdcmd (6999): spindown 4
Mar 10 00:21:33 Ruprecht kernel: mdcmd (7006): spindown 0
Mar 10 00:21:49 Ruprecht kernel: mdcmd (7008): spindown 0
Mar 10 00:21:50 Ruprecht kernel: mdcmd (7009): spindown 1
Mar 10 00:22:24 Ruprecht kernel: mdcmd (7013): spindown 2
Mar 10 00:22:32 Ruprecht kernel: mdcmd (7014): spindown 4
Mar 10 00:22:43 Ruprecht kernel: mdcmd (7016): spindown 4
Mar 10 00:23:28 Ruprecht kernel: mdcmd (7022): spindown 0
Mar 10 00:23:44 Ruprecht kernel: mdcmd (7025): spindown 0
Mar 10 00:23:45 Ruprecht kernel: mdcmd (7026): spindown 1
Mar 10 00:23:46 Ruprecht kernel: mdcmd (7027): spindown 2
Mar 10 00:23:55 Ruprecht kernel: mdcmd (7028): spindown 4
Mar 10 00:24:06 Ruprecht kernel: mdcmd (7030): spindown 4
Mar 10 00:24:48 Ruprecht kernel: mdcmd (7035): spindown 0
Mar 10 00:25:01 Ruprecht kernel: mdcmd (7038): spindown 0
Mar 10 00:25:02 Ruprecht kernel: mdcmd (7039): spindown 1
Mar 10 00:25:06 Ruprecht kernel: mdcmd (7040): spindown 2
Mar 10 00:25:15 Ruprecht kernel: mdcmd (7041): spindown 4
Mar 10 00:25:27 Ruprecht kernel: mdcmd (7043): spindown 4
Mar 10 00:26:09 Ruprecht kernel: mdcmd (7048): spindown 0
Mar 10 00:26:37 Ruprecht kernel: mdcmd (7050): spindown 0
Mar 10 00:26:38 Ruprecht kernel: mdcmd (7051): spindown 1
Mar 10 00:26:39 Ruprecht kernel: mdcmd (7053): spindown 2
Mar 10 00:26:46 Ruprecht kernel: mdcmd (7054): spindown 4
Mar 10 00:26:57 Ruprecht kernel: mdcmd (7056): spindown 4
Mar 10 00:27:51 Ruprecht kernel: mdcmd (7063): spindown 0
Mar 10 00:28:11 Ruprecht kernel: mdcmd (7065): spindown 0
Mar 10 00:28:12 Ruprecht kernel: mdcmd (7066): spindown 1
Mar 10 00:28:15 Ruprecht kernel: mdcmd (7067): spindown 2
Mar 10 00:28:24 Ruprecht kernel: mdcmd (7068): spindown 4
Mar 10 00:28:36 Ruprecht kernel: mdcmd (7070): spindown 4
Mar 10 00:29:50 Ruprecht kernel: mdcmd (7079): spindown 0
Mar 10 00:30:09 Ruprecht kernel: mdcmd (7082): spindown 0
Mar 10 00:30:09 Ruprecht kernel: mdcmd (7083): spindown 1
Mar 10 00:30:10 Ruprecht kernel: mdcmd (7084): spindown 2
Mar 10 00:30:17 Ruprecht kernel: mdcmd (7085): spindown 4
Mar 10 00:30:28 Ruprecht kernel: mdcmd (7087): spindown 4
Mar 10 00:31:13 Ruprecht kernel: mdcmd (7093): spindown 0
Mar 10 00:31:43 Ruprecht kernel: mdcmd (7096): spindown 0
Mar 10 00:31:44 Ruprecht kernel: mdcmd (7097): spindown 1
Mar 10 00:31:45 Ruprecht kernel: mdcmd (7098): spindown 2
Mar 10 00:31:51 Ruprecht kernel: mdcmd (7099): spindown 4
Mar 10 00:32:02 Ruprecht kernel: mdcmd (7101): spindown 4
Mar 10 00:32:56 Ruprecht kernel: mdcmd (7107): spindown 0
Mar 10 00:33:16 Ruprecht kernel: mdcmd (7110): spindown 0
Mar 10 00:33:16 Ruprecht kernel: mdcmd (7111): spindown 1
Mar 10 00:33:17 Ruprecht kernel: mdcmd (7112): spindown 2
Mar 10 00:33:23 Ruprecht kernel: mdcmd (7113): spindown 4
Mar 10 00:33:35 Ruprecht kernel: mdcmd (7115): spindown 4
Mar 10 00:34:19 Ruprecht kernel: mdcmd (7121): spindown 0
Mar 10 00:34:40 Ruprecht kernel: mdcmd (7123): spindown 0
Mar 10 00:34:40 Ruprecht kernel: mdcmd (7124): spindown 1
Mar 10 00:34:43 Ruprecht kernel: mdcmd (7125): spindown 2
Mar 10 00:34:52 Ruprecht kernel: mdcmd (7126): spindown 4
Mar 10 00:35:03 Ruprecht kernel: mdcmd (7129): spindown 4
Mar 10 00:36:11 Ruprecht kernel: mdcmd (7137): spindown 0
Mar 10 00:36:32 Ruprecht kernel: mdcmd (7139): spindown 0
Mar 10 00:36:32 Ruprecht kernel: mdcmd (7141): spindown 1
Mar 10 00:36:33 Ruprecht kernel: mdcmd (7142): spindown 2
Mar 10 00:36:39 Ruprecht kernel: mdcmd (7143): spindown 4
Mar 10 00:36:50 Ruprecht kernel: mdcmd (7145): spindown 4
Mar 10 00:37:45 Ruprecht kernel: mdcmd (7152): spindown 0
Mar 10 00:37:56 Ruprecht kernel: mdcmd (7154): spindown 0
Mar 10 00:37:56 Ruprecht kernel: mdcmd (7155): spindown 1
Mar 10 00:38:37 Ruprecht kernel: mdcmd (7158): spindown 2
Mar 10 00:38:47 Ruprecht kernel: mdcmd (7159): spindown 4
Mar 10 00:40:15 Ruprecht kernel: mdcmd (7170): spindown 0
Mar 10 00:40:33 Ruprecht kernel: mdcmd (7172): spindown 0
Mar 10 00:40:34 Ruprecht kernel: mdcmd (7173): spindown 1
Mar 10 00:40:37 Ruprecht kernel: mdcmd (7174): spindown 2
Mar 10 00:40:45 Ruprecht kernel: mdcmd (7175): spindown 4
Mar 10 00:41:16 Ruprecht kernel: mdcmd (7177): spindown 4
Mar 10 00:42:30 Ruprecht kernel: mdcmd (7186): spindown 0
Mar 10 00:42:59 Ruprecht kernel: mdcmd (7188): spindown 0
Mar 10 00:43:00 Ruprecht kernel: mdcmd (7190): spindown 1
Mar 10 00:43:01 Ruprecht kernel: mdcmd (7191): spindown 2
Mar 10 00:43:07 Ruprecht kernel: mdcmd (7192): spindown 4
Mar 10 00:43:18 Ruprecht kernel: mdcmd (7194): spindown 4
Mar 10 00:44:13 Ruprecht kernel: mdcmd (7201): spindown 0
Mar 10 00:44:29 Ruprecht kernel: mdcmd (7203): spindown 0
Mar 10 00:44:30 Ruprecht kernel: mdcmd (7204): spindown 1
Mar 10 00:44:56 Ruprecht kernel: mdcmd (7206): spindown 2
Mar 10 00:45:11 Ruprecht kernel: mdcmd (7207): spindown 4
Mar 10 00:46:40 Ruprecht kernel: mdcmd (7218): spindown 0
Mar 10 00:47:07 Ruprecht kernel: mdcmd (7221): spindown 0
Mar 10 00:47:07 Ruprecht kernel: mdcmd (7222): spindown 1
Mar 10 00:47:09 Ruprecht kernel: mdcmd (7223): spindown 2
Mar 10 00:47:14 Ruprecht kernel: mdcmd (7224): spindown 4
Mar 10 00:47:26 Ruprecht kernel: mdcmd (7226): spindown 4
Mar 10 00:48:20 Ruprecht kernel: mdcmd (7232): spindown 0
Mar 10 00:48:52 Ruprecht kernel: mdcmd (7234): spindown 0
Mar 10 00:48:52 Ruprecht kernel: mdcmd (7236): spindown 1
Mar 10 00:48:53 Ruprecht kernel: mdcmd (7237): spindown 2
Mar 10 00:48:59 Ruprecht kernel: mdcmd (7238): spindown 4
Mar 10 00:49:10 Ruprecht kernel: mdcmd (7240): spindown 4
Mar 10 00:50:05 Ruprecht kernel: mdcmd (7247): spindown 0
Mar 10 00:50:25 Ruprecht kernel: mdcmd (7249): spindown 0
Mar 10 00:50:26 Ruprecht kernel: mdcmd (7250): spindown 1
Mar 10 00:50:33 Ruprecht kernel: mdcmd (7251): spindown 2
Mar 10 00:50:41 Ruprecht kernel: mdcmd (7252): spindown 4
Mar 10 00:50:54 Ruprecht kernel: mdcmd (7254): spindown 4
Mar 10 00:52:07 Ruprecht kernel: mdcmd (7263): spindown 0
Mar 10 00:52:33 Ruprecht kernel: mdcmd (7265): spindown 0
Mar 10 00:52:34 Ruprecht kernel: mdcmd (7267): spindown 1
Mar 10 00:52:35 Ruprecht kernel: mdcmd (7268): spindown 2
Mar 10 00:52:41 Ruprecht kernel: mdcmd (7269): spindown 4
Mar 10 00:52:52 Ruprecht kernel: mdcmd (7271): spindown 4
Mar 10 00:53:47 Ruprecht kernel: mdcmd (7278): spindown 0
Mar 10 00:54:15 Ruprecht kernel: mdcmd (7280): spindown 0
Mar 10 00:54:16 Ruprecht kernel: mdcmd (7281): spindown 1
Mar 10 00:54:17 Ruprecht kernel: mdcmd (7283): spindown 2
Mar 10 00:54:23 Ruprecht kernel: mdcmd (7284): spindown 4
Mar 10 00:54:34 Ruprecht kernel: mdcmd (7286): spindown 4
Mar 10 00:55:29 Ruprecht kernel: mdcmd (7293): spindown 0
Mar 10 00:55:58 Ruprecht kernel: mdcmd (7295): spindown 0
Mar 10 00:55:59 Ruprecht kernel: mdcmd (7296): spindown 1
Mar 10 00:56:01 Ruprecht kernel: mdcmd (7297): spindown 2
Mar 10 00:56:10 Ruprecht kernel: mdcmd (7298): spindown 4
Mar 10 00:56:38 Ruprecht kernel: mdcmd (7300): spindown 4
Mar 10 00:57:52 Ruprecht kernel: mdcmd (7309): spindown 0
Mar 10 00:58:12 Ruprecht kernel: mdcmd (7311): spindown 0

Something is spinning up the drives and (probably) not going through the "md" interface.

 

What, "add-ons" are you running? 

 

Since unRAID is not aware of the drive spinning up, it keeps spinning it down.

  • Author

unraid 1.3

Monthly parity check

screen

 

I'm also preclearing a drive.

Something is spinning up the drives and (probably) not going through the "md" interface.

 

What, "add-ons" are you running? 

 

Since unRAID is not aware of the drive spinning up, it keeps spinning it down.

If unRAID is not aware of the drive spinning up (i.e., it thinks the disk is spun down) then why would it be trying to spin it down at this time??

 

And even if unRAID detects that a disk has been spun up for some reason (i.e., now unRAID is aware of the drive spinning up),

it should not try to spin it down immediately. It should reset its timer and try to spin it down after the predefined time period.

 

I too noticed at one time that unRAID started to constantly try to spin down my disks. I was not doing anything behind the md driver's back.

I didn't investigate then, I just disabled the unRAID's spin down option, and haven't used it since.

There may be something buggy with unRAID's spindown logic.

 

If unRAID is not aware of the drive spinning up (i.e., it thinks the disk is spun down) then why would it be trying to spin it down at this time??

I'm guessing the logic in emhttp is something like this:

 

while forever

  sleep 1

  If the disk is spinning

    if the spin-down timer has expired (time between last access and now > spin-down-interval)

        spin down the disk.

end while

 

And even if unRAID detects that a disk has been spun up for some reason (i.e., now unRAID is aware of the drive spinning up),

it should not try to spin it down immediately. It should reset its timer and try to spin it down after the predefined time period.

That would be a logical improvement if it tracked internally the spin-status.  If it just looked at the drive itself, it would not know what was expected.

I too noticed at one time that unRAID started to constantly try to spin down my disks. I was not doing anything behind the md driver's back.

I didn't investigate then, I just disabled the unRAID's spin down option, and haven't used it since.

There may be something buggy with unRAID's spindown logic.

The use of hdparm, or smartctl on the /dev/sdX device would be "behind the 'md' driver's back"  Other than that, you might be right.

 

If unRAID is not aware of the drive spinning up (i.e., it thinks the disk is spun down) then why would it be trying to spin it down at this time??

I'm guessing the logic in emhttp is something like this:

 

while forever

 sleep 1

 If the disk is spinning

    if the spin-down timer has expired (time between last access and now > spin-down-interval)

       spin down the disk.

end while

 

From above, let's take the line "If the disk is spinning". The check can be either one of the following:

1) look up the actual disk status: something as easy as hdparm -C

or

2) consult your own local variable THIS_DISK_IS_SPINNING=false

 

From your words "unRAID is not aware of the drive spinning up" I take it you believe it's #2.

But then, if unRAID thinks that the drive is spun down, then why would it attempt to spin it down instead of just do nothing?

Doesn't make sense!

So it has to be #1.

But then unRAID is aware that for some reason the drive has spun up.

UnRAID also knows that it personally spun down that darn disk less than a minute ago, and expected to find it spun down.

In that case unRAID should only reset the "last access" stamp, instead of trying to spin down the disk immediately, over and over again!

 

---

BTW, I fear that the spindown script is indeed trying to keep track of a disk's spin status through the value of some variable, and I think that's a really bad idea. Any time it needs a disk status, it could simply query hdparm. That wouldn't disturb a sleeping disk at all.

This goes on for hours.  Is this actually doing something or just a logging problem?  Could this possibly be harming my drives?

My spindown delay is set for 4 hours. 

 

Can you post the contents of disk.cfg?  It is a file found in the config folder of your unRAID flash drive.

  • Author

This goes on for hours.  Is this actually doing something or just a logging problem?  Could this possibly be harming my drives?

My spindown delay is set for 4 hours. 

 

Mar 9 23:53:14 Ruprecht kernel: mdcmd (6764): spindown 0
Mar 9 23:54:02 Ruprecht kernel: mdcmd (6770): spindown 0
Mar 9 23:54:12 Ruprecht kernel: mdcmd (6773): spindown 0
Mar 9 23:54:33 Ruprecht kernel: mdcmd (6776): spindown 1
Mar 9 23:54:34 Ruprecht kernel: mdcmd (6777): spindown 2
Mar 9 23:55:16 Ruprecht kernel: mdcmd (6782): spindown 0
Mar 9 23:55:45 Ruprecht kernel: mdcmd (6784): spindown 0
Mar 9 23:55:45 Ruprecht kernel: mdcmd (6786): spindown 1
Mar 9 23:55:47 Ruprecht kernel: mdcmd (6787): spindown 2
Mar 9 23:56:58 Ruprecht kernel: mdcmd (6795): spindown 0
Mar 9 23:57:24 Ruprecht kernel: mdcmd (6797): spindown 0
Mar 9 23:57:24 Ruprecht kernel: mdcmd (6799): spindown 1
Mar 9 23:57:25 Ruprecht kernel: mdcmd (6800): spindown 2
Mar 9 23:58:37 Ruprecht kernel: mdcmd (6808): spindown 0
Mar 9 23:58:50 Ruprecht kernel: mdcmd (6811): spindown 0
Mar 9 23:58:50 Ruprecht kernel: mdcmd (6812): spindown 1
Mar 9 23:58:55 Ruprecht kernel: mdcmd (6813): spindown 2
Mar 9 23:59:53 Ruprecht kernel: mdcmd (6820): spindown 0
Mar 10 00:00:18 Ruprecht kernel: mdcmd (6822): spindown 0
Mar 10 00:00:18 Ruprecht kernel: mdcmd (6823): spindown 1
Mar 10 00:00:20 Ruprecht kernel: mdcmd (6824): spindown 2
Mar 10 00:02:01 Ruprecht kernel: mdcmd (6836): spindown 0
Mar 10 00:02:23 Ruprecht kernel: mdcmd (6838): spindown 0
Mar 10 00:02:24 Ruprecht kernel: mdcmd (6839): spindown 1
Mar 10 00:02:27 Ruprecht kernel: mdcmd (6840): spindown 2
Mar 10 00:04:11 Ruprecht kernel: mdcmd (6852): spindown 0
Mar 10 00:04:25 Ruprecht kernel: mdcmd (6855): spindown 0
Mar 10 00:04:26 Ruprecht kernel: mdcmd (6856): spindown 1
Mar 10 00:04:30 Ruprecht kernel: mdcmd (6857): spindown 2
Mar 10 00:05:29 Ruprecht kernel: mdcmd (6864): spindown 0
Mar 10 00:05:49 Ruprecht kernel: mdcmd (6866): spindown 0
Mar 10 00:05:50 Ruprecht kernel: mdcmd (6867): spindown 1
Mar 10 00:05:51 Ruprecht kernel: mdcmd (6869): spindown 2
Mar 10 00:07:03 Ruprecht kernel: mdcmd (6877): spindown 0
Mar 10 00:07:29 Ruprecht kernel: mdcmd (6879): spindown 0
Mar 10 00:07:29 Ruprecht kernel: mdcmd (6880): spindown 1
Mar 10 00:07:31 Ruprecht kernel: mdcmd (6881): spindown 2
Mar 10 00:09:26 Ruprecht kernel: mdcmd (6893): spindown 0
Mar 10 00:09:43 Ruprecht kernel: mdcmd (6896): spindown 0
Mar 10 00:09:43 Ruprecht kernel: mdcmd (6897): spindown 1
Mar 10 00:09:47 Ruprecht kernel: mdcmd (6898): spindown 2
Mar 10 00:10:38 Ruprecht kernel: mdcmd (6904): spindown 4
Mar 10 00:10:52 Ruprecht kernel: mdcmd (6907): spindown 0
Mar 10 00:11:05 Ruprecht kernel: mdcmd (6910): spindown 0
Mar 10 00:11:06 Ruprecht kernel: mdcmd (6911): spindown 1
Mar 10 00:11:12 Ruprecht kernel: mdcmd (6912): spindown 2
Mar 10 00:11:21 Ruprecht kernel: mdcmd (6913): spindown 4
Mar 10 00:11:32 Ruprecht kernel: mdcmd (6915): spindown 4
Mar 10 00:12:17 Ruprecht kernel: mdcmd (6921): spindown 0
Mar 10 00:12:31 Ruprecht kernel: mdcmd (6924): spindown 0
Mar 10 00:12:32 Ruprecht kernel: mdcmd (6925): spindown 1
Mar 10 00:12:35 Ruprecht kernel: mdcmd (6926): spindown 2
Mar 10 00:12:44 Ruprecht kernel: mdcmd (6927): spindown 4
Mar 10 00:12:55 Ruprecht kernel: mdcmd (6929): spindown 4
Mar 10 00:13:35 Ruprecht kernel: mdcmd (6934): spindown 0
Mar 10 00:14:00 Ruprecht kernel: mdcmd (6936): spindown 0
Mar 10 00:14:00 Ruprecht kernel: mdcmd (6937): spindown 1
Mar 10 00:14:03 Ruprecht kernel: mdcmd (6938): spindown 2
Mar 10 00:14:12 Ruprecht kernel: mdcmd (6939): spindown 4
Mar 10 00:14:32 Ruprecht kernel: mdcmd (6941): spindown 4
Mar 10 00:15:45 Ruprecht kernel: mdcmd (6950): spindown 0
Mar 10 00:16:01 Ruprecht kernel: mdcmd (6952): spindown 0
Mar 10 00:16:02 Ruprecht kernel: mdcmd (6953): spindown 1
Mar 10 00:16:14 Ruprecht kernel: mdcmd (6956): spindown 2
Mar 10 00:16:21 Ruprecht kernel: mdcmd (6957): spindown 4
Mar 10 00:16:32 Ruprecht kernel: mdcmd (6959): spindown 4
Mar 10 00:17:17 Ruprecht kernel: mdcmd (6965): spindown 0
Mar 10 00:17:33 Ruprecht kernel: mdcmd (6968): spindown 0
Mar 10 00:17:34 Ruprecht kernel: mdcmd (6969): spindown 1
Mar 10 00:17:36 Ruprecht kernel: mdcmd (6970): spindown 2
Mar 10 00:17:45 Ruprecht kernel: mdcmd (6971): spindown 4
Mar 10 00:17:59 Ruprecht kernel: mdcmd (6973): spindown 4
Mar 10 00:18:40 Ruprecht kernel: mdcmd (6978): spindown 0
Mar 10 00:18:51 Ruprecht kernel: mdcmd (6981): spindown 0
Mar 10 00:18:52 Ruprecht kernel: mdcmd (6982): spindown 1
Mar 10 00:18:58 Ruprecht kernel: mdcmd (6983): spindown 2
Mar 10 00:19:07 Ruprecht kernel: mdcmd (6984): spindown 4
Mar 10 00:19:18 Ruprecht kernel: mdcmd (6986): spindown 4
Mar 10 00:19:59 Ruprecht kernel: mdcmd (6991): spindown 0
Mar 10 00:20:19 Ruprecht kernel: mdcmd (6993): spindown 0
Mar 10 00:20:19 Ruprecht kernel: mdcmd (6994): spindown 1
Mar 10 00:20:20 Ruprecht kernel: mdcmd (6996): spindown 2
Mar 10 00:20:27 Ruprecht kernel: mdcmd (6997): spindown 4
Mar 10 00:20:38 Ruprecht kernel: mdcmd (6999): spindown 4
Mar 10 00:21:33 Ruprecht kernel: mdcmd (7006): spindown 0
Mar 10 00:21:49 Ruprecht kernel: mdcmd (7008): spindown 0
Mar 10 00:21:50 Ruprecht kernel: mdcmd (7009): spindown 1
Mar 10 00:22:24 Ruprecht kernel: mdcmd (7013): spindown 2
Mar 10 00:22:32 Ruprecht kernel: mdcmd (7014): spindown 4
Mar 10 00:22:43 Ruprecht kernel: mdcmd (7016): spindown 4
Mar 10 00:23:28 Ruprecht kernel: mdcmd (7022): spindown 0
Mar 10 00:23:44 Ruprecht kernel: mdcmd (7025): spindown 0
Mar 10 00:23:45 Ruprecht kernel: mdcmd (7026): spindown 1
Mar 10 00:23:46 Ruprecht kernel: mdcmd (7027): spindown 2
Mar 10 00:23:55 Ruprecht kernel: mdcmd (7028): spindown 4
Mar 10 00:24:06 Ruprecht kernel: mdcmd (7030): spindown 4
Mar 10 00:24:48 Ruprecht kernel: mdcmd (7035): spindown 0
Mar 10 00:25:01 Ruprecht kernel: mdcmd (7038): spindown 0
Mar 10 00:25:02 Ruprecht kernel: mdcmd (7039): spindown 1
Mar 10 00:25:06 Ruprecht kernel: mdcmd (7040): spindown 2
Mar 10 00:25:15 Ruprecht kernel: mdcmd (7041): spindown 4
Mar 10 00:25:27 Ruprecht kernel: mdcmd (7043): spindown 4
Mar 10 00:26:09 Ruprecht kernel: mdcmd (7048): spindown 0
Mar 10 00:26:37 Ruprecht kernel: mdcmd (7050): spindown 0
Mar 10 00:26:38 Ruprecht kernel: mdcmd (7051): spindown 1
Mar 10 00:26:39 Ruprecht kernel: mdcmd (7053): spindown 2
Mar 10 00:26:46 Ruprecht kernel: mdcmd (7054): spindown 4
Mar 10 00:26:57 Ruprecht kernel: mdcmd (7056): spindown 4
Mar 10 00:27:51 Ruprecht kernel: mdcmd (7063): spindown 0
Mar 10 00:28:11 Ruprecht kernel: mdcmd (7065): spindown 0
Mar 10 00:28:12 Ruprecht kernel: mdcmd (7066): spindown 1
Mar 10 00:28:15 Ruprecht kernel: mdcmd (7067): spindown 2
Mar 10 00:28:24 Ruprecht kernel: mdcmd (7068): spindown 4
Mar 10 00:28:36 Ruprecht kernel: mdcmd (7070): spindown 4
Mar 10 00:29:50 Ruprecht kernel: mdcmd (7079): spindown 0
Mar 10 00:30:09 Ruprecht kernel: mdcmd (7082): spindown 0
Mar 10 00:30:09 Ruprecht kernel: mdcmd (7083): spindown 1
Mar 10 00:30:10 Ruprecht kernel: mdcmd (7084): spindown 2
Mar 10 00:30:17 Ruprecht kernel: mdcmd (7085): spindown 4
Mar 10 00:30:28 Ruprecht kernel: mdcmd (7087): spindown 4
Mar 10 00:31:13 Ruprecht kernel: mdcmd (7093): spindown 0
Mar 10 00:31:43 Ruprecht kernel: mdcmd (7096): spindown 0
Mar 10 00:31:44 Ruprecht kernel: mdcmd (7097): spindown 1
Mar 10 00:31:45 Ruprecht kernel: mdcmd (7098): spindown 2
Mar 10 00:31:51 Ruprecht kernel: mdcmd (7099): spindown 4
Mar 10 00:32:02 Ruprecht kernel: mdcmd (7101): spindown 4
Mar 10 00:32:56 Ruprecht kernel: mdcmd (7107): spindown 0
Mar 10 00:33:16 Ruprecht kernel: mdcmd (7110): spindown 0
Mar 10 00:33:16 Ruprecht kernel: mdcmd (7111): spindown 1
Mar 10 00:33:17 Ruprecht kernel: mdcmd (7112): spindown 2
Mar 10 00:33:23 Ruprecht kernel: mdcmd (7113): spindown 4
Mar 10 00:33:35 Ruprecht kernel: mdcmd (7115): spindown 4
Mar 10 00:34:19 Ruprecht kernel: mdcmd (7121): spindown 0
Mar 10 00:34:40 Ruprecht kernel: mdcmd (7123): spindown 0
Mar 10 00:34:40 Ruprecht kernel: mdcmd (7124): spindown 1
Mar 10 00:34:43 Ruprecht kernel: mdcmd (7125): spindown 2
Mar 10 00:34:52 Ruprecht kernel: mdcmd (7126): spindown 4
Mar 10 00:35:03 Ruprecht kernel: mdcmd (7129): spindown 4
Mar 10 00:36:11 Ruprecht kernel: mdcmd (7137): spindown 0
Mar 10 00:36:32 Ruprecht kernel: mdcmd (7139): spindown 0
Mar 10 00:36:32 Ruprecht kernel: mdcmd (7141): spindown 1
Mar 10 00:36:33 Ruprecht kernel: mdcmd (7142): spindown 2
Mar 10 00:36:39 Ruprecht kernel: mdcmd (7143): spindown 4
Mar 10 00:36:50 Ruprecht kernel: mdcmd (7145): spindown 4
Mar 10 00:37:45 Ruprecht kernel: mdcmd (7152): spindown 0
Mar 10 00:37:56 Ruprecht kernel: mdcmd (7154): spindown 0
Mar 10 00:37:56 Ruprecht kernel: mdcmd (7155): spindown 1
Mar 10 00:38:37 Ruprecht kernel: mdcmd (7158): spindown 2
Mar 10 00:38:47 Ruprecht kernel: mdcmd (7159): spindown 4
Mar 10 00:40:15 Ruprecht kernel: mdcmd (7170): spindown 0
Mar 10 00:40:33 Ruprecht kernel: mdcmd (7172): spindown 0
Mar 10 00:40:34 Ruprecht kernel: mdcmd (7173): spindown 1
Mar 10 00:40:37 Ruprecht kernel: mdcmd (7174): spindown 2
Mar 10 00:40:45 Ruprecht kernel: mdcmd (7175): spindown 4
Mar 10 00:41:16 Ruprecht kernel: mdcmd (7177): spindown 4
Mar 10 00:42:30 Ruprecht kernel: mdcmd (7186): spindown 0
Mar 10 00:42:59 Ruprecht kernel: mdcmd (7188): spindown 0
Mar 10 00:43:00 Ruprecht kernel: mdcmd (7190): spindown 1
Mar 10 00:43:01 Ruprecht kernel: mdcmd (7191): spindown 2
Mar 10 00:43:07 Ruprecht kernel: mdcmd (7192): spindown 4
Mar 10 00:43:18 Ruprecht kernel: mdcmd (7194): spindown 4
Mar 10 00:44:13 Ruprecht kernel: mdcmd (7201): spindown 0
Mar 10 00:44:29 Ruprecht kernel: mdcmd (7203): spindown 0
Mar 10 00:44:30 Ruprecht kernel: mdcmd (7204): spindown 1
Mar 10 00:44:56 Ruprecht kernel: mdcmd (7206): spindown 2
Mar 10 00:45:11 Ruprecht kernel: mdcmd (7207): spindown 4
Mar 10 00:46:40 Ruprecht kernel: mdcmd (7218): spindown 0
Mar 10 00:47:07 Ruprecht kernel: mdcmd (7221): spindown 0
Mar 10 00:47:07 Ruprecht kernel: mdcmd (7222): spindown 1
Mar 10 00:47:09 Ruprecht kernel: mdcmd (7223): spindown 2
Mar 10 00:47:14 Ruprecht kernel: mdcmd (7224): spindown 4
Mar 10 00:47:26 Ruprecht kernel: mdcmd (7226): spindown 4
Mar 10 00:48:20 Ruprecht kernel: mdcmd (7232): spindown 0
Mar 10 00:48:52 Ruprecht kernel: mdcmd (7234): spindown 0
Mar 10 00:48:52 Ruprecht kernel: mdcmd (7236): spindown 1
Mar 10 00:48:53 Ruprecht kernel: mdcmd (7237): spindown 2
Mar 10 00:48:59 Ruprecht kernel: mdcmd (7238): spindown 4
Mar 10 00:49:10 Ruprecht kernel: mdcmd (7240): spindown 4
Mar 10 00:50:05 Ruprecht kernel: mdcmd (7247): spindown 0
Mar 10 00:50:25 Ruprecht kernel: mdcmd (7249): spindown 0
Mar 10 00:50:26 Ruprecht kernel: mdcmd (7250): spindown 1
Mar 10 00:50:33 Ruprecht kernel: mdcmd (7251): spindown 2
Mar 10 00:50:41 Ruprecht kernel: mdcmd (7252): spindown 4
Mar 10 00:50:54 Ruprecht kernel: mdcmd (7254): spindown 4
Mar 10 00:52:07 Ruprecht kernel: mdcmd (7263): spindown 0
Mar 10 00:52:33 Ruprecht kernel: mdcmd (7265): spindown 0
Mar 10 00:52:34 Ruprecht kernel: mdcmd (7267): spindown 1
Mar 10 00:52:35 Ruprecht kernel: mdcmd (7268): spindown 2
Mar 10 00:52:41 Ruprecht kernel: mdcmd (7269): spindown 4
Mar 10 00:52:52 Ruprecht kernel: mdcmd (7271): spindown 4
Mar 10 00:53:47 Ruprecht kernel: mdcmd (7278): spindown 0
Mar 10 00:54:15 Ruprecht kernel: mdcmd (7280): spindown 0
Mar 10 00:54:16 Ruprecht kernel: mdcmd (7281): spindown 1
Mar 10 00:54:17 Ruprecht kernel: mdcmd (7283): spindown 2
Mar 10 00:54:23 Ruprecht kernel: mdcmd (7284): spindown 4
Mar 10 00:54:34 Ruprecht kernel: mdcmd (7286): spindown 4
Mar 10 00:55:29 Ruprecht kernel: mdcmd (7293): spindown 0
Mar 10 00:55:58 Ruprecht kernel: mdcmd (7295): spindown 0
Mar 10 00:55:59 Ruprecht kernel: mdcmd (7296): spindown 1
Mar 10 00:56:01 Ruprecht kernel: mdcmd (7297): spindown 2
Mar 10 00:56:10 Ruprecht kernel: mdcmd (7298): spindown 4
Mar 10 00:56:38 Ruprecht kernel: mdcmd (7300): spindown 4
Mar 10 00:57:52 Ruprecht kernel: mdcmd (7309): spindown 0
Mar 10 00:58:12 Ruprecht kernel: mdcmd (7311): spindown 0

 

I'm beginning to think unmenu is somehow involved in this.  Up till now I have typically left a browser window open with the unmenu Main screen being displayed.  This screen does a refresh every minute - my drives spin down every minute - Hmmm?  I've since switched to leaving unmenu on the MyMain page.  This page does not normally refresh.  After my drives spin down I notice additional spindown messages every time I refresh this unmenu page.  

 

First let me just say that what I know about unRAID and / or Linux couldn't fill a thimble, but...  My theory is that somehow by reading the drive information displayed on these unmenu screens unRAID thinks the drives have been spun up and then spins them down.    

This goes on for hours.  Is this actually doing something or just a logging problem?  Could this possibly be harming my drives?

My spindown delay is set for 4 hours.  

 

Mar 9 23:53:14 Ruprecht kernel: mdcmd (6764): spindown 0
Mar 9 23:54:02 Ruprecht kernel: mdcmd (6770): spindown 0
Mar 9 23:54:12 Ruprecht kernel: mdcmd (6773): spindown 0
Mar 9 23:54:33 Ruprecht kernel: mdcmd (6776): spindown 1
Mar 9 23:54:34 Ruprecht kernel: mdcmd (6777): spindown 2
Mar 9 23:55:16 Ruprecht kernel: mdcmd (6782): spindown 0
Mar 9 23:55:45 Ruprecht kernel: mdcmd (6784): spindown 0
Mar 9 23:55:45 Ruprecht kernel: mdcmd (6786): spindown 1
Mar 9 23:55:47 Ruprecht kernel: mdcmd (6787): spindown 2
Mar 9 23:56:58 Ruprecht kernel: mdcmd (6795): spindown 0
Mar 9 23:57:24 Ruprecht kernel: mdcmd (6797): spindown 0
Mar 9 23:57:24 Ruprecht kernel: mdcmd (6799): spindown 1
Mar 9 23:57:25 Ruprecht kernel: mdcmd (6800): spindown 2
Mar 9 23:58:37 Ruprecht kernel: mdcmd (6808): spindown 0
Mar 9 23:58:50 Ruprecht kernel: mdcmd (6811): spindown 0
Mar 9 23:58:50 Ruprecht kernel: mdcmd (6812): spindown 1
Mar 9 23:58:55 Ruprecht kernel: mdcmd (6813): spindown 2
Mar 9 23:59:53 Ruprecht kernel: mdcmd (6820): spindown 0
Mar 10 00:00:18 Ruprecht kernel: mdcmd (6822): spindown 0
Mar 10 00:00:18 Ruprecht kernel: mdcmd (6823): spindown 1
Mar 10 00:00:20 Ruprecht kernel: mdcmd (6824): spindown 2
Mar 10 00:02:01 Ruprecht kernel: mdcmd (6836): spindown 0
Mar 10 00:02:23 Ruprecht kernel: mdcmd (6838): spindown 0
Mar 10 00:02:24 Ruprecht kernel: mdcmd (6839): spindown 1
Mar 10 00:02:27 Ruprecht kernel: mdcmd (6840): spindown 2
Mar 10 00:04:11 Ruprecht kernel: mdcmd (6852): spindown 0
Mar 10 00:04:25 Ruprecht kernel: mdcmd (6855): spindown 0
Mar 10 00:04:26 Ruprecht kernel: mdcmd (6856): spindown 1
Mar 10 00:04:30 Ruprecht kernel: mdcmd (6857): spindown 2
Mar 10 00:05:29 Ruprecht kernel: mdcmd (6864): spindown 0
Mar 10 00:05:49 Ruprecht kernel: mdcmd (6866): spindown 0
Mar 10 00:05:50 Ruprecht kernel: mdcmd (6867): spindown 1
Mar 10 00:05:51 Ruprecht kernel: mdcmd (6869): spindown 2
Mar 10 00:07:03 Ruprecht kernel: mdcmd (6877): spindown 0
Mar 10 00:07:29 Ruprecht kernel: mdcmd (6879): spindown 0
Mar 10 00:07:29 Ruprecht kernel: mdcmd (6880): spindown 1
Mar 10 00:07:31 Ruprecht kernel: mdcmd (6881): spindown 2
Mar 10 00:09:26 Ruprecht kernel: mdcmd (6893): spindown 0
Mar 10 00:09:43 Ruprecht kernel: mdcmd (6896): spindown 0
Mar 10 00:09:43 Ruprecht kernel: mdcmd (6897): spindown 1
Mar 10 00:09:47 Ruprecht kernel: mdcmd (6898): spindown 2
Mar 10 00:10:38 Ruprecht kernel: mdcmd (6904): spindown 4
Mar 10 00:10:52 Ruprecht kernel: mdcmd (6907): spindown 0
Mar 10 00:11:05 Ruprecht kernel: mdcmd (6910): spindown 0
Mar 10 00:11:06 Ruprecht kernel: mdcmd (6911): spindown 1
Mar 10 00:11:12 Ruprecht kernel: mdcmd (6912): spindown 2
Mar 10 00:11:21 Ruprecht kernel: mdcmd (6913): spindown 4
Mar 10 00:11:32 Ruprecht kernel: mdcmd (6915): spindown 4
Mar 10 00:12:17 Ruprecht kernel: mdcmd (6921): spindown 0
Mar 10 00:12:31 Ruprecht kernel: mdcmd (6924): spindown 0
Mar 10 00:12:32 Ruprecht kernel: mdcmd (6925): spindown 1
Mar 10 00:12:35 Ruprecht kernel: mdcmd (6926): spindown 2
Mar 10 00:12:44 Ruprecht kernel: mdcmd (6927): spindown 4
Mar 10 00:12:55 Ruprecht kernel: mdcmd (6929): spindown 4
Mar 10 00:13:35 Ruprecht kernel: mdcmd (6934): spindown 0
Mar 10 00:14:00 Ruprecht kernel: mdcmd (6936): spindown 0
Mar 10 00:14:00 Ruprecht kernel: mdcmd (6937): spindown 1
Mar 10 00:14:03 Ruprecht kernel: mdcmd (6938): spindown 2
Mar 10 00:14:12 Ruprecht kernel: mdcmd (6939): spindown 4
Mar 10 00:14:32 Ruprecht kernel: mdcmd (6941): spindown 4
Mar 10 00:15:45 Ruprecht kernel: mdcmd (6950): spindown 0
Mar 10 00:16:01 Ruprecht kernel: mdcmd (6952): spindown 0
Mar 10 00:16:02 Ruprecht kernel: mdcmd (6953): spindown 1
Mar 10 00:16:14 Ruprecht kernel: mdcmd (6956): spindown 2
Mar 10 00:16:21 Ruprecht kernel: mdcmd (6957): spindown 4
Mar 10 00:16:32 Ruprecht kernel: mdcmd (6959): spindown 4
Mar 10 00:17:17 Ruprecht kernel: mdcmd (6965): spindown 0
Mar 10 00:17:33 Ruprecht kernel: mdcmd (6968): spindown 0
Mar 10 00:17:34 Ruprecht kernel: mdcmd (6969): spindown 1
Mar 10 00:17:36 Ruprecht kernel: mdcmd (6970): spindown 2
Mar 10 00:17:45 Ruprecht kernel: mdcmd (6971): spindown 4
Mar 10 00:17:59 Ruprecht kernel: mdcmd (6973): spindown 4
Mar 10 00:18:40 Ruprecht kernel: mdcmd (6978): spindown 0
Mar 10 00:18:51 Ruprecht kernel: mdcmd (6981): spindown 0
Mar 10 00:18:52 Ruprecht kernel: mdcmd (6982): spindown 1
Mar 10 00:18:58 Ruprecht kernel: mdcmd (6983): spindown 2
Mar 10 00:19:07 Ruprecht kernel: mdcmd (6984): spindown 4
Mar 10 00:19:18 Ruprecht kernel: mdcmd (6986): spindown 4
Mar 10 00:19:59 Ruprecht kernel: mdcmd (6991): spindown 0
Mar 10 00:20:19 Ruprecht kernel: mdcmd (6993): spindown 0
Mar 10 00:20:19 Ruprecht kernel: mdcmd (6994): spindown 1
Mar 10 00:20:20 Ruprecht kernel: mdcmd (6996): spindown 2
Mar 10 00:20:27 Ruprecht kernel: mdcmd (6997): spindown 4
Mar 10 00:20:38 Ruprecht kernel: mdcmd (6999): spindown 4
Mar 10 00:21:33 Ruprecht kernel: mdcmd (7006): spindown 0
Mar 10 00:21:49 Ruprecht kernel: mdcmd (7008): spindown 0
Mar 10 00:21:50 Ruprecht kernel: mdcmd (7009): spindown 1
Mar 10 00:22:24 Ruprecht kernel: mdcmd (7013): spindown 2
Mar 10 00:22:32 Ruprecht kernel: mdcmd (7014): spindown 4
Mar 10 00:22:43 Ruprecht kernel: mdcmd (7016): spindown 4
Mar 10 00:23:28 Ruprecht kernel: mdcmd (7022): spindown 0
Mar 10 00:23:44 Ruprecht kernel: mdcmd (7025): spindown 0
Mar 10 00:23:45 Ruprecht kernel: mdcmd (7026): spindown 1
Mar 10 00:23:46 Ruprecht kernel: mdcmd (7027): spindown 2
Mar 10 00:23:55 Ruprecht kernel: mdcmd (7028): spindown 4
Mar 10 00:24:06 Ruprecht kernel: mdcmd (7030): spindown 4
Mar 10 00:24:48 Ruprecht kernel: mdcmd (7035): spindown 0
Mar 10 00:25:01 Ruprecht kernel: mdcmd (7038): spindown 0
Mar 10 00:25:02 Ruprecht kernel: mdcmd (7039): spindown 1
Mar 10 00:25:06 Ruprecht kernel: mdcmd (7040): spindown 2
Mar 10 00:25:15 Ruprecht kernel: mdcmd (7041): spindown 4
Mar 10 00:25:27 Ruprecht kernel: mdcmd (7043): spindown 4
Mar 10 00:26:09 Ruprecht kernel: mdcmd (7048): spindown 0
Mar 10 00:26:37 Ruprecht kernel: mdcmd (7050): spindown 0
Mar 10 00:26:38 Ruprecht kernel: mdcmd (7051): spindown 1
Mar 10 00:26:39 Ruprecht kernel: mdcmd (7053): spindown 2
Mar 10 00:26:46 Ruprecht kernel: mdcmd (7054): spindown 4
Mar 10 00:26:57 Ruprecht kernel: mdcmd (7056): spindown 4
Mar 10 00:27:51 Ruprecht kernel: mdcmd (7063): spindown 0
Mar 10 00:28:11 Ruprecht kernel: mdcmd (7065): spindown 0
Mar 10 00:28:12 Ruprecht kernel: mdcmd (7066): spindown 1
Mar 10 00:28:15 Ruprecht kernel: mdcmd (7067): spindown 2
Mar 10 00:28:24 Ruprecht kernel: mdcmd (7068): spindown 4
Mar 10 00:28:36 Ruprecht kernel: mdcmd (7070): spindown 4
Mar 10 00:29:50 Ruprecht kernel: mdcmd (7079): spindown 0
Mar 10 00:30:09 Ruprecht kernel: mdcmd (7082): spindown 0
Mar 10 00:30:09 Ruprecht kernel: mdcmd (7083): spindown 1
Mar 10 00:30:10 Ruprecht kernel: mdcmd (7084): spindown 2
Mar 10 00:30:17 Ruprecht kernel: mdcmd (7085): spindown 4
Mar 10 00:30:28 Ruprecht kernel: mdcmd (7087): spindown 4
Mar 10 00:31:13 Ruprecht kernel: mdcmd (7093): spindown 0
Mar 10 00:31:43 Ruprecht kernel: mdcmd (7096): spindown 0
Mar 10 00:31:44 Ruprecht kernel: mdcmd (7097): spindown 1
Mar 10 00:31:45 Ruprecht kernel: mdcmd (7098): spindown 2
Mar 10 00:31:51 Ruprecht kernel: mdcmd (7099): spindown 4
Mar 10 00:32:02 Ruprecht kernel: mdcmd (7101): spindown 4
Mar 10 00:32:56 Ruprecht kernel: mdcmd (7107): spindown 0
Mar 10 00:33:16 Ruprecht kernel: mdcmd (7110): spindown 0
Mar 10 00:33:16 Ruprecht kernel: mdcmd (7111): spindown 1
Mar 10 00:33:17 Ruprecht kernel: mdcmd (7112): spindown 2
Mar 10 00:33:23 Ruprecht kernel: mdcmd (7113): spindown 4
Mar 10 00:33:35 Ruprecht kernel: mdcmd (7115): spindown 4
Mar 10 00:34:19 Ruprecht kernel: mdcmd (7121): spindown 0
Mar 10 00:34:40 Ruprecht kernel: mdcmd (7123): spindown 0
Mar 10 00:34:40 Ruprecht kernel: mdcmd (7124): spindown 1
Mar 10 00:34:43 Ruprecht kernel: mdcmd (7125): spindown 2
Mar 10 00:34:52 Ruprecht kernel: mdcmd (7126): spindown 4
Mar 10 00:35:03 Ruprecht kernel: mdcmd (7129): spindown 4
Mar 10 00:36:11 Ruprecht kernel: mdcmd (7137): spindown 0
Mar 10 00:36:32 Ruprecht kernel: mdcmd (7139): spindown 0
Mar 10 00:36:32 Ruprecht kernel: mdcmd (7141): spindown 1
Mar 10 00:36:33 Ruprecht kernel: mdcmd (7142): spindown 2
Mar 10 00:36:39 Ruprecht kernel: mdcmd (7143): spindown 4
Mar 10 00:36:50 Ruprecht kernel: mdcmd (7145): spindown 4
Mar 10 00:37:45 Ruprecht kernel: mdcmd (7152): spindown 0
Mar 10 00:37:56 Ruprecht kernel: mdcmd (7154): spindown 0
Mar 10 00:37:56 Ruprecht kernel: mdcmd (7155): spindown 1
Mar 10 00:38:37 Ruprecht kernel: mdcmd (7158): spindown 2
Mar 10 00:38:47 Ruprecht kernel: mdcmd (7159): spindown 4
Mar 10 00:40:15 Ruprecht kernel: mdcmd (7170): spindown 0
Mar 10 00:40:33 Ruprecht kernel: mdcmd (7172): spindown 0
Mar 10 00:40:34 Ruprecht kernel: mdcmd (7173): spindown 1
Mar 10 00:40:37 Ruprecht kernel: mdcmd (7174): spindown 2
Mar 10 00:40:45 Ruprecht kernel: mdcmd (7175): spindown 4
Mar 10 00:41:16 Ruprecht kernel: mdcmd (7177): spindown 4
Mar 10 00:42:30 Ruprecht kernel: mdcmd (7186): spindown 0
Mar 10 00:42:59 Ruprecht kernel: mdcmd (7188): spindown 0
Mar 10 00:43:00 Ruprecht kernel: mdcmd (7190): spindown 1
Mar 10 00:43:01 Ruprecht kernel: mdcmd (7191): spindown 2
Mar 10 00:43:07 Ruprecht kernel: mdcmd (7192): spindown 4
Mar 10 00:43:18 Ruprecht kernel: mdcmd (7194): spindown 4
Mar 10 00:44:13 Ruprecht kernel: mdcmd (7201): spindown 0
Mar 10 00:44:29 Ruprecht kernel: mdcmd (7203): spindown 0
Mar 10 00:44:30 Ruprecht kernel: mdcmd (7204): spindown 1
Mar 10 00:44:56 Ruprecht kernel: mdcmd (7206): spindown 2
Mar 10 00:45:11 Ruprecht kernel: mdcmd (7207): spindown 4
Mar 10 00:46:40 Ruprecht kernel: mdcmd (7218): spindown 0
Mar 10 00:47:07 Ruprecht kernel: mdcmd (7221): spindown 0
Mar 10 00:47:07 Ruprecht kernel: mdcmd (7222): spindown 1
Mar 10 00:47:09 Ruprecht kernel: mdcmd (7223): spindown 2
Mar 10 00:47:14 Ruprecht kernel: mdcmd (7224): spindown 4
Mar 10 00:47:26 Ruprecht kernel: mdcmd (7226): spindown 4
Mar 10 00:48:20 Ruprecht kernel: mdcmd (7232): spindown 0
Mar 10 00:48:52 Ruprecht kernel: mdcmd (7234): spindown 0
Mar 10 00:48:52 Ruprecht kernel: mdcmd (7236): spindown 1
Mar 10 00:48:53 Ruprecht kernel: mdcmd (7237): spindown 2
Mar 10 00:48:59 Ruprecht kernel: mdcmd (7238): spindown 4
Mar 10 00:49:10 Ruprecht kernel: mdcmd (7240): spindown 4
Mar 10 00:50:05 Ruprecht kernel: mdcmd (7247): spindown 0
Mar 10 00:50:25 Ruprecht kernel: mdcmd (7249): spindown 0
Mar 10 00:50:26 Ruprecht kernel: mdcmd (7250): spindown 1
Mar 10 00:50:33 Ruprecht kernel: mdcmd (7251): spindown 2
Mar 10 00:50:41 Ruprecht kernel: mdcmd (7252): spindown 4
Mar 10 00:50:54 Ruprecht kernel: mdcmd (7254): spindown 4
Mar 10 00:52:07 Ruprecht kernel: mdcmd (7263): spindown 0
Mar 10 00:52:33 Ruprecht kernel: mdcmd (7265): spindown 0
Mar 10 00:52:34 Ruprecht kernel: mdcmd (7267): spindown 1
Mar 10 00:52:35 Ruprecht kernel: mdcmd (7268): spindown 2
Mar 10 00:52:41 Ruprecht kernel: mdcmd (7269): spindown 4
Mar 10 00:52:52 Ruprecht kernel: mdcmd (7271): spindown 4
Mar 10 00:53:47 Ruprecht kernel: mdcmd (7278): spindown 0
Mar 10 00:54:15 Ruprecht kernel: mdcmd (7280): spindown 0
Mar 10 00:54:16 Ruprecht kernel: mdcmd (7281): spindown 1
Mar 10 00:54:17 Ruprecht kernel: mdcmd (7283): spindown 2
Mar 10 00:54:23 Ruprecht kernel: mdcmd (7284): spindown 4
Mar 10 00:54:34 Ruprecht kernel: mdcmd (7286): spindown 4
Mar 10 00:55:29 Ruprecht kernel: mdcmd (7293): spindown 0
Mar 10 00:55:58 Ruprecht kernel: mdcmd (7295): spindown 0
Mar 10 00:55:59 Ruprecht kernel: mdcmd (7296): spindown 1
Mar 10 00:56:01 Ruprecht kernel: mdcmd (7297): spindown 2
Mar 10 00:56:10 Ruprecht kernel: mdcmd (7298): spindown 4
Mar 10 00:56:38 Ruprecht kernel: mdcmd (7300): spindown 4
Mar 10 00:57:52 Ruprecht kernel: mdcmd (7309): spindown 0
Mar 10 00:58:12 Ruprecht kernel: mdcmd (7311): spindown 0

 

I'm beginning to think unmenu is somehow involved in this.

 

I don't use unmenu, but I've seen this problem.  The spindown logic seems broken.

It shouldn't be issuing spindown commands 30 seconds apart over and over again no matter what.

 

Email Limetech, and point them to this thread!

[email protected]

 

  • 1 month later...

Hi, i think i am having the same issue  ???

 

I have unRAID v4.5.3 (Plus)

 

Addons:

 

unMenu

uTorrent (ruTorrent)

 

I noticed a few days ago that i was constantly having two of my disks spin up and down

 

 

partial extract from syslog:

Apr 15 08:21:04 Tower kernel: mdcmd (86172): spindown 0

Apr 15 08:21:05 Tower kernel: mdcmd (86173): spindown 4

Apr 15 08:51:04 Tower kernel: mdcmd (86353): spindown 0

Apr 15 08:51:05 Tower kernel: mdcmd (86354): spindown 4

Apr 15 09:21:04 Tower kernel: mdcmd (86534): spindown 0

Apr 15 09:21:05 Tower kernel: mdcmd (86535): spindown 4

Apr 15 09:51:04 Tower kernel: mdcmd (86715): spindown 0

Apr 15 09:51:05 Tower kernel: mdcmd (86716): spindown 4

Apr 15 10:21:04 Tower kernel: mdcmd (86896): spindown 0

Apr 15 10:21:05 Tower kernel: mdcmd (86897): spindown 4

Apr 15 10:51:04 Tower kernel: mdcmd (87077): spindown 0

Apr 15 10:51:05 Tower kernel: mdcmd (87078): spindown 4

Apr 15 11:21:04 Tower kernel: mdcmd (87258): spindown 0

Apr 15 11:21:04 Tower kernel: mdcmd (87259): spindown 4

Apr 15 11:51:04 Tower kernel: mdcmd (87439): spindown 0

Apr 15 11:51:04 Tower kernel: mdcmd (87440): spindown 4

Apr 15 12:21:04 Tower kernel: mdcmd (87620): spindown 0

Apr 15 12:21:04 Tower kernel: mdcmd (87621): spindown 4

Apr 15 12:51:04 Tower kernel: mdcmd (87801): spindown 0

Apr 15 12:51:04 Tower kernel: mdcmd (87802): spindown 4

Apr 15 13:21:04 Tower kernel: mdcmd (87982): spindown 0

Apr 15 13:21:04 Tower kernel: mdcmd (87983): spindown 4

Apr 15 13:51:04 Tower kernel: mdcmd (88163): spindown 0

Apr 15 13:51:04 Tower kernel: mdcmd (88164): spindown 4

Apr 15 14:21:04 Tower kernel: mdcmd (88344): spindown 0

Apr 15 14:21:04 Tower kernel: mdcmd (88345): spindown 4

Apr 15 14:51:04 Tower kernel: mdcmd (88525): spindown 0

Apr 15 14:51:04 Tower kernel: mdcmd (88526): spindown 4

Apr 15 15:21:04 Tower kernel: mdcmd (88706): spindown 0

Apr 15 15:21:04 Tower kernel: mdcmd (88707): spindown 4

Apr 15 15:51:04 Tower kernel: mdcmd (88887): spindown 0

Apr 15 15:51:04 Tower kernel: mdcmd (88888): spindown 4

Apr 15 16:21:03 Tower kernel: mdcmd (89068): spindown 0

Apr 15 16:21:04 Tower kernel: mdcmd (89069): spindown 4

Apr 15 16:51:03 Tower kernel: mdcmd (89249): spindown 0

Apr 15 16:51:04 Tower kernel: mdcmd (89250): spindown 4

Apr 15 17:21:03 Tower kernel: mdcmd (89430): spindown 0

Apr 15 17:21:04 Tower kernel: mdcmd (89431): spindown 4

Apr 15 17:51:03 Tower kernel: mdcmd (89611): spindown 0

Apr 15 17:51:04 Tower kernel: mdcmd (89612): spindown 4

Apr 15 18:21:03 Tower kernel: mdcmd (89801): spindown 0

Apr 15 18:21:04 Tower kernel: mdcmd (89802): spindown 4

 

The delay is exaclty 30 minutes apart and Disk4 is the one i use for my torrent downloads. This lead me to be suspicious of torrent addon, but seeing the posts here looks like people are having the same issue without running the torrent add on.

 

Please let me know what else i can do to help you assist with the debugging. Attached is my full syslog and screenshot of my unMain screen. Below is the contents of my disk.cfg file

 

# Disk configuration

spindownDelay=15

queueDepth=1

spinupGroups=no

md_num_stripes_default=1280

md_write_limit_default=768

md_sync_window_default=288

parity=pci-0000:00:08.0-scsi-0:0:0:0

disk1=pci-0000:00:08.0-scsi-1:0:0:0

disk2=pci-0000:00:07.0-scsi-0:0:0:0

disk3=pci-0000:01:00.0-scsi-0:0:0:0

disk4=pci-0000:01:00.0-scsi-1:0:0:0

diskSpindownDelay.0=-1

diskSpindownDelay.1=-1

diskSpindownDelay.2=-1

diskSpindownDelay.3=-1

diskSpindownDelay.4=-1

diskSpinupGroup.0=host3

diskSpinupGroup.1=host1

diskSpinupGroup.2=host1

diskSpinupGroup.3=host1

diskSpinupGroup.4=host2

 

 

thanks!!!

Main.jpg.38fec34a11013742270d9eadbb429f73.jpg

Syslog_16APR10.txt

Monza, that too beggs for a email.  [email protected]

 

done Purko

 

Have not tried rebooting my server yet - anyone who has this same issue and HAS rebooted their server care to comment before i try myself?

I have noticed the same behavior, i'm on 4.5.3 Pro.

 

I'm using the following addons:

unraid_notify-2.55

powerdown-1.02

 

It seems to only happen when there is activity on the server. I first noticed spindown messages every minute whilst preclearing a new HDD and then again when transferring files to the new drive. When there is little or no activity everything looks normal.

 

For the time being I have resorted to disabling the spindown feature as I'm concerned when I can hear the drives spinning up and down all the time unnecessarily.

 

I can post my logs if that helps.

I can post my logs if that helps.

Nothing we can do here to help you, so an email to Limetech would be more helpful. (include syslog)

They should hear from more people about that, so they will hopefully address this issue.

[email protected]

 

  • 1 month later...

Did anyone hear back from Limetech?  I'm seeing this now too?

 

Jim

Did anyone hear back from Limetech?  I'm seeing this now too?

Did you email them?

 

Not yet..  I wanted to see first if anyone else heard back from them..  If they are aware of the problem then I don't want to bug them with a "me too" response..

 

It's been a couple months.  I was looking for an update.

 

Jim

Not yet..  I wanted to see first if anyone else heard back from them..  If they are aware of the problem then I don't want to bug them with a "me too" response..

 

It's been a couple months.  I was looking for an update.

 

Jim

before you do, you will need to disable any add-ons to ensure they are not spinning up the drive (and the unRAID process then spins it down )

 

Can't expect lime-tech to investigate very far if it is something you've done that is the issue.  The one-per minute is too likely to be something you've installed.

 

The older versions of unMENU directly accessed the physical disks to spin them up by reading a random block of data.  That was before unRAID added its own spinup timers and individual spinup/spindown commands.  The newer versions of unMENU use the new spinup and spindown options available through "mdcmd".     

 

The very first thing I'd do is upgrade to the new 1.3 version of unMENU available from here: http://lime-technology.com/forum/index.php?topic=5568.0  Then, if the issue continues, you can isolate further.  The unMENU pages that look at disks are the only ones that could possibly be spinning them up, so migrate to something other than "main" or "myMain" and see if the spindown commands continue.

 

Joe L.

I'm running

 

unmenu.awk: Version 1.3 Revision: 97

 

and unraid

 

version: 4.5.4

 

So I think I'm running the latest..

 

I'm also running unraid_notify

 

 

That is the newest version of unMENU. 

 

Time to disable one or the other to isolate the issue.

 

I don't run unraid_notify, so I don't know how it acts with the newest version of unRAID. 

I see no "spinup" messages here as you are describing, but then, more often than not, many of my disks are spinning.

 

The biggest clue is the frequency of the spindown messages. 

The auto-refresh interval in unMENU's main page is 60 seconds.  You can change that in the unmenu.conf file or by creating an unmenu_local.conf file with one line like this:

REFRESH_INTERVAL = 45

You'll need to re-start unMENU to get it to use the updated value.

 

I do see this note in the unraid_notify thread: 

NOTE:  If you are using unraid_notify with Unraid 4.5beta-12 or greater, you must update to unraid_notify 2.50 or greater.

 

Joe L.

 

  • 3 weeks later...

Not yet..  I wanted to see first if anyone else heard back from them..  If they are aware of the problem then I don't want to bug them with a "me too" response..

 

It's been a couple months.  I was looking for an update.

 

Jim

before you do, you will need to disable any add-ons to ensure they are not spinning up the drive (and the unRAID process then spins it down )

 

Can't expect lime-tech to investigate very far if it is something you've done that is the issue.  The one-per minute is too likely to be something you've installed.

 

Whatever things you've installed, those things are not the ones issuing the spindown commands.  Those things can only be causing disk activity.  And any disk activity on the system is duly recorded in  /sys/block/DEVICE/stat .  There is no excuse for the spindown daemon to miss the fact that disk activity has occured, regardless of what you've installed.  Spindown commands should be only issued after  spindownDelay  minutes of continuous inactivity.

 

  • 2 months later...

I'm having ths problem to, in my case I've got cache_dirs running and I'm moving files from one disk to another.  I have very low memory free according to top, but still 60mb.

I'm wondering if this is happening because of the low memory?  I don't see a pattern in that it's happening every minute or something like that.

 

top - 16:55:45 up 1 day,  5:02,  2 users,  load average: 2.67, 1.49, 1.04

Tasks:  94 total,  4 running,  90 sleeping,  0 stopped,  0 zombie

Cpu(s): 11.9%us, 39.7%sy,  0.0%ni,  7.0%id, 15.2%wa, 15.9%hi, 10.3%si,  0.0%st

Mem:  1294724k total,  1233868k used,    60856k free,  334372k buffers

Swap:        0k total,        0k used,        0k free,  708216k cached

 

Sep 11 16:52:27 Tower kernel: mdcmd (14665): spindown 4

Sep 11 16:52:42 Tower kernel: mdcmd (14667): spindown 4

Sep 11 16:52:42 Tower kernel: mdcmd (14668): spindown 5

Sep 11 16:52:42 Tower kernel: mdcmd (14669): spindown 6

Sep 11 16:52:48 Tower kernel: mdcmd (14670): spindown 7

Sep 11 16:52:59 Tower kernel: mdcmd (14672): spindown 7

Sep 11 16:53:04 Tower kernel: mdcmd (14674): spindown 15

Sep 11 16:53:05 Tower kernel: mdcmd (14675): spindown 16

Sep 11 16:54:15 Tower kernel: mdcmd (14684): spindown 1

Sep 11 16:54:21 Tower kernel: mdcmd (14685): spindown 2

Sep 11 16:54:32 Tower kernel: mdcmd (14687): spindown 2

Sep 11 16:54:32 Tower kernel: mdcmd (14688): spindown 3

Sep 11 16:54:35 Tower kernel: mdcmd (14689): spindown 4

Sep 11 16:54:50 Tower kernel: mdcmd (14691): spindown 4

Sep 11 16:54:50 Tower kernel: mdcmd (14692): spindown 5

Sep 11 16:54:50 Tower kernel: mdcmd (14693): spindown 6

Sep 11 16:54:56 Tower kernel: mdcmd (14694): spindown 7

Sep 11 16:55:07 Tower kernel: mdcmd (14696): spindown 7

Sep 11 16:55:12 Tower kernel: mdcmd (14697): spindown 15

Sep 11 16:55:12 Tower kernel: mdcmd (14698): spindown 16

Sep 11 16:55:22 Tower kernel: mdcmd (14701): spindown 1

Sep 11 16:55:28 Tower kernel: mdcmd (14702): spindown 2

Sep 11 16:55:38 Tower kernel: mdcmd (14704): spindown 2

Sep 11 16:55:38 Tower kernel: mdcmd (14705): spindown 3

 

I'm using 4.5.6 and newest cache_dirs script.

The drives being spun up is likely due to your memory constraints. It's highly probable that you don't have enough memory for cache_dirs and the linux kernel to keep the file and directory entries in memory. When it runs the next cycle since the dentries are not in the memory buffers, it has to read them off the physical drives, hence causing them to spin up.

 

With that said, it's odd that something is trying to spin down your drives when they should likely have recent usage indicators. The disk activity should reset the idle timer so it shouldn't attempt to spin them down.

Sounds like a bug to me too.  The disk activity should have reset the timer that unRAID uses for its spindown timer. 

 

It uses a "time-stamp" of the last I/O on every disk being accessed through the /dev/md devices.  Every so often it compares the time-stamp to the current time.  If the elapsed time is greater than the spin-down interval, the disk is spun down and the timer is reset to "0"  ("0" is supposed to indicate the drive is sleeping.)

 

The only way I can think of repeated spin-down attempts is if the time-stamp is not being set to zero, OR, the disk is spinning up on its own attempting to perform an internal calibration, or a "sort" or "long" test, or something accessing the raw disk device and not going through /dev/mdX.

 

Joe L.

The drives being spun up is likely due to your memory constraints. It's highly probable that you don't have enough memory for cache_dirs and the linux kernel to keep the file and directory entries in memory. When it runs the next cycle since the dentries are not in the memory buffers, it has to read them off the physical drives, hence causing them to spin up.

 

With that said, it's odd that something is trying to spin down your drives when they should likely have recent usage indicators. The disk activity should reset the idle timer so it shouldn't attempt to spin them down.

 

How can I find the info how much mem I would need for cache_dirs ? Memstatus always shows all memory allocated for buffers, right?

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.