Hi,
Are you able to write to the nfs share from other devices on the network?
Also to check to see if is a local issue, we could try recreating the mount point.
sudo systemctl stop transmission-daemon
sudo umount /mnt/siusti
sudo rmdir /mnt/siusti
sudo mkdir /mnt/siusti
sudo reboot 0
Then try @bmillham suggestion again:
Thanks Tom.
Thanks Tom for support inso late time.
Here it is : osmc@osmc : ~ $ sudo systemctl stop transmission-daemon
Failed to stop transmission-daemon.service: Unit transmission-daemon.service not loaded.
osmc@osmc : ~ $ sudo umount /mnt/siusti
osmc@osmc : ~ $ sudo rmdir /mnt/siusti
rmdir: failed to remove ‘/mnt/siusti’: Device or resource busy
osmc@osmc : ~ $ sudo mkdir /mnt/siusti
mkdir: cannot create directory ‘/mnt/siusti’: File exists
osmc@osmc : ~ $ sudo reboot 0
Connection to 192.168.1.14 closed by remote host.
Connection to 192.168.1.14 closed.
My vero 4K rebooted
Then connect again by SSH
and
osmc@osmc : ~ $ touch /mnt/siusti/test
touch: cannot touch ‘/mnt/siusti/test’: Read-only file system
osmc@osmc : ~ $ ls -l /mnt/siusti/test
ls: cannot access ‘/mnt/siusti/test’: No such file or directory
osmc@osmc : ~ $
Regarding your quescion: -"Are you able to write to the nfs share from other devices on the network?
For example from my computer I can copy or move to folder “siusti” what ever I want.
I just drag and drop from my computer two small pictures. And I can open them on my computer from NAS folder “siusti” . Is that what you wanted to ask?
Thanks
Ariux
Hi
Hi sorry that should have been (got confused with another transmission setup):
sudo systemctl stop transmission
Could you try the steps again, with the above change?
Regards Tom.
Ok i will do
osmc@osmc : ~ $ sudo systemctl stop transmission
osmc@osmc : ~ $ sudo umount /mnt/siusti
osmc@osmc : ~ $ sudo rmdir /mnt/siusti
rmdir: failed to remove ‘/mnt/siusti’: Device or resource busy
osmc@osmc : ~ $ sudo mkdir /mnt/siusti
mkdir: cannot create directory ‘/mnt/siusti’: File exists
osmc@osmc : ~ $ sudo reboot 0
Connection to 192.168.1.14 closed by remote host.
Connection to 192.168.1.14 closed.
When my vero rebooted, on TV was warning that no free space (didnt understand until the end on vero memory or transmission directory… This info was very quick and then kodi start.)
When I again connected SSH
osmc@osmc : ~ $ touch /mnt/siusti/test
touch: cannot touch ‘/mnt/siusti/test’: Read-only file system
osmc@osmc : ~ $ ls -l /mnt/siusti/test
ls: cannot access ‘/mnt/siusti/test’: No such file or directory
osmc@osmc : ~ $
This suggests its failing to unmount, there is is no point trying the reset of steps untill you able to umount and remove directory. Another application is probably still trying to read or write to the directory. Have you installed any other apps for the myosmc store?
Thanks Tom.
P.S @Ariux
I’ve just seen this in your log:
Commandline: /usr/bin/apt-get-real install autofs
Are you trying to mount this share with fstab & autofs? Should be one or the other?
Thanks Tom.
It is installed just Transmission and SSH client nothing more. I have skins Confluence, and Estuary. Nothing more.
Then I saw warning info on tv when wero rebooted about no free spase on …
I went to settings - system info- storage
Here is picture of it
Looks that my vero have no free space? Strange
About the freespace being null, i guess the Transmission has writen to /mnt//siusti when the drive has not been properly mounted, filling the Vero’s internal storage
How can I free disk space? Is any way?
Or I have to run fresh install? It would be good to make back up, but when internal storage is full, can i do back up to NAS storage?
Hi Tom
Regarding:
Commandline: /usr/bin/apt-get-real install autofs
Are you trying to mount this share with fstab & autofs? Should be one or the other?"
I have read in the forum about autofs and tried to mount in this way, but even didnt remember what exactly. I didnt mount anythisng seccesfully as I remember. How to uninstall autofs package
Hi,
Dilthedog has pointed this out to me, the above suggests the share is indeed being mounted by fstab. As for working out whats filled out the internal drive, I suspect Joakim_s; trying the following should confirm:
sudo systemctl disable autofs
Comment out or removing the following entry from fstab:
192.168.1.5:/mnt/USB/USB1_c2/CloudUSB1/siusti /mnt/siusti nfs x-systemd.automount,noauto 0 0
reboot
check the output of:
mount|grep siusti
I would expect this to be blank, as it shouldn’t be mounted.
Then check:
/mnt/siusti/
If there any files and folders listed, these should be backed up to your nas and then deleted from the vero4k.
Once completed I would:
sudo systemctl enable autofs
reboot and then provide the output of:
mount|grep siusti
Thanks Tom.
Hi Tom
I removed the entry from FSTAB
192.168.1.5:/mnt/USB/USB1_c2/CloudUSB1/siusti /mnt/siusti nfs x-systemd.automount,noauto 0 0
rebooted
then
osmc@osmc : ~ $ mount|grep siusti
osmc@osmc : ~ $ /mnt/siusti/
-bash: /mnt/siusti/: Is a directory
osmc@osmc : ~ $ sudo systemctl enable autofs
Synchronizing state of autofs.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable autofs
osmc@osmc : ~ $ Connection to 192.168.1.14 closed by remote host.
After reboot
osmc@osmc : ~ $ mount|grep siusti
osmc@osmc : ~ $
My vero 4k shows in system info-storage is 12 GB free again
Thanks very much
sorry that should have been:
ls /mnt/slusti
Ok but if its showing 12gb free again, lets try the following and provide the output:
ls /mnt/slusti
mount|grep siusti if the output of this isn’t blank, please proceed with:
touch /mnt/siusti/test
ls -l /mnt/siusti/test
Thanks Tom.
osmc@osmc : ~ $ ls /mnt/slusti
ls: cannot access ‘/mnt/slusti’: No such file or directory
osmc@osmc : ~ $ mount|grep siusti
osmc@osmc : ~ $ touch /mnt/siusti/test
touch: cannot touch ‘/mnt/siusti/test’: Permission denied
osmc@osmc : ~ $ ls -l /mnt/siusti/test
ls: cannot access ‘/mnt/siusti/test’: No such file or directory
Hi,
Ok I’m not sure whats going here, as it looks like autofs was working but isn’t now; lets try the following:
sudo systemctl disable autofs
re-add this entry to fstab:
192.168.1.5:/mnt/USB/USB1_c2/CloudUSB1/siusti /mnt/siusti nfs x-systemd.automount,noauto 0 0
sudo mkdir /mnt/siusti/
reboot, then provide the output of:
mount|grep siusti
ls /mnt/siusti/
touch /mnt/siusti/test
ls -l /mnt/siusti/test
Thanks Tom.
With your help I will be super user of OSMC 
osmc@osmc : ~ $ sudo systemctl disable autofs
Synchronizing state of autofs.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable autofs
osmc@osmc : ~ $ sudo nano /etc/fstab
osmc@osmc : ~ $ sudo mount -a
osmc@osmc : ~ $ sudo systemctl daemon-reload
osmc@osmc : ~ $ sudo systemctl restart remote-fs.target
osmc@osmc : ~ $ ls /mnt/siusti
Screen Shot 2018-11-01 at 20.29.05.png Screen Shot 2018-11-01 at 20.30.58.png
osmc@osmc : ~ $ sudo mkdir /mnt/siusti/
mkdir: cannot create directory ‘/mnt/siusti/’: File exists
osmc@osmc : ~ $ Connection to 192.168.1.14 closed by remote host.
Connection to 192.168.1.14 closed.
KristinaArunass-iMac:~ Namai$ ssh osmc@192.168.1.14
osmc@192.168.1.14’s password:
Linux osmc 3.14.29-126-osmc #1 SMP Wed Oct 31 17:34:23 UTC 2018 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Nov 2 00:26:33 2018 from 192.168.1.251
osmc@osmc : ~ $ mount|grep siusti
systemd-1 on /mnt/siusti type autofs (rw,relatime,fd=38,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
osmc@osmc : ~ $ ls /mnt/siusti/
Screen Shot 2018-11-01 at 20.29.05.png Screen Shot 2018-11-01 at 20.30.58.png
osmc@osmc : ~ $ touch /mnt/siusti/test
touch: cannot touch ‘/mnt/siusti/test’: Read-only file system
osmc@osmc : ~ $ ls -l /mnt/siusti/test
ls: cannot access ‘/mnt/siusti/test’: No such file or directory
osmc@osmc : ~ $
Hi,
please try:
sudo apt-get remove autofs
reboot and provide the output of:
mount|grep siusti
&
df -h
Thanks Tom.
Here it is
osmc@osmc:~$ sudo apt-get remove autofs
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages will be REMOVED:
autofs
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 2047 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database … 30856 files and directories currently installed.)
Removing autofs (5.1.2-1) …
osmc@osmc:~$ Connection to 192.168.1.14 closed by remote host.
Connection to 192.168.1.14 closed.
KristinaArunass-iMac:~ Namai$ ssh osmc@192.168.1.14
osmc@192.168.1.14’s password:
Linux osmc 3.14.29-126-osmc #1 SMP Wed Oct 31 17:34:23 UTC 2018 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Nov 2 00:33:39 2018 from 192.168.1.251
osmc@osmc:~$ mount|grep siusti
systemd-1 on /mnt/siusti type autofs (rw,relatime,fd=38,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
osmc@osmc:~$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 774M 0 774M 0% /dev
tmpfs 895M 8.5M 887M 1% /run
/dev/vero-nand/root 14G 1.6G 12G 12% /
tmpfs 895M 0 895M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 895M 0 895M 0% /sys/fs/cgroup
tmpfs 179M 0 179M 0% /run/user/1000
osmc@osmc:~$
Hi,
Now try:
ls /mnt/siusti/
touch /mnt/siusti/test
ls mnt/siusti/test
If it still reports readonly system and you are sure the share is set as writable on your nas, then I would back up (you can do this via myosmc) and reinstall the vero4k:
you can also restore your settings via myosmc.
Thanks Tom.