[19:59] <Stumped25> Hey folks, I need help with an issue. I'm trying to set a mount point for my NAS server in .wine, so I can access my Nas inside programs running in wine. For example, I have a ton of DAZ studio assets that I store on my NAS. I can access the nas in Thunar with no issue, but can't from inside wine. I've tried mounting it to the wine Z: drive, I've
[19:59] <Stumped25> installed cifs utils, Samba, running Samba 4.17, & tried running the following, "sudo mount -t cifs -o username=chris, //192.168.88.244/sharename /media/Data/" as Data was the only file under the z:/media folder, but I keep getting the following error "mount error(22): Invalid argument
[19:59] <Stumped25> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)" I've tried adding "ver 1.0" as well as the same through 4.0 to push it, but it just won't budge. Any ideas?
[20:00] <Eickmeyer> !morehelp | Stumped25
[20:02] <Eickmeyer> You might also try #xubuntu since it looks like you're in xfce, implying Ubuntu Studio 20.04
[20:03] <Eickmeyer> But, you're trying some advanced networking stuff, so not likely to find help in here.
[20:04] <Stumped25> valid. I appreciate that thanks
[20:05] <Stumped25> Hey, Eickmeyer[m], your user name looks like the last name of someone I know & it's fairly uncommon, forgive me for asking, but is your first name by any chance Ray?
[20:05] <Eickmeyer> I have a cousin named Ray.
[20:05] <Stumped25> in Washington State? If so, I think I know your cousin
[20:06] <Eickmeyer> Yep, Chelan.
[20:06] <Stumped25> Heh, Small world
[20:06] <Eickmeyer> Nice.
[20:07] <Stumped25> Back in the late 90s & early 2000's we used to be part of the same small circle of church groups, mostly connected through Ross Point camp & the Exodus Bible study group we had. Next time you see or talk to him, tell him Chris from Spokane said hey.
[20:41] <arraybolt3> Slappy: You're Christian? Awesome, never thought I'd run into another brother in Christ in the Ubuntu Studio channel!
[20:52] <Eickmeyer> Slappy: Will do!
[20:52] <Eickmeyer> arraybolt3: Also a brother in Christ.
[20:53] <Slappy> Nice. good to hear man.
[20:53]  * Iamthehuman12 is Xian too
[20:53] <arraybolt3> Seriously?! Wow. That's really cool. God bless, and thanks for the awesome OS!
[20:53] <Eickmeyer> arraybolt3: heh, I'm doing my best.
[20:54] <Slappy> Ah are you the guy who made Ubuntu studio?
[20:54] <Eickmeyer> Actually, doing church audio/video for 28 years is what broght me to working on Studio in the first place. I'll be publishing a blog post on it soon.
[20:54] <arraybolt3> Slappy: Yep, this is Eickmeyer's doing.
[20:54] <arraybolt3> And it's awesome.
[20:54] <Iamthehuman12> mmm... after reinstalling everything (Win 11 & US) and only then hooking the new replacement dock from Lenovo and upgrading its firmware and the system really seems to be working. to celebrate this I've been cleaning my flat
[20:54] <Eickmeyer> I didn't make it, but I am continuing it.
[20:55] <Eickmeyer> Picked it up in 2018.
[20:55] <arraybolt3> Eickmeyer: I actually intended to do Christian music recording and lyric videos, and that's how my journey into Linux started. KXStudio 14.04 was my first distro, loaded into VBox, and the rest is history.
[20:55] <arraybolt3> I still have yet to get anything recorded, but it's definitely on the to-do list.
[20:56] <Slappy> Nice. Well hey man, Got a question for you, maybe you can help on this end. Any way to configure the OS to run DAZ Studio natively? For clarity, DAZ Studio is kinda like Blendr
[20:56] <arraybolt3> Hmm, never heard of it. Lemme look it up...
[20:56] <Eickmeyer> I'm working in ${DAYJOB} at the moment, so, unfortuantely, I can't answer too many questions right now.
[20:59] <arraybolt3> Slappy: I assume you've already tried Wine for running DAZ Studio?
[21:00] <Iamthehuman12> Eickmeyer: I really enjoy this one streaming free church on Sundays .. it is on at 11:30 Sundays so I can make it to the evangelical lutheran mass at 10:00, greet friends in the park and still have plenty of time to get home to watch the streaming one. Or often, stayed up too late to go to ev. lut., but not too late to miss the streaming church. Maximum respect to the church AV crews!
[21:01] <arraybolt3> Slappy: Looks like this is what you're looking for: https://www.daz3d.com/forums/discussion/60901/daz-studio-and-linux/p47
[21:01] <Slappy> YEah. I mean I'm able to get it to run, no sweat there. It's just all my daz assets are all on my nas. The idea was, in daz, I'd just create a new base directory in DAZ connecting to my file with all my assets on my NAS, so that I could just pull the assets straight from my nas, As this laptop only has 250 GB & the file on my nas is over 800 GB
[21:02] <arraybolt3> Iamthehuman12: That's so cool! I'll definitely have to remember that in the event I ever do AV stuff at a church. I ran a lyrics projector once, it was fun.
[21:02] <Iamthehuman12> Always a good time to sing praise to the Lord
[21:02] <arraybolt3> Slappy: Can't you just mount your NAS to a directory on your system, then navigate to it from within DAZ using the Z: drive in Wine?
[21:03] <arraybolt3> Iamthehuman12: Amen!
[21:03] <Slappy> That's what I've been trying to do. Worked great on my mint machine, but for some reason, isn't working on this or my other studio machines
[21:04] <arraybolt3> And the NAS is accessible from within Linux, but not from DAZ?
[21:04] <Slappy> So lemme run what I've done so far by you, see what your thoughts are
[21:04] <Slappy> EXACTLY
[21:04] <Slappy> In Thunar, it's already right there. No sweat
[21:05] <Slappy> So if I'm just going straight from linux to the NAS, no issues. It's right there under networks. But when I go under the wine environment in .wine, it's like a brick wall
[21:06] <arraybolt3> Slappy: OK, well, maybe Wine is having some problem with how the NAS is mounted. What protocol are you using? NFS? SFTP? (I'm not too familiar with this stuff, but I've gotten SFTP up and running between a laptop and a Pi once.)
[21:06] <Slappy> So here's what I've done so far. I installed Cifs untils, I've installed Samba, running samba 4.17
[21:07] <Slappy> Well the share is an SMB share, but I have SMB, AFP, NFS, FTP & iSCSI all turned on in TrueNAS
[21:08] <arraybolt3> OK. I can already find stuff about problems with accessing SMB shares in Wine with some searching.
[21:09] <Slappy> So, in .wine/dosdevices/media/ The only file in there was Data right? So I tried using that frist, So I ran "sudo mount -t cifs -o username=chris //192.168.88.244/sharename /mnt/share/NAS" & got "mount error(2): No such file or directory
[21:09] <Slappy> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)"
[21:10] <Slappy> So I then did "Mkdir /mnt/share/NAS" right? Tried the same command, pointing it this time to mnt/share/NAS instead of media/Data
[21:10] <Slappy> Same error.
[21:11] <Slappy> So I went into winecfg, tried mapping to that spot directly & setting it as a network drive, even tried switching compatibility from win 10 to win 7, now getting "mount error(22): Invalid argument
[21:11] <Slappy> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)"
[21:12] <Slappy> Also tried adding the "ver 1.0" as well as 2.0, 3.0, etc... No dice
[21:12] <arraybolt3> That sounds like the problem is in mount, not Wine. You're trying to do the mount *within* Wine? Like, are you using the Wine terminal to do the mount, or are you in the Wineprefix in a Linux terminal and trying to do the mount? Or...?
[21:12] <arraybolt3> Back in 2010, this worked for someone: "Mount that share with SAMBA, point Wine to mount point with winecfg (add a drive and point to mount). Tell your program to use local disk instead of remote share."
[21:13] <arraybolt3> Got that from https://forum.winehq.org/viewtopic.php?t=7838
[21:13] <Slappy> hmmm... lemme give it a look
[21:13] <Slappy> but yeah, I'm trying to make the mount within wine
[21:14] <Slappy> well within /home/chris/.wine/dosdevices/z: to be precise
[21:14] <arraybolt3> Slappy: Maybe the symbolic link is messing you up (I think z: is just a symbolic link to /)
[21:15] <arraybolt3> Slappy: I'd just open a Linux terminal, do "cd /", "mkdir /mnt/share/NAS", "sudo mount (big complicated thingy here)", then it should be accessible within wine from the Z: drive automatically. You don't need to be in Z: for it to be visible in Z:.
[21:16] <Slappy> Yes, z: was initially routed to /. I tried changing the route path in Winecfg, but that's where the error 22 started
[21:16] <Slappy> Ok lemme try that. So lemme get a bit of clarity
[21:17] <Slappy> So I cd to /, then mount the NAS share there?
[21:17] <arraybolt3> Slappy: OK, hold on. Start over.
[21:17] <arraybolt3> Slappy: First, make Z: point to / again.
[21:17] <Slappy> copy
[21:17] <arraybolt3> Slappy: Then, in a Linux terminal, do "cd /" to make sure you're not in any symbolic link mess.
[21:18] <arraybolt3> Slappy: Now, make the directory you want to mount the SAMBA share to (i.e., mkdir /mnt/share/NAS)
[21:18] <arraybolt3> Slappy: Now mount the SAMBA share in the new directory.
[21:18] <arraybolt3> Slappy: Now DAZ Studio should be able to find your SAMBA share under Z:\mnt\share\NAS
[21:18] <Slappy> Ok trying that now
[21:21] <Slappy> Ok so I have /mnt/share/NAS under /
[21:22] <Slappy> Now is this the correct command to mount the SAMBA share to /mnt/share/NAS? "sudo mount -t cifs -o username=chris,vers=4.13.17 //192.168.88.244/sharename /mnt/share/NAS"
[21:23] <arraybolt3> It *looks* right, but I don't know for sure.
[21:23] <arraybolt3> You might need a password in there.
[21:23] <Slappy> mount error(22): Invalid argument
[21:23] <Slappy> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
[21:23] <arraybolt3> https://askubuntu.com/questions/101029/how-do-i-mount-a-cifs-share
[21:23] <Slappy> Well it prompts me for a password, then after entering it, it gives me that error
[21:24] <arraybolt3> Can you remove the "vers=4.13.17" bit?
[21:25] <Slappy> OOO didn't even see that, thanks
[21:27] <arraybolt3> (That's the only thing I can see that looks iffy about the command line, and "invalid argument" means that mount can't figure out what you're telling it to do, so I figure maybe that's making it grumpy.)
[21:31] <Slappy> Ok so I ran "sudo mount -t cifs -o username=chris,password=redacted //192.168.xxx.xxx/shares /mnt/share/NAS" Now it's back to giving the no such file or directory error. But I clearly did create the mountpoint
[21:32] <Slappy> Obviously the password & IP I actually typed were the actual ones
[21:33] <arraybolt3> Are you messing up the share name? Mount is now accepting your command, but probably can't find the "shares" you're trying to mount. Maybe check your TrueNAS settings to find out what the share name is.
[21:34] <arraybolt3> Slappy: You might also want to make sure that the NAS server and your computer can talk to each other. You're able to access the share in ways other than the mount command, right?
[21:34] <Slappy> ohhhhhhh I was putting the routepath of the mount I created in linux.
[21:35] <Slappy> So in linux, the mount point is /mnt/share/NAS. hmm.. well the share name is correct, but when I log into the web interface, I do have to log in as root
[21:37] <arraybolt3> Hmm. And mount didn's like that vers argument you were giving it. In the "vers=" argument, can you change "4.13.17" to just "4.13" and try it again?
[21:38] <arraybolt3> Like "sudo mount -t cifs -o username=chris,password=redacted,vers=4.13 //192.168.xxx.xxx/shares /mnt/share/NAS"
[21:39] <Slappy> might be worth a shot
[21:39] <Slappy> btw, so here's some data from the NAS end
[21:41] <Slappy> https://snipboard.io/kCOhng.jpg
[21:43] <Slappy> https://snipboard.io/iw0IRj.jpg
[21:44] <arraybolt3> Try plopping "--verbose" right before the "-o", copy it into a text document, redact anything sensitive, then pastebin it and let me see. I might be able to figure out where its getting hung up.
[21:44] <arraybolt3> (OK, that was ambiguous. Put "--verbose" before the "-o" in the mount command, run it, and redact and pastebin the output.)
[21:46] <Slappy> Will do, btw, I tried adding the "ver 4.13" & even just 4.0, got the invalid argument erros again
[21:47] <arraybolt3> Yeah, it looks like they removed the "vers" argument from SAMBA if I'm interpreting the man page I found properly.
[21:47] <arraybolt3> Er, from mount.cifs, I mean.
[21:48] <Slappy> ok so try this then? "sudo mount -t cifs --verbose -o username=chris, //192.168.88.244/sharename /mnt/share/NAS"
[21:49] <Slappy> ok so try this then? "sudo mount -t cifs --verbose -o username=chris, //192.168.xxx.xxx/sharename /mnt/share/NAS"
[21:50] <Slappy> Ok apprently there's no option for editing a post. Neat
[21:50] <arraybolt3> I believe so. Only, you have a spurious comma after the "chris".
[21:52] <Slappy> ok
[21:52] <arraybolt3> (Yeah, IRC is sorta "better make sure you wanna sned tht befr you ht entr].
[21:53] <Slappy> mount.cifs kernel mount options: ip=192.168.88.244,unc=\\192.168.88.244\sharename,user=chris,pass=********
[21:53] <Slappy> mount error(2): No such file or directory
[21:53] <Slappy> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
[21:53] <Slappy> Wow.... So verbose....
[21:53] <Slappy> lol
[21:53] <Slappy> apparently it ignored the verbose tag
[21:54] <arraybolt3> Wow, no clue then. That's so weird. Maybe try NFS and see if things go better.
[21:56] <Slappy> no clue even how to do that. lol
[21:57] <arraybolt3> Slappy: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_file_systems/mounting-nfs-shares_managing-file-systems
[22:00] <Slappy> whooo. Darn near had a stroke just skimming it over. lol
[22:00] <arraybolt3> Didn't realize it was so in-depth - the important part is probably at section 3.7.
[22:01] <Slappy> I'll give it a shot. I'd LIKE to get it working on Studio, Especially now that I know the guy manning it is my old buddy Ray's cousin
[22:01] <arraybolt3> I wonder if using a newer version of TrueNAS or Ubuntu Studio would shake things into working? You could boot an Ubuntu Studio Jammy Jellyfish live USB and see if you can mount the CIFS share there.
[22:12] <Slappy> Wait, it was updated to Jammy? Well crud, yeah that's a good starting point. lol. I thought it was still on the 20.04 platform, since I recently DLed it from distrowatch, though in hindsight, It WAS a couple months ago at least now that I think of it
[22:13] <Slappy> Ok so I'm trying it on the NFS side, though I'm not clear on some of the language. "options
[22:13] <Slappy>     A comma-delimited list of mount options." Not quite clear on what that menas
[22:15] <Slappy> Oh I think I figured it out
[22:15] <Slappy> the mount options type I mean
[22:15] <arraybolt3> Yeah, Jammy is released, and Kinetic is in the works.
[22:21] <Slappy> Ah I just realized, NFS wont work because I haven't actually created NFS shares on the server side, only enabled the NFS service. The only share is an SMB one, so I think I'm stuck with making it work on SMB
[22:22] <Slappy> & sadly, I reached out for help in the #samba channel close to an hour ago, Not a single response
[22:23] <Slappy> Not sure if they don't actually pay attention to the chat there, or if it's just another elitist server that ignores everyone, (ton's of those I've found), either way though, it's rough
[22:51] <Slappy> Hey arraybolt3 Got more info. So Here's a pastebin I got from dmesg
[22:51] <Slappy> https://pastebin.com/hTSFWvbH
[22:52] <Slappy> I followed the steps in this video https://www.youtube.com/watch?v=v2WMnZoiGog
[22:53] <Slappy> When I did sudo mount -a, it gave me error 22, so I did dmesg, apparently it's claiming that the host location is a bad address, but in dmesg, it lists my IP/sharename, but I listed it as ip/chris, which is the actual sharename