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

Re: btfrs_root_node 38

sebastianci
Aspirant

btfrs_root_node 38

Today I fiorst staterd to get info that my nas is write protectected when tried to write , the I have powered it down from web interface.

After that NAS does not boot , instead on display I am getting  btfrs_root_node 38 message.

Please help

Sebastian

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 1 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Sorry for typo it is btrfs_root _node 38 message

 

Message 2 of 21
JohnCM_S
NETGEAR Employee Retired

Re: btfrs_root_node 38

Hi sebastianci,

 

Do you have a backup of your data? There could be an issue with the file system of your NAS based on the error message.

 

Is the NAS still detected on RAIDar? If yes, you can try downloading the system logs and check what caused it.

 

Regards,

Message 3 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Hi,

Thanks for answer, as with backup it is not teh freshest so I'd loos 2 weeks of my data what is a pain, so I'd like to try some recovering.

RAIDar does not see the NAS though I can ping NAS.

Unfortunatelly ssh is disabled so I do not know how to access NAS without RAIDar or web gui.

Sebastian

 

Message 4 of 21
JohnCM_S
NETGEAR Employee Retired

Re: btfrs_root_node 38

Hi sebastianci,

 

It will be best for you to contact NETGEAR support. They should be able to remotely access your NAS and check if the data can be recovered (https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service). 

 

Regards,

Message 5 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Yes, but I am long after the warranty period, do you know if they provide out of warranty service?

Message 6 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Also my NAS RN104 is "end of life", do you know how to contact them to check if they will support it?

Message 7 of 21
Sandshark
Sensei

Re: btfrs_root_node 38

As long as you are the original purchaser and have registered the NAS with Netgear, they will support it.  Not for free, of course.  Recovery isn't covered by warranty, anyway.

Message 8 of 21
JohnCM_S
NETGEAR Employee Retired

Re: btfrs_root_node 38

Hi sebastianci,

 

The pay-per-incident support and data recovery contract purchase should still be available for your device. You can purchase the support contract by logging in to my.netgear.com. You can also open a support ticket there.

 

Regards,

Message 9 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Hi I feel a bit lost.

I have paid £80 for 3 year support ( per case support was not available for my NAS) Spent 45 minutes on call and been told that I need to buy data recovery from Netgear for £160/ hour. ( My support contract can be credited towards recoery).

So no guarantee that my data recovery will not extend for another few hours.

I can easily telnet on the NAS in the Tech support mode, I am seriously considering trying it by myself though it might cost some time.

I tried to build the RAID by running start_raid.sh, but it looks like this script is not found .

Any help?

 

Message 10 of 21
StephenB
Guru

Re: btfrs_root_node 38


@sebastianci wrote:

 

I can easily telnet on the NAS in the Tech support mode, I am seriously considering trying it by myself though it might cost some time.

 


If you don't know what you are doing, it will cost you your data.

 

Do you have any experience with btrfs data recovery?

Message 11 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

I do not have experience in btrfs recovery , I am aware it might cost me data though willing to try , if worse come to worse I will have to revert to backup and loose 2 weeks ( already started recreating lost data from othe rsources).  Can you help with further steps for btrfs recovery?

Message 12 of 21
StephenB
Guru

Re: btfrs_root_node 38


@sebastianci wrote:

Can you help with further steps for btrfs recovery?


I haven't needed to do it myself, so it's not something I can give much guidance on.

 

I can say that you should start in tech support mode with 

# rnutil chroot

That will both start RAID and chroot.

 

If for some reason, you only want to start RAID, then with OS-6 you'd enter

# start_raids

(not start_raid)

 

If you have ever expanded your RAID array vertically, you probably will need to enter

# btrfs device scan

This shouldn't hurt if you don't need it.

 

If you want to try to mount the volume, the normal command is

# mount /dev/md127 /data

But most BTRFS repair tools can't be run on a mounted volume.

 

You should read up on btrfs check --repair and maybe also btrfs restore

 

 

 

 

 

 

Message 13 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Great thanks

It is good starting point i will do some reading, just to make my work easier: how to gracefully shutdown NAS in tech support mode, shall I run something to stop RAID, I guess I just exit from chroot. How to shutdown NAS then, shutdown command does not work?

 

Message 14 of 21
StephenB
Guru

Re: btfrs_root_node 38


@sebastianci wrote:

How to shutdown NAS then, shutdown command does not work?

 


# shutdown now

should work.  Are you sayng it doesn't?

Message 15 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Yes

# shutdown now
-sh: shutdown: not found

 

 

Message 16 of 21
Sandshark
Sensei

Re: btfrs_root_node 38

Try rn_shutdown.  That's an r & n (for ReadyNAS), not an m before the underscore.   That's the command for standard SSH, I have never tried it in tech support mode.  It's located in /usr/bin.

Message 17 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Hi sorry for delay. To minimise interactions with my NAS , I was waiting for new HDD.

Now I started and not sure why my nas is md126, see attached screenshot.

Unfortunatelly btrfs commands do not work on md127, md126 checksum incorrect.

Can you say if md126 is an sensible raid alias or i need to rearange something?

Sebastian

 

Message 18 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

also,  rn_shutdown is also not present ?

Message 19 of 21
StephenB
Guru

Re: btfrs_root_node 38


@sebastianci wrote:

Now I started and not sure why my nas is md126, see attached screenshot.

Unfortunatelly btrfs commands do not work on md127, md126 checksum incorrect.

Can you say if md126 is an sensible raid alias or i need to rearange something?

 


Your NAS was vertically expanded (disks 1 and 3 appear to be larger), so you have two RAID groups.  Normally md127 would be the original group.  But in your case that appears to be md126.

 

Have you given up on Netgear tech support?  They should have gotten back to you by now.

 


@sebastianci wrote:

rn_shutdown is also not present 

 


You appear to be missing several commands that you ought to have.  shutdown should be in /sbin; rn_shutdown should be in /usr/bin

 

Did you start with

# rnutil chroot

Or did you skip that?

Message 20 of 21
sebastianci
Aspirant

Re: btfrs_root_node 38

Thanks for answer,

On the subject of btrfs, thanks: md126 it is.

Mounting as ro does not work : btrfs_root_node+38

Running check --repair:

root@3EPB43EE0025E:/# btrfs check --repair /dev/md126
enabling repair mode
checksum verify failed on 9150299111424 found 10BC57A5 wanted 18B79090
checksum verify failed on 9150299111424 found 10BC57A5 wanted 18B79090
parent transid verify failed on 9150299111424 wanted 88714 found 86890
checksum verify failed on 9150299111424 found 10BC57A5 wanted 18B79090
Csum didn't match
ERROR: cannot open file system

I know you not an expert on btrfs, though any suggestion might put me in right direction.

 

On netgear tech support

They contacted me origianly, spent 45 minutes on the NAS and decided I need to pay ~£160/hour for data recovery - of course no guarantee.

I am afraid they either want more hours, or recover partial data which does not contain what I have really lost. I accept I will loose 2 weeks of family pictures, so be it.

 

On shutdown

In chroot I can see both files

/sbin/shutdown

/usr/bin/rn_shutdown

issuing rn_shutdown: causes some noise from disks and nothing happends,

issuing shutdown: "Running in chroot, ignoring request"

After typing "exit",  rn_shutdown, shutdown are no longer present.

If I run new telent also rn_shutdown, shutdown are not present unless I enter chroot

Thanks

 

Message 21 of 21
Top Contributors
Discussion stats
  • 20 replies
  • 2292 views
  • 0 kudos
  • 4 in conversation
Announcements