This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
We had a power cut and when the ReadyNAS 214 powered back up it was stuck at "Booting... 90%" with a flashing blue power button for over 4 hours. It was restarted and same happened again.
Using RAIDar the status is "Management service is offline".
The Diagnostics logs contain the following text:
System
Volume root is 100.00% full
/var is consuming 300 MB
Volume DATA-3 is inactive
Logs
No errors found.
System Management
2019-01-06 12:50:13: DB (main) schema version: 24 ==> 24
2019-01-06 12:50:13: rndb_create() ==> 3 (123ms)
2019-01-06 12:50:13: Error create table (db)
2019-01-06 12:50:13: dba create failed
2019-01-06 12:50:11: Failed to start ReadyNAS System Daemon.
The firmware version is 6.9.4. The disks in RAIDar are all showing with a green tick.
ReadyNAS did not boot properly and this might be due to the Volume root is 100.00% full message you are getting, This usually happens if you have installed an App that uses the OS volume filling it's capacity.
Inactive volume might be due to the same reason but hopefully you have a backup of your data.
Doing a Factory reset might be advised but if you have not backed up your data the best thing to do is to contact Support.
You can always login to my.netgear.com to create a case and contact Support for assistance, this needs escalation to fix the issue.
If you are comfortable using SSH, Community members might be able to advice you some steps to take.
ReadyNAS did not boot properly and this might be due to the Volume root is 100.00% full message you are getting, This usually happens if you have installed an App that uses the OS volume filling it's capacity.
Inactive volume might be due to the same reason but hopefully you have a backup of your data.
Doing a Factory reset might be advised but if you have not backed up your data the best thing to do is to contact Support.
You can always login to my.netgear.com to create a case and contact Support for assistance, this needs escalation to fix the issue.
If you are comfortable using SSH, Community members might be able to advice you some steps to take.
