NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
upgraded to latest OS, now all volumes are gone
so I upgraded to 6.10.7 on my rn214 last night. I thought all went well until I tried to write to the volume.
I could not write as it was in read only mode.
so i rebooted the NAS, and now the volume is gone. what the heck?
I do at least have a recent backup, THANKFULLY!!!!!
but it's 4 x 4TB drives and the volume had like 755Gig free. so there's a lot to copy over again from backup.
any thoughts about why this happened or is thins a known issue? I simply clicked check for upgrades within the web page and allowed it to upgrade.
if I simply create a new volume, will it magically make the data available that is on the drives again?
thanks!
Mike B
only entries in my logs here:
| May 19, 2022 02:10:44 AM | System: ReadyNASOS background service started. | |
| May 19, 2022 02:10:22 AM | System: External storage device connected. | |
| May 19, 2022 02:10:18 AM | Volume: The volume NGear_NAS encountered an error and was made read-only. It is recommended to backup your data. | |
| May 19, 2022 02:10:18 AM | System: Firmware was upgraded to 6.10.7. | |
| May 19, 2022 02:10:18 AM | Volume: Less than 10% of volume NGear_NAS's capacity is free. NGear_NAS'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. | |
| May 19, 2022 02:05:09 AM | System: The system is rebooting. | |
| May 19, 2022 12:05:09 AM | Backup: Successfully completed backup job job_001. |
6 Replies
Replies have been turned off for this discussion
exibar wrote:
only entries in my logs
You'll almost certainly see more details in the log zip at the time when the NAS reported it went read-only.
System.log, kernel.log, and systemd-journal.log are some useful places to look. You can also get a better handle on disk health by looking at disk_info.log
exibar wrote:
so I upgraded to 6.10.7 on my rn214 last night. I thought all went well until I tried to write to the volume.
I could not write as it was in read only mode.
so i rebooted the NAS, and now the volume is gone. what the heck?
I do at least have a recent backup, THANKFULLY!!!!!
but it's 4 x 4TB drives and the volume had like 755Gig free. so there's a lot to copy over again from backup.
Still, less than 10% free space. That's actually quite risky with BTRFS. Personally I make sure I never go below 15%.
There are several possible causes, so you could potentially pursue it with paid Netgear support, and possibly avoid rebuilding the NAS volume. Personally I'd just rebuild it myself (and FWIW, my volume is bigger than yours).
exibar wrote:
if I simply create a new volume, will it magically make the data available that is on the drives again?
The new volume would be empty.
lots of ethernet errors.... looks like the NICs aren't bonded
-- Logs begin at Thu 2022-05-19 07:33:12 EDT, end at Thu 2022-05-19 14:12:21 EDT. --
May 19 13:36:22 NetgearNAS kernel: bond0: An illegal loopback occurred on adapter (eth1)
Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
May 19 13:36:22 NetgearNAS kernel: bond0: An illegal loopback occurred on adapter (eth0)
Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
May 19 13:36:23 NetgearNAS kernel: bond0: An illegal loopback occurred on adapter (eth1)
Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
May 19 13:36:23 NetgearNAS kernel: bond0: An illegal loopback occurred on adapter (eth0)
Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
May 19 13:36:24 NetgearNAS kernel: bond0: An illegal loopback occurred on adapter (eth1)
Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
May 19 13:36:24 NetgearNAS kernel: bond0: An illegal loopback occurred on adapter (eth0)
Check the configuration to verify that all adapters are
exibar wrote:
lots of ethernet errors.... looks like the NICs aren't bonded
Did you ever look at these logs before? This could have been the case all along. Is the switch configured to use LACP bonding? Many just support static LAG.
Are you seeing any disk-related errors or BTRFS errors? Or are the ethernet errors swamping the logs?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
