NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS RN20400 Spindown issues, spindown cancelled
I hope someone can help me here before I send this otherwise great NAS back to the supplier.
One big draw for the RN204 was the disk spindown and it just doesnt work. Well I say it doesnt work,...
Hi BrianL,
I have raised this as a support case and have also done some further testing.
I put a power meter on the NAS and it seems to be running at 17W when idle and around 35W when being accessed.
Does this suggest that 2 of the 4 disks are always powered up? And would this be the O/S disk + the disk required to provide RAID 5?
I can understand that some O/S tasks may need to access disk from time to time when idle, but all the time would seem excessive.
Maybe its nothing to do with this but thought you might find the test useful.
Every RAID-5 write requires accessing two drives (and depending on how it is done, could require accessing all four)..
Since the data is striped across the drives, a sustained read will of course require all drives to be spun up.
01 16:52:14 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:52:24 Readynas kernel: smbd(26624): dirtied inode 35339 (26624) on md0
Nov 01 16:52:31 Readynas kernel: fvdropbox(3989): WRITE block 1654000 on md0 (8 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: fvdropbox(3989): WRITE block 1654008 on md0 (8 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:52:31 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:52:46 Readynas noflushd[22873]: Spinning down disk 3 (/dev/sdb).
Nov 01 16:52:46 Readynas kernel: rnutil(26638): dirtied inode 35339 (event.sq3-journal) on md0
Nov 01 16:52:46 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:52:46 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:52:46 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:52:48 Readynas kernel: fvdropbox(3989): WRITE block 1654016 on md0 (8 sectors)
Nov 01 16:52:48 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:52:48 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:52:48 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:52:48 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:52:50 Readynas kernel: fvdropbox(3989): WRITE block 1654024 on md0 (8 sectors)
Nov 01 16:52:50 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:52:50 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:52:50 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:52:50 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:52:54 Readynas noflushd[22873]: Spinning up disk 3 (/dev/sdb) after 0:00:05.
Nov 01 16:52:54 Readynas kernel: rnutil(26644): dirtied inode 35339 (event.sq3-journal) on md0
Nov 01 16:52:54 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:52:54 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:52:54 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:04 Readynas noflushd[22873]: Spinning down disk 1 (/dev/sdd).
Nov 01 16:53:04 Readynas kernel: rnutil(26650): dirtied inode 35339 (event.sq3-journal) on md0
Nov 01 16:53:04 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:04 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:04 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:06 Readynas kernel: fvdropbox(3989): WRITE block 1654032 on md0 (8 sectors)
Nov 01 16:53:06 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:53:06 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:53:06 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:53:06 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:53:07 Readynas noflushd[22873]: Spinning down disk 2 (/dev/sdc).
Nov 01 16:53:07 Readynas kernel: rnutil(26655): dirtied inode 35339 (event.sq3-journal) on md0
Nov 01 16:53:07 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:07 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:07 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:08 Readynas kernel: fvdropbox(3989): WRITE block 1654040 on md0 (8 sectors)
Nov 01 16:53:09 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:53:09 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:53:09 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:53:09 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:53:09 Readynas kernel: _get_ups_info.D(26657): dirtied inode 59728 (_get_ups_info.Dg2PHy) on tmpfs
Nov 01 16:53:14 Readynas noflushd[22873]: Spinning up disk 1 (/dev/sdd) after 0:00:07.
Nov 01 16:53:14 Readynas kernel: rnutil(26662): dirtied inode 35339 (event.sq3-journal) on md0
Nov 01 16:53:14 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:14 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:15 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:24 Readynas kernel: smbd(26667): dirtied inode 35339 (26667) on md0
Nov 01 16:53:25 Readynas kernel: readynasd(3687): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:25 Readynas kernel: readynasd(3687): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:25 Readynas kernel: fvdropbox(3989): WRITE block 1654048 on md0 (8 sectors)
Nov 01 16:53:25 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:53:25 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:53:25 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:53:25 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:53:30 Readynas kernel: fvdropbox(3989): WRITE block 1654056 on md0 (8 sectors)
Nov 01 16:53:30 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:53:30 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:53:30 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:53:30 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:53:35 Readynas noflushd[22873]: Spinning up disk 2 (/dev/sdc) after 0:00:26.
Nov 01 16:53:35 Readynas kernel: rnutil(26674): dirtied inode 35339 (event.sq3-journal) on md0
Nov 01 16:53:35 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:35 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:35 Readynas kernel: readynasd(3987): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:46 Readynas kernel: readynasd(3687): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:46 Readynas kernel: readynasd(3687): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:53:47 Readynas kernel: fvdropbox(3989): WRITE block 1654064 on md0 (8 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: fvdropbox(3989): WRITE block 1654072 on md0 (8 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sda1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdd1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdc1 (1 sectors)
Nov 01 16:53:47 Readynas kernel: md0_raid1(1474): WRITE block 8 on sdb1 (1 sectors)
Nov 01 16:53:56 Readynas kernel: readynasd(3687): dirtied inode 4026532032 (LCD) on proc
Nov 01 16:54:04 Readynas kernel: fvdropbox(3989): WRITE block 1654080 on md0 (8 sectors)I accept that activity will cause disks to spin, but my concern is that if during sustained periods of no activity there is so much activity that the disks never actually spin down for more than a few seconds, then the feature is not worth having.
I have experienced the spin down working so I know it can work, however in its current state, my NAS is not able to operate it correctly.
As I mentioned before, I raised a case with Netgear support and Level 3 have been able to reproduce the problem in their labs. I am now awaiting a repsonse to their findings.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
