NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NAS not starting any services #25220444
I had a hard time coming up with a good subject for this problem, since I don't really know what's wrong and how to describe it. Here's the story:
Suddenly I noticed that CIFS was not behaving normally. I could browse shares, but not add any files.
This can of course be because of a million things, so I figured I try disabling and enabling that service in RAIDiator (4.2.27). So I disabled it and tried enabling it again, but selecting that service and clicking apply does absolutely nothing. The checkbox disappears and nothing more happens. No error message. Weird...? FTP still worked though, at least for browsing.
So I restarted the NAS. Then the CIFS service was still off and can't be started and the shares (naturally) disappeared from the network. Uh?! Not only that, but FTP had disabled itself. And, yeah, it won't start either. SSH had stopped working. Addons like Transmission as well won't start. I have Crashplan running on it, which I can't access either, so I don't really know if that starts or not.
Browsing via HTTPS still works, so the volume and the shares are still there. Everything looks green. Disks are ok etc. Status display on the front of the NAS seems normal.
So I turn to the logs. "No logs exist." Ehh? I try do download all logs anyway and it gives me some XML error message, which I guess is normal when no logs exist. I sure haven't deleted them.
So I try the memory test on the boot menu. No problems there. I also try the disk test on the boot menu. Finished fine and the NAS booted up again.
So I figure that the OS Reinstall on the boot menu should be able to solve this. Something is very corrupt/weird with how the NAS behaves! I think I managed to download a copy of the settings before I proceeded, since I wasn't sure what would actually be reset, and then I did the OS Reinstall.
The only thing that has changed is that the admin password is reset to standard - and I can't even change that. I fill in the fields and try to apply it. And, yes, nothing happens.
Then it struck me, maybe it's the browser (Chrome) or something?? So I tried IE as well, but no luck there. Also tried Safari in my phone.
I then tried getting SSH to work again by trying to upload that addon file, but I just got "Update file is not valid for this architecture" as error message.
So now I'm pretty much stuck here. I'm out of ideas! The NAS says everything is A-OK, but refuses to run anything I want to run on it and it doesn't tell me why. I can't even start rsync, which does not bode well either...
Please help! :(
Suddenly I noticed that CIFS was not behaving normally. I could browse shares, but not add any files.
This can of course be because of a million things, so I figured I try disabling and enabling that service in RAIDiator (4.2.27). So I disabled it and tried enabling it again, but selecting that service and clicking apply does absolutely nothing. The checkbox disappears and nothing more happens. No error message. Weird...? FTP still worked though, at least for browsing.
So I restarted the NAS. Then the CIFS service was still off and can't be started and the shares (naturally) disappeared from the network. Uh?! Not only that, but FTP had disabled itself. And, yeah, it won't start either. SSH had stopped working. Addons like Transmission as well won't start. I have Crashplan running on it, which I can't access either, so I don't really know if that starts or not.
Browsing via HTTPS still works, so the volume and the shares are still there. Everything looks green. Disks are ok etc. Status display on the front of the NAS seems normal.
So I turn to the logs. "No logs exist." Ehh? I try do download all logs anyway and it gives me some XML error message, which I guess is normal when no logs exist. I sure haven't deleted them.
So I try the memory test on the boot menu. No problems there. I also try the disk test on the boot menu. Finished fine and the NAS booted up again.
So I figure that the OS Reinstall on the boot menu should be able to solve this. Something is very corrupt/weird with how the NAS behaves! I think I managed to download a copy of the settings before I proceeded, since I wasn't sure what would actually be reset, and then I did the OS Reinstall.
The only thing that has changed is that the admin password is reset to standard - and I can't even change that. I fill in the fields and try to apply it. And, yes, nothing happens.
Then it struck me, maybe it's the browser (Chrome) or something?? So I tried IE as well, but no luck there. Also tried Safari in my phone.
I then tried getting SSH to work again by trying to upload that addon file, but I just got "Update file is not valid for this architecture" as error message.
So now I'm pretty much stuck here. I'm out of ideas! The NAS says everything is A-OK, but refuses to run anything I want to run on it and it doesn't tell me why. I can't even start rsync, which does not bode well either...
Please help! :(
47 Replies
Replies have been turned off for this discussion
- You would not want to do a symbolic link of tmp to the data volume.
I edited the config file that sets the temp directory for Crashplan to use the data volume but perhaps that didn't stick either. - Thanks for your replies! If you're interested, I did a little more digging and thinking. :)
I found out that every time Crashplan starts it puts one of those jna1234567890123456789.tmp files of exactly 136883 bytes in tmp. They're definitely related to Java. From my googling it seems it might have to do with how Java is installed and that there might be a way to stop this from happening by unpacking some jar file to somewhere and pointing some config towards that instead. Well... not for me... :)
I'm not sure how such files could constitute 2.5GB though. That would be 18.000+ of them. Perhaps the files grow over time? Perhaps they are created at other times as well? Were there that many or of larger sizes in there? In any case, if deleted, Crashplan still works.
I did not find any specific temp path in the Crashplan config. Only for cache. The only references to "tmp" are for files/folders that should be hidden in the GUI I think so you don't select them for backup.
Right now the total Crashplan cache size is small, but I'll keep an eye on it in parallel with the tmp folder.
Would it be possible to force the creation of these jna*.tmp files on the data volume via some symbolic link or something? I found this, but I'm not sure I'm understanding it. Running what program?
http://stackoverflow.com/questions/1010 ... -io-tmpdirI don't know how well this will work, but I just moved /usr/local/crashplan to /c/.crashplan and then created a sym link to it:
ln -s /c/.crashplan /usr/local/crashplan
Crashplan seems to be working ok that way
I did the same thing for the /tmp dir, moved it to /c/.tmp/ and sym linked to it. That one I am not as confident I won't run into some strange problem sooner or later, but I'm trying it for a while.
This should prevent either /tmp nor /usr/local/crashplan from ever filling up the root partition again.
Dewdman42 wrote:
I don't know how well this will work, but I just moved /usr/local/crashplan to /c/.crashplan and then created a sym link to it:
ln -s /c/.crashplan /usr/local/crashplan
Crashplan seems to be working ok that way
I did the same thing for the /tmp dir, moved it to /c/.tmp/ and sym linked to it. That one I am not as confident I won't run into some strange problem sooner or later, but I'm trying it for a while.
This should prevent either /tmp nor /usr/local/crashplan from ever filling up the root partition again.
I moved the cache by changing my.service.xml (look for <cachePath>) but left the rest alone.
If /c/ couldn't be mounted you might have some issues running w/o /tmp. So I'm not confident in that one either.
It sounds like you ran out of memory?
- The cache was several hundred MBs. I removed it. Not sure why the change didn't stick.
1. There were a whole of files starting with jna and ending in .tmp in the /tmp directory. Did the change of /tmp directory for Crashplan stick?
2. You can delete files from there, though some of the files in there may be in use by an application at the time e.g. if a Frontview backup job is in progress you shouldn't delete the temporary backup job log for that backup.
3. You should periodically check the fullness of the OS partition and take steps to find out what's going on if the usage is unexpectedly high.
4. No the OS partition is fixed at 4GB in size.Hi!
I have the exact same problem with my ReadyNas Ultra 2 and created a ticket, 25880935.
I would really really appreciate som help from you :)
I cant connect to my ReadyNas with SSH anymore so I cant do just about anything about my problem...
Reinstalled OS, and now the volume settings shows nothing in the webinsterface (which is the only accessble service on the device...)
but I HOPE the data is still on the disks..
Thanks in advance!
Markus
nosstrannel wrote:
Hi!
I have the exact same problem with my ReadyNas Ultra 2 and created a ticket, 25880935.
I would really really appreciate som help from you :)
The ultra is running crashplan???
- I'm not sure exactly what crashplan is putting into /tmp/ - I'm not seeing anything there on my system.
The crashplan cache can get much bigger - mine has ~1.2GB at the moment. - Thanks mdgm so much for your help! Everything is fine again. I had to reenable FTP and redo the share settings for that. And also reupload the SSH plugin. But that was pretty much it!
(Btw, good call vandermerwe. :wink:)
It seems your new setting for the Crashplan cache folder didn't stick. I found this in the config file, which seems to be the default location:<cachePath>/usr/local/crashplan/cache</cachePath>
But if that was [only] a couple of hundred megs, then I guess the real problem was whatever was in tmp, right?
I have definitely learned a valuable lesson here. So I'm keen in making sure I don't run into this problem again in the future. Therefore, I have a couple of questions that I hope you can help me with:
1.
The 2.5GB in tmp, what did it consist of mainly? What was the main culprit? Something I've installed? Or can this happen with just standard everything?
2.
Can I delete anything in tmp at anytime? I mean if it allows itself to be deleted that is and is not locked.
3.
Is it possible to schedule some form of routine clean-up of tmp? Or should I manually set a reminder for myself to go in and do some house cleaning now and then?
4.
One final question, which I guess I already know the answer to, but I might as well ask. Is it possible to expand the OS partition or does that require some custom firmware or something? THAT I'm not getting into...! - Yes, your OS partition was full.
tmp had 2.5GB of files in it.
/usr/local/crashplan/cache had hundreds of MBs in it as well.
I changed the crashplan configuration to store the cache and the tmp files on the data volume.
Hopefully this helps.
Your services configuration was corrupt (probably due to trying to start/stop services when the OS partition was full), so I replace it with the default one. So you may need to re-enable some services and install some apps over the top of themselves. - I hear you... Thanks a lot for your input!
Here's hoping somebody at Netgear will do me a solid! *crossing fingers and standing by*
EDIT: I went ahead and created a support case as well: #25220444 - No, the OS partition is separate from the data volume and sometimes fills up with logs from apps etc.
You can either wait here to see if anyone can help (I'm afraid I can't) or contact Netgear support who will help you but will charge.
It is possible this is not a full OS partition and/ or there may be other problems. vandermerwe wrote: and definitely don't download any logs, that will make things worse, and may have already.
Ouch! I did not know that. :(
I'm guessing that the OS partition is not the same thing and the volume C then, since that one is at about 85%.
Yeah, since I can't access it via SSH I guess I'm out of luck regarding those simple commands, right? :(
I would of course appreciate the help with the "Tech support" boot menu option if someone at Netgear would be willing to help me out. I do not have a local full backup of the volume and Crashplan was nowhere near done with this either.
Could I trouble someone with this? I suspect logs related to Crashplan could maybe be the problem. :/ Although I've been running Crashplan for a couple of years already.- It's possible that these are symptoms of a full OS partition.
Do you have a backup?
If you had ssh enabled you could look at how full the OS partition is with some simple commands, and also fix it.
Sometimes deleting some logs helps to free up some space and get things working again, and in your case may allow you to install the ssh add on. Try deleting all the backup job logs. I wouldn't delete the system logs just yet, and definitely don't download any logs, that will make things worse, and may have already.
The other methods for fixing a full OS partition are remotely (Netgear support), or a factory default.
I think you are going to need help with one of these. There may be someone here who can help you with this as a courtesy.
Disk problems manifest in a wide range of symptoms so it's worth checking all your disks with vendor tools too. You'll need to power down, remove and label the disks and hook them up to a PC to do this.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
