Trying to push image to client - Mounting File System Fail



  • I am trying to push an image to a client and the process get’s stuck at "Mounting File System…Failed " and then I see the repeated message “mount:mounting 10.1.8.10:/media/BFD_/images/ on /images failed: Connection timed out”. Any idea what could be causing this?

    I am running Fog 1.2.0 on Ubuntu 12.04.!!0_1463068487094_Fog Error 51216.JPG



  • @Sebastian-Roth Ours was quite a few firmware updates behind and we weren’t able to jump from our current strait to the newest, but stepping up just one version solved it.


  • Developer

    @PageTown Great to hear that you you found a solution! So with the old firmware (or possibly configuration?) NFS was not allowed to pass through I reckon.



  • @fry_p We updated the firmware on our Cisco switch and I was able to push out images again! Thanks for chiming in about your experience, this could’ve stretched out for a long time!


  • Testers

    @PageTown @Mentaloid I just tested this using updated firmware on the Cisco SB switch. I left all settings default and I was able to push an image to a client on the switch! As for the linksys, my networking knowledge is limited. I’m accustomed to running DHCP on a Windows Server. I’m sure one of these other fine gentlemen can help with that. You can also try updated firmware for the SB switch here: https://software.cisco.com/download/navigator.html?mdfid=283018960

    (Should have all models of SB switch firmware there. I didn’t need a login to download. You can update through the switch GUI)



  • @fry_p That is EXACTLY what we have. I am trying to test this theory using a little Linksys router to handle DHCP, but I am unable to get my host machine to PXE boot. I have changed the settings in the router and set up a matching connection on the Fog server, but so far no luck. Any ideas?


  • Testers

    @Mentaloid said in Trying to push image to client - Mounting File System Fail:

    @fry_p sidenote: The only SB switches I had issues with were some of the <24 port switches - and this was a issue with the stupid security they had messing with UDP/NFS; this was fixed with a firmware upgrade.

    Ah, yes mine was a little 8 port SB. I didn’t have time to mess with it since a class was using the lab I was imaging the next period, but I’ll keep that in mind. Those things are a pain!



  • @fry_p sidenote: The only SB switches I had issues with were some of the <24 port switches - and this was a issue with the stupid security they had messing with UDP/NFS; this was fixed with a firmware upgrade.


  • Testers

    @PageTown I don’t mean to derail this thread, but do the clients that you are trying to push to happen to be connected to a Cisco Small Business managed switch? It’s a shot in the dark, but I have gotten the exact same error you have when trying to use that. Our IOS based Cisco Catalyst switches are no problem, but there is something about the Cisco SB series that doesn’t play nice with FOG (there is probably a way to configure it properly, but I couldn’t figure it out). I apologize if this isn’t the case. If you are using that, try a dumb switch. That’s what resolved my issue.


  • Developer

    /images directory structure is looking good. But what about the other two commands I posted?



  • @Sebastian-Roth Here’s what I get after running la -lahRt /images now:

    0_1463672058984_Fog ls lahRt images.jpg


  • Developer

    @PageTown Then what do you get from ls -lahRt /images, mount and exportfs -v??



  • @Wayne-Workman No. My path should be /images now.



  • @PageTown Doubtful that the Windows Server is causing issues. Are you using the /media/BFD_ path again?


  • Developer

    @PageTown said:

    I was able to upload an image without any issues, but when I try to push that image to a machine I am still getting hung up on the Mounting thing.

    That sounds really strange. Why would it upload (to NFS) but not download from it? Again, show us the output you get from ls -lahRt /media/BFD_/images! As well please show us the full output of mount (I am wondering what filesystem that external drive is formated with).

    Could something in the server setup be causing this issue?

    No I don’t think so. NFS has nothing to do with PXE boot or DHCP in general.

    Changing the default image paths is not as easy as it might seem on first sight. I count it to the more advanced things to adjust on your FOG server and I would only recommend it to people having played with FOG and linux a fair bit. That said I am wondering if you are aware of the possibility to mount external devices to pretty much any directory within your filesystem. Doesn’t have to be /media/XXX. So if you ever consider to setup things from scratch again you might want to simply mount your external disk to /images before installing FOG.



  • I did a HDD wipe and re-install of Ubuntu 12.04 and Fog 1.2.0. I was able to upload an image without any issues, but when I try to push that image to a machine I am still getting hung up on the Mounting thing.

    Before I start the troubleshooting process again, I wanted to mention that I am running Fog over a Server 2012 network. Fog is not handling the DHCP. On the server I have 066 Boot Server Host Name & 067 Bootfile Name configured to allow undionly.kpxe and Fog to boot over the network. Could something in the server setup be causing this issue?



  • @PageTown That’s because the /dev directory doesn’t exist, from the below output. You could just make the directory with mkdir /media/BFD_/images/dev



  • @Wayne-Workman

    It wouldn’t take ‘touch /media/BFD_/images/dev/.mntcheck’. It said that the location didn’t exist which makes me think that something has happened to all my images.

    I have decided to wipe my server and start from scratch. Thanks for the help.



  • @PageTown You’re missing the .mntcheck files.

    Here’s the command to make them, and to set permissions afterwards:
    touch /media/BFD_/images/.mntcheck
    touch /media/BFD_/images/dev/.mntcheck
    chmod -R 777 /media/BFD_/images



  • @Wayne-Workman Here’s what I am seeing when I run that command:

    0_1463149695242_IMG_0385.JPG


 

343
Online

41.5k
Users

11.9k
Topics

113.2k
Posts