NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jonalex
Dec 19, 2019Aspirant
My ReadyNas 102 won't complete boot. Blinking power button
MacOS Sierra NAS RN102 Firmeware 6.9.1 Today, while in the midle of transfer from my NAS to a local drive, my NAS was not seen by my network and the transfer was cancelled. I tried to reconnect...
jonalex
Dec 20, 2019Aspirant
Update: I read in this thread by StephenB that I could try to boot with one drive, which I did and managed to get a bit further.
I have now been able to download a log zip and got a different response on the RAIDar which I've attached.
Anyone have an idea what to look for in the logs?
- jonalexDec 20, 2019Aspirant
So this is strange.
I'm able to get to the admin page and view information on the drives, and even see the Volumnes and Shares in my NAS if I boot with one drive. Either one.
I'm assuming that I can't access any of the shares since the information is distribuited among two drives.
Anyone?- StephenBDec 26, 2019Guru - Experienced User
jonalex wrote:
I'm assuming that I can't access any of the shares since the information is distribuited among two drives.If you are using XRAID, you can access the shares from either drive.
I am thinking that one of the drives might have failed. So look for disk errors and btrfs errors in system.log and kernel.log.
Make a backup, since the data is at risk.
- jonalexDec 26, 2019Aspirant
Thanks StephenB !
I had 2 4tb disks configured as one extended drive of 8tb with a bunch of shares.
I'm hoping the unit is the one failing, rather than disks (which is still a pretty big issue).
I found the last records of the two logs you mentioned.
System.log:Dec 02 15:42:08 ndm_raid apache2[2260]: [error] [client 192.168.100.17] Connect rddclient failed, referer: https://169.254.116.184/admin/ Dec 02 15:44:07 ndm_raid apache_access[2195]: Suppressed 38 duplicate messages Dec 02 15:44:08 ndm_raid apache_access[2195]: 192.168.100.17 "-" 408 Dec 02 15:46:13 ndm_raid connmand[2035]: eth0 {RX} 5994 packets 846843 bytes Dec 02 15:46:13 ndm_raid connmand[2035]: eth0 {TX} 3314 packets 3045821 bytes Dec 02 15:46:14 ndm_raid connmand[2035]: eth0 {update} flags 36867 <UP> Dec 02 15:46:34 ndm_raid apache2[2200]: [error] [client 192.168.100.17] Connect rddclient failed, referer: https://169.254.116.184/admin/ Dec 02 15:46:35 ndm_raid connmand[2035]: eth0 {newlink} index 2 address 28:C6:8E:35:9A:16 mtu 1500 Dec 02 15:46:35 ndm_raid connmand[2035]: eth0 {newlink} index 2 operstate 2 <DOWN> Dec 02 15:46:35 ndm_raid apache_access[2195]: Suppressed 4 duplicate messages Dec 02 15:46:35 ndm_raid apache_access[2195]: 192.168.100.17 "POST /dbbroker HTTP/1.1" 200 Dec 02 15:46:37 ndm_raid avahi-daemon[2009]: Withdrawing address record for 169.254.116.184 on eth0.
Kernel.log:Dec 02 11:59:23 ndm_raid kernel: [ 2468] 0 2468 11867 327 25 0 486 0 smbd Dec 02 11:59:24 ndm_raid kernel: Out of memory: Kill process 2276 (apt-get) score 24 or sacrifice child Dec 02 11:59:24 ndm_raid kernel: Killed process 2276 (apt-get) total-vm:35900kB, anon-rss:1612kB, file-rss:980kB
Is there any other way of accessing the contents of the drives? Most of the data was fortunately backed up on a sepearate archive drive... I'm just missing a couple of folders that I'm desperately trying to gain access to.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!