Re: RN102 6.4.2 Update: Previously formatted disk(s) detected (Dirty Disks) #26453094

Beerchief · ‎2016-02-10

Hi all,

I just recently upgraded to OS 6.4.2. After the install/upgrade, my RN is now saying in RAIDar:

"Previously formatted disk(s) detected (Dirty Disks)"

I'm not sure what else to try, apart from already reinstalling the OS. It's currently only got 1x3TB disk installed.

Any help apart from "Format the disks" would be great, as data loss due to an OS upgrade from netgear is ridiculous.

mdgm-ntgr · ‎2016-02-10

In ReadyNAS OS 6: Firmware Upgrade Guide and Tips we provide general advice in which we recommend updating your regular backup before updating the firmware.

Normally a firmware update works smoothly but there are rare cases in which it may not.

Beerchief · ‎2016-02-10

Thanks mdgm,

An update.

I put in a different disk, of which it said the same thing. I did format this one (as it had nothing on it), and now it's saying on that drive:

"Corrupt Root"

I believe, if fixing this root problem, the data on the disk i've removed should be good to go. So I imagine a factory reset?

mdgm-ntgr · ‎2016-02-10

You formatted this other drive using RAIDar? Or some other way and you still got corrupt root?

Support has responded to your case and provided instructions on what they need. You should power down the NAS, remove the disk you are experimenting with and put the disk with your data back in the NAS and follow their instructions.

They can then analyse what is going on.

Beerchief · ‎2016-02-10

Thanks mate,

Yeah double dipped shortly after posting here.

I've sent support what they need.

FYI: It was formatting via RAIDar.

mdgm-ntgr · ‎2016-02-10

Support has not yet received your agreement to our Remote Access Policy. They are waiting for this.

mdgm-ntgr · ‎2016-02-11

Support has identified that your disk has 64728 reallocated sectors and 8 current pending sectors and 300 ATA errors. This disk is clearly bad.

It is recommended to check for a failing disk before doing a firmware update. You should not do a firmware update if there is a bad disk in the system. This is mentioned in the guide I referred to earlier.

If you need a data recovery attempt you may need to purchase a data recovery contract. It may be necessary to try cloning the disk using a tool designed to clone a failing disk e.g. dd_rescue

mcdonian · ‎2016-02-22

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), 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. this sounds similiar to this issue. 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 ?

mcdonian · ‎2016-02-22

ie partial log from 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<sda2>
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<sda2>
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.Error:org.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.

StephenB · ‎2016-02-22

The NAS firmware cannot create bad sectors on a disk. 64728 bad sectors is not only unhealthy - it is hopeless.

Since the disk is only 2 years old, it is still under warranty. Contact WDC and arrange for an RMA.

mcdonian · ‎2016-02-25

Please note there are two queries here from different customers. they are potentially linked .... i would appreciate a reply or would you like me to raise as new item/topic ?

StephenB · ‎2016-02-25

@mcdonian wrote:

i would appreciate a reply or would you like me to raise as new item/topic ?

FWIW my earlier reply was directed to you.

Though it is better to start your own thread, since there is often a lot of confusion for responders whn we are trying to sort out what's been happening with multiple posters. So perhaps start again in a new thread.