jrhodes1 Trusted Contributor.
Trusted Contributor.
1476 views

2017 U4 imaging not working

Hi

I have just updated to 2017 update 4 and imaging is not working I get this error “Encountered a bad control data during image restoration. Check if tuxera is present.”

When I try to apply the Tuxera driver I get the following error “Checksum of the uploaded Tuxera NTFS driver file does not match with the expected checksum in the NTFSDriver.conf file.”

Has anyone got any ideas what I need to do? I have been trying to see if there is a newer imaging driver update but cannot seem to find one.

Any information will be very much appreciated,

Thanks,

John
Labels (1)
0 Likes
28 Replies
Micro Focus Expert
Micro Focus Expert

Re: 2017 U4 imaging not working

Did you download the newest Tuxeria Driver again before uploading?
Each Tuxera Driver is needs to match the imaging driver versins, since the Tuxera driver has to be in synch with the Linux Kernel.
0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

Yes I have downloaded and applied the tntfs.zip from the “Go Here” link on the preboot services > Tuxera High Performance NTFS Driver Integration Settings page, I have done this multiple times and I have made sure the file is not renamed.

I have just tried it again now and this time I did not get the Checksum error when applying tntfs.zip, however when I try to restore an image I am still getting this error

“Encountered a bad control data during image restoration. Check if tuxera is present.”

Is there a newer/different version of the tntfs.zip file I should be using? The download link in preboot services is https://tuxera.com/download/novell/zenworks/4.4.73-5-default_2/tntfs.zip

Thanks,

John
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

Jrhodes,
> Is there a newer/different version of the tntfs.zip file I should be
> using? The download link in preboot services is
> https://tuxera.com/download/novell/zenworks/4.4.73-5-default_2/tntfs.zip


That is what I have, but have you verified that your imaging server indeed
has the updated file in /stv/tftp?

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

The files do appear to be in my Novell\ZENworks\share\tftp\17.4.0 not /stv/tftp I assume that is for Linux our server is a Windows server 2016 not sure how to check they are the correct ones as I cannot open them and there is no version number that I can find
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: 2017 U4 imaging not working

You can compare some of the time stamps....

There is one GOTCHA that can get you....

After you hit OK to Upload the TNTFS ZIP file......
You need to scroll to the bottom of the page and hit OK.

That trips up folks left and right.....
0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

I have tried different combinations of pressing the buttons I have tried just pressing the “OK” button at the bottom, I have clicking “Apply” and then “OK”, I have just pressed “Apply”. The only button I have not tried yet is “Reset” not sure what it fully does so did not want to press it just in case.

I have just tried it again but this time I downloaded the tntfs.zip file on my home computer to make sure that nothing was being cached anywhere and then I clicked the “Apply” then ”OK” buttons at the bottom but I am still getting “Encountered a bad control data during image restoration. Check if tuxera is present.”

I have also checked the times on the tntfs.ko files in Novell\ZENworks\share\tftp\17.4.0\x86_64 and Novell\ZENworks\share\tftp\17.4.0\x86 they both say 24/04/2019 00:31 which is around the time uploaded them.

I have even now uninstalled the antivirus and disabled the firewall on the server to make sure nothing is interfering with the imaging process.
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

Jrhodes,
> /stv/tftp I assume that is for Linux our server is a Windows server 2016


Nevertheless they should copy down to the machine yuu are imaging. Try
this:

PXE Boot
find / -name tntfs.ko
modinfo /path/tntfs.ko

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

i have tried this and when tryping find / -name tntfs.ko does not outout any information (not sur if it should or not) and with modinfo /path/tntfs.ko i get this error "modinfo: ERROR: Module /path/tntfs.ko not found."
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

Jrhodes,
> i have tried this and when tryping find / -name tntfs.ko does not outout
> any information (not sur if it should or not) and with modinfo
> /path/tntfs.ko i get this error "modinfo: ERROR: Module /path/tntfs.ko
> not found."


Does not sound that you have any tntfs.ko at all. All my imaging servers
are linux and on those the file should be in /srv/tftp. On windows:
%ZENWORKS_HOME%\share\tftp\

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

this is weird the tntfs.ko files are deffinatly in the following folders on my server Novell\ZENworks\share\tftp\17.4.0\x86 and Novell\ZENworks\share\tftp\17.4.0\x86_64 i have triple checked it
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

Jrhodes,
> this is weird the tntfs.ko files are deffinatly in the following folders
> on my server Novell\ZENworks\share\tftp\17.4.0\x86 and
> Novell\ZENworks\share\tftp\17.4.0\x86_64 i have triple checked it


But not present on the inaged workstateion after PXE booting? Are you sure
it is hitting the same imaging server you checked?


- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

We only have one Zenworks server so I cannot see it using another server.

What has happened recently is that we have just replaced/moved our zenworks server from Windows Server 2012 to Windows Server 2016. We mainly did the server replace because we have just moved from our old XenCenter virtual platform (with 8 year old servers that where getting a bit dodgy) to our new VMWare platform which is on our new blade server.

The new 2016 server has the same name and IP address of the old server which I know is no longer running as it is powered down and I disabled its network access so that it could not talk to the network if it accidently got turned on.

When I am PXE booting the test machines it says

ZENworks PreBoot Execution (PXE) Agent: v17.4.0
(C) Copyright 2008- 2019 Micro Focus or one of its affiliates.
Sending Queries to “the correct IP Address”

So as far as I know it should be contacting the correct server.
0 Likes
Knowledge Partner
Knowledge Partner

Re: 2017 U4 imaging not working

OK. But for some reason does it not receive tntfs.ko.

Alt-F2 on the imaged machine when you have selected "Manual
Maintenance" shows some info. In fact Alt-F1..F4 do.

Try yanking up the logging level of TFTP on the imaging server and see:
https://support.novell.com/Platform/Publishing/989/3418069_f.1.html

What I have seen a lot is that tntfs.ko never gets replicated to the
correct dir on the imaging server.

- Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jrhodes1 Trusted Contributor.
Trusted Contributor.

Re: 2017 U4 imaging not working

I have tired pressing F2 is there something specific I am looking for? I did see this whilst it was loading into maintenance mode

loading tftp://IP_ADDRESS/efi/x86_64/config -> /download/file_0000
error 68:
loading tftp://IP_ADDRESS/efi/x86_64/root -> /download/file_0001

also I tried gathering the logs it did come up with an error saying it

error: [Error 5] Access is denied: 'C:\\Users\\USERNAME\\AppData\\Local\\Temp\\5/zen-info\\conf\\loader\\AddPatchlinkAnalyzeReporting.xml'

is this normal? However I did get some info from it I think do trying to pick thought it

Thanks for the help
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.