So the trouble I’ve had with this box is that it falls in the middle of the bios/UEFI game. I’m dealing with Win7 (doesn’t play UEFI) and an i210 NIC (doesn’t seem to play Legacy). Upping to Win10, and booting fully UEFI would be the fix for this last quibble with this box.
Best posts made by geardog
-
RE: NVME boot drive not found after image capture .. doh !
-
RE: connection timed out chainloading failed
@sebastian-roth So I’m not sure what has changed, as I’ve had to focus on other things, but now it works. I didn’t follow the most recent direction, but I’m booting various boxes via pxe successfully. No idea. …
-
RE: A couple images won't shrink/resize on capture..
I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.
Nice thought, but the thread you note doesn’t hold my solution.
https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
Bit locker is off as evidenced by the encryption control commands.
manage-bde -off
manage-bde -status“Way 1” from the FOG wiki made no change either.
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_BitI believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.
-
RE: Cannot find disk on system, NVMe, RAID mode, Intel RST
lspci -nn showed the drive to be in raid mode
using a tutorial on bcdedit via cmd for safemode boot I was able to change the setting without reinstalling windows
now the machine is imaged
resolved and thankyou
coming back to this with a fresh mind and some new info helped
-
RE: No configuration methods succeeded (I210 NIC) HP-Z240
Tried disabling Spanning tree with no effect.
It turned out to be a bios/UEFI setting “option rom launch policies.” New to me. In my defense, this box’s bios is pretty massive and clumsy to navigate through, but works now!
I feel stupid, but my issue appears resolved! Thank you very much George. I might not have ever stumbled through those screens again if it weren’t for you.As an aside, the MAC address cloning is a little odd as fog find and tries to get an IP on the wrong NIC first, before it gives up and tries the next NIC.
Latest posts made by geardog
-
could not mount images folder /bin/fog.upload
Installed ubu 22
fstab mount big drives at /images
installed fog without dhcp
restored a fog config
installed dnsmasq with the suggested config
see my hosts and images in UI dashboard
start client capture task
mounting file system failed
could not mount images folder /bin/fog.upload
args passed reason mount mounting <fog_IP>/images/dev on /images failed permission deniedchecked and reset permissions via chown fogproject:root and chmod 777
.mntcheck is there
I reinstalled fog just to overwrite any old restored config settings that might be lingering and I get the
update /opt/fog.fogsettings message
Well it didn’t note that I also needed to update the fogproject pw, but I had different values in the .fogsettings vs the dashboard so made them match …
reinstall fog, and it’s clean, but the snmysqluser=‘fogstorage’ in .fogsettings I was told to use in install messages has reverted to fog master, and now I cant see my node usage? Default member is unauthorized…still can’t mount the folder …
uhg does any of this make sense to anyone?
::edit:: ehhh just wiped the fog stuff and reinstalled
node is back to showing, but all host and image data is gone
merging two config backups and will restore one with just the good stuff from bothso it’s capturing an image
not sure why I couldn’t sort out credentials after restoring a config -
RE: Could not mount images folder (/bin/fog.download)
@sebastian-roth
Wow, so is my only known option for external storage making the NAS behave as a storage node? It has a flaky proprietary OS/GUI that has warning everywhere. “You will brick me if…” -
RE: Could not mount images folder (/bin/fog.download)
@sebastian-roth
So I’ve edited fstab to mount the images folder (on the NAS) with NFS, it shows up in dashboard, and I can write to it from fog terminal. I’m still, however, getting the same error upon trying to deploy an image to the box. Thoughts?netadmin@V-Ubu-Fog:/media/Images$ df -h Filesystem Size Used Avail Use% Mounted on udev 395M 0 395M 0% /dev tmpfs 88M 952K 87M 2% /run /dev/mapper/ubuntu--vg-ubuntu--lv 20G 7.5G 12G 41% / tmpfs 439M 0 439M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 439M 0 439M 0% /sys/fs/cgroup /dev/sda2 976M 390M 520M 43% /boot /dev/loop0 56M 56M 0 100% /snap/core18/1988 /dev/loop1 56M 56M 0 100% /snap/core18/1997 /dev/loop2 70M 70M 0 100% /snap/lxd/19188 /dev/loop3 71M 71M 0 100% /snap/lxd/19647 /dev/loop4 33M 33M 0 100% /snap/snapd/11402 /dev/loop5 33M 33M 0 100% /snap/snapd/11588 /dev/sda1 511M 7.9M 504M 2% /boot/efi //172.17.17.201/Backup__Desk-1 3.7T 2.9T 844G 78% /media/4TBusb //172.17.17.201/Data 7.3T 4.4T 3.0T 60% /media/Data //172.17.17.201/VMs 7.3T 4.4T 3.0T 60% /media/VMs tmpfs 88M 0 88M 0% /run/user/1000 172.17.17.201:/shares/Images 7.3T 4.3T 3.0T 60% /media/Images netadmin@V-Ubu-Fog:/media/Images$
netadmin@V-Ubu-Fog:/media$ ls -l total 8 drwxr-xr-x 2 root root 0 Apr 14 17:15 4TBusb drwxr-xr-x 2 root root 0 Mar 11 01:30 Data drwxrwxrwx 22 1003 root 4096 Apr 14 19:25 Images drwxr-xr-x 2 root root 0 Feb 7 05:50 namespace drwxr-xr-x 4 root root 4096 Apr 9 13:40 test drwxr-xr-x 2 root root 0 Dec 15 15:43 VMs netadmin@V-Ubu-Fog:/media$ cd Images netadmin@V-Ubu-Fog:/media/Images$ ls -l total 84 drwxrwxrwx 2 501 netadmin 4096 Apr 5 15:28 1old-images1 drwxrwxrwx 2 501 netadmin 4096 Mar 21 2019 aero0- drwxrwxrwx 2 501 netadmin 4096 Mar 21 2019 Alpha0- drwxrwxrwx 2 501 netadmin 4096 Mar 21 2019 Alpha1- drwxrwxrwx 2 501 netadmin 4096 Apr 4 2019 conf-desk--- drwxrwxrwx 4 501 netadmin 4096 Jan 28 18:09 dev drwxrwxrwx 2 501 netadmin 4096 Mar 21 2019 Engineering1 drwxrwxrwx 2 501 netadmin 4096 Mar 21 2019 Engineering3 drwxrwxrwx 2 501 netadmin 4096 May 23 2019 inspection1--- drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 inspection2- drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 inspection-CMM-- drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 inspection-OGP- drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 postdownloadscripts drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 sales-04-- drwxrwxrwx 2 501 netadmin 4096 Jun 25 2019 sales-acc drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 scot-pc-- drwxrwxrwx 2 501 netadmin 4096 Apr 4 2019 ship-main- drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 shipping- drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 tc- -rw-r--r-- 1 501 netadmin 3 Apr 14 19:25 text drwxrwxrwx 2 501 netadmin 4096 Mar 22 2019 ubu1 netadmin@V-Ubu-Fog:/media/Images$
root@NAS Images # ls -l drwxrwxrwx 2 nobody share 4096 Apr 5 10:28 1old-images1 drwxrwxrwx 2 nobody share 4096 Mar 21 2019 Alpha0- drwxrwxrwx 2 nobody share 4096 Mar 21 2019 Alpha1- drwxrwxrwx 2 nobody share 4096 Mar 21 2019 Engineering1 drwxrwxrwx 2 nobody share 4096 Mar 21 2019 Engineering3 drwxrwxrwx 2 nobody share 4096 Mar 21 2019 aero0- drwxrwxrwx 2 nobody share 4096 Apr 4 2019 conf-desk--- drwxrwxrwx 4 nobody share 4096 Jan 28 12:09 dev drwxrwxrwx 2 nobody share 4096 Mar 21 2019 inspection-CMM-- drwxrwxrwx 2 nobody share 4096 Mar 21 2019 inspection-OGP- drwxrwxrwx 2 nobody share 4096 May 23 2019 inspection1--- drwxrwxrwx 2 nobody share 4096 Mar 21 2019 inspection2- drwxrwxrwx 2 nobody share 4096 Mar 21 2019 postdownloadscripts drwxrwxrwx 2 nobody share 4096 Mar 21 2019 sales-04-- drwxrwxrwx 2 nobody share 4096 Jun 25 2019 sales-acc drwxrwxrwx 2 nobody share 4096 Mar 21 2019 scot-pc-- drwxrwxrwx 2 nobody share 4096 Apr 4 2019 ship-main- drwxrwxrwx 2 nobody share 4096 Mar 22 2019 shipping- drwxrwxrwx 2 nobody share 4096 Mar 22 2019 tc- -rw-r--r-- 1 nobody share 3 Apr 14 14:25 text drwxrwxrwx 2 nobody share 4096 Mar 22 2019 ubu1 root@NAS Images #
I’m stumped again.
-
RE: Could not mount images folder (/bin/fog.download)
@sebastian-roth
I made the image folder public, and it didn’t change anything.
It’s actually mounted in fstab using cifs utils, and the NAS shows it has NFS support. I’ll look into a different way to mount it. -
Could not mount images folder (/bin/fog.download)
Reason: mount: mounting 172.17.17.82:/media/Images/ on /images failed: Permission denied
I have migrated fog from a physical server to a VM and have moved image storage from said physical server to a NAS folder which is mounted at /Images on the fog VM. The storage location is entered in the default storage node attributes. The node comes up as expected in the dashboard, and old captured images are seen in dashboard as well. Based on the message and having read some of the similar error messages, I suspect permission issues, but I’m not sure how to address them.
I’m running fog 1.5.9
netadmin@V-Ubu-Fog:/media/Images$ df -h Filesystem Size Used Avail Use% Mounted on udev 395M 0 395M 0% /dev tmpfs 88M 972K 87M 2% /run /dev/mapper/ubuntu--vg-ubuntu--lv 20G 7.5G 12G 41% / tmpfs 439M 0 439M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 439M 0 439M 0% /sys/fs/cgroup /dev/sda2 976M 390M 520M 43% /boot /dev/loop0 56M 56M 0 100% /snap/core18/1988 /dev/loop1 56M 56M 0 100% /snap/core18/1997 /dev/loop3 71M 71M 0 100% /snap/lxd/19647 /dev/loop2 70M 70M 0 100% /snap/lxd/19188 /dev/loop4 33M 33M 0 100% /snap/snapd/11402 /dev/loop5 33M 33M 0 100% /snap/snapd/11588 /dev/sda1 511M 7.9M 504M 2% /boot/efi //172.17.17.201/Backup__Desk-1 3.7T 2.9T 844G 78% /media/4TBusb //172.17.17.201/Images 7.3T 4.4T 3.0T 60% /media/Images //172.17.17.201/Data 7.3T 4.4T 3.0T 60% /media/Data //172.17.17.201/VMs 7.3T 4.4T 3.0T 60% /media/VMs tmpfs 88M 0 88M 0% /run/user/1000 netadmin@V-Ubu-Fog:/media/Images$
netadmin@V-Ubu-Fog:/media/Images$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 55.5M 1 loop /snap/core18/1988 loop1 7:1 0 55.5M 1 loop /snap/core18/1997 loop2 7:2 0 69.9M 1 loop /snap/lxd/19188 loop3 7:3 0 70.4M 1 loop /snap/lxd/19647 loop4 7:4 0 32.3M 1 loop /snap/snapd/11402 loop5 7:5 0 32.3M 1 loop /snap/snapd/11588 sda 8:0 0 35G 0 disk ├─sda1 8:1 0 512M 0 part /boot/efi ├─sda2 8:2 0 1G 0 part /boot └─sda3 8:3 0 33.5G 0 part └─ubuntu--vg-ubuntu--lv 253:0 0 20G 0 lvm / netadmin@V-Ubu-Fog:/media/Images$
netadmin@V-Ubu-Fog:/media/Images$ sudo touch /images/{,dev/}.mntcheck && sudo chmod -R 777 /media/Images netadmin@V-Ubu-Fog:/media/Images$
image storage from fog
netadmin@V-Ubu-Fog:/media/Images$ ls -l total 0 drwxr-xr-x 2 root root 0 Apr 5 15:28 1old-images1 drwxr-xr-x 2 root root 0 Mar 21 2019 aero0- drwxr-xr-x 2 root root 0 Mar 21 2019 Alpha0- drwxr-xr-x 2 root root 0 Mar 21 2019 Alpha1- drwxr-xr-x 2 root root 0 Apr 4 2019 conf-desk--- drwxr-xr-x 2 root root 0 Jan 28 18:09 dev drwxr-xr-x 2 root root 0 Mar 21 2019 Engineering1 drwxr-xr-x 2 root root 0 Mar 21 2019 Engineering3 drwxr-xr-x 2 root root 0 May 23 2019 inspection1--- drwxr-xr-x 2 root root 0 Mar 22 2019 inspection2- drwxr-xr-x 2 root root 0 Mar 22 2019 inspection-CMM-- drwxr-xr-x 2 root root 0 Mar 22 2019 inspection-OGP- drwxr-xr-x 2 root root 0 Mar 22 2019 postdownloadscripts drwxr-xr-x 2 root root 0 Mar 22 2019 sales-04-- drwxr-xr-x 2 root root 0 Jun 25 2019 sales-acc drwxr-xr-x 2 root root 0 Mar 22 2019 scot-pc-- drwxr-xr-x 2 root root 0 Apr 4 2019 ship-main- drwxr-xr-x 2 root root 0 Mar 22 2019 shipping- drwxr-xr-x 2 root root 0 Mar 22 2019 tc- drwxr-xr-x 2 root root 0 Mar 22 2019 ubu1 netadmin@V-Ubu-Fog:/media/Images$
image storage from NAS
root@NAS Images # ls -l drwxrwxrwx 2 fog share 4096 Apr 5 10:28 1old-images1 drwxrwxrwx 2 fog share 4096 Mar 21 2019 Alpha0- drwxrwxrwx 2 fog share 4096 Mar 21 2019 Alpha1- drwxrwxrwx 2 fog share 4096 Mar 21 2019 Engineering1 drwxrwxrwx 2 fog share 4096 Mar 21 2019 Engineering3 drwxrwxrwx 2 fog share 4096 Mar 21 2019 aero0- drwxrwxrwx 2 fog share 4096 Apr 4 2019 conf-desk--- drwxrwxrwx 4 fog share 4096 Jan 28 12:09 dev drwxrwxrwx 2 fog share 4096 Mar 21 2019 inspection-CMM-- drwxrwxrwx 2 fog share 4096 Mar 21 2019 inspection-OGP- drwxrwxrwx 2 fog share 4096 May 23 2019 inspection1--- drwxrwxrwx 2 fog share 4096 Mar 21 2019 inspection2- drwxrwxrwx 2 fog share 4096 Mar 21 2019 postdownloadscripts drwxrwxrwx 2 fog share 4096 Mar 21 2019 sales-04-- drwxrwxrwx 2 fog share 4096 Jun 25 2019 sales-acc drwxrwxrwx 2 fog share 4096 Mar 21 2019 scot-pc-- drwxrwxrwx 2 fog share 4096 Apr 4 2019 ship-main- drwxrwxrwx 2 fog share 4096 Mar 22 2019 shipping- drwxrwxrwx 2 fog share 4096 Mar 22 2019 tc- drwxrwxrwx 2 fog share 4096 Mar 22 2019 ubu1 root@NAS Images #
netadmin@V-Ubu-Fog:/media/Images$ sudo chown fog 1old-images1 [sudo] password for netadmin: chown: invalid user: ‘fog’
The image folder is mounted using smb credentials of a user “fog” created on the NAS, and I can create files on the mount from fog based on those credentials. I’ll happily change this to clear any ambiguity, but I’m chasing my tail I think.
Where am I? -
RE: connection timed out chainloading failed
@sebastian-roth So I’m not sure what has changed, as I’ve had to focus on other things, but now it works. I didn’t follow the most recent direction, but I’m booting various boxes via pxe successfully. No idea. …
-
RE: connection timed out chainloading failed
@sebastian-roth
What does this get me into? Will I have to recreate/replace these when I reinstall fog? I may be ham fisted, as I’ve probably reinstalled fog 15 times during my use of it. I’d like to be aware of complications in SOP, moving forward. -
RE: connection timed out chainloading failed
@sebastian-roth
Well, I made the following edit in ltsp.conf# Set the root directory for files available via FTP. tftp-root=/tftpboot/10secdelay
rebooted the fog vm
no apparent change in behavior…
Chainloading still fails, and shell>config output shows no proxydhcp section -
RE: connection timed out chainloading failed
so a montage of my poking around
In short, after chainloading fails and I run config, there is no proxydhcp listed
when I run dhcp net0 from shell
I then get fog popping up in proxydhcp with the correct ipWhat does this mean?
net0
net0
proxydhcp