Posts by messier63

  • Losing Ethernet with Latest OMV Update

    Quote from chente

    For situations like that in which access is permanently remote, I recommend installing OMV on a pendrive (or SD card) and having a duplicate of that pendrive. If something like this happens, replace the pendrive with the duplicate one and restart.

    Getting something like piKVM/Jetkvm is probably recommended for fully remote servers.

  • OMV filesystem/disk almost full, can i delete /dev/sdg2?

    Hi,


    I had a problem where i couldn't access the web gui but SSH was available.

    From running df -h via ssh, I was able to determine the cause as my omv disk being full. I now have temporary relief by running apt-get autoremove.

    I've discovered that my disk space is mostly being used by /dev/sdg2 as per below. How do i clear or reduce the amount of space being used by /dev/sdg2?


  • [HowTo] SnapRAID in OMV

    Quote from auanasgheps

    Can you please elaborate better? I don't know Tmux.

    My scripting capabilities are limited, but the code is on Github.

    I'm not well versed in linux so my request might be a stretch.

    With tmux you can essentially resume from where you left off in terminal. A good overview is provided here

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    Your snapraid script works and i run it overnight. The only issue is that sometimes when i wake up in the morning I'm not certain sure of how far along the script is. The only confirmation or status that you get is once the script is complete.

  • "No space left on device" error despite having enough disk space

    Nothing from above seems to indicate a full drive

    Running df - i shows no issues as well as per below

    On windows, creating a folder in any shared folder creates the same error

    forum.openmediavault.org/wsc/index.php?attachment/26349/


    I'd appreciate help with identifying the issue?

  • "No space left on device" error despite having enough disk space

    Hi all,


    As per the subject, i am getting a "No space left on device" error despite having enough disk space


    Below is the output from running df -ha

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Hi all,


    I started docker all over again and things seem to be working so far. I ran an apt-clean via OMV GUI and deleted the docker folder. Also this time around I allowed OMV to create the folder itself rather than doing it via putty previously.

    From below we see that the + is gone from the docker folder.


    Before reinstall

    Code
    drwxr-xr-x   6 root root  4.0K Apr 27 14:01 .
drwxr-xr-x  12 root root  4.0K Apr 20 00:09 ..
-rw-------   1 root root  9.0K Apr 27 00:47 aquota.group
-rw-------   1 root root  8.0K Apr 27 00:47 aquota.user
drwx--x---+ 13 root root  4.0K Apr 27 00:48 docker
drwxrwsr-x   5 root users 4.0K Apr 27 14:15 dockerappdata
drwxr-xr-x   2 root root  4.0K Apr 27 14:04 dockerscripts
drwx------   2 root root   16K Apr 19 22:45 lost+found

    After reinstall

    Code
    drwxr-xr-x  6 root root  4.0K Apr 27 22:36 .
drwxr-xr-x 12 root root  4.0K Apr 20 00:09 ..
-rw-------  1 root root  9.0K Apr 27 00:47 aquota.group
-rw-------  1 root root  8.0K Apr 27 00:47 aquota.user
drwx--x--- 13 root root  4.0K Apr 27 22:36 docker
drwxrwsr-x  3 root users 4.0K Apr 27 22:54 dockerappdata
drwxr-xr-x  2 root root  4.0K Apr 27 14:04 dockerscripts
drwx------  2 root root   16K Apr 19 22:45 lost+found


    Also previously i was asked to run the commands below which should have yielded -rw-r--r-- for /etc/resolv.conf. Now i am getting the same result whilst previoously i was getting -rw-r----- for /etc/resolv.conf.

    Code
    $ docker run --rm -it --entrypoint="/bin/sh" lscr.io/linuxserver/jellyfin
# ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 59 Apr 27 12:17 /etc/resolv.conf
# exit
$

    So in conclusion the issue seems to boil down to permission issues. and in particular the + for the docker folder?

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Quote from Zoki

    ls lah /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5 to see, if something is wrong with permissions.

    Just guessing at the moment.

    Code
    drwxr-xr-x   6 root root  4.0K Apr 27 14:01 .
drwxr-xr-x  12 root root  4.0K Apr 20 00:09 ..
-rw-------   1 root root  9.0K Apr 27 00:47 aquota.group
-rw-------   1 root root  8.0K Apr 27 00:47 aquota.user
drwx--x---+ 13 root root  4.0K Apr 27 00:48 docker
drwxrwsr-x   5 root users 4.0K Apr 27 14:15 dockerappdata
drwxr-xr-x   2 root root  4.0K Apr 27 14:04 dockerscripts
drwx------   2 root root   16K Apr 19 22:45 lost+found

    docker directory looks a bit funny, is it ok in terms of permissions? dockerappdata, where container config files are kept, look ok to me?


    Extra info below


    Code
    # file: srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5/docker
# owner: root
# group: root
user::rwx
group::--x
other::---
default:user::rwx
default:group::rw-
default:other::---
    Code
    getfacl: Removing leading '/' from absolute path names
# file: srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5/dockerappdata/
# owner: root
# group: users
# flags: -s-
user::rwx
group::rwx
other::r-x

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Quote from Zoki

    Did you move the docker root folder to some disk?

    If yes:

    • what file system
    • does the directory have special permissions

    My docker files are on my OS SSD drive which has been partitioned into two volumes; one for OMV the other for docker.

    The partition for docker is nvme0n1p4 259:4 0 100G 0 part /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5 from below. It


    Code
    nvme0n1
├─nvme0n1p1 vfat        FAT32            C734-6663                               509M     0% /boot/efi
├─nvme0n1p2 ext4        1.0              50f3acc7-ebc6-42f0-9245-0eff87d18623   12.7G    20% /
├─nvme0n1p3 swap        1                033dca22-5645-4359-8b52-8d97bb8a55ae                [SWAP]
└─nvme0n1p4 ext4        1.0              7655cb82-5790-4f01-a9a0-42688f930df5   89.6G     3% /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Quote from Agricola

    Soma is right. You need to start with a fresh install of Jellyfin. Since you are using Stacks you need to:

    1. In Portainer stop the Jellyfin container if it is running, and delete it.
    2. Go into images and delete the unused Jellyfin image.
    3. From your Shared folders you need to delete your config folder at dockerappdata/jellyfin.
    4. Adjust your stack. Comment out the lines that Soma mentioned above.
    5. Redeploy in Stacks.

    I've done steps 1 to 5 and same result. I think my installation is completely messed up somehow


    Quote from Zoki

    messier63 Something is wrong with your docker installation. The problem is not related to the jellyfin image, as the permissions are wrong for the debain contaienr too.


    What are you running OMV / debian on and how did you install docker?

    I'm running;

    OMV Version: 6.0.22-1 (Shaitan)

    Processor: Intel(R) Pentium(R) Gold G7400T

    Kernel: Linux 5.16.0-0.bpo.4-amd64


    To install docker, I used the install option via omv-extras