I’m an OSMC newbie with a very shallow knowledge of Linux. I just got an RPi3 with noobs pre-installed (I bought a Canakit) and I’m working on getting the Pi set up to run OSMC. I’ve had a couple problems, and I’d appreciate any help I could get. Thanks in advance.
As background, I have NextPVR running on a Windows 10 computer as my “back end”. I have Kodi running on a Windows 7 laptop with the NextPVR client enabled and properly configured. I can see and play my recorded TV programs and videos that are stored on the Windows 10 PC from the Windows 7 laptop. I have “shared” certain directories on the Windows 10 computer and was able to browse to their locations on the Windows 7 PC when adding videos to it.
My objective with the Pi is to replace the laptop with it, thereby reclaiming my laptop for other uses.
Today I began trying to set up the Pi with this in mind. I booted the Pi up into noobs and connected to my wifi. I was presented with several operating system options, as expected. One of them was OSMC Pi2. That seemed like a problem to me since I’m running a Pi3, so I looked around for what to do. The best I could find was to create a bootable SD card from scratch and boot from it. I don’t have a spare SD card, and if I have to do that, I’ll get one and do it. In the meantime, I went ahead and chose OSMC Pi2. The result was an apparently successful installation of OSMC, but I’m wondering if I should have a different version installed, specific to the Pi3.
I enabled the NextPVR addon inside OSMC and configured it to access the backend by entering appropriate configuration information. As a result, I can watch live and previously-recorded TV, I can see all the channel logos and channel guide, almost exactly like they appear on the Windows 7 PC. Live TV is a bit choppy at times, and I understand I need to install the two codecs available from the Raspberry Pi Foundation. I found the serial number on my Pi and I’ll soon order the codecs.
Now I’m trying to access other (not recorded TV) videos I have stored on the Windows 10 computer. I go to “Add Videos” and try to browse to their location, but I can’t. The Windows 10 shares don’t appear as they did on the Windows 7 laptop. I also try to navigate directly to the directories containing the videos by entering either smb:\192.168.1.66\Recorded TV or smb:\LACROSSE\Recorded TV as I had done on the Windows 7 laptop (LaCrosse is the name of my Windows 10 computer, and 192.168.1.66 is it’s IP address on my network.) No joy. OSMC seems to accept the path and asks me to give the source a name. I do that, but it just keeps asking me for a name after I’ve entered one. I have read here that there is a problem with samba and I have to use a different approach to access the shares, but I can’t figure out what to do; it’s probably due to my lack of Linux skills. Or perhaps I simply need to install samba from the app store? I have not done that.
Can anyone help me access my shared videos? Do I have the wrong version of OSMC installed on my Pi3?
I would recommended using fstab mounted shares, rather than the kodi shares; as you will no longer have these browsing issues and should get better throughput.
Thank you, Tom. I’ll try your suggestion, but just a couple more questions, please.
As I said, my knowledge of Linux is shallow. I don’t use a username or password to access my shared folders. I’ve shared them with “everyone” via Windows 10. Is there something I need to do in Windows to set this up? Can I omit the username and password in your tutorial?
I have not set a root password on the Pi. Is sudo going to ask for one?
While standing by about the username and password question, perhaps I should mention a couple other points.
First, I went ahead and enabled the smb addon from the app store. I then proceeded to try to add the directory containing my videos. I got to the point where I selected “browse” and saw the “Windows (SMB)” option available. I selected that and after a couple seconds, OSMC returned nothing. Evidently it found no SMB shares, even though I know the files are there and I’ve shared them with another Windows device.
Also, while we’re at it, can someone confirm that I haven’t goofed up by selecting the Pi2 (instead of Pi3) option while in noobs?
Pi2 and Pi3 use the same image, so no worries there.
Samba install from the store is to share your pi3s files to a windows computer. Say you got an usb disc connected to the pi3 with alot of media on it and you wanted to view it from your windows machine or add to it, then samba from the store makes it posible.
Whenit comes to pi3 as smb-client I’d go for the fstab option.
As Joakim_Sandstrom has stated the samba app in the osmc store, is for sharing files from the pi; not for accessing shares on other network devices.
As for adding shares via browse, Windows SMB; doesn’t working unless you change the smb protocol to smbv1 (but this ins’t considered very secure) You can find this option under settings, services smb client. Alternatively you can specify the path manually, you should be ok just to copy the path used by kodi on the windows 7 pc.
As for fstab just to clarify bmillham’s post, the example from his guide using guest instead looks like this:
I don’t think Win10 allows anonymous (guest) ie passwordless access without a registry hack. ‘Everyone’ means anybody with a login on the server, so you will have to use your own login or create a new user just to access the shares.
I don’t think Win10 allows anonymous (guest) ie passwordless access without a registry hack. ‘Everyone’ means anybody with a login on the server, so you will have to use your own login or create a new user just to access the shares.
I’m not exactly sure what this means, but right now I’m accessing my shared files on the Windows 10 machine from my Windows 7 laptop. My laptop has a username but no password. Maybe this is just one of those “Windows” things; i.e., you need a “proper” login to get files to Linux but not to another Windows machine.
I will try the “guest” approach. If that doesn’t work, I’ll create a username and password on the Windows 10 computer for use by Pi3 running OSMC. Then I’ll report back my results.
I couldn’t make either approach work. I think I’m having some syntax issues with Linux. But, for what it’s worth, there is currently only one line in the /etc/fstab file. So the line I added was line 2. I copied exactly the guest line Tom provided above, then typed:
sudo mount -a
I got the following response:
mount: /etc/fstab: parse error at line 2 – ignored
mount: mount point 0 does not exist
Then I added an account for kodi’s use to my Windows 10 machine and entered those details into line 2 in /etc/fstab (there are now 3 lines, with the second one continuing using the "" character)/
I then typed, as before sudo mount -a, and got exactly the same response.
For reference, this is exactly what I put in lines 2 and 3 of my /etc/fstab file (my shared folder name has spaces):
Obviously something is wrong with the way I’m creating the mount point, but my very shallow knowledge of Linux prevents me from figuring out what to do.
Again, any help is appreciated. Apologies for my lack of Linux knowledge.
This indicates a problem with your fstab file. Exactly how are you editing the file? And is your username really kodi with space? That’s how it looks to be from what you copied.
Tell us this, what is the share you are mounting? It is “Other TV Shows” and you want it mounted as “LaCrosse TV Shows”?
What is the username and password, I find it hard to believe they are what you have in the fstab. (Don’t share the password, just confirm if it has spaces in it)
My username is kodi. The password is abc123_kodi (not the real password, but it has numbers, letters, and an underscore in it. (The “with space” stuff appeared in the document I was reading and I thought I needed to copy it exactly. Clearly that was wrong.)
The share I’m trying to mount is Other TV Shows. It’s a folder on the Windows 10 machine located at G:\Other TV Shows. I want to call it LaCrosse_Other TV Shows on OSMC. LaCrosse is the name I gave to the Windows 10 machine.
Again, thanks very much or your quick and helpful responses.