NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN104: ghost “NG-8TB-Seagate” volume (RAID unknown) Inactive/Unprotected
I have a ReadyNAS RN104 that’s working fine from the data point of view, but the volume configuration seems corrupted and is generating constant volume health alerts that I cannot clear. I’m hopi...
Based on your and StephenB 's posts, it looks like the issue with the 3TB phantom should now be gone. Is that the case? mdstat shows the right MDADM configuration, at least at the point you made the log, for all four drives. But with the status toggling, that may not always be the case.
Do you have drive spin-down enabled? If so, try turning it off. It's a wild guess, but easy enough to try. If that does make a difference, then the issue may be your power supply not quite having enough power to spin up the drives in the allocated time.
StephenB , do you see any spin-down entries in the logs? And if so, do they correlate with the status toggling?
do you see any spin-down entries in the logs?
A few. 6 March entries are
Mar 06 12:09:57 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 3 (/dev/sdb).
Mar 06 12:10:02 BrAinZ-NAS104 noflushd[2321]: Spindown of disk 3 (/dev/sdb) cancelled.
Mar 06 12:37:08 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 3 (/dev/sdb).
Mar 06 12:37:11 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 2 (/dev/sdc).
Mar 06 12:37:13 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 1 (/dev/sdd).
Mar 06 12:39:37 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 4 (/dev/sda).
Mar 06 12:55:51 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 4 (/dev/sda) after 0:16:11.
Mar 06 12:55:55 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 3 (/dev/sdb) after 0:18:44.
Mar 06 12:55:55 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 2 (/dev/sdc) after 0:18:42.
Mar 06 12:56:00 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 1 (/dev/sdd) after 0:18:44.
Mar 06 13:16:01 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 4 (/dev/sda).
Mar 06 13:16:05 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 3 (/dev/sdb).
Mar 06 13:16:07 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 2 (/dev/sdc).
Mar 06 13:16:09 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 1 (/dev/sdd).
Mar 06 14:10:34 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 4 (/dev/sda) after 0:54:29.
Mar 06 14:10:39 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 2 (/dev/sdc) after 0:54:30.
Mar 06 14:30:37 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 4 (/dev/sda).
Mar 06 14:30:44 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 2 (/dev/sdc).
Mar 06 14:57:40 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 4 (/dev/sda) after 0:27:01.
Mar 06 15:17:42 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 4 (/dev/sda).
Mar 06 15:30:16 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 4 (/dev/sda) after 0:12:31.
Mar 06 15:50:19 BrAinZ-NAS104 noflushd[2321]: Spinning down disk 4 (/dev/sda).
Mar 06 16:00:46 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 4 (/dev/sda) after 0:10:25.
Mar 06 16:00:47 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 3 (/dev/sdb) after 2:44:39.
Mar 06 16:00:57 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 2 (/dev/sdc) after 1:30:11.
Mar 06 16:00:57 BrAinZ-NAS104 noflushd[2321]: Spinning up disk 1 (/dev/sdd) after 2:44:45.
And if so, do they correlate with the status toggling?
No. The status is toggling much faster. This snippet is toggling while SDD is spun down, and continues after it spins up at 16:00:57.
[26/03/06 15:59:59 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:00:10 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:00:12 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:00:23 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:00:24 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:00:36 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:00:37 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:00:48 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:00:50 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:01:01 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:01:03 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:01:16 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:01:17 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:01:28 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:01:30 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:01:41 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:03:19 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:03:30 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:03:32 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:03:43 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:03:44 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:03:55 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:03:57 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:04:08 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:04:10 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/06 16:04:22 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/06 16:04:24 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
