Apt-get update error "Unable to locate package apt-transport-https"

Ah gotcha now,

I got the following section after I did the ls command:

handle_packet: type = 5
handle_packet_missing_direct: token 17, name /mnt/Videos, request pid 13419
attempting to mount entry /mnt/Videos
lookup_mount: lookup(file): looking up /mnt/Videos
lookup_mount: lookup(file): /mnt/Videos → -fstype=cifs,rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0 ://192.168.1.223/Videos
parse_mount: parse(sun): expanded entry: -fstype=cifs,rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0 ://192.168.1.223/Videos
parse_mount: parse(sun): gathered options: fstype=cifs,rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0
parse_mount: parse(sun): dequote(“://192.168.1.223/Videos”) → ://192.168.1.223/Videos
parse_mount: parse(sun): core of entry: options=fstype=cifs,rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0, loc=://192.168.1.223/Videos
sun_mount: parse(sun): mounting root /mnt/Videos, mountpoint /mnt/Videos, what //192.168.1.223/Videos, fstype cifs, options rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0
do_mount: //192.168.1.223/Videos /mnt/Videos type cifs options rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0 using module generic
mount_mount: mount(generic): calling mkdir_path /mnt/Videos
mount_mount: mount(generic): calling mount -t cifs -s -o rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc,vers=3.0 //192.168.1.223/Videos /mnt/Videos
spawn_mount: mtab link detected, passing -n to mount

mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount(generic): failed to mount //192.168.1.223/Videos (type cifs) on /mnt/Videos
dev_ioctl_send_fail: token = 17
failed to mount /mnt/Videos
st_expire: state 1 path /-
expire_proc: exp_proc = 3061840704 path /-
expire_cleanup: got thid 3061840704 path /- stat 0
expire_cleanup: sigchld: exp 3061840704 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
^Cdo_notify_state: signal 2
master_notify_state_change: sig 2 switching /- from 1 to 5
st_prepare_shutdown: state 1 path /-
expire_proc: exp_proc = 3060792128 path /-
expire_cleanup: got thid 3060792128 path /- stat 0
expire_cleanup: sigchld: exp 3060792128 finished, switching from 5 to 7
st_shutdown: state 5 path /-
umount_multi: path /mnt/Logs/ incl 0
umounted direct mount /mnt/Logs/
umount_multi: path /mnt/Videos incl 0
umounted direct mount /mnt/Videos
automount_path_to_fifo: fifo name /var/run/autofs.fifo–
shut down path /-
autofs stopped

I guess the relevant comments are:

mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount(generic): failed to mount //192.168.1.223/Videos (type cifs) on /mnt/Videos
dev_ioctl_send_fail: token = 17

dmesg | tail
[10066.976401] CIFS VFS: Unknown vers= option specified: 3.0
[10347.928907] CIFS VFS: Unknown vers= option specified: 3.0
[10619.224942] CIFS VFS: Unknown vers= option specified: 3.0
[10761.398234] CIFS VFS: Unknown vers= option specified: 3.0
[10849.962320] CIFS VFS: Unknown vers= option specified: 3.0
[12714.751825] CIFS VFS: Unknown vers= option specified: 3.0
[12719.450546] CIFS VFS: Unknown vers= option specified: 3.0
[12847.777624] CIFS VFS: Unknown vers= option specified: 3.0
[12849.713573] CIFS VFS: Unknown vers= option specified: 3.0
[19256.097942] CIFS VFS: Unknown vers= option specified: 3.0

Found this page https://forums.developer.nvidia.com/t/mount-network-folder-samba-cifs/70922/12

Is it possible that version 3.0 is not installed in the kernel? (forgive me if I don’t make sense but my Linux experience is very limited)

The strange thing is that Samba is working on version 3.0 (Windows 10) so it must support it in some way.

Regards,

fbagnato

Yes most likely Kernel to old.
But you might be able to use SMB2. BTW I don’t think that this will have the magic performance improve.
You could try to replace vers=3.0 with vers=2.0 but not sure if that option actually exist. Or you can try without vers=3.0

From https://wiki.samba.org/index.php/SMB3_kernel_status

The minimum version for use of the Linux kernel SMB3 support is kernel version 3.12

The Apple Box is uname -r 4.2.3-25-osmc

So it should support it.

You could try to replace vers=3.0 with vers=2.0 but not sure if that option actually exist. Or you can try without vers=3.0

No, neither works…

Is there anything I can do to get autofs working?

From https://forums.developer.nvidia.com/t/mount-network-folder-samba-cifs/70922/12

gunzip -c /proc/config.gz | grep CONFIG_CIFS_SMB2

Or in my case

gunzip -c /proc/config.gz | grep CONFIG_CIFS_SMB3

These commands do not work in my environment.

Is there a command I can do on the OSMC box that would confirm that the kernel does not have SMB3 support?

Regards,

fbagnato

The unzipped kernel config should be (at least is on the current Vero) at /boot/configxxxxx

Thanks,

I found the line:

CONFIG_CIFS_SMB2 is not set

There is no # CONFIG_CIFS_SMB3 entry.

If I uncomment the # CONFIG_CIFS_SMB2 is not set and change it to

CONFIG_CIFS_SMB2=y

and add CONFIG_CIFS_SMB3=y

Will that invoke a change?

Regards,

fbagnato

No, that file just show you how the current kernel was configured at the time of compiling.
So currently in that file CONFIG_CIFS_SMB2=y is #CONFIG_CIFS_SMB2=y? if so then no chance to mount via autofs

No it is: # CONFIG_CIFS_SMB2 is not set

And there’s no # CONFIG_CIFS_SMB3 entry at all

So I cannot use autofs…that is what your saying.

What about fstab, can I use that to mount the Windows shares?

Regards,

fbagnato

No Autofs and fstab both use the kernel driver (that’s the reason why they are more performant). So if the kernel is not configured with SMB2 you can not use them.

OK, at least I know now.

Can I compile the kernel on OSMC to include SMB3 support?

Are the sources included on the OSMC box?

Regards,

fbagnato

You would need to grab old sources and build.

Hi Sam,

Where would I find the old sources to OSMC?

I looked in /usr/src/ but it is empty.

Regards,

fbagnato

Rather than messing with building a kernel you might want to just enable SMBv1 in Windows to see how much of a difference a system mount makes in the first place. There’s also the option of installing software on your Windows box that provides NFS server functions and use NFS instead of SMB.

It also just dawned on me that another downside to being stuck on such an old version of Kodi is a lack of updates to the scrapers. At some point you might have to generate nfo files just to add in new content.

You can find it on GitHub with the rest of the sources.

Hello darwindesign,

Sorry for the late reply, I had to attend to some matters.

Rather than messing with building a kernel you might want to just enable SMBv1 in Windows to see how much of a difference a system mount makes in the first place.

This was a great suggestion. I installed SMB1 support in Windows 10 and my shares are now showing.

I added the videos library and this time it wasn’t rebooting like it was with Samba shares.

There’s also the option of installing software on your Windows box that provides NFS server functions and use NFS instead of SMB.

I know native NFS support is included in Windows 10 Pro and above but not Home (which is what my laptop with the shares is running).

There also seems to be some NFS apps that might run on Windows 10 Home, such as FreeNFS (Freeware), Allegro NFS Server for Windows (Commercial), etc.

@darwindesign you were right about the addons. I tried about 20 addons and found a lot of incompatibility problems. The 2 major ones were that:

  1. Kodi Widevine is not supported in OSMC (needs Kodi 18 and up). A lot of the addons needed Widevine Support to function (like a lot of the streaming services).

  2. Almost 100% of the time if I left InputStream Adaptive turned on in the relevant addons that used it (it is turned on by default), opening a Live Streaming or On-Demand video file would cause a reboot of the Apple TV box.

Regards,

fbagnato

Hi Sam,

Ignore my ignorance, but can you provide a link to the Github page that has the 2017.08-1- Apple TV kernel sources.

I looked around but am not familiar with Github and I couldn’t find it.

Regards,

fbagnato

@sam_nazarko @fzinken @darwindesign

I want to thank the 3 of you for your help again.

I thought it was over when you guys helped me fix up the Samba shares but I think I will be out of your hair for now.

The box has been pretty well setup (as best as it can be).

I have learnt more about Linux because of your help.

Regards,

fbagnato

Be aware that Windows might automatically disable that in the future which will require you to enable it again.

Pro can do NFS client but you have to have Windows Server to get NFS server options from Microsoft. I think there is a workaround by using WSL to spin up a VM and then use that to provide the share but i’ve never tried it. I know there is a few people around here that run haneWIN to provide this service.

You welcome.

Hi darwindesign,

Be aware that Windows might automatically disable that in the future which will require you to enable it again.

Thanks. Will remember this.

Pro can do NFS client but you have to have Windows Server to get NFS server options from Microsoft. I think there is a workaround by using WSL to spin up a VM and then use that to provide the share but i’ve never tried it. I know there is a few people around here that run haneWIN to provide this service.

My new computer which is still sitting in many boxes (awaiting some spare time to assemble it…sigh) will be running Linux/Windows 10 dual boot and WSL will be looked into.

Had never heard of haneWIN. Just had a look at it.

Regards,

fbagnato

I’ve used HaneWIN NFS server for years, and it works well. It’s shareware, but free to evaluate.

Hello angry.sardine,

Thanks for you post.

I will take a look at it.

Regards,

fbagnato