NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas 314 (6.5.0-T338 - Retry startup)
Hi, Parts of my shares stopped working, so I did a proper reboot of my ReadyNAS device. It now won't restart, every time it does it says 'Retry startup' I let it start fully, no shares work,...
Backup what 9TB to where :P
Because this Beta software fixed bugs in the older software I was using, and I haven't touched/messed with it since :|
I just took all the disks out, put a new one in and upgraded the Firmware to 6.6.0.
trying stuff now to see if I can at least get into the logs.
The device starts and is healthy now, but i can't access anything - and all shares are disabled etc...
The logs I found this..
9 21:07:13 Redwood-NAS systemd[1]: systemd-journald.service: main process exited, code=killed, status=7
Jan 09 21:07:13 Redwood-NAS readynasd[1936]: DB sanity check failed! Trying backup readynasd_2017_01_09_080036.db.
Jan 09 21:07:13 Redwood-NAS readynasd[1936]: readynasd started. (restarted=0)
Jan 09 21:07:13 Redwood-NAS readynasd[1936]: DB (main) schema version: new ==> 20
Jan 09 21:07:14 Redwood-NAS readynasd[1936]: cp: writing `/var/backups/readynasd/db.sq3': No space left on device
Jan 09 21:07:14 Redwood-NAS readynasd[1936]: cp: failed to extend `/var/backups/readynasd/db.sq3': No space left on deviceso I think running out of space and it needs cleaning out.. but where do I start?
So all my shares have 'X' next to them
only HTTP/HTTPS services are running - nothing else, so no SMB/FTP etc, and SSH isn't running - I can't enable it either due to this error:
Model: ReadyNAS 314
Firmware: 6.6.0
Context: system_panel_support
Error:
15002020817Also now getting
2017-01-09 22:24:37: Assertion 'f->data_hash_table' failed at ../src/journal/journal-file.c:1047, function journal_file_link_data(). Aborting.
Random things happening, MY data is accessible thorugh readyCloud online, but not locally
when I try to create a share, or enable smb etc I get
Invalid SNMP community.
Invalid Communit() (rc=1).
Code: 1002030817Any advice?
-- I've sent in my logs as per the sig :) Any help is appreciated!
Beta firmware is beta, so you should update your regular backup before updating to it or if that's not possible update your regular backup after updating to the beta. You certainly should not remain on it once production firmware is released.
Having said that having run into a problem like this it's unwise to update the firmware before dealing with why the root volume is so full in the first place.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
