NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
alaaes
Apr 13, 2019Aspirant
netgear redynas rn2120v2 - inactive volume
I lost my data.. error message :volum is inactive or dead. I have raid 5 and global spare.. why I lost the volum.. netgear redynas rn2120v2 sn:<redacted>
Hopchen
Apr 14, 2019Prodigy
Hi alaaes
I took a look at the logs. Thanks for sending them over StephenB
The data volume appears dead because it cannot mount. Your disks and raids are fine but the volume filesystem is damaged. This likely happened because the volume got very full.
[19/04/09 01:24:25 EET] warning:volume:LOGMSG_VOLUME_USAGE_CRITICAL Less than 5% of volume MayData's capacity is free. MayData's performance is degraded and you risk running out of usable space. To improve performance and stability, you must add capacity or make free space.
Shortly after the data volume getting so full, we see it go into read-only mode due to filesystem errors.
[19/04/12 23:05:20 EET] warning:volume:LOGMSG_VOLUME_READONLY The volume MayData encountered an error and was made read-only. It is recommended to backup your data.
Upon next boot, the volume can no longer mount. Here are the filesystem errors upon the boot.
[Sat Apr 13 00:06:29 2019] BTRFS: device label xxxxxxxx:MayData devid 1 transid 267526 /dev/md127 [Sat Apr 13 00:06:30 2019] BTRFS info (device md127): setting nodatasum [Sat Apr 13 00:06:30 2019] BTRFS info (device md127): has skinny extents [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 2243902102695562974 18224709369856 [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 2243902102695562974 18224709369856 [Sat Apr 13 00:06:30 2019] BTRFS warning (device md127): failed to read tree root [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 2243902102695562974 18224709369856 [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 2243902102695562974 18224709369856 [Sat Apr 13 00:06:30 2019] BTRFS warning (device md127): failed to read tree root [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 11380574474146357643 18224706617344 [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 11380574474146357643 18224706617344 [Sat Apr 13 00:06:30 2019] BTRFS warning (device md127): failed to read tree root [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 18374686479654780670 18224704028672 [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 18374686479654780670 18224704028672 [Sat Apr 13 00:06:30 2019] BTRFS warning (device md127): failed to read tree root [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 13915544454450785711 18224701997056 [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): bad tree block start 13915544454450785711 18224701997056 [Sat Apr 13 00:06:30 2019] BTRFS warning (device md127): failed to read tree root [Sat Apr 13 00:06:30 2019] BTRFS error (device md127): open_ctree failed
BTRFS, as with other filesystems, struggle when you fill it so much. I suspect that it encountered some corruption due to lack of free space.
In any case, you need assistance getting the data volume back. The above filesystems errors are usually recoverable and data can typically be restored. There are several BTRFS built-in tools to deal with this.
If the data is important and you don't have a backup, then I recommend that you contact NETGEAR and enquire about a data recovery contract. They can help attempt to restore the data (best effort basis) but it will cost a couple hundred bucks minimum.
Cheers
- alaaesApr 14, 2019Aspirant
thanks for every thing..
I have some questions about the same problem:
The volume has 4 hard disks and each size is 8TB .. One of them is spare and the rest used by raid5 .. The volume has been hidden to LUN1 size 8TB, LUN2 2TB and LUN3 2TB
And size of the final volume is just over 14TB .. The size of the data that i copied to the volume does not exceed 2TB on LUN1 and less than 1.5TB on LUN2 ..
If the size of the stored data does not exceed 4TB ..
Now why do you say there is no free space for file system errors?
Question 2: What do you mean by leaving free space for file system errors and where?
The third question: Is if the number of files is too large as we have. Does it have an effect?Question 4: When the snapshot is activated, the LUN becomes protected .. How can I allow users to write and read from it?
Where this process lasted for a whole day Because the number of files is too large.finally
If the file count is too large about 30 million files per 1TB? What do you recommend..Thanks again..
- StephenBApr 14, 2019Guru - Experienced User
alaaes wrote:
And size of the final volume is just over 14TB .. The size of the data that i copied to the volume does not exceed 2TB on LUN1 and less than 1.5TB on LUN2 ..
If you made "thick" LUNs then the three LUNs would take 12 TB of space on the NAS even if they held no data at all. Snapshot space could easily fill up the rest of the volume.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!