- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Root drive filled up and now things are broken
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Root drive filled up and now things are broken
I need some help. 6.9.2. I think TVHeadEnd addon is a bit broken - and dumped a whole load of ts files in my root directory. This is the second time this has happened. I deleted the *.ts files the first time and this time i thought I'd move them and see what they are to help in determining what is going on.
So tried a few things, restarted readynas and - sluggish performance, no shares mounted or available. log files showed dropbox start fail, email sending fail.
Anyway, the issue is now, admin login page will not get through to the dashboard - it goes the horizontal-bar screen then "ReadyNAS Admin Page is offline".
This is what I did from the start:
Shell in a box didn't work (typing name and then "enter" just resulted in "session closed"
Tried to enabling SSH - which would enable, then would reload the config page with SSH showing disabled.
Quickly enabled it and hammered NAS with PuTTY to connect. Successful
root log in and moved all TS files to my raid array directory and a folder
df is all good, 47% used instead of 100%
shutdown -r now works, but can't log in
systemctl list-units shows readynasd as active failed failed
htop shows no real issue - apache is up and working
I guess somewhere the full root disk has stuffed up some readynas core files or config or something?
Please help?! How can I enable diagnostics if I can't get to the readynas web config page?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
Could be all sorts of different problems created with the config when the 4GB root volume gets full.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
so...... what can i do?
systemctl list-units shows readynasd.service as loaded failed failed
failed in red... where is the log for readynasd please?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
It's in the journal. So if you want the last say 5000 lines of the journal related to readynasd you'd do e.g.
# journalctl -an5000 CATEGORY=readynasd.log
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
Aug 31 09:48:15 Sextuple readynasd[5593]: dba import failed
Aug 31 09:48:15 Sextuple readynasd[5672]: readynasd log started
Aug 31 09:48:15 Sextuple readynasd[5672]: readynasd started. (restarted=0)
Aug 31 09:48:16 Sextuple readynasd[5672]: Error rndb_import() ==> rc=5
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
journalctl -xe shows my shares are not available or unmountable... Is this something I can fix? The files are still on the NAS and can navigate to them...
-- Unit readynasd.service has begun starting up. Aug 31 11:20:58 Sextuple readynasd[12066]: readynasd log started Aug 31 11:20:58 Sextuple readynasd[12066]: readynasd started. (restarted=0) Aug 31 11:20:58 Sextuple readynasd[12066]: DB (main) schema version: 23 ==> 23 Aug 31 11:20:58 Sextuple readynasd[12066]: DB (queue) schema version: ne w ==> 0 Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Backups/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Multimedia/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Downloads/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Archive/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Discs/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Dropbox/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/Documents/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/eBooks/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/istat/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/RNXconfig/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Cannot parse cifs share conf file. /Raid-6/._share/OneDrive/samba.conf Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:58 Sextuple readynasd[12066]: Non exist share='(null)' is s pecified in AFP config. Skip the config. Aug 31 11:20:59 Sextuple readynasd[12066]: Malformed json file. Aug 31 11:20:59 Sextuple readynasd[12066]: rndb_one_drive_import() ==> 5 (0ms) Aug 31 11:20:59 Sextuple apache2[3335]: [error] [client 192.168.1.101] C onnect rddclient failed, referer: https://192.168.1.103/admin/ Aug 31 11:20:59 Sextuple readynasd[12066]: rndb_import() ==> 5 (815ms) Aug 31 11:20:59 Sextuple readynasd[12066]: Error rndb_import() ==> rc=5 Aug 31 11:20:59 Sextuple readynasd[12066]: dba import failed Aug 31 11:20:59 Sextuple systemd[1]: readynasd.service: Main process exi ted, code=exited, status=255/n/a Aug 31 11:20:59 Sextuple systemd[1]: Failed to start ReadyNAS System Dae
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
You could create a new share and fix e.g. /Raid-6/._share/Backups/samba.conf based on that and then do
# cat /data/._share/*/samba.conf > /etc/frontview/samba/Shares.conf
Or
# touch /var/readynasd/.need_export # systemctl restart readynasd
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
No good.
Tried and OS Re-install and it stuck on Checking FS...
In fact, getting to the boot menu is hit and miss - once I get it on the front panel, I cant use the front panel touch controls to change the option. It worked once and hasn't worked since.
Anyway to do an OS reinstall WITHOUT the boot menu?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
OK. I did an OS reinstall but stuck booting 97%. All data is there and Frontview won't let me in. I can see my data but readynasd keeps failing due to shares being stuffed. Would you be so kind as to assist me with getting these shares working again?
I can then update my backups (which are 1 month old) and wipe and reinstall the firmware from scratch.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
Managed to boot into DebugMode.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
Note I'm no longer at NETGEAR (my last day was yesterday) so you'll need to see if others can help or fix this yourself.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
What happened to your signature? I tried clicking on one of your old messages and now everything errors out.. I need to know how to send log files! Congrats on the retirement
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
Oh, noone asked me to send logs but im sure they will. Thanks for your help.
To op: my root drive also filled up after a disk failure. I found that my backup of amazon drive caused it. even though I had no working array, it just downloaded it onto the root drive.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Root drive filled up and now things are broken
No one from netgear followed-up on this - so I factory reset and reloaded from a backup.
To be fair, my 2013 Ultra 6 was upgraded to OS6 in 2015, and then died earlier this year and the drives seemlessly inserted into the 316... it was probably time after 3 years and going from 6.2.4 through 6.9.2 to reinstall...
Things I found
Root disk was 65% full and on a factory reset, 20%
Re-installed apps actually work first time
Still need to reinstall SpiderOak via SSH - it would be really, REALLY nice if SpiderOak was an option alongside GoogleDrive, Dropbox, OneDrive etc.....