You have to remember one thing. The fog client service runs at the SYSTEM user not the current logged in user. So the drive is being mapped as SYSTEM and it works for the SYSTEM context, that context doesn’t apply the current logged in user. While I haven’t tried this, but log into a windows computer as a normal user, open a command shell as an administrator (or different user). Then map a drive as that admin user, is that drive visible in the normal user’s shell. Is a drive mapped in the normal user’s shell available to the admin user’s command window. I’m suspecting not.
Posts made by george1421
-
RE: Problem to mapping network drive using snapin with batch file
-
RE: Deploying image, "~empty image might cause issues," but it initially shows as 65GB then 0.0 after deploy
@geardog On the plus side FOS sees your disk (/dev/sda) so that issue is not it.
Can you show the output of this command
ls -la /images/sales-04
There has to be a reason why its saying “No image files found…” -
RE: Deploying image, "~empty image might cause issues," but it initially shows as 65GB then 0.0 after deploy
@geardog I’ve seen this similar error when in uefi mode and the disk controller is set to raid-on mode.
Can you schedule another capture or deployment to this target computer, but before you submit the job, tick the debug check box then pxe boot the target computer. After a few enter key-presses on the target computer you will be dropped to a linux command prompt. At the command prompt please key in the following command.
lsblk
and post the results here. -
RE: Deploying image, "~empty image might cause issues," but it initially shows as 65GB then 0.0 after deploy
Can we get a bit more details on the target computer?
Who made it and what model number?
Is this in uefi or bois (legacy mode)?
From the FOG iPXE menu did you see if the hardware was compatible with FOG? Did both network and disk pass? -
RE: Portable Fog Server
@imagingmaster21 I have around 250MB of fog owned files. That number was rounded up a bit. But 250MB is a good budget number. But also realize that this is only for the fog system itself. It doesn’t include all of the distros libraries that FOG installs during installation.
-
RE: More Storage
I have a tutorial for that here: https://forums.fogproject.org/topic/10450/adding-additional-image-storage-space-to-fog-server
There are several other ways to go about adding additional space to a fog server. A lot depends on how / if your fog server uses LVM volumes. If your fog server is setup for LVM (logical volume manager) then you would just add the new disk to the current root volume, expand the file system and you are done. Your fog server will see the new space.
Secondly, if you typically deploy by a single unicast stream at a time using an ssd on a fog server is a bit of a waste for image storage. I would go with a large 7200 rpm HDD over a SSD here. It is a more cost effective spend of your money. You simply don’t need the speed on the fog server side. The fog server only moves data from its local hard drive to the network adapter. Now if you try to deploy 3 or more unicast images at a time then an SSD would be helpful, but beyond 2-3 unicast streams you will start to saturate your FOG server’s 1GbE network link. You can do what you want, but adding a SSD for image storage on the fog server isn’t necessary in most cases.
-
RE: No DHCP Response on Eth0
@bartont126 I’m glad you have it all worked out. I checked in on the other threads and it looks like you found out about the dirty bits and shutting windows down properly and how to add additional storage to your fog server. well done.
-
RE: No DHCP Response on Eth0
@bartont126 If you are getting 3GB/min right now that is acceptable. I may have your thread mixed up with another one with a similar issue.
Adding a second hard drive is a topic for another thread. But there are a few ways to go about it.
- If your system uses lvm, just add the new disk to the lvm pool and your done.
- Add the new disk as a second storage node on your fog server
- Mount the new disk over /images to place all of your images on the new disk while the original disk is just used for the OS and FOG.
If you look in the tutorial section of the forums you will see many of my posts, some discuss adding additional space to your fog server. The easiest I my say is the LVM route.
-
RE: No DHCP Response on Eth0
@bartont126 well now don’t forget your original issue with spanning tree. Make sure you get that bit fixed on your enterprise switch so you get the best deployment times. Ideal times for deployment are around 6GB/min according to the partclone screen. Capture times will be less of course. Less rates to just under 2GB/min are typically seen, but 6GB/min is ideal with a typical SSD dual or quad core target computer. I have seen speeds as high as 10GB/min with a new 7280 and 7285 Dell laptop with nvme drives. Just so you are aware the target computer has a bigger impact on deployment speeds than the FOG server.
-
RE: Hyper V and Pxe boot to Fog problems
@paulman9 OK great, that means that the currently shipping version of iPXE does resolve your issue. I suspected that it would not work 100%, but what did work was getting past the initializing devices. I’ll take a look at creating the full undionly.kpxe boot kernel in a while for you to test. But for now it looks like we have a path forward.
@Developers be aware that the current version of iPXE addresses hyper-v booting. I’ve seen this in a few threads lately.
-
RE: No DHCP Response on Eth0
@bartont126 can you also run these commands? (hint if you connect to your FOG server using a terminal program like putty you can copy and paste outputs a bit easier).
ls -la /images/dev
ls -la /images
-
RE: No DHCP Response on Eth0
@bartont126 those settings are correct. You have 2 shares. /images and /images/dev. (I assume the missing slash in front of /images was a type-o).
I’m still a bit confused why your target computer is reporting “Unable to locate image store”. Did you do the prerequisites of disabling the firewall and setting selinux to permissive?
-
RE: Hyper V and Pxe boot to Fog problems
@paulman9 Ok, so now we’ve determined that a bios mode vm running under Win10 1709 stops at initializing devices in the iPXE kernel. I’m going to create an updated (test) ipxe kernel for you to try with this new hyper-v host. Understand this is not a supported route, but I’m interested to see if the issue with 1709 has already been addressed by the iPXE group.
The basic steps I’m doing is using the rom-o-matic site https://rom-o-matic.eu/ to create a new undionly.kpxe also I’ll include the ipxe script from github https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src/ipxescript
I’ll leave the file here for a few days to give you a chance to to see if it works. https://drive.google.com/open?id=1fmy2CKSxGlMAv4gW6CFk_ncA694KaOpm
Will it work?? Hopefully yes, but maybe not. Lets see…
-
RE: Deny FOG webpage login
What version of FOG are we talking about? I just confirmed that at least in 1.4.4. the mobile / quick access option is available still.
-
RE: WoL and VLAN
WOL is just network communications, so what ever your network router is, is also your wol gateway. WOL is just a directed broadcast. Your vlan router must support directed broadcasts.
-
RE: No DHCP Response on Eth0
@bartont126 ok on the FOG server, will you key in the following command
showmount -e 127.0.0.1
That will show the NFS share on the fog server. It should present two lines one for /images and one for /images/dev I’m traveling right now so I don’t have immediate access to a fog server to give you an example. -
RE: No DHCP Response on Eth0
@bartont126 Can you get me a clear shot of the kernel parameters, I need to see the entire line. Its in the section kernel variables and settings. The target computer can’t reach the fog server. I have a felling the answer is in the settings
-
RE: No DHCP Response on Eth0
@bartont126 Sorry I didn’t see your second (third) image. That means that the target computer can’t reach the FOG server. Did you happen to change the IP address of the FOG server after FOG was installed? FOG doesn’t like having its IP address changed or assigned by dhcp.
-
RE: No DHCP Response on Eth0
@bartont126 said in No DHCP Response on Eth0:
Cisco Catalyst 2960 Series
So you have a business class switch here. Either change the stp mode to rstp (or fast-STP what ever its called). That should address your issue, or as I said test with an unmanaged switch to see if you can get it past this point.