NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
btrfs corruption AGAIN
So I noticed today after trying to write a file to the nas that it was read only (Access denied) coudl not even edit files from the admin page.
Sure enough i went in to SSH to peek at the dmes...
- So a quick update to this. I know it's been a year since my last post, but since this shows up in google now I may as well put a closing comment.
Since my last post, Volume failures have continued and i've pretty much just come to accept this to be a quirk of bad implementation on Netgear's part and that these devices are simply unreliable due to the well known failings of BTRFS as a file system in general everywhere else in the linux community. I really wish the devices used XFS, but alas; we're stuck with the poor design choices Netgear gave us - short of hacking and flashing them with something else.
In subsequent failures, i've not even bothered SSH'ing in to the devices, and used only factory provided tools (Exluding SSH which is still factory provided too btw) and used instead regular backup options as well as ReadyDR. - the file system still crashes. even at 90% which is a huge waste of otherwise perfectly usable free space.
Regular volume house keeping has always been in place, weekly scrubs, monthly defrags, etc.
Currently in the process of switching the disks over from Seagate Barracudas to WD Reds with X2 the capacity to hopefully mitigate the volume almost full self destruct issue that shouldn't exist in the first place (On any sane file system)
But if even this fails to help and i end up once again with a busted volume later down the line, my advise to the general populace at the moment would be "Don't use these devices for anything mission critical where you expect the free space to become limited. If you do, don't trust the RAID configurations and stick to single disk shares, as bugs in BTRFS regarding RAID will likely leave you with a busted volume 6 months down the line."
Until Netgear either fix the bugs in BTRFS (Unlikly) Or switch to a more mature and reliable Filesystem (Like XFS) these NAS drives are volatile at best.
The same thing happend to me today. All the shares now appear empty. I never used SSH and didn't do anything unusual. Using the latest firmware (6.9.3).
[Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS info (device md127): no csum found for inode 8749 start 406678265856 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096 [Mon Jun 4 12:07:15 2018] BTRFS critical (device md127): unable to find logical 13599006130176 len 4096
I'm going to try to run a scrub but I think i'll have to reinstall the NAS.
The volume maintenance options in the GUI are not the way to deal with problems like this.
If you don’t have an up to date backup and need a data recovery attempt you could contact support.
- So a quick update to this. I know it's been a year since my last post, but since this shows up in google now I may as well put a closing comment.
Since my last post, Volume failures have continued and i've pretty much just come to accept this to be a quirk of bad implementation on Netgear's part and that these devices are simply unreliable due to the well known failings of BTRFS as a file system in general everywhere else in the linux community. I really wish the devices used XFS, but alas; we're stuck with the poor design choices Netgear gave us - short of hacking and flashing them with something else.
In subsequent failures, i've not even bothered SSH'ing in to the devices, and used only factory provided tools (Exluding SSH which is still factory provided too btw) and used instead regular backup options as well as ReadyDR. - the file system still crashes. even at 90% which is a huge waste of otherwise perfectly usable free space.
Regular volume house keeping has always been in place, weekly scrubs, monthly defrags, etc.
Currently in the process of switching the disks over from Seagate Barracudas to WD Reds with X2 the capacity to hopefully mitigate the volume almost full self destruct issue that shouldn't exist in the first place (On any sane file system)
But if even this fails to help and i end up once again with a busted volume later down the line, my advise to the general populace at the moment would be "Don't use these devices for anything mission critical where you expect the free space to become limited. If you do, don't trust the RAID configurations and stick to single disk shares, as bugs in BTRFS regarding RAID will likely leave you with a busted volume 6 months down the line."
Until Netgear either fix the bugs in BTRFS (Unlikly) Or switch to a more mature and reliable Filesystem (Like XFS) these NAS drives are volatile at best.Hi ronlaws86,
We have released a ReadyNASOS 6.10.2-T49 (Beta 1) firmware which includes an improved BTRFS stability on ARM units (102/104/2120/202/204/212/214). This may lessen the file system issues on those units (Inactive Volume or Volume offline). You may try that firmware and see if there will be an improvement.
You can download it here: https://community.netgear.com/t5/ReadyNAS-Beta/ReadyNASOS-6-10-2-T49-Beta-1/m-p/1792843#M10659
Regards,
The 104 does have limited memory. Are you running any apps that might use that up and cause the lock-ups? They may be related -- the lock-up directly causing the corruption or the hard reset doing so. Read errors on the drive can also cause lock-ups. I have seen that in some of my experiments, where I often use some old drives I retired due to too many errors.
As for your comment on BTRFS stability, I see a lot about BTRFS RAID instability, but the ReadyNAS uses MDADM RAID with BTRFS on top to avoid that. I have had only one volume go bad on me in multiple machines (excluding the experiments where a known bad drive or my schenanigans likely caused it), and that was on an EDA500 where the cable had come partly loose. But, my only ARM machine is a 102 I have just for experiments. Maybe the latest improvments for ARM will make your experience more like mine; which is to say, trouble free.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
