NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chyzm
Jan 23, 2019Aspirant
Volume degraded after firmware update to 6.9.5 on RN212
NAS device was upgraded to the 6.9.5 version this evening and after reboot my drive in slot 1 is now showing as degraded. I rebooted and have power reset with no fix. Ran disk tests also with no luck...
Hopchen
Apr 14, 2019Prodigy
ccbnz wrote:
Did you get this sorted?
I seem to have the same problem on my ReadyNAS Pro (upgraded to OS6).
I updated the firmware to 6.9.5 and later disk 1 showed as Failed. I rebooted the NAS and the disk now shows OK but the resync didn’t complete and the NAS display is flashing “Data Degraded”. Not sure what caused this.
Don't assume you hit the same problem because symptoms are similar :) Chances are that your disk is just bad.
If you want to, let me take a look at the logs for you. Download them from the NAS and upload to Google link or similar and PM me the link.
Also, take a backup of the data if you don't have one already. Now is a good time.
ccbnz
Apr 14, 2019Aspirant
Thanks Hopchen .
Yes it may not be the firmware upgrade. I did three things prior to it failing:
(i) Upgraded firmware to 6.9.5
(ii) Changed power settings to disk spin down after 10mins of inactivity
(iii) Installed Plex
It may be related to (ii). From what I've read, it's better to leave the disks spinning all of the time rather than spinning them up. I have an unproven theory that maybe the disks didn't spin up fast enough and the system mapped one as bad. But that's only speculation. This is this alos happend with disk 3 briefly but a reboot fixed it.
I've factory reset the NAS and it seems to be all fine now.
Thanks for the offer of looking at the Log files. I'll take you up on the offer. What I have noticed in mdstat is that /dev/md/data-0 all of the disks are OK but in /dev/md/data-1 it's showing 4 active devices, 5 working devices and 1 spare. UNless somehow disk 3 was also mapped as bad and that's led to a situation where the disks can't resync.
- chyzmApr 14, 2019AspirantI changed the disk spin up setting as you mentioned and will factory reset to see if that fixes issue. I think my issue is support. Netgear makes it so difficult to contact support and then they don’t follow up. It’s a reason to make me leave Netgear products. Thanks for the info!
- StephenBApr 15, 2019Guru - Experienced User
ccbnz wrote:
From what I've read, it's better to leave the disks spinning all of the time rather than spinning them up. I
There's more than one view on that. Personally I enable spindown on all my backup NAS. On the main NAS I enable spindown on off-hours - the idea there is that I don't want to wait for spinup to complete before accessing data. That's annoying, especially with my media player.
It's hard to say if spindown extends the life of the drives (or not). But it does save power.
- ccbnzApr 15, 2019Aspirant
Thanks StephenB . I have used disk spindown before with no problems - but maybe not with these WD Red drives. What I'm wondering is whether my transient disk failure could be related to this spindown/up. I had two disks reporting briefly as failed which seem now perfectly OK following a restart. Both are showing virtually zero errors in their reported health data. What could have caused them to report as being failed? As mentioned previously, I changed three things shortly before this problem ocurred - upgraded to 6.9.5 firmware, set disk spindown after 10 min of inactivity and loaded Plex app. Sort of strange. Any ideas?
- StephenBApr 15, 2019Guru - Experienced User
ccbnz wrote:
Thanks StephenB . I have used disk spindown before with no problems - but maybe not with these WD Red drives.
I am using WD20EFRX, WD30EFRX, WD60EFRX and WD80EFZX with spindown enabled.
The firmware update process updates the OS partition on all the drives. So if you did the reboot fairly quickly after you applied the update, then the disks should still have been all spun up. Either way, the drives are all spun down as part of the shutdown process, and they all are spun up as part of the boot process. While I wouldn't rule your spindown theory out, I think it's not a likely cause.
ccbnz wrote:
I had two disks reporting briefly as failed which seem now perfectly OK following a restart. Both are showing virtually zero errors in their reported health data.
What errors do you see?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!