Posts by Solid Kuro

    This could be my problem:


    The question is if there's a way to fix it without a PCI card (I only have PCIe ones).

    This happened to me initially and still does sometimes, try Ctrl + Shift + R the refresh should work

    Yeah, I had this in mind too and tried Ctrl + Shift + R in my browser as well, but it didn't help.


    Highly likely that the ip address has changed after the reboot, check your router, one way around this might be to set a static ip address on the initial boot (before you shutdown and remove the graphics card). However you need to check your router they all behave differently, as an example mine has a dhcp scope from 65 - 253, so any address before 65 can be used as a static ip, some will allow an option to 'always use the same ip address'. But again you need to set this before the shutdown.

    My OMV server has a static IP on local network, so this is not the solution either, unfortunately. Thank you for your suggestions though.

    Thank you for the suggestions, but this is not the solution of my problem, unfortunately.


    I have edited /etc/default/grub by changing GRUB_CMDLINE_LINUX_DEFAULT from "quiet" to "nomodeset text" and adding the line GRUB_TERMINAL_OUTPUT=console, saved, thoroughly checked the code for typos a few times. Shut down the server, plugged the graphics card out, started again and got the same result. Tried rebooting the server a few times, but it didn't work. Then plugged the card back in and everything works just fine again (and I have reverted the changes now).


    Having read the thread with Google Translate, just to clarify, I think that person's problem is a bit different: while he has trouble starting OMV6 with a monitor plugged out, my problem appears only when a graphics card is plugged out (I don't have a monitor connected to the server at all).

    Did you enable access via ssh before removing the graphics card?

    Yes, I have SSH enabled and whenever I have a graphics card plugged in, OMV's web interface and PuTTy work perfectly fine.

    Using ssh/putty checking for errors during boot via dmesg is the recommended approach

    However, when a GPU is not plugged in, I can't get any remote access to the server whatsoever, so I can't access the terminal as well. Or do you mean I should check some kind of system logs?

    I've been using my 15-year old hardware (Core 2 Duo E4500) as an OMV server for a few years now (OMV 4, 5, 6). This CPU doesnt have integrated graphics, so I've been using a separate graphics card for installing OMV (Nvidia 8600GT at first, Radeon X300 later on). Whenever the installation via a monitor had been done, I shut the server down, removed the card for power consumption and noise reduction purposes, started it again, and from then on controlled it only over OMV web interface and PuTTy. However with a fresh install of OMV 6 (my first time using it), I don't seem to be able to do it the same way anymore. Whenever I try to start the server with my graphics card out, I'm getting "Software Failure" on web interface, "Network error: connection timed out" on PuTTy and my qbittorrent client is unreachable as well. I have tried doing it multiple times with the same result.


    Am I missing something here or is it intended to work this way in OMV 6?

    This is important to me as if I can't solve the problem, I will have to change my server's hardware configuration. Thank you for your time and I love the new OMV 6 control panel and functionality by the way.

    But then, if I understand it correctly, I'll need to run this command every time I add any new files as the default permissions is set to "-rw-rw-r--". I need a permanent solution for all the files added to my 2 ext4 hdd's. I want all of those files to be fully readable/writable/executable for 2 OMV users who have access to SMB/CIFS shared folders (no guests allowed though) and also not to have any writing/execution problems with those files if I transfer them to another computer.

    Thank you for those links. With their help I have executed the following commands:

    Code
    chown -R root: /srv/dev-disk-by-label-1tb
    chown -R root: /srv/dev-disk-by-label-3tb
    chgrp root /srv/dev-disk-by-label-1tb
    chgrp root /srv/dev-disk-by-label-3tb
    chmod -R 777 /srv/dev-disk-by-label-1tb
    chmod -R 777 /srv/dev-disk-by-label-3tb

    Looking back, 'chown' and 'chgrp' weren't really needed as I've set all files' permissions to rwx (777) anyway.


    However, this doesn't solve the problem with the newly added files, as they get the default permissions.

    Code
    root@SERVER:~# ls -l /srv/dev-disk-by-label-3tb/Stuff/qsfv.exe
    -rw-rw-r-- 1 DESKTOP users 372736 Jul 6 18:50 /srv/dev-disk-by-label-3tb/Stuff/qsfv.exe

    Having read your links and a bunch of other stuff on the topic of umask and default permissions, I got a bit confused how to permanently change them to rwx for my 2 folders. What would the solution for OMV be?

    Is the executable bit set on file system level?

    How do I do that? (I'm fairly new to linux systems).


    ***


    Meanwhile, I followed the guide from one of your previous links and i added the line

    Code
    OMV_FSTAB_MNTOPS_EXT4="defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0"

    to /etc/default/openmediavault, so now when I mount my ext4 drives, there's no 'noexec' attribute by deafault. The problem is still there.


    ***


    Another thought. Could the problem be that OMV overrides access rights to R/W only when you set up a folder to share?

    macom thank you for your reply.


    I've followed the instructions from TDL's video (removed the noexec attribute, saved, rebooted), deleted all shared folders from SMB/CIFS and "Shared folders", then shared them again, but the problem remains.


    Following additional checks from the second link here's what i got:

    1. /etc/openmediavault/config.xml

    2. /etc/fstab

    3. cat /proc/mounts


    In the last part there's an 'rw' attribute in these lines:

    Code
    /dev/sda1 /srv/dev-disk-by-label-3tb ext4 rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0
    /dev/sdc1 /srv/dev-disk-by-label-1tb ext4 rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0


    Could this be the problem? Any other ideas?

    While using Win10, I'm trying to run .exe files from folders shared with SMB/CIFS, but I keep getting this kind of error:

    JLZIpay.png


    Wherever I look in OMV control panel I can only find the configuration of read/write permissions. I have 2 user accounts in OMV and basically want them to do whatever they want with those shares. How can I do that?

    Can you try to free up some more space on / ?

    Now there's only 8% used.

    BTW: if you did a clean install yesterday, how can you have images from January?

    That's what I was wondering about as well. I had been using OMV 4 with qbittorrent for a few months (I have a 20MB qbittorrent appdata folder), but have never used Portainer before. By looking at the images' tags I'm assuming Portainer somehow downloaded as many qbittorrent builds as it was possible given the size of my system disk.

    Last line show that your root filesystem is full.


    You need to find out what is filling the filesystem.

    Start from / cd /

    with du -xhd1 you can see how much space each folder is using. Move in the biggest folder and repeat until you know which folder is filling your drive.

    I have just checked the Portainer control panel and there's like dozens of qbittorrent images:

    G4qgNLq.png

    For the login loop:


    have you checked if your root filesytem is full?

    df

    To be exact, I'm out of the login loop now. When entering the control panel, I get the login screen, try to login and then get the message I posted above.

    Here's what I get when entering the 'df' command:

    ***

    service minidlna status:

    ejI5DSq.png

    Yesterday I made a clean install of OMV 5 (+ OMV extras, qbittorrent (Portainer), MiniDLNA).


    Everything worked fine until MiniDLNA failed today (couldn't get access to it from my TV).

    Tried logging into OMV control panel, but couldn't (login loop).

    Cleared browser cache, made a few reboots, tried this ( https://pcmac.biz/openmediavault-5-login-loop-issue/), omv-firstaid (clean apt, clear web control panel cache) and now I'm getting this message when trying to login:

    Code
    Error #0:
    OMV\Exception: Failed to read file '/var/cache/openmediavault/cache.omv\controlpanel\login_js.json' (size=0). in /usr/share/php/openmediavault/json/file.inc:207
    Stack trace:
    #0 /usr/share/php/openmediavault/json/file.inc(223): OMV\Json\File->getContents()
    #1 /usr/share/php/openmediavault/controlpanel/controlpanelabstract.inc(198): OMV\Json\File->read()
    #2 /var/www/openmediavault/index.php(46): OMV\ControlPanel\ControlPanelAbstract->render()
    #3 {main}

    I still have access to the shared folders and qbittorrent, so I just can't login and MiniDLNA doesn't work. Never had anything like this in OMV4.

    Any ideas?