Hobbyist Toolkit
Cannot see mounted HDD in Raspberry PI 4
Solved!
I am not sure how to deal with this but I bet the reason you don't see it is because LabVIEW is installed in a separate chroot. The fact that you can see the hard drive from the Raspberry Pi OS does not mean it is available to the LabVIEW chroot. I would look into how to make the hard drive available to a chroot and maybe that will help you.
David is right. The LabVIEW system runs in its own schroot environment, which is basically a lightweight VM system for Linux. The "root" of said VM system is located inside a subdirectory of the host system and unless there is a specific mapping in the configuration file for the specific chroot environment, any process running inside the chroot has absolutely NO access to anything outside that root path!
That configuration makes for instance parts of the /dev/.. filesystem accessible to the chroot environment at the local /dev/... tree.
Some further explanation about this and a trick to access the host resources from the chroot environment over SSH: https://www.instructables.com/LabVIEW-Raspberry-Pi-SSH-Trick/
But it's also possible to add according file mappings to the labview chroot configuration script that is used to startup the chroot environment so that host system paths can be remapped to a path inside the chroot. Trying to mount host paths to the chroot can't work as the host path simply is not accessible inside the chroot unless it is specifically mapped as chroot alias during initialization of the chroot environment. Otherwise an important aspect of using chroot would be pretty much moot. The system is meant to isolate as much as possible whatever is running inside the chroot from the actual host system so that even rogue software could not harm the host system. NI doesn't really use it for this but in order to be able to install a Linux environment that is binary compatible to a single LabVIEW for ARM runtime system, without having to create a new LabVIEW for ARM runtime environment for every new Raspbian and BBB OS version.
This was not meant to solve your problem but give you an idea how the chroot file system is located inside the host file system. The host can access actual paths inside the chroot (but won’t see virtual paths that are mounted on startup of the chroot). The chroot environment can’t see paths outside of its own root at all unless they are mapped during startup to local paths.
