Okay so I had to do a combo of Way 1 and 2. I had done Way 1 yesterday when I updated to 3431 per Tom’s forum post. Then to fix the issue that 3431 caused I updated to 3432. Since I didn’t check immediately not sure if the password never took in the Storage Node or not. I repeated Way 1 today then checked the Storage Node in FOG and found that I had to manually change the password there. Maybe you need to stop and start a service in FOG after changing .fogsettings?
Anyway it is fixed.
I am on version 3432 and I can upload new images to FOG, but I cannot Download images to systems. I have checked the permissions on /images and nothing has changed recently, but now when I try and schedule a Download Task I get the below error:
ALready in the process of decrypting after turning it off. Will post once I try imaging it.
This system that I am starting with was deployed before I got here and set up FOG. The person has now left the company and before I start messing with creating a Generic Image for all the new Surfaces I want to back this one up as is. I would not care about the size of the image except I am waiting on more storage space to become available and don’t have the room at the moment to have a 250 GB image sitting out there.
Okay, so a bit of info about Surface Pro 3. Once you boot into Windows the Drive itself is encrypted. The files are still open so if you copy them off you can access them, but you cannot access anything in the drive or manipulate the Partitions from outside the OS.
The only way to dycrypt the drive that I have found so far and am about to test is to turn BitLocker on fully sending the keys to a flash drive, then turn off Bitlocker.
I will let you know if that works. According the Internet if you do not boot into the OS then the drive should not be encrypted.
I am about to get 5 or 6 Surfaces in and want to get a standard image ready to go. I am able to register the Surface and set it up for imaging, but using the Single Disk Resizable it tries to grab an image of the whole Partition rather than just the used space like all the other systems I have imaged.
Has anyone run into this issue? I am going to try the other Image types but figured I would ask here as well.
Thanks.
Awesome, thanks I am up and running again. Glad it wasn’t something I did.
After updating to SVN 3431 I cannot Schedule Upload or Download Tasks. In the Creation screen I get Advanced Settings option of Schedule Shutdown after task completion, but none of the other tasks, like Schedule as a CRON job. When I click the Create Upload Task button It just sends me back to a Host Management screen with nothing in the center confirming the scheduled task. I have all the normal side and top menus.
Just for reference this is a self contained FOG Server all Storage Nodes are local.
okay, it is fixed I had to restart both mysql and tftp.
Thanks I am bookmarking the pages out of your signature.
mj@fog-server:~$ sudo ls -al /var/www/fog/service/ipxe
total 34192
drwxr-xr-x 3 fog www-data 4096 May 14 15:41 .
drwxr-xr-x 3 www-data www-data 4096 May 11 08:21 …
-rw-r–r-- 1 fog www-data 1105 May 11 08:20 advanced.php
-rw-r–r-- 1 fog www-data 44908 May 11 08:20 bg.png
-rw-r–r-- 1 fog www-data 756 May 11 08:20 boot.php
-rw-r–r-- 1 fog www-data 6169392 May 11 08:20 bzImage
-rw-r–r-- 1 fog www-data 6170512 May 11 08:20 bzImage32
-rw-r–r-- 1 fog www-data 234697 May 11 08:20 grub.exe
drwxr-xr-x 2 root root 4096 May 14 15:51 hiren
-rw-r–r-- 1 fog www-data 9577456 May 11 08:20 init_32.xz
-rw-r–r-- 1 fog www-data 10914208 May 11 08:20 init.xz
-rw-r–r-- 1 fog www-data 25340 May 11 08:20 memdisk
-rw-r–r-- 1 fog www-data 1839104 May 11 08:20 memtest.bin
mj@fog-server:~$ sudo ls -ld /tftpboot
drwxr-xr-x 2 fog root 4096 May 11 08:25 /tftpboot
mj@fog-server:~$ sudo ls -al /tftpboot
total 2572
drwxr-xr-x 2 fog root 4096 May 11 08:25 .
drwxr-xr-x 25 root root 4096 May 11 08:25 …
-rw-r–r-- 1 fog root 840 May 11 08:25 boot.txt
-rw-r–r-- 1 root root 293 May 11 08:25 default.ipxe
-rw-r–r-- 1 fog root 389009 May 11 08:25 ipxe.kkpxe
-rw-r–r-- 1 fog root 389057 May 11 08:25 ipxe.kpxe
-rw-r–r-- 1 fog root 388044 May 11 08:25 ipxe.krn
-rw-r–r-- 1 fog root 389073 May 11 08:25 ipxe.pxe
-rw-r–r-- 1 fog root 25340 May 11 08:25 memdisk
-rw-r–r-- 1 fog root 16794 May 11 08:25 pxelinux.0.old
-rw-r–r-- 1 fog root 165088 May 11 08:25 snponly.efi
-rw-r–r-- 1 fog root 101989 May 11 08:25 undionly.kkpxe
-rw-r–r-- 1 fog root 102037 May 11 08:25 undionly.kpxe
-rw-r–r-- 1 fog root 382650 May 11 08:25 undionly.kpxe.INTEL
-rw-r–r-- 1 fog root 102053 May 11 08:25 undionly.pxe
-rw-r–r-- 1 fog root 147728 May 11 08:25 vesamenu.c32
Also now that I am on the FOG machine locally, if I try and go to the management website it tells me the Database schema needs to be updated. I was able to open up and log into the same page without issue from my regular workstation until I logged onto the FOG server, now it too says the schema needs to be updated. Weird!!
Yesterday everything was working fine without issue. Ubuntu came up and asked to install some updates, so I let it.
Today when a client boots to FOG it gets an error “pxe-e32 tftp open timeout” and when I try and TFTP GET undionly.kpxe it says connection request failed.
I checked 66 and 67 on the DHCP server and they are the same.
I will post the results of ls -al /var/www/fog/service/ipxe and ls -ld /tftpboot in a moment, but they look to be correct to me.
Thanks!
Thanks, I will test this out incase this issue comes up again. My colleague was able to get a license from a reseller of the old application.
Yes I verified that it was RAID 1 through the RAID controller. I may try undionly.kkpxe. Basically it pulled the image fine into FOG, but when I push the image to a Test system it Blue Screens with INACCESSIBLE_BOOT_DEVICE.
We have a situation where a system that is using a RAID 1 is on it’s lst leg. We have backups of the system but we were wanting to grab an image of it to use for some testing. It is an old system and there is software on it that we no longer have the install media or license key for and are unable to locate the license key even through the company that we purchased it from all those years ago.
I tried booting to FOG from the machine but it was having issues getting the undionly.kpxe, so I pulled the drive out and connected it to another machine and was able to get FOG to Image it, but it appears that due to it being in a RAID it is looking for either the RAID Card or the other drive.
Anyone have any experience pulling an image from a RAIDed machine?
Thanks!
need2 was correct. I tried on some newer systems and it boots properly. My Test machine is older and we only have about 10 in production so I am okay with it not working on those systems till we get them replaced. On our newest systems Dell Optiplex 9020, when it gets to the point where is was trying to go to the DHCP server for the default.ipxe file, it asks for the TFTP server IP. Once I put that in it boots to Fog normally.
I am good with the state I have it right now and will inquire about changing the DHCP options with the Vendor and my Boss.
I checked the only active DHCP server and neither option 66 or option 67 are checked/enabled. I will talk to the vendor that handles our Network to see if there is anywhere else this might be set up.
From need2’s comment it looks like I might just need to have Option 66 set. I was really hoping to not have to touch the DHCP server as I am new to this company and don’t want to push my boundries yet.
Forgot the Destination MAC. It is 78:45:C4:3D:8F:E7
Here is the issue.pcap. I will transfer it to my Windows box and look at it with Wireshark, but figured you guys would find stuff faster than I. Changed extension to .txt since it wouldn’t let me upload .pcap or .tar.gz
[url=“/_imported_xf_attachments/1/1972_issue.txt?:”]issue.txt[/url]