This error indicates a problem extracting files into place on the target filesystem. Please attach a display and usb keyboard to the PXIe-8861. Log in as user admin. The password should be blank at this point. At the shell prompt try the following commands to provide more detail.
# nisafemodeversion # df -h # ls -l /tmp/* # tail /etc/natinst/share/log/installationStatus.log
If /etc/natinst/share/log/installationStatus.log does not exist, try tail /tmp/installationStatus.log instead.
What that shows us may point to a specific /tmp/install_*.log that will contain further information about the source of the failure.
Dear jwp200, thanks for your answer. However we don´t get a result of the "tail" command. Here is the screen:
Can you do the following:
1. Format the controller.
2. Attempt to install software.
3. Check to see if the installationStatus.log file now exists.
I tried this on a Linux target where the log file was missing and it has now been created. Not sure what removed it, as this is a target that gets reformatted regularly.
Can you confirm which version of LV you are using?
Personally I use FilleZilla to navigate the file system (enable sshd) as it allows me to download files more easily.
Siliconworker, thanks for running those commands and providing the results.
The /tmp contents indicates the target has been rebooted since the original failure you reported since no logs were present. Please reproduce the problem again as AustinManinTown suggested and then follow my same instructions as before. Make sure the keyboard and display are attached to the PXI prior to performing the installation from MAX
DO NOT enable SSH after the failure as was suggested by AustinManinTown, at least not from MAX. If you enable SSH on the target from MAX it will reboot the target and again the logs in /tmp that might have helped will be lost. If needed I can tell you how to enable SSH from the console without rebooting the target.
Dear AustinManinTown and JWP2000, thanks for further hints. After that I have found the "installationStatus.log" in two folders. Please see the screen photo, which lists also the file content.
Many thanks for your support. The problem has been solved by installation from another PC with very similar configuration (OS and LV). However we don´t see any reason, why the first PC caused the reported error.
The problem was caused by an additional ethernet PCI-card with "Realtek PCI GBE Family Controller" hardware and two different drivers found in Windows 10 or by online search. Now the RT-system runs with a Logilink ethernet USB-adapter without any difficulties.