Forum / NoMachine for Mac / NoMachine cannot connect remote hard disk
- This topic has 19 replies, 4 voices, and was last updated 3 years, 3 months ago by tsotne.
-
AuthorPosts
-
August 5, 2021 at 08:39 #34718lottolearnParticipant
Just looked like something relevant, sorry
This is the only other error really but it’s for unmounting, which after it fails it unmounts?
error11:21:21.176945-0500
kernel
System Policy: nxfs(11622) deny(1) file-unmount /System/Volumes/Data
This is the whole log file (attached), when I first try to mount it does everything but once it fails and I try to mount, it just has the two lines at then end displayed. It’s a bit long
Attachments:
August 5, 2021 at 08:43 #34725CarinParticipant@lottolearn The log file was long, so we have removed it from the thread and added it in the attachments.
August 5, 2021 at 12:06 #34729tsotneParticipantHi again,
I ran out of ideas, but it still seems like, nxfs is blocked and not loaded that’s why you see deny error log.
When you are connected to Mac, run:
sudo kextload -vvv /Library/Application\ Support/NoMachine/Extensions/nxfs.kext
And copy its output, if it gives any.
when I first try to mount it does everything but once it fails and I try to mount, it just has the two lines at then end displayed
What do you mean here? Did it work at least once?
August 5, 2021 at 16:46 #34736lottolearnParticipantHi,
I ran that and no luck — also for the last line confusion, I had pasted the log file but it was too long. I attached a word doc
I was basically talking about these lines
default11:21:20.696147-0500kernelnxfs: caller is not a member of nxfs admin group. Either add user (id=501) to group (id=0), or set correct ‘vfs.generic.nxfs.tunables.admin_group’ sysctl value.
error11:21:21.176945-0500kernelSystem Policy: nxfs(11622) deny(1) file-unmount /System/Volumes/Data
If you look at the log, the first time I try to attach the disk it takes a while and outputs all of that — then fails. Once I try to mount it again, it just throws the two lines posted above every time, not the whole startup that’s in the log
Also, running your command nothing was coming up in the console for some reason.
Attachments:
August 6, 2021 at 12:04 #34748tsotneParticipantHi,
yes I saw your logs. That’s because initialization is done only once in session, when you first tried to forward disk, so all corresponding lines are how MacOs handles and checks if it is able to run kext. Then when it is sure that kext is runnable nxfs is run when it is needed. That’s why you see only those two lines for the next attempts. But somehow according to that deny log your system still thinks it has no access. Also, you can check if you close the session and open a new one, when you will try forward disk you will still see the first initialization logs.
You can find the instructions on how to collect server-side logs here: https://knowledgebase.nomachine.com/DT11R00182 and upload it.
-
AuthorPosts
This topic was marked as solved, you can't post.