NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Lost all disks after firmware 6.9.4 upgrade
Shortly after upgrading to firmware 6.9.4 I lost the data volume and all four disks are marked red. There's an alarm saying "Remove inactive volumes to use the disk. Disk #1,2,3,4."
I have a ba...
UnknownAXHF wrote:
I have a feeling it may be related to 6.9.4, as I upgraded the other day and I've had the same issue as you.
Generally speaking, there are quite a few posts reporting it after a firmware update (not necessarily 6.9.4). I'm not convinced the update itself is the cause - it's also quite possible that some checking that is done post-update (or even during the reboot) is uncovering a latent issue that was actually there before. Most people only reboot their NAS after an update.
It would be good if Netgear provided more information on the causes, and looked into prevention or repair of the more common ones. This issue happens much too often.
Not to flame anyone/anything or accuse anyone/netgear:
Don't you agree that this have been happening more often after the introduction of 6.9.3?
There have been lots of new firmwares and the inactive disc/s juste showed up?
I'm one of thoose that got affected by it and never really found the root cause.
I reboot now and then, have schedules for discmanagement running and never had any errors there. Or warnings.
Anyway, i think Netgear have good products, semi decent support OF COURSE WITH exceptions to the better...
keep up the good work this community does!!
Regards
// Hans
I remote access your NAS and find filesystem is failed, so data volume can't be mounted after NAS reboot.
Could you please create a support case?
https://www.netgear.com/support/
it takes time to recovery data.
root@NAS04:~# btrfsck /dev/md127
checksum verify failed on 20176179691520 found AB26D242 wanted 00000000
checksum verify failed on 20176179691520 found AB26D242 wanted 00000000
checksum verify failed on 20176179691520 found AB26D242 wanted 00000000
checksum verify failed on 20176179691520 found AB26D242 wanted 00000000
bytenr mismatch, want=20176179691520, have=0
Couldn't read tree root
ERROR: cannot open file systemHi Evan2
Thank you for looking into this.
Unfortunately I've tried to create a support case for a week, but the website is not accepting the serial number (error message "Something went wrong. Please contact support team.".
I getting a bit tired of the whole situation and don't plan on spending much more time on this now. I have a full backup but wanted to find out if the problem with the drives was 1) because of firmware upgrade 2) user/operational error or 3) product fault, so I could learn from this and hopefully avoid it in the future. I frankly don't think I'll get an answer and I think I'll just wipe the whole thing and restore data and just hope it'll be long until the disks disapear on me again.
Tore
Below is my suggestion,
1. Too many snapshots would get high resource of btrfs, so please just take snapshots on necessary share folders and with an appropriate frequency.
2. I advise you to run a weekly volume balance. (System -> Volumes -> Volume Settings -> Volume Schedule)
3. I advise you to set snapshot pruning occurs when the volume reaches a used capacity of 80%. (System -> Volumes -> Volume Settings -> Snapshot Pruning)
viperhansa wrote:
Not to flame anyone/anything or accuse anyone/netgear:
Don't you agree that this have been happening more often after the introduction of 6.9.3?
I've been seeing inactive volume posts since at least 2015, with firmware as old as 6.2.4. I don't see a spike with 6.9.3, but there might have been one with 6.9.0 in last year - hard to say. They do seem to be more common with recent releases, but that might be because the installed base is growing (there were no OS 6 ReadyNAS before 2013).
Whatever the trend, this happens often enough that I think Netgear should provide more information in the UI to allow users to diagnose why their volume can't be mounted. They should also analyze the common causes to see if there are preventative measures (for example frequency of maintenance tasks, or new maintenance task that checks the file system or RAID) that could be added to the UI, or if there is some detection/repair possible in the new safe mode. They might also reconsider the SMART thresholds they are using in their alerts (and at least make them configurable).
Thanks for the reply!
Good answer too!
Yes it would be good if there were more info at hand when things like this happens.
We could probably discuss this for a loong time . :-)
regards
// Hans
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
