NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Readynasd not starting after creating /.force_snapshots_upgrade
Hello! On my ReadyNAS I face currently the following issue, that the readynasd service is not starting. Therefore my access to the admin page is not available. Background: within upgrading to curr...
Hi,
will consider reinstalling when I have physical acces to the ReadyNAS. Currently I am trying to fix it from about 1500 km away :)
Here are the requested outputs:
Database
root@WG-LAN:~# sqlite3 --header --column /var/readynasd/db.sq3 'select * from "$timemachine_quota"' user_id enabled capacity_mb ---------- ---------- ----------- 110 1 5000 111 1 5000
Timemachine config
root@WG-LAN:~# cat /etc/netatalk/timemachine.conf # DO NOT EDIT. [MaxTv's timemachine] path = /SERIEN/.timemachine/MaxTv rwlist = MaxTv valid users = MaxTv invalid users = guest nobody @guest @nogroup vol size limit = 4768 time machine = yes [admin2's timemachine] path = /SERIEN/.timemachine/admin2 rwlist = admin2 valid users = admin2 invalid users = guest nobody @guest @nogroup vol size limit = 4768 time machine = yes
Start with debug log-level
root@WG-LAN:~# readynasd -v 5 -l - [19/08/12 21:01:48] 32056:32056 readynasd.c:1040 () readynasd log started [19/08/12 21:01:51] 32056:32056 context.c:239 (debug) NEW GLOBAL_CONTEXT: db.sq3=0xc3d118 [19/08/12 21:01:51] 32056:32056 context.c:286 (debug) NEW GLOBAL_CONTEXT: event.sq3=0xc41128 [19/08/12 21:01:51] 32056:32056 context.c:289 (debug) NEW GLOBAL_CONTEXT: globalctx=0xc3cdb8 [19/08/12 21:01:51] 32056:32056 readynasd.c:1299 () readynasd started. (restarted=0) [19/08/12 21:01:53] 32056:32056 db_access.c:127 (error) Error rndb_import() ==> rc=3 [19/08/12 21:01:53] 32056:32056 readynasd.c:1358 (error) dba import failed
As stated before, I already manually removed the btrfs subvolumes. Can this cause issues with the timemachine configuration?
I tried now to fiddle around with the timemachine.conf (haven't found this file before) and replaced it with an empty file with same access rights and the webinterface is now accessible again. For now it is fine to me, but reinstalling the device is still something to consider.
Hi StephenB,
I deleted the /.force_snapshots_upgrade already, but it'll still run into the issue described above.
Will it be safe for the stored Data to reinstall the OS?
gronaix wrote:Will it be safe for the stored Data to reinstall the OS?
It should be (it's designed to be non-destructive). Though it is always a good idea to have a backup.
In addition to partially reinstalling the OS, it will
- reset the admin password to password
- reset the network configuration to use DHCP with no bonding
- turn off volume quota
The procedure is documented on pages 28-29 here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
Can you post your $timemachine_quota table?
sqlite3 --header --column /var/readynasd/db.sq3 'select * from "$timemachine_quota"'
and your timemachine config:
cat /etc/netatalk/timemachine.conf
Starting readynasd with verbose debug logging might also help identifying cause:
readynasd -v 5 -l -
(start readynasd with Debug log-level and output log to stdout)
Hi,
will consider reinstalling when I have physical acces to the ReadyNAS. Currently I am trying to fix it from about 1500 km away :)
Here are the requested outputs:
Database
root@WG-LAN:~# sqlite3 --header --column /var/readynasd/db.sq3 'select * from "$timemachine_quota"' user_id enabled capacity_mb ---------- ---------- ----------- 110 1 5000 111 1 5000
Timemachine config
root@WG-LAN:~# cat /etc/netatalk/timemachine.conf # DO NOT EDIT. [MaxTv's timemachine] path = /SERIEN/.timemachine/MaxTv rwlist = MaxTv valid users = MaxTv invalid users = guest nobody @guest @nogroup vol size limit = 4768 time machine = yes [admin2's timemachine] path = /SERIEN/.timemachine/admin2 rwlist = admin2 valid users = admin2 invalid users = guest nobody @guest @nogroup vol size limit = 4768 time machine = yes
Start with debug log-level
root@WG-LAN:~# readynasd -v 5 -l - [19/08/12 21:01:48] 32056:32056 readynasd.c:1040 () readynasd log started [19/08/12 21:01:51] 32056:32056 context.c:239 (debug) NEW GLOBAL_CONTEXT: db.sq3=0xc3d118 [19/08/12 21:01:51] 32056:32056 context.c:286 (debug) NEW GLOBAL_CONTEXT: event.sq3=0xc41128 [19/08/12 21:01:51] 32056:32056 context.c:289 (debug) NEW GLOBAL_CONTEXT: globalctx=0xc3cdb8 [19/08/12 21:01:51] 32056:32056 readynasd.c:1299 () readynasd started. (restarted=0) [19/08/12 21:01:53] 32056:32056 db_access.c:127 (error) Error rndb_import() ==> rc=3 [19/08/12 21:01:53] 32056:32056 readynasd.c:1358 (error) dba import failed
As stated before, I already manually removed the btrfs subvolumes. Can this cause issues with the timemachine configuration?
I tried now to fiddle around with the timemachine.conf (haven't found this file before) and replaced it with an empty file with same access rights and the webinterface is now accessible again. For now it is fine to me, but reinstalling the device is still something to consider.
The only issue I can see with that config is if either user "MaxTv" or "admin2" have been deleted, when you delete a user it should also delete its timemachine (and its entry in this config file)... Do you still have the two users? If not, did you delete them from GUI or SSH? If you deleted the user from SSH that would explain it as it does not clean up the database / config files if you do so.
Deleting the snapshots from SSH is fine and should not cause any issues.
Can you post output of:
ls -lah /SERIEN/.timemachine/
and
grep -Ei "maxtv|admin2" /etc/passwd sqlite3 /var/readynasd/db.sq3 'select * from "$user" where uname = "MaxTv" or uname = "admin2";'
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
