No Volume Exists

[Icauto]

This morning I realzied my NAS was full. I could not get to it. So I powered it down and powered it back up. When I log into it I get a message:

No volume Exists.NetGear recommneds you create a volume befoer configuring other settings.

Whats up? All the drivesd show healthy?

I have posted the Log file but this forum wont let me uploaded it as it is a ZIP. The NAS created the file when I clicked on download Logs.

if the NAS gets full does that take out all the files?

[Icauto]

BTW, it is setup for RAID 5, X-RAID.

[StephenB]

Best to contact paid support for this issue (via my.netgear.com).  

One potential cause is that the RAID array is out of sync.  Did you power down the NAS cleanly, or pull the plug?

[Icauto]

Powered donw cleanly.

[Icauto]

Is paid for support available? I went to the lnik you posted and see my device is registered. But it shows not support. How do I pay for support? Do I have to take out a service contract for a year? I see that option available? Is ther pay for support per incident available?

[StephenB]

---

@Icauto wrote:

But it shows not support. How do I pay for support? Do I have to take out a service contract for a year? I see that option available? Is ther pay for support per incident available?

---

You can create a support case for your registered devices.

As far as what support contract you'd need (or whether per-incident support is available for your problem):  the best resource for that are the mods ( @JohnCM_S or @Marc_V ).  Your particular problem might require a data recovery contract (depending on what exactly happened).  https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service

You could send them a private message (using the envelope icon at the upper right of the forum page).  You can include a download link to your log zip (after uploading it to cloud storage - google drive, drop box, etc), and a link to this forum thread.

Don't post your log zip publicly - there is some privacy leakage if you do that.

[Icauto]

Thank you. I just did it.

[Icauto]

Good morning,

I posted a message as you said to:

mods ( @JohnCM_S or @Marc_V

About a week ago. I have not heard back. Anyone else I should post to?

[StephenB]

---

@Icauto wrote:

I posted a message as you said to:

mods ( @JohnCM_S or @Marc_V

About a week ago. I have not heard back. Anyone else I should post to?

---

They are the two Netgear mods who normally follow this forum.

@rn_enthusiast and @mdgm are forum members who might also be willing to take a look.

[Icauto]

Good afternoon,

I hate to be a pest. I tried those and the mail says there are no uers with those names.

Can you double check the spelling?

[Sandshark]

Just click on their user names in his message.

[rn_enthusiast]

Hi @Icauto 

I just saw this message. Thanks for tagging me @StephenB 

I will have a look tonight.

Cheers!

[rn_enthusiast]

Hi @Icauto 

The good news is that your raid is healthy and your disks are OK.

I can see from the BTRFS filesystem log that your system was indeed ~100% full, as you mentioned yourself. I cannot see any detailed information about the filesystem but the BTRFS log does recognise the volume (which is good). I can verify that the reason the volume is "dead", is because it cannot mount the raid filesystem.

The NAS cannot mount the filesystem because it cannot read the filesystem tree root.

[Wed Jun 23 06:03:51 2021] BTRFS info (device md127): setting nodatasum
[Wed Jun 23 06:03:51 2021] BTRFS info (device md127): has skinny extents
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 18310888549789614757 18132006830080
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 18310888549789614757 18132006830080
[Wed Jun 23 06:03:51 2021] BTRFS warning (device md127): failed to read tree root
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 18310888549789614757 18132006830080
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 18310888549789614757 18132006830080
[Wed Jun 23 06:03:51 2021] BTRFS warning (device md127): failed to read tree root
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 16322404533381684543 18132006502400
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 16322404533381684543 18132006502400
[Wed Jun 23 06:03:51 2021] BTRFS warning (device md127): failed to read tree root
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 4608298277984602956 18132005421056
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 4608298277984602956 18132005421056
[Wed Jun 23 06:03:51 2021] BTRFS warning (device md127): failed to read tree root
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 13369222079368885361 18131992215552
[Wed Jun 23 06:03:51 2021] BTRFS error (device md127): bad tree block start 13369222079368885361 18131992215552
[Wed Jun 23 06:03:51 2021] BTRFS warning (device md127): failed to read tree root
[Wed Jun 23 06:03:52 2021] BTRFS error (device md127): open_ctree failed

BTRFS actually holds backup/versions of the tree root, as seen in the BTRFS log:

backup_roots[4]:
	backup 0:
		backup_tree_root:	18131992215552	gen: 458959	level: 1
		backup_chunk_root:	21331968	gen: 458957	level: 1
		backup_extent_root:	18131991920640	gen: 458959	level: 2
		backup_fs_root:		18131990413312	gen: 458958	level: 0
		backup_dev_root:	18131991724032	gen: 458958	level: 1
		backup_csum_root:	18131987267584	gen: 458958	level: 0
		backup_total_bytes:	11987462651904
		backup_bytes_used:	11881543176192
		backup_num_devices:	1

	backup 1:
		backup_tree_root:	18132005421056	gen: 458960	level: 1
		backup_chunk_root:	21331968	gen: 458957	level: 1
		backup_extent_root:	18131992477696	gen: 458960	level: 2
		backup_fs_root:		18131990413312	gen: 458958	level: 0
		backup_dev_root:	18131991724032	gen: 458958	level: 1
		backup_csum_root:	18131998572544	gen: 458960	level: 0
		backup_total_bytes:	11987462651904
		backup_bytes_used:	11881542696960
		backup_num_devices:	1

	backup 2:
		backup_tree_root:	18132006502400	gen: 458961	level: 1
		backup_chunk_root:	21331968	gen: 458957	level: 1
		backup_extent_root:	18132006371328	gen: 458961	level: 2
		backup_fs_root:		18131990413312	gen: 458958	level: 0
		backup_dev_root:	18131991724032	gen: 458958	level: 1
		backup_csum_root:	18131998572544	gen: 458960	level: 0
		backup_total_bytes:	11987462651904
		backup_bytes_used:	11881542696960
		backup_num_devices:	1

	backup 3:
		backup_tree_root:	18132006830080	gen: 458962	level: 1
		backup_chunk_root:	21331968	gen: 458957	level: 1
		backup_extent_root:	18132006731776	gen: 458962	level: 2
		backup_fs_root:		18131990413312	gen: 458958	level: 0
		backup_dev_root:	18131991724032	gen: 458958	level: 1
		backup_csum_root:	18131998572544	gen: 458960	level: 0
		backup_total_bytes:	11987462651904
		backup_bytes_used:	11881542696960
		backup_num_devices:	1

I would deem that the data here can definitely be saved. Filling any filesystem to near 100% is always detrimental and likely an antagonist to this issue. Luckily, BTRFS has many tools to help recover from this situation and it should be possible... but it isn't something to be done over a forum in all honesty. It likely requires a manual mount with either recovery mode or even use of BTRFS restore with a different tree root, in order to recover the volume but it should absolutely be possible. Even BTRFS repair from a clean tree root is a possibility.

However, unless you are good with Linux and has some knowledge of BTRFS, then don't attempt this on your own. Best advise I can give you, is to ask Netgear for assistance against paid data recovery contract. Of course there are many resources online too and even the BTRFS mailing list but again, unless you are very comfortable in the Linux world, this would be too complicated to attempt. Netgear Level 3 support deals with these recovery cases and they would be a good shout for you. You can reference this post if you like.

Cheers

[Icauto]

OK. Thank you for the great answer. Very much  appreciated.

Its our fault. We let t he formware get out of date, gmail stopped excepting emails from the NAS for security, Netgear updated the firmware so Gmail woiuld except them, and we did not update the firmware so we did notknow it was getting full. Our fault.