Halo guys. Have a big problem. My NAS is Readynas Pro 6, running 6.10.0-T185 All of the sudden I lost possibility to open shares, admin page and even transmission page. Ping is working fine. IP is hardcoded in NAS and in router. I was trying OS reinstall twice, but no joy. RAIDar can find the device, showing correct MAC and IP addresses, serial number etc. But it also says Volume data, raid5, inactive... Diagnostic option shows something like this: System Volume data is inactive Logs 2018-12-16 08:48:42: kernel BUG at fs/btrfs/print-tree.c:124! 2018-12-16 02:22:58: Fixing recursive fault but reboot is needed! 2018-12-16 02:22:57: general protection fault: 0000 [#16] SMP 2018-12-16 02:22:57: RIP [] filp_close+0x9/0x6f 2018-12-16 02:21:58: general protection fault: 0000 [#15] SMP 2018-12-16 02:21:58: RIP [] __fget+0x39/0x65 2018-12-16 02:18:35: general protection fault: 0000 [#14] SMP I also downloaded zip file with all logs, but cant find anything usefull there. Reboot, performed from RAIDar interface works, but changes nothing.... still no access to my stuff nor to admin page. What can I do to make it working again ? It was working fine, then I turned it off for a day or two... After power up, here we go - no access... Would appreciate any advice :) Thank you Stan

May PM OOM-9 and see if Netgear development wants to take a look. Do you have a backup of the data?

Hi, Thanks forreply :) Well....this was supossed to be a backup... I do not mind movies, music and stuff, but I just was replacing my workstation which I use to do my job stuff, so I have moved about 2 Tb of important data to the NAS, checked for consistency and destroyed the source...Well... it turns out now I have a problem...:( Since it is responding to ping, and I can ssh as root to it, I was thinking... Maybe it is possible to reasamble raid using LVM or mdadm ? It is inactive, not destroyed or degraded after all... Problem is I do not know Netgear specific changes done to regular Linux...

Stan78 wrote: Well....this was supossed to be a backup... A "backup" by definition is not primary storage. So if it is a backup, then all the data you care about is also saved elsewhere. RAID alone is not enough to keep your data safe, and in your case Netgear support is not available to you since you are running OS-6 on a legacy NAS. On top of that you are running beta firmware. However, that could work in your favor, as Netgear might want to analyze what happened. Stan78 wrote: Since it is responding to ping, and I can ssh as root to it, I was thinking... Maybe it is possible to reasamble raid using LVM or mdadm ? It is inactive, not destroyed or degraded after all... The SMP error generally is a memory-related issue (for instance de-referencing a null pointer). So you might want to check the memory seating and run the boot-menu memory diagnostic. Another test would be to remove all the drives (labeling by slot), and doing a factory install to a test disk (that you don't mind reformatting). That would give you reasonable confirmation that the chassis is working normally. OS-6 does use mdadm, but this is a btrfs error. That sugggests that the RAID array is assembled correctly, but there is file system corruption. Note the OS partition itself is also formatted as btrfs. You could try booting the system into tech support mode. From there, you can enter the commands below to mount the data volume as read-only. Note this assumes a healthy array, so you likely will get an error somewhere along the way. # start_raids # rnutil chroot # btrfs device scan# btrfs fi show# mount -o -ro /dev/md127 /data

Wow :) Many thanks for this... I'd never think about memory modules.... Well... so far I did the first part... ran memory test... 3 passes total (1 sucessful, 2 with error) - went strangly quick (3 passes took below 20 minutes together, 2x2gb PC2 modules, 4Gb in total)... So I replaced memory modules (I put 2x1Gb PC2) and ran test... this time, 3 pasess took nearly 60 minutes (while it was just half of original capacity) and no errors... So I left the new memory in and ran the device. Still no joy - RAID inactive... but this time... RAIDar diagnostics says : System Volume data is inactive Logs No errors found. So... looks like it is a bit better... More of that... admin page still not working (not even Neatgear logo or so - just regular page not found), but I can now see the shares in windows...I can't open them tough - getting windows error 0x80070035 - network path not found... I will be proceeding further :)

Well... I wrote post yesterday but now it is gone... :( Shame as I included a lotof console output for refference... It looks like partition md0 btrfs file system is lying to linux df about free space... All I'm trying to do (apt-get install, or even delete some files) ends up with 'no space left on device' msg... I can't do the balancing...same msg appears df -h tells me I have 4gb partition with 44% usage, but btrfs fi show tells me that 3,98gb of 4gb is used... demsg | tail says also that no space left on device and because of that, some jurnals can't be turned (whatever that means:) For partition md127 - mounted to /data, which is probably my raid, the df and btfrs are preaty similar - meaning - no problem on that partition So... how to check what is eating my disk space and what do do in order to prevent it / free up some ? I do not know if this is a result or a cause of my problem, but obvieusly till this is mittigated, the problem will not be solved..

Stan78

Aspirant

Dec 16, 2018

No access to shares nor to admin page

Halo guys. Have a big problem.

My NAS is Readynas Pro 6, running 6.10.0-T185

All of the sudden I lost possibility to open shares, admin page and even transmission page.

Ping is working fine. IP is hardcoded in NAS and in router. I was trying OS reinstall twice, but no joy.

RAIDar can find the device, showing correct MAC and IP addresses, serial number etc.

But it also says Volume data, raid5, inactive...

Diagnostic option shows something like this:

System

Volume data is inactive

Logs

2018-12-16 08:48:42: kernel BUG at fs/btrfs/print-tree.c:124!
2018-12-16 02:22:58: Fixing recursive fault but reboot is needed!
2018-12-16 02:22:57: general protection fault: 0000 [#16] SMP
2018-12-16 02:22:57: RIP [] filp_close+0x9/0x6f
2018-12-16 02:21:58: general protection fault: 0000 [#15] SMP
2018-12-16 02:21:58: RIP [] __fget+0x39/0x65
2018-12-16 02:18:35: general protection fault: 0000 [#14] SMP

I also downloaded zip file with all logs, but cant find anything usefull there.

Reboot, performed from RAIDar interface works, but changes nothing.... still no access to my stuff nor to admin page.

What can I do to make it working again ?

It was working fine, then I turned it off for a day or two... After power up, here we go - no access...

Would appreciate any advice :)

Thank you

Stan

Feature Request & Feedback

Tips from other users

28 Replies

StephenB
Guru
Dec 17, 2018
May PM OOM-9 and see if Netgear development wants to take a look.

Do you have a backup of the data?
- Stan78
  Aspirant
  Dec 17, 2018
  Hi, Thanks forreply :)
  
  Well....this was supossed to be a backup...
  
  I do not mind movies, music and stuff, but I just was replacing my workstation which I use to do my job stuff, so I have moved about 2 Tb of important data to the NAS, checked for consistency and destroyed the source...Well... it turns out now I have a problem...:(
  
  Since it is responding to ping, and I can ssh as root to it, I was thinking... Maybe it is possible to reasamble raid using LVM or mdadm ? It is inactive, not destroyed or degraded after all... Problem is I do not know Netgear specific changes done to regular Linux...
  - StephenB
    Guru
    Dec 17, 2018
    Stan78 wrote:
    
    Well....this was supossed to be a backup...
    
    A "backup" by definition is not primary storage. So if it is a backup, then all the data you care about is also saved elsewhere.
    
    RAID alone is not enough to keep your data safe, and in your case Netgear support is not available to you since you are running OS-6 on a legacy NAS.
    
    On top of that you are running beta firmware. However, that could work in your favor, as Netgear might want to analyze what happened.
    
    Stan78 wrote:
    
    Since it is responding to ping, and I can ssh as root to it, I was thinking... Maybe it is possible to reasamble raid using LVM or mdadm ? It is inactive, not destroyed or degraded after all...
    
    The SMP error generally is a memory-related issue (for instance de-referencing a null pointer). So you might want to check the memory seating and run the boot-menu memory diagnostic. Another test would be to remove all the drives (labeling by slot), and doing a factory install to a test disk (that you don't mind reformatting). That would give you reasonable confirmation that the chassis is working normally.
    
    OS-6 does use mdadm, but this is a btrfs error. That sugggests that the RAID array is assembled correctly, but there is file system corruption. Note the OS partition itself is also formatted as btrfs. You could try booting the system into tech support mode. From there, you can enter the commands below to mount the data volume as read-only. Note this assumes a healthy array, so you likely will get an error somewhere along the way.
    
    # start_raids
    
    # rnutil chroot
    
    # btrfs device scan
    # btrfs fi show
    # mount -o -ro /dev/md127 /data

Forum Discussion

No access to shares nor to admin page

System

Logs

28 Replies

Related Content

Shares lost from admin page

unable to access router admin page due to https

USB Share not accessible when WAN is down

Cannot access Orbi Admin login screen

Router working, can't access admin page

NETGEAR Academy

ProSupport for Business