Using an old MAC Pro as a NAS and I need HELP!

Help and Support Vero 4K / Vero 4K +
45

NAS Exports set at:
Volumes/4TBshare1/Movies -network 192.168.40.0 -mask 255.255.255.0

Fstab set at:
192.168.40.164:/Volumes/4TBshare1/Movies /mnt/Server_Movies nfs noauto,x-systemd.automount 0

Vero gives:
osmc@osmc:~$ showmount -e 192.168.40.164
Export list for 192.168.40.164:
osmc@osmc:~$

NAS Exports set at:
Volumes/4TBshare1/Movies -network 192.168.40.164 -mask 255.255.255.0

Fstab set at:
192.168.40.164:/Volumes/4TBshare1/Movies /mnt/Server_Movies nfs noauto,x-systemd.automount 0

Vero gives:
osmc@osmc:~$ showmount -e 192.168.40.164
Export list for 192.168.40.164:
/Volumes/4TBshare1/Movies 192.168.40.164
osmc@osmc:~$
osmc@osmc:~$ mount -a -v
/mnt/Server_Movies : ignored

46

Ok, that bottom one is almost working but you need to change the export on the Mac to have the vero ip on it rather than the Mac ip

Don’t touch the fstab on the vero, the ip addresses are supposed to be different

47

NAS exports set to:
/Volumes/4TBshare1/Movies -network 192.168.40.84 -mask 255.255.255.0

Vero fstab set to:
192.168.40.164:/Volumes/4TBshare1/Movies /mnt/Server_Movies nfs noauto,x-systemd.automount 0

osmc@osmc:~$ cd /mnt/Server_Movies
-bash: cd: /mnt/Server_Movies: No such device

osmc@osmc:~$ mount -a -v
/mnt/Server_Movies : ignored

Rebooted devices after every change. NOW WHAT?

48

Is showmount still good?

Maybe try the mount command with just -a and not the -v too

It all looks good to me now

49

osmc@osmc:~$ mount -a
osmc@osmc:~$ showmount -e 192.168.40.164
Export list for 192.168.40.164:
/Volumes/4TBshare1/Movies 192.168.40.84
osmc@osmc:~$ cd /mnt/Server_Movies
-bash: cd: /mnt/Server_Movies: No such device
osmc@osmc:~$ cd /mnt
osmc@osmc:/mnt$ ls
Server_Movies ServerMovies
osmc@osmc:/mnt$ cd /mnt/ServerMovies
osmc@osmc:/mnt/ServerMovies$ ls
osmc@osmc:/mnt/ServerMovies$

50

Sorry, no idea, I don’t know why it’s not mounting. To me everything looks good.

I’ll see if I can bring a Mac home from work and play around and see if I can replicate this

51

Additional possible cause:

Re-imaged Vero with OSMC_TGT_vero3_20221101.img and initial setting to Estuary UI is not sticking.
What the heck else might be funky?? My files/folders set in FSTAB keep coming up blank!
Gonna try OSMC_TGT_vero3_20220918.img
Both images checked out with good MD5 hashes, still not sticking UI.
Wondering if I’ve killed my Vero with static??? Looking for the master reset button.
on it or ME ?!?!
Thanks for all your efforts!!

52

Hi,

I would try a different SD card, sounds like the vero4k hasn’t booted it.

Regards Tom.

53

FASCINATING! New SD card on a new Raspberry Pi 4k with the latest image for that platform (same MD5 hash check) gives SAME non-sticky Estuary UI.

Must be a bug! Other issues kinda point to the rights on the NAS MAC…

54

HI,

Looks like I misunderstood your last apologies. So on both vero4k & pi4 you are getting a fresh install, but changing the Estuary Skin is not being retained. What happens if after selecting the Estuary, you exit kodi rather than say power of system or reboot? Is Estuary then retained? If not could you please create a new topic with logs? As it does indeed sound like a bug.

I suspect this is the case. Unfortunately I think we are beyond the scope of OSMC support, I don’t think there are many here with experience of using a Mac as a NFS server.

Regards Tom.

55

Playing with this at work for you to try and replicate this with my setup, maybe my mount -a command was wrong or somehow conflicting with you mount options, that doesn’t seem to do anything for me when I try, can you instead try this on the Vero 4K:
sudo mount /mnt/Server_Movies

If I change the fstab to take out all the noauto,x-systemd.automount gubbins and replace that with defaults then mount -a works properly

This is using 10.13.6 as the macOS host and Ubuntu 20.04 as the client so a little bit different from your setup but not all that different. I’ll take the MacBook home tonight and have a play there.

1 Like
56

Ok, i’m at home now with the Vero 4K and the borrowed MacBook and this is working just fine for me, worked straight away first time.

My home IP addresses are:
Vero 4K - 192.168.1.100
Mac - 192.168.1.69

This is the /etc/fstab on the Vero
192.168.1.69:/Users/administrator /home/osmc/jb nfs noauto,x-systemd.automount 0 0

This is the /etc/exports on the Mac
/Users/administrator -network 192.168.0.0 -mask 255.255.0.0

This one works ok too and tightens things down a bit more to just the 192.168.1.x range
/Users/administrator -network 192.168.1.0 -mask 255.255.255.0

This one works too and locks things down to just the Vero IP address
/Users/administrator 192.168.1.100

I can confirm that what i was asking you to try before when doing the sudo mount -a -v does actually fail for me with this setup so i was wrong to tell you to try using that, just performing an ls or a cd into that folder is enough to mount it automagically.

I’ve tested this with an external drive using the path /Volumes/NONAME and that works just fine too.

Hope this helps getting you going, if you look back through your replies there is usually at least one small thing wrong in each on the replies so try settings similar to mine and see if that gets you going at all. This should all ‘just work’.

2 Likes
57

WHACKY!! I got the RasPi working fine with the FSTAB & Exports below

Did NOT work on the VERO, but I’ll keep trying with your latest suggestions, none yet working. THANKS AGAIN!!

//192.168.40.164/Movies /mnt/Server_Movies cifs x-systemd.automount,noauto,rw,iocharset=utf8,credentials=/home/osmc/.credentials,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,vers=1.0 0 0

//192.168.40.164/TV /mnt/Server_TV cifs x-systemd.automount,noauto,rw,iocharset=utf8,credentials=/home/osmc/.credentials,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,vers=1.0 0 0

//192.168.40.164/Music /mnt/Server_Music cifs x-systemd.automount,noauto,rw,iocharset=utf8,credentials=/home/osmc/.credentials,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,vers=1.0 0 0

==========================

/Volumes/4TBshare1/Movies -network 192.168.40.3 -mask 255.255.255.0

/Volumes/4TBshare1/TV -network 192.168.40.3 -mask 255.255.255.0

/Volumes/4TBshare2/Music -network 192.168.40.0 -mask 255.255.255.0

58

Those fstab settings look like you are now trying SMB connection rather than NFS, this should all just work by NFS ok.

There are still differences in the exports regarding the ip address but if it’s working for you then great