August 16, 201213 yr I was monitoring the progress of a new drive that was clearing (via the web interface) and noticed around 83% all the drives were flashing and spundown. Any idea why the drives all spun down for no apparent reason? The syslog shows the following: Aug 15 19:49:19 Tower emhttp: ... clearing 65% complete Aug 15 19:55:51 Tower emhttp: ... clearing 66% complete Aug 15 20:02:19 Tower emhttp: ... clearing 67% complete Aug 15 20:08:52 Tower emhttp: ... clearing 68% complete Aug 15 20:15:24 Tower emhttp: ... clearing 69% complete Aug 15 20:21:52 Tower emhttp: ... clearing 70% complete Aug 15 20:28:21 Tower emhttp: ... clearing 71% complete Aug 15 20:34:50 Tower emhttp: ... clearing 72% complete Aug 15 20:41:22 Tower emhttp: ... clearing 73% complete Aug 15 20:47:54 Tower emhttp: ... clearing 74% complete Aug 15 20:54:35 Tower emhttp: ... clearing 75% complete Aug 15 21:01:21 Tower emhttp: ... clearing 76% complete Aug 15 21:07:53 Tower emhttp: ... clearing 77% complete Aug 15 21:14:32 Tower emhttp: ... clearing 78% complete Aug 15 21:21:19 Tower emhttp: ... clearing 79% complete Aug 15 21:28:16 Tower emhttp: ... clearing 80% complete Aug 15 21:35:04 Tower emhttp: ... clearing 81% complete Aug 15 21:41:55 Tower emhttp: ... clearing 82% complete Aug 15 21:49:01 Tower emhttp: ... clearing 83% complete Aug 15 21:52:00 Tower kernel: mdcmd (40): spindown 0 Aug 15 21:52:00 Tower kernel: mdcmd (41): spindown 1 Aug 15 21:52:01 Tower kernel: mdcmd (42): spindown 2 Aug 15 21:52:02 Tower kernel: mdcmd (43): spindown 3 Aug 15 21:52:03 Tower kernel: mdcmd (44): spindown 4 Aug 15 21:52:03 Tower kernel: mdcmd (45): spindown 5 Aug 15 21:52:03 Tower kernel: mdcmd (46): spindown 6 Aug 15 21:52:03 Tower kernel: mdcmd (47): spindown 7 Aug 15 21:52:04 Tower kernel: mdcmd (48): spindown 8 Aug 15 21:52:04 Tower kernel: mdcmd (49): spindown 9 Aug 15 21:52:04 Tower kernel: mdcmd (50): spindown 10 Aug 15 21:52:05 Tower kernel: mdcmd (51): spindown 11 Aug 15 21:52:11 Tower kernel: mdcmd (53): spindown 11 Aug 15 21:52:15 Tower kernel: mdcmd (55): spindown 11 Aug 15 21:52:35 Tower kernel: mdcmd (57): spindown 11
August 16, 201213 yr Author From tailing the syslog, it looks like it's still clearing the new drive - but I'm seeing the following: Aug 15 21:53:19 Tower in.telnetd[2333]: connect from 10.0.1.2 (10.0.1.2) Aug 15 21:53:20 Tower login[2334]: ROOT LOGIN on `pts/0' from `10.0.1.2' Aug 15 21:55:29 Tower emhttp: ... clearing 84% complete Aug 15 21:57:02 Tower kernel: mdcmd (59): spindown 11 Aug 15 21:57:35 Tower kernel: mdcmd (61): spindown 11 Aug 15 21:57:42 Tower kernel: mdcmd (63): spindown 11 Aug 15 21:58:00 Tower kernel: mdcmd (65): spindown 11 Aug 15 22:01:28 Tower emhttp: ... clearing 85% complete
August 16, 201213 yr From tailing the syslog, it looks like it's still clearing the new drive - but I'm seeing the following: Aug 15 21:53:19 Tower in.telnetd[2333]: connect from 10.0.1.2 (10.0.1.2) Aug 15 21:53:20 Tower login[2334]: ROOT LOGIN on `pts/0' from `10.0.1.2' Aug 15 21:55:29 Tower emhttp: ... clearing 84% complete Aug 15 21:57:02 Tower kernel: mdcmd (59): spindown 11 Aug 15 21:57:35 Tower kernel: mdcmd (61): spindown 11 Aug 15 21:57:42 Tower kernel: mdcmd (63): spindown 11 Aug 15 21:58:00 Tower kernel: mdcmd (65): spindown 11 Aug 15 22:01:28 Tower emhttp: ... clearing 85% complete What version of unRAID are you using?
Archived
This topic is now archived and is closed to further replies.