@Sebastian-Roth Well I got it working. There was a problem with the hard drive in the PC. I changed it out and it works great. Sorry for wasting everyone’s time. Probably should have checked for the obvious. You did mention that the latest FOG Trunk is available as well as FOG 1.3.0, where can I download those? Does FOG 1.3.0 support UEFI booting and imaging?

Thanks again!

@Tom-Elliott
@george1421 after updating to the latest version the deployments to the NCR still fail. I am able to image PCs and laptops so I will just use a different solution for the NCRs and leave it at that. Thanks everyone for all of your help and assistance!

Thanks,

Anthony

@Tom-Elliott
@george1421 Thank you for clarifying. I am still getting the same error message when I try to update the client. Is there some where else this password could be messed? I did install the latest FOG update, so I am at 1.4.4. I will try a deployment and let you know if I have any success.

Thanks,

Anthony

@george1421 I confirmed the passwords and they do match. I can connect via a Windows FTP client, but when I run the update I still get the error listed below.

Thanks,

Anthony

@Sebastian-Roth
@Tom-Elliott

Yes before it freezes I am not able to switch. On another interesting note, I tried updating to the latest client and i get the error message below:

Could this be related?

Thanks,

Anthony

@Sebastian-Roth Correct. I am not able to switch when using CTRL-ALT-Fx.

@Sebastian-Roth Thanks! What is the key combination to switch VTY lines? I am unable to switch them using CTRL-ALT-Fx or any other combination of those keys.

Thanks!

@Sebastian-Roth Do you have a VT2 version for init_32.xe? I can only use the NCR and they are 32 bit.

@Sebastian-Roth “I think I have found part of it given this output. Please let me know.” I though that last output capture being blank may have been a problem, but you said all looks good to you. I am unable to switch between the VTYs.

Thanks,

Anthony

@Sebastian-Roth The deployments started freezing again with the new init.xz and the old one.

Below are the screen captures you requested:

ls -al Vertix
total 9526116
drwxrwxrwx 2 fog root 4096 Jun 15 11:07 .
drwxrwxrwx 11 fog root 4096 Jun 15 11:07 …
-rwxrwxrwx 1 root root 1 Jun 15 10:21 d1.fixed_size_partitions
-rwxrwxrwx 1 root root 512 Jun 15 10:21 d1.mbr
-rwxrwxrwx 1 root root 132 Jun 15 10:21 d1.minimum.partitions
-rwxrwxrwx 1 root root 15 Jun 15 10:21 d1.original.fstypes
-rwxrwxrwx 1 root root 0 Jun 15 10:21 d1.original.swapuuids
-rwxrwxrwx 1 root root 9754708186 Jun 15 11:07 d1p1.img
-rwxrwxrwx 1 root root 132 Jun 15 10:21 d1.partitions

cat /images/Vertix/d1.partitions
label: dos
label-id: 0x708be90c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 63, size= 78134424, type=7, bootable

cat /images/Vertix/d1.minimum.partitions
label: dos
label-id: 0x708be90c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 63, size= 24918072, type=7, bootable

cat /images/Vertix/d1.fixed_size_partitions

fogadmin@INC-FOG01:~$

I think I have found part of it given this output. Please let me know.

Thanks,

Anthony

@Sebastian-Roth Below is the screenshots from the fdisk -l

I will be running the tests shortly with old init.xz and will get back to you.

Thanks,

Anthony