NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
disk failure on firmware upgrade to 6.4.2
I upgraded at the weekend to 6.4.2 from 6.4.1. immediately afterwards the disk in drive 1 failed (on 102). i don't believe in co-incidences. both disks were healthy prior to the upgrade (cycle count 55, status new and all green with no email alerts re system degrade status). There were no errors shown in the log prior to upgrade. The system is now degraded with drive 1 not being recognized in spite of being removed and re-inserted (with power recycle). both disks are 3 Tb WD red .... both bought at the same time and about 2 yrs old. logs are available. I am only using < 20% of capacity so not that either. running in RAID 1.
however as co-incidence would be unlikely, I suspect there is a problem with the upgrade process. I have downgraded to 6.4.1 with no success. thoughts ?
partial log: (logs were saved immediately after the upgrade)
Feb 21 12:58:58 macnas5 snapperd[3152]: Listening for method calls and signals
Feb 21 12:58:58 macnas5 kernel: md1: detected capacity change from 536543232 to 0
Feb 21 12:58:58 macnas5 kernel: md: md1 stopped.
Feb 21 12:58:58 macnas5 kernel: md: unbind
Feb 21 12:58:58 macnas5 kernel: md: export_rdev(sda2)
Feb 21 12:58:58 macnas5 mdadm[2547]: DeviceDisappeared event detected on md device /dev/md1
Feb 21 12:58:58 macnas5 kernel: md: bind
Feb 21 12:58:58 macnas5 kernel: md/raid1:md1: active with 1 out of 1 mirrors
Feb 21 12:58:58 macnas5 kernel: md1: detected capacity change from 0 to 536281088
Feb 21 12:58:58 macnas5 mdadm[2547]: NewArray event detected on md device /dev/md1
Feb 21 12:58:58 macnas5 kernel: Adding 523708k swap on /dev/md1. Priority:-1 extents:1 across:523708k
Feb 21 12:58:58 macnas5 readynasd[2889]: find_available_disk: Searching for disk to repair 'data'...
Feb 21 12:58:58 macnas5 readynasd[2889]: find_available_disk: Checking disk sda...
Feb 21 12:58:58 macnas5 rn-expand[2889]: Trying auto-expand (in-place)
Feb 21 12:58:59 macnas5 readynasd[2889]: ResetFailedUnit: GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
Feb 21 12:58:59 macnas5 apache2[3268]: [Sun Feb 21 12:58:59 2016] [warn] Useless use of AllowOverride in line 4 of /etc/frontview/apache/apps-https.conf.
Feb 21 12:58:59 macnas5 apache2[3268]: [Sun Feb 21 12:58:59 2016] [warn] Useless use of AllowOverride in line 4 of /etc/frontview/apache/apps-https.conf.
Feb 21 12:58:59 macnas5 apache2[3268]: apache2: Could not reliably determine the server's fully qualified domain name, using fd8c:34fd:cf75:100:2ac6:8eff:fe34:9244 for ServerName
Feb 21 12:58:59 macnas5 apache2[3268]: Syntax OK
Feb 21 12:59:00 macnas5 rn-expand[2889]: Trying auto-extend (grow onto additional disks)
Feb 21 12:59:00 macnas5 rn-expand[2889]: Trying xraid-expand (tiered expansion)
Feb 21 12:59:00 macnas5 apache2[2886]: [warn] RSA server certificate CommonName (CN) `nas-34-92-44.local' does NOT match server name!? Feb 21 12:59:00 macnas5 apache2[2886]: [warn] long lost child came home! (pid 2887)
Feb 21 12:59:00 macnas5 apache2[2886]: [warn] long lost child came home! (pid 2888)
Feb 21 12:59:00 macnas5 fvbackup-q[3290]: Start fvbackup-q
Feb 21 12:59:00 macnas5 readynasd[2889]: Volume data is Degraded.
Feb 21 12:59:00 macnas5 upnphttpd[3300]: upnphttpd is started
Feb 21 12:59:00 macnas5 systemd[1]: Startup finished in 53s 876ms 578us (kernel) + 1min 4s 683ms 73us (userspace) = 1min 58s 559ms 651us.
Feb 21 12:59:00 macnas5 upnphttpd[3300]: registering uuid:0c35b4ef-dd25-4e58-a4f4-f91fcbe480a6, desc=http://192.168.1.18:10000/nasService.xml, uuid=0c35b4ef-dd25-4e58-a4f4-f91fcbe480a6
Feb 21 12:59:00 macnas5 upnphttpd[3300]: registering upnp:rootdevice, desc=http://192.168.1.18:10000/nasService.xml, uuid=0c35b4ef-dd25-4e58-a4f4-f91fcbe480a6
Feb 21 12:59:00 macnas5 upnphttpd[3300]: registering urn:schemas-upnp-org:device:networkstoragedevice:, desc=http://192.168.1.18:10000/nasService.xml, uuid=0c35b4ef-dd25-4e58-a4f4-f91fcbe480a6
Feb 21 12:59:00 macnas5 readynasd[2889]: ReadyNASOS background service started.
Feb 21 12:59:02 macnas5 msmtpq[3377]: mail for [ -C /etc/msmtprc email@email --timeout=60 ] : send was successful
Feb 21 12:59:03 macnas5 readynasd[2889]: Firmware was upgraded to 6.4.2.
I managed to connect the failed drive to my pc. unfortunately it is completely dead... not recognised by BIOS (so never got to the utilities). it will be on its way back to WD for replacement. I had fortunately ordered a new identical disk during the week and installed it last night. it took about 8 hours to synch but we are now back to normal, although the original disk will no doubt fail soon too.
Thank you for your help. I will see if i can swap out the other disk too with the high load cycle count (and certainly reset it). Then i will go for the upgrade again.
Thank you
6 Replies
Replies have been turned off for this discussion
It'd be best to definitively rule out the disk.
Have you connected the disk to a windows PC and run WDC's Lifeguard diagnostic?
Can you send me your logs (see the Sending Logs link in my sig)?
I would suggest that you test the disk as StephenB suggested.
Your logs show the disk still in the NAS has a very high load cycle count so It was from a batch of WD RED disks with a poor WDIDLE3 setting.
mdgm wrote:
Your logs show the disk still in the NAS has a very high load cycle count so It was from a batch of WD RED disks with a poor WDIDLE3 setting.That's rather unusual - limited to a few early production models. It can be reset (and I suggest you do so). There is a tool you can download from WDC(WD Red Smart Load/Unload Utility): http://download.wdc.com/sata/wd5741.exe
I would suggest that you test the disk as StephenB suggested.
Your logs show the disk still in the NAS has a very high load cycle count so It was from a batch of WD RED disks with a poor WDIDLE3 setting.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
