Image Capture Issue
-
I am having issues capturing an image. I have FOG installed on Ubuntu 16.04. FOG version is 1.4.2. I am trying to save my images on a Buffalo NAS model LS-CH500L. Hopefully that is possible. I added the storage node and all of the credentials are correct. I took a picture of the error but it fails to upload. The error says it fails to mount the file system at the top. After the box that says and error has been detected it says the path and then connection refused. Thank you for any help.
-
How do you have that NAS setup? Is it configured as a FOG storage node or are you trying to mount the NAS onto your fog server and save files through the fog server to the nas?
-
I have configured it using the FOG web GUI. The Buffalo NAS itself has a web GUI that you use to create directories and share with permissions. I made a directory called FOG and gave the user “imaging” read and write privileges to that directory.
I went into FOG and set up the storage node. As I was going down the steps to add the node I used Windows to FTP into the shared directory and create the folders inside that were listed on the page used to add the node. I put the user and password for the directory that I created inside of the Buffalo NAS control panel down as the credentials before I saved the node.
-
@datastream To setup a NAS as a storage node, you need to make that storage node appear to be configured as a real fog server. So you need to have ftp and nfs setup on that storage node. You have to get the paths correct from both the nfs and ftp sides. FOG will use ftp to replicate the images from the master fog node to the storage node. The clients will use nfs to download the images from the storage node.
I do have a write up on how to do this with a synology nas and a windows 2012 server. You may have to translate that document into how your NAS is configured.
https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node
https://forums.fogproject.org/topic/10097/setting-up-a-windows-2012-server-as-a-fog-storage-node -
@george1421 I don’t see an NFS option on the Buffalo Linkstation. Windows, Apple, FTP, and Disk Backup are the check boxes in shared folder support. I’m wondering if that is the issue. I have an old XServe that I am backing up now so I can wipe it. I am going to configure a NAS on it and use it. It is just sitting in the rack anyways.
I am still going to work on the Linkstation though. It would be nice to have several nodes. I am wondering if I can upgrade firmware or install different firmware on the Linkstation to make it more flexible.
-
@datastream said in Image Capture Issue:
I have an old XServe that I am backing up now so I can wipe it.
Why not make it a fog storage node then instead of a NAS (which is just a skinny linux OS anyway)?
I have you ask about your design/FOG deployment strategy. What do you hope to gain by adding multiple storage nodes if they are on the same subnet/network?
-
@george1421 The Xserve has a lot of space on it so I would like to get more use out of it than just for FOG. If I have multiple nodes wouldn’t that make imaging faster by taking the load off of one distribution point? I have a lot of computers that I want to use FOG for.
-
@datastream said in Image Capture Issue:
If I have multiple nodes wouldn’t that make imaging faster by taking the load off of one distribution point
I’ve asked one of the developers for clarity on this. But my guess is that you will get no benefit from having multiple storage nodes on the same subnet. Just from a CPU performance perspective FOG itself doesn’t need a real powerful system since all of the heavy lifting is done by the target computers. The FOG server manages the imaging process and replicates to storage nodes. If you have a lot of target computers using the FOG client then the Master FOG server also manages and talks to the FOG clients.
As for using the xserve for other activities I can understand that.
-
https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Storage_Management
This page might help a bit with understanding the purpose of nodes and such.
It is my understanding that storage groups are designed for different physical locations and nodes for scalability and redundancy. I could be wrong of course.
Based on that premise, it should be possible, provided you set it up correctly.
edit: I feel the need to clarify that while it’s technically possible, it wouldn’t necessarily give much benefit since the bottlenecks are likely to be elsewhere, primarily network connection and target clients
-
@george1421 Are you meaning leave OS X on the Xserve and set it up as a storage node?
-
@datastream Can it supply the required services to make it a storage node? While we haven’t done that before (on the surface) OSX could function as a FOG storage node.
-
@george1421 I’m not going to attempt it. Apple has quit supporting the Xserve so the OS can’t be upgraded anymore. That is why I am getting ready to do something else with them after I get stuff set up elsewhere. I have 3 of them. I haven’t used this one for a while so I am installing Ubuntu now to create the NAS.
I also use Casper Imaging for our Apple laptops. That is on another Xserve. I have configured another VM with Ubuntu to run Casper. Ubuntu can’t run the imaging portion of the suite though so I am going to work on getting the imaging of my Apple laptops working with FOG and hopefully package distribution later. Then I can get rid of Casper for FOG completely and not have the licensing bill that comes with Casper. That will get rid of that Xserve.
-
@datastream said in Image Capture Issue:
If I have multiple nodes wouldn’t that make imaging faster by taking the load off of one distribution point?
OK I received some clarity and a bit of education on this issue too. If you have 2 or more FOG servers (master or storage node) in the same storage group and you are not using the location plugin, the Master FOG server will switch the target computers between all nodes in the storage group. So you will achieve a unicast deployment benefit from having more than one “fog” server on a single subnet.
I would still debate the (no) value in having more than one fog server on a single subnet. If you are deployment more than 5 unicast images at a time, I would propose you use multicasting (assuming your network is capable) to avoid consuming your entire network bandwidth with unicast images.
-
@datastream said in Image Capture Issue:
I am installing Ubuntu now to create the NAS
This is fine, then once you get ubuntu setup, install FOG on it as a storage node. Once that is done you can use it for anything else too. I was just concerned that you were going to use one of those “off the shelf” nas’s like freenas. That would limit your ability to do “other” things.
-
@datastream For Macs, please be aware of the current issue concerning iPXE boot capabilities
https://forums.fogproject.org/topic/10261/macos-update-broke-ipxe
Basically, some of the newer OS X updates will update the firmware which might break current compatibility with the iPXE binaries.
Devs are looking into it, but it might be a while before a solution can be found.
-
@Quazz I am using the Ubuntu VM as my FOG server. I don’t want to use the whole server with ESXi for storage also, just for the server portion. That is why the old Xserve is getting Ubuntu installed and set up as the NAS. I can then use it as a storage node as well as storage for files for things like computer backup and storage for files from our art department. Since the Xserve is just going to be a NAS the IPXE thing shouldn’t matter.
