Unable to Mount NFS
-
Well I did a fresh install on my home server and encountered no errors whatsoever. Sadly my network would not play ball and I don’t have the energy to deal with it so I can’t say if FOG would totally work. But since none of my research has turned up anything that makes sense it seems the best course of action is to delete the whole VM and start from scratch. Something somewhere may have been corrupted and I’d rather burn the house down then try to root out all of the termites. Fortunately I have a three day weekend to get started.
-
Awesome then. I’m sorry about all the hassle.
-
Not feeling the awesomeness myself, but thank you for all of your help, Tom. Hopefully this will be of use to future users. I suspect something became corrupted during one of the reruns of the installer. It’s too bad there isn’t a script to uninstall the way one installs. If only I had the programming skills I’d write one. Till next time … :D.
-
I can probably make that all happen for you.
The only issue I forsee with it is the deleting of the fog database (if you’re doing a full install of course)
-
Well even Windows programs leave pieces of themselves behind. FOG runs in a virtual machine so I can delete and recreate without much difficulty. I made that decision for this very reason. Part of the issue here is also that I didn’t make a copy of the VM like I should have.
An uninstall script would make a lot of sense for a future release. The effect may be mostly psychological, but it helps to know I can get rid of a program by clicking a file and running a command or two. Also to be perfectly honest after weeks of work I want something guaranteed to be effective. No offense, but I feel a clean slate is badly needed right now and the delete key has yet to fail me :p. Also there is a soft deadline to all of this. The library must go to Windows 7 by April which really means Spring Break (Mid-March) since there will be no other time before then when the library will be nearly empty. So I have to figure all of this out and by then. Except the Dean wants to meet in a week or two and I need something to show him.
-
A thought. Could the names of the NFS services be the root cause of all of this nonsense? The proper terms for my fresh install were nfs-common and nfs-kernel-server as opposed to nfs-common.dpkg-new and nfs-kernel-server.dpkg-new. Portmapper is running, mountd is running, there is no firewall, the config files seem fine. There is no other differences I can spot between my home server install and the one at work.
-
It’s possible, I’m assuming your home server you’re using Debian 7 as well?
-
Yes, that’s why I chose to put it there. It’s not being used for anything else, but is already configured so it was just a matter of downloading and installing FOG. Of course there is a firewall and one of these new Motorola Surfboard modem/router combo deals on the network which will make any PXE booting attempt a pain. So I’ll still create the second VM just in case and rename those files come Tuesday.
-
I have a motorola Surfboard Modem on my network and have yet to have any issues pxe booting. It listens for tftp yes, but only from the isp, not my network as the specifics it’s looking for is unavailable on my network.
-
Hmmm maybe I’ll give it a shot. I just can’t stop thinking about this but don’t want to go into work on a Saturday.
-
All perfectly understandable. I don’t expect you to go to work on a saturday, but if you work at home on your own systems, you might come up with a workable procedure for yourself when you finally do get back to work.
-
A fresh install did the trick. I am in the process of imaging my desktop PC. For some reason it would only work if I set the OS to be windows 7 (it runs 8.1) and multiple partitions. However it is currently working. The only problem is my laptop refuses to connect to the internet which has forced me to write this from a cellphone. But that is a temporary problem. Over the next two days I will recreate the fog server in a virtual machine on my laptop in case renaming the NFS services does not help.
-
In regards to the test machine at work, renaming the services corrected the issue. I was able to start the imaging process. Unfortunately I could not finish because it is necessary to repartition the virtual hard drive to make more space which might require some doing. I have but two questions:
1. Why do active tasks always display as “queued” until finished?
2. For some reason pressing * does not cancel an image upload in progress. -
If the image type is not single-partition, resizable, the base FOG code does not update the task status until it finishes. There is a quick code change that will enable showing of progress for multiple partition, single disk images.
I don’t think the code is in place yet to show progress on upload tasks either.
-
chad,
progress does get displayed now, on all imaging tasks.
-
What sort of code change are we talking about? The feature would be nice, but is not critical.
