× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: NAS 104 Locked Up

broad01
Tutor

NAS 104 Locked Up

NAS has locked up.  Can not access.  Can not even ping.

 

See attached photo of the display.

 

Will not soft shutdown using power button.

 

Any ideas?

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 1 of 13
Marc_V
NETGEAR Employee Retired

Re: NAS 104 Locked Up

@broad01

 

Can you still access the Boot menu? Were you able to check the status of the NAS on RAIDar? 

 

You may want to try booting it on Ready only mode. Kindly check if you can download the logs as well.

 

 

Many thanks!

 

 

Regards

Message 2 of 13
broad01
Tutor

Re: NAS 104 Locked Up

Hi Mark

 

As I said in my post

 

"Can not access.  Can not even ping."

 

Not even with RAIDar.  RAIDar says no devices found. 

 

What do you make of the message on the display?   What does this tell you what problem is?

 

I think the only thing I can do is unplug it.   How much risk is there of data loss if I do this?   Surly the display message will tell you the issue and if a hard reboot will cause data loss?

 

Thanks

 

Adam

Message 3 of 13
Sandshark
Sensei

Re: NAS 104 Locked Up

A hard reboot in this case should not cause a volume issue.  Buit, you may already have a volume issue that will only become apparent after a re-boot.  Re-booting in read-only mode may be prudent.

 

Frankly, though, what choice do you have?  With no GUI or SSH access, you have no way to do anything else.

Message 4 of 13
broad01
Tutor

Re: NAS 104 Locked Up

So i power cycled the NAS.   It came back and all looked OK.   A few days later a new message appeared, 

 

"btrfs_search_forward+2ac"

 

Again NAS totally locked up.  power cycled again.   Now NAS shows a popup which says  "No volume exists"   with a warning message "Remove inactive volumes to use the disk.   Disk #1,2,3,4."!!!!!!!!!!!!

 

Lookes like I have lost all my data again....   Anyway to recover?

 

logs attached.

 

This is the third time with a Netgear NAS. 

Message 5 of 13
StephenB
Guru

Re: NAS 104 Locked Up


@broad01 wrote:

 

This is the third time with a Netgear NAS. 


It looks like you are keeping the data volume too full (90-95%).

 


@broad01 wrote:

 

Lookes like I have lost all my data again....   Anyway to recover?

 


Paid support (my.netgear.com) might be able to remount it.

Message 6 of 13
broad01
Tutor

Re: NAS 104 Locked Up

Hi

 

I have tried re-booting into read only mode.   Still no volume.

 

I want to SSH into the unit to check if the data is still there and try a re-mount.   I get a connection refused.   i went to settings in admin and see under services that SSH is not selcted.   I am unable to enable SSH, when I try it says "cannot start service without a volume"!!   Is there any way I get enable SSH or get in bypassing the admin setup?   How about the tech mode in the boot menu?

 

Thanks

 

Adam

Message 7 of 13
StephenB
Guru

Re: NAS 104 Locked Up

You could telnet into the NAS in tech support mode, and then use the linux CLI.

 

Log in as root with password infr8ntdebug.

 

Start RAID and chroot with 

# rnutil chroot

The normal steps to mount the data volume will likely fail, but are

# btrfs device scan
# btrfs fi show
# mount /dev/md127 /data

You could potentially try running

# btrfs check /dev/md127

before you try to do the mount.  That won't repair anything, it will just check the volume.

Message 8 of 13
broad01
Tutor

Re: NAS 104 Locked Up

Here are the results.   Any further ideas...

3EP134E501109 login: root

Password:

# rnutil chroot

mdadm: /dev/md/0 has been started with 4 drives.

mdadm: /dev/md/1 has been started with 4 drives.

mdadm: /dev/md/data-0 has been started with 4 drives.

mount: mounting LABEL=0e346740:data on /data failed: No such file or directory

root@3EP134E501109:/#

root@3EP134E501109:/# btrfs check /dev/md127

checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8

checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8

checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4

checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4

bytenr mismatch, want=27623876067328, have=6109277914453778088

Couldn't read tree root

Couldn't open file system

root@3EP134E501109:/# btrfs device scan

Scanning for Btrfs filesystems

root@3EP134E501109:/# btrfs fi show

Label: '0e346740:data'  uuid: a5008274-7a77-450f-b098-dff8dd3dc285

        Total devices 1 FS bytes used 20.10TiB

        devid    1 size 21.82TiB used 21.77TiB path /dev/md127

 

root@3EP134E501109:/# mount /dev/md127 /data

mount: wrong fs type, bad option, bad superblock on /dev/md127,

       missing codepage or helper program, or other error

 

       In some cases useful info is found in syslog - try

       dmesg | tail or so.

root@3EP134E501109:/# dmesg | tail

[  153.836981]  disk 2, o:1, dev:sdc3

[  153.836988]  disk 3, o:1, dev:sdd3

[  153.837203] md127: detected capacity change from 0 to 23989784936448

[  154.337435] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)

[  229.016409] BTRFS: device label 0e346740:data devid 1 transid 1575622 /dev/md127

[  270.024702] BTRFS: has skinny extents

[  270.241458] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328

[  270.241879] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328

[  270.241917] BTRFS: failed to read tree root on md127

[  270.300229] BTRFS: open_ctree failed

root@3EP134E501109:/#

 

 

Message 9 of 13
broad01
Tutor

Re: NAS 104 Locked Up

I am trying to post the results, but my posts keep disappearing???

Does the Community System automatically delete posts with telnet Commands?

Tried to post my results 3 times and they disappear........

 

OK managed to add my results as a ODF.  Any further suggestions? 

 

 StephenB  How do you create the gray boxes you post commands into? 
 
 

 

 

Message 10 of 13
broad01
Tutor

Re: NAS 104 Locked Up

I will try again.

Here are the results, any further suggestions?

 

Spoiler

# rnutil chroot

mdadm: /dev/md/0 has been started with 4 drives.

mdadm: /dev/md/1 has been started with 4 drives.

mdadm: /dev/md/data-0 has been started with 4 drives.

mount: mounting LABEL=0e346740:data on /data failed: No such file or directory

Spoiler

root@3EP134E501109:/# btrfs check /dev/md127

checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8

checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8

checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4

checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4

bytenr mismatch, want=27623876067328, have=6109277914453778088

Couldn't read tree root

Couldn't open file system

Spoiler

root@3EP134E501109:/# btrfs device scan

Scanning for Btrfs filesystems

root@3EP134E501109:/# btrfs fi show

Label: '0e346740:data'  uuid: a5008274-7a77-450f-b098-dff8dd3dc285

        Total devices 1 FS bytes used 20.10TiB

        devid    1 size 21.82TiB used 21.77TiB path /dev/md127

Spoiler

root@3EP134E501109:/# mount /dev/md127 /data

mount: wrong fs type, bad option, bad superblock on /dev/md127,

       missing codepage or helper program, or other error

 

       In some cases useful info is found in syslog - try

       dmesg | tail or so.

Spoiler

root@3EP134E501109:/# dmesg | tail

[  153.836981]  disk 2, o:1, dev:sdc3

[  153.836988]  disk 3, o:1, dev:sdd3

[  153.837203] md127: detected capacity change from 0 to 23989784936448

[  154.337435] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)

[  229.016409] BTRFS: device label 0e346740:data devid 1 transid 1575622 /dev/md127

[  270.024702] BTRFS: has skinny extents

[  270.241458] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328

[  270.241879] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328

[  270.241917] BTRFS: failed to read tree root on md127

[  270.300229] BTRFS: open_ctree failed

Adam

Message 11 of 13
StephenB
Guru

Re: NAS 104 Locked Up


@broad01 wrote:

I am trying to post the results, but my posts keep disappearing???



There is an automated spam filter that was kicking in.  I released the most recent one.

 


@broad01 wrote:
 StephenB  How do you create the gray boxes you post commands into? 
 

 

 


Click on the </> icon in the toolbar.

 

Message 12 of 13
StephenB
Guru

Re: NAS 104 Locked Up


@broad01 wrote:

I will try again.

Here are the results, any further suggestions?

 

Spoiler

# rnutil chroot

mdadm: /dev/md/0 has been started with 4 drives.

mdadm: /dev/md/1 has been started with 4 drives.

mdadm: /dev/md/data-0 has been started with 4 drives.

mount: mounting LABEL=0e346740:data on /data failed: No such file or directory

Spoiler

root@3EP134E501109:/# btrfs check /dev/md127

checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8

checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8

checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4

checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4

bytenr mismatch, want=27623876067328, have=6109277914453778088

Couldn't read tree root

Couldn't open file system

Spoiler

root@3EP134E501109:/# btrfs device scan

Scanning for Btrfs filesystems

root@3EP134E501109:/# btrfs fi show

Label: '0e346740:data'  uuid: a5008274-7a77-450f-b098-dff8dd3dc285

        Total devices 1 FS bytes used 20.10TiB

        devid    1 size 21.82TiB used 21.77TiB path /dev/md127

Spoiler

root@3EP134E501109:/# mount /dev/md127 /data

mount: wrong fs type, bad option, bad superblock on /dev/md127,

       missing codepage or helper program, or other error

 

       In some cases useful info is found in syslog - try

       dmesg | tail or so.

Spoiler

root@3EP134E501109:/# dmesg | tail

[  153.836981]  disk 2, o:1, dev:sdc3

[  153.836988]  disk 3, o:1, dev:sdd3

[  153.837203] md127: detected capacity change from 0 to 23989784936448

[  154.337435] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)

[  229.016409] BTRFS: device label 0e346740:data devid 1 transid 1575622 /dev/md127

[  270.024702] BTRFS: has skinny extents

[  270.241458] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328

[  270.241879] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328

[  270.241917] BTRFS: failed to read tree root on md127

[  270.300229] BTRFS: open_ctree failed

Adam


The data volume is corrupted.  RAID recovery software might work.

Message 13 of 13
Top Contributors
Discussion stats
  • 12 replies
  • 1978 views
  • 0 kudos
  • 4 in conversation
Announcements