× The readycloud.netgear.com login issue with the Chrome browser is now fixed. We are actively working on resolving a similar issue with the Safari browser and recommend you use an alternate browser until this error has been resolved.

Reply

Re: ReadyNas 104 Volume inactive or dead

tasone
Aspirant

ReadyNas 104 Volume inactive or dead

I am hoping someone can help me.

 

I was not able to access my network share that i have setup on my Readynas

 

So I logged into my Readynas 104 and everythinig looked ok, so i did a quick reboot to see if that fixed everything

 

Now all i get is the  "Volume inactive or dead"; all the 4 disks look ok, and i cant see anything in the logs to say something is wrong

 

on the volume page is says "Remove inactive volumes to use the disk disk #1,2,3,4.

 

Any ideas anyone?

 

I tried booting in read only mode, but nothing.

 

There is data on here that would be a magor lost; but i dont have ther money for any recovery service and to top it all off, i just bought a nice 8 bay nas for another location for the data!

 

Thanks

 

Andrew

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 1 of 19
Sandshark
Sensei

Re: ReadyNas 104 Volume inactive or dead

On the Volumes tab, how many volumes are shown (typically, you'll see "data" "data-0", etc.)?

 

On the Performance tab, hovering the mouse over the dot for each drive, which ones say they are a part of which volume?

Message 2 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead


@Sandshark wrote:

On the Volumes tab, how many volumes are shown (typically, you'll see "data" "data-0", etc.)?

 

On the Performance tab, hovering the mouse over the dot for each drive, which ones say they are a part of which volume?



Hi
On the volumes tab their is only one volume showing the cleverly name "Volumeone" (all showing red)

On the Performance tab
Disk 1 - is part of volumeone
Disk 2 - is part of volumeone
Disk 3 - is part of volumeone
Disk 4 - is part of volumeone

On this tab all disks are showing as green with no errors.

Thanks
Andrew

Message 3 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead

Can you download the full log zip file, and post the contents of mdstat.log here?  Just copy/paste it into a reply (the forum won't accept .log files).  Don't post a downloadable link to the full zip, as there is some stuff in there that shouldn't be publicly posted.

Message 4 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead

here is the log file mdstat.log
 
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sdd3[0] sdb3[2] sda3[3] sdc3[4]
      11706506496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
     
md1 : active raid10 sda2[4] sdc2[3] sdd2[2] sdb2[1]
      1046528 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
     
md0 : active raid1 sdd1[0] sdc1[4] sdb1[2] sda1[5]
      4190208 blocks super 1.2 [4/4] [UUUU]
     
unused devices: <none>
/dev/md/0:
           Version : 1.2
     Creation Time : Thu Sep 10 12:41:44 2015
        Raid Level : raid1
        Array Size : 4190208 (4.00 GiB 4.29 GB)
     Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent
       Update Time : Mon Sep 23 18:40:06 2019
             State : active
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0
Consistency Policy : unknown
              Name : 2fe64c78:0  (local to host 2fe64c78)
              UUID : 7c69389f:26cc0e69:b33e47e8:1b7c9c3f
            Events : 1791
    Number   Major   Minor   RaidDevice State
       0       8       49        0      active sync   /dev/sdd1
       5       8        1        1      active sync   /dev/sda1
       2       8       17        2      active sync   /dev/sdb1
       4       8       33        3      active sync   /dev/sdc1
/dev/md/1:
           Version : 1.2
     Creation Time : Mon Mar 11 13:54:24 2019
        Raid Level : raid10
        Array Size : 1046528 (1022.00 MiB 1071.64 MB)
     Used Dev Size : 523264 (511.00 MiB 535.82 MB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent
       Update Time : Mon Sep 23 17:41:48 2019
             State : clean
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0
            Layout : near=2
        Chunk Size : 512K
Consistency Policy : unknown
              Name : 2fe64c78:1  (local to host 2fe64c78)
              UUID : c612366e:755998df:e3e83b5b:953c00f9
            Events : 42
    Number   Major   Minor   RaidDevice State
       4       8        2        0      active sync set-A   /dev/sda2
       1       8       18        1      active sync set-B   /dev/sdb2
       2       8       50        2      active sync set-A   /dev/sdd2
       3       8       34        3      active sync set-B   /dev/sdc2
/dev/md/Volumeone-0:
           Version : 1.2
     Creation Time : Thu Sep 10 14:09:36 2015
        Raid Level : raid5
        Array Size : 11706506496 (11164.19 GiB 11987.46 GB)
     Used Dev Size : 3902168832 (3721.40 GiB 3995.82 GB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent
       Update Time : Mon Sep 23 18:25:08 2019
             State : clean
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0
            Layout : left-symmetric
        Chunk Size : 64K
Consistency Policy : unknown
              Name : 2fe64c78:Volumeone-0  (local to host 2fe64c78)
              UUID : 527ab021:cd91839c:042685ab:432b4a60
            Events : 14117
    Number   Major   Minor   RaidDevice State
       0       8       51        0      active sync   /dev/sdd3
       4       8       35        1      active sync   /dev/sdc3
       3       8        3        2      active sync   /dev/sda3
       2       8       19        3      active sync   /dev/sdb3
Message 5 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead


@tasone wrote:
 
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sdd3[0] sdb3[2] sda3[3] sdc3[4]
...

This is curious, as it is showing that all four drives are still part of the RAID array.  Maybe also look in system.log and kernel.log for BTRFS errors?

 

One option is to send a private message to one of the mods ( @JohnCM_S  or @Marc_V ) with a downloadable link to the full log zip file, and ask them to review it for you.  Don't post the link publicly.  You send a PM using the envelope icon in the upper right of the forum page.

 

Unfortunately I think you will probably need the help of paid support to mount your volume. 

 

 

Message 6 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead

kernel.log is full of btrfs errors

 

Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188839624704 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188839624704 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188839624704 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188839624704 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS warning (device md127): failed to read tree root
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096
Sep 23 18:25:09 TD-Archive kernel: BTRFS warning (device md127): failed to read tree root
Sep 23 18:25:09 TD-Archive kernel: BTRFS error (device md127): open_ctree failed
Sep 23 18:25:17 TD-Archive kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 23 18:25:21 TD-Archive kernel: mvneta d0070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Sep 23 18:25:21 TD-Archive kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

 

and the system log is full of failed path error

Sep 23 18:39:28 TD-Archive snapperd[3153]: THROW: open failed path:/Volumeone/MasterBackups errno:2 (No such file or directory)
Sep 23 18:39:28 TD-Archive snapperd[3153]: reading failed
Sep 23 18:39:28 TD-Archive snapperd[3153]: THROW: open failed path:/Volumeone/Google-Vault errno:2 (No such file or directory)
Sep 23 18:39:28 TD-Archive snapperd[3153]: reading failed
Sep 23 18:39:28 TD-Archive snapperd[3153]: THROW: open failed path:/Volumeone/OneDrive-Vault errno:2 (No such file or directory)
Sep 23 18:39:28 TD-Archive snapperd[3153]: reading failed
Sep 23 18:40:03 TD-Archive apache_access[2593]: 192.168.45.201 "POST /dbbroker HTTP/1.1" 401
Sep 23 18:40:10 TD-Archive rnutil[5285]: Failed to get tier from /dev/md0 : 25

(just small parts of the logs)

 

 

 

Message 7 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead


@tasone wrote:

kernel.log is full of btrfs errors

 

Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188839624704 len 4096

...


 

I was afraid that might be the case. Unfortunately it sounds like you'll need data recovery.

 

If you can connect all four disks to a Windows PC (using sata or USB adapters/enclosures) you could see if ReclaiMe's software could find the files in the volume.  You'd be able to do that prior to purchase.

Message 8 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead

Hi

What is worrying me is that i got no warning about this, it was working and then it was not.

No warning, and it was setup as a raid5 and it is connected to a UPS as well.

 

My worry is i dont know if i can trust netgear nas's  as my old nas broke the same way as well, no warning no nothing it just broke (it was a 2 bay unit, for my media storage so everything was fully backed up)

This is the first time that the data will be a super pain to get back (its backed to various cd/dvd's (over 3000 of them) it was the day before the nas drive, i just had all the old data on this 4 bay archive drive)

 

you can also say yeah  it was the first time i accessed it for ages as i needed a old file from  it, and  it was working ok everything was up then all of a sudding  all  folders went bye bye no warnings no errors just nothing.

 

trying to work out if i should get another make of NAS drive as i dont know netgears devices can be trusted

 

Andrew

Message 9 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead


@tasone wrote:

What is worrying me is that i got no warning about this, it was working and then it was not.

...

trying to work out if i should get another make of NAS drive as i dont know netgears devices can be trusted

 


This one is confusing, as there is no indication of disk failure.  Though it might also be worth looking at smart.log and maybe looking for disk i/o errors in kernel.log.

 

FWIW, Netgear has apparently made some btrfs stability improvments for the arm-based NAS in the most recent beta.  But I don't know what those are (or whether those improvements would have made any difference).  

Message 10 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead

what i find werid is  in the smart history log, it only goes to 2019-03-08 and it lists a hardrive that is not even in the unit!

time                 model                 serial                realloc_sect  realloc_evnt  spin_retry_cnt  ioedc       cmd_timeouts  pending_sect  uncorrectable_err  ata_errors
-------------------  --------------------  --------------------  ------------  ------------  --------------  ----------  ------------  ------------  -----------------  ----------
2019-03-08 19:06:32  ST4000VN000-1H4168    Z303WEME              2504          2504          0               0           15            2592          2592               2        
2019-03-08 19:09:13  ST4000VN000-1H4168    Z303WEME              2576          2576          0               0           15            2624          2624               2        
2019-03-08 19:13:07  ST4000VN000-1H4168    Z303WEME              2704          2704          0               0           15            2688          2688               2        
2019-03-08 19:16:47  ST4000VN000-1H4168    Z303WEME              2944          2944          0               0           16            2776          2776               2        
2019-03-08 19:19:40  ST4000VN000-1H4168    Z303WEME              3064          3064          0               0           16            2920          2920               2        
2019-03-08 19:22:27  ST4000VN000-1H4168    Z303WEME              3176          3176          0               0           16            3072          3072               2        
2019-03-08 19:27:23  ST4000VN000-1H4168    Z303WEME              3376          3376          0               0           16            3336          3336               2        
2019-03-08 19:31:05  ST4000VN000-1H4168    Z303WEME              3576          3576          0               0           16            3416          3416               2        
2019-03-08 19:36:28  ST4000VN000-1H4168    Z303WEME              3664          3664          0               0           16            3744          3744               2        
2019-03-08 19:39:48  ST4000VN000-1H4168    Z303WEME              3736          3736          0               0           16            3808          3808               2        
2019-03-08 19:42:41  ST4000VN000-1H4168    Z303WEME              3872          3872          0               0           16            3888          3888               2        
2019-03-08 19:47:04  ST4000VN000-1H4168    Z303WEME              4024          4024          0               0           16            4128          4128               2        

 

three of the drives are - ST4000VN000-1H4168 but not that serial number, i also have not changed any disk in this unit so none of it make any  sense

 

 

Message 11 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead


@tasone wrote:

what i find werid is  in the smart history log, it only goes to 2019-03-08 and it lists a hardrive that is not even in the unit!

time                 model                 serial                realloc_sect  realloc_evnt  spin_retry_cnt  ioedc       cmd_timeouts  pending_sect  uncorrectable_err  ata_errors
-------------------  --------------------  --------------------  ------------  ------------  --------------  ----------  ------------  ------------  -----------------  ----------
    
2019-03-08 19:47:04  ST4000VN000-1H4168    Z303WEME              4024          4024          0               0           16            4128          4128               2        

 

three of the drives are - ST4000VN000-1H4168 but not that serial number, i also have not changed any disk in this unit so none of it make any  sense

 

 


The serial number is a mystery.  That particular drive certainly is (was?) in bad shape though.

 

Are you seeing that serial number in disk_info.log?  If you are, that should show you what bay the NAS thinks that disk is in.

Message 12 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead


@StephenB wrote:

@tasone wrote:

what i find werid is  in the smart history log, it only goes to 2019-03-08 and it lists a hardrive that is not even in the unit!

time                 model                 serial                realloc_sect  realloc_evnt  spin_retry_cnt  ioedc       cmd_timeouts  pending_sect  uncorrectable_err  ata_errors
-------------------  --------------------  --------------------  ------------  ------------  --------------  ----------  ------------  ------------  -----------------  ----------
    
2019-03-08 19:47:04  ST4000VN000-1H4168    Z303WEME              4024          4024          0               0           16            4128          4128               2        

 

three of the drives are - ST4000VN000-1H4168 but not that serial number, i also have not changed any disk in this unit so none of it make any  sense

 

 


The serial number is a mystery.  That particular drive certainly is (was?) in bad shape though.

 

Are you seeing that serial number in disk_info.log?  If you are, that should show you what bay the NAS thinks that disk is in.

 

 

 

disk info log

 

Device:             sdd
Controller:         0
Channel:            0
Model:              ST4000VN000-1H4168
Serial:             Z3048JLV
Firmware:           SC46
Class:              SATA
RPM:                5900
Sectors:            7814037168
Pool:               Volumeone
PoolType:           RAID 5
PoolState:          5
PoolHostId:         2fe64c78
Health data
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  End-to-End Errors:              0
  Command Timeouts:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    48
  Start/Stop Count:               85
  Power-On Hours:                 34538
  Power Cycle Count:              86
  Load Cycle Count:               85
Device:             sdc
Controller:         0
Channel:            1
Model:              WDC WD40EFRX-68WT0N0
Serial:             WD-WCC4E1LTP9XX
Firmware:           82.00A82
Class:              SATA
RPM:                5400
Sectors:            7814037168
Pool:               Volumeone
PoolType:           RAID 5
PoolState:          5
PoolHostId:         2fe64c78
Health data
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    49
  Start/Stop Count:               13943
  Power-On Hours:                 22821
  Power Cycle Count:              26
  Load Cycle Count:               13941
Device:             sdb
Controller:         0
Channel:            2
Model:              ST4000VN000-1H4168
Serial:             Z303WFDR
Firmware:           SC46
Class:              SATA
RPM:                5900
Sectors:            7814037168
Pool:               Volumeone
PoolType:           RAID 5
PoolState:          5
PoolHostId:         2fe64c78
Health data
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  End-to-End Errors:              0
  Command Timeouts:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    45
  Start/Stop Count:               69
  Power-On Hours:                 33186
  Power Cycle Count:              70
  Load Cycle Count:               70
Device:             sda
Controller:         0
Channel:            3
Model:              ST4000VN000-1H4168
Serial:             Z303ZVG3
Firmware:           SC46
Class:              SATA
RPM:                5900
Sectors:            7814037168
Pool:               Volumeone
PoolType:           RAID 5
PoolState:          5
PoolHostId:         2fe64c78
Health data
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  End-to-End Errors:              0
  Command Timeouts:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    42
  Start/Stop Count:               69
  Power-On Hours:                 33189
  Power Cycle Count:              70
  Load Cycle Count:               70
 
 
all disk look good to me, i have no idea to what is happening here

 

Message 13 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead


@tasone wrote:
all disk look good to me, i have no idea to what is happening here

 


The stats are fine.  You could enable ssh, and look for errors saved for each disk.  The commands for that are

# smartctl -x /dev/sda
# smartctl -x /dev/sdb
# smartctl -x /dev/sdc
# smartctl -x /dev/sdd

This reports a lot of stuff (including the stats you already have).  The interesting section is a list of cached disk i/o commands that had errors.

Message 14 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead


@StephenB wrote:

@tasone wrote:
all disk look good to me, i have no idea to what is happening here

 


The stats are fine.  You could enable ssh, and look for errors saved for each disk.  The commands for that are

# smartctl -x /dev/sda
# smartctl -x /dev/sdb
# smartctl -x /dev/sdc
# smartctl -x /dev/sdd

This reports a lot of stuff (including the stats you already have).  The interesting section is a list of cached disk i/o commands that had errors.


Hi

 

i am just going to drop the netgear  brand, as i got zero warning or anything it just want pop a  raid 5 gone.

 

I will buy another type of NAS drive i have lost all trust with netgear now

 

Thanks tho for your time and help

 

Andrew

Message 15 of 19
Sandshark
Sensei

Re: ReadyNas 104 Volume inactive or dead

I too am confused, as every other indication is that the volume should be intact.  You didn't unintentionally do an "Export", did you?

 

Does btrfs device scan show anything useful?  Did you try re-booting again?  Maybe something just hiccupped on this one boot.

Message 16 of 19
Danthelf
Guide

Re: ReadyNas 104 Volume inactive or dead

Let's not forget about this:

[...]
Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096 Sep 23 18:25:09 TD-Archive kernel: BTRFS critical (device md127): unable to find logical 16188835102720 len 4096 Sep 23 18:25:09 TD-Archive kernel: BTRFS warning (device md127): failed to read tree root Sep 23 18:25:09 TD-Archive kernel: BTRFS error (device md127): open_ctree failed

mdadm array is intact yes, but there are filesystem issues preventing it from mounting.

Message 17 of 19
StephenB
Guru

Re: ReadyNas 104 Volume inactive or dead


@Danthelf wrote:

... mdadm array is intact yes, but there are filesystem issues preventing it from mounting.


I agree.

Message 18 of 19
tasone
Aspirant

Re: ReadyNas 104 Volume inactive or dead

well i have wiped the disks and started again with a synology 4 bay drive, and i am using the same disks and it is working fine!

 

thank everyone that tried to help, Smiley Happy

Message 19 of 19
Top Contributors
Discussion stats
  • 18 replies
  • 1856 views
  • 0 kudos
  • 4 in conversation
Announcements