Posts by olahaye74

    Forgive me for not extensively reading all of your unpleasant posts. I got one of your many problems wrong from reading the last couple of posts. My bad. You picked one thing that 99.9% of the time is because of the common solutions thread I mentioned. But what would I know. Your "solution" has been posted about before. ntfs is something we tell people over and over not to use and 99% of ntfs filesystems in my experience have a label.
    Who on earth would use an ntfs disk on a Linux system that drives are supposed to be connected to permanently??

    No problem for bad reading, you're forgiven, and sorry for unpleasant post, but I can tell you that searching for relevant solutions in all the OVM forums is a nightmare. For example when you try to find nginx error with unsupported address family (obvious problem with ivp6 addressing and thus maybe network problem, 1st install update process failed, kernel, not updated or any other issue that end with no ipv6 available in OMV booted system, you only see messages like check your power supply, use good SD card, try reboot and more fancy answers or simple RTFM (that doesn't give diagnostic or solution to this). This is the same for usb disk, if it is ntfs, no relevant solution, or, if any, lost within all the irrelevant answers asking for disk brand and such.
    Of course, now I found the thread about space in label using google No volumes in Shared Folders and the guy who faced that had to solve himself the problem.
    Space in labels is common. Many manufacturer ship drives formatted with space in label (example "My Passport").

    Regarding the use of ntfs, this is the only filesystem that is supported by all OSes on earth. That is, when I bought my LG 4K TV, it shipped with an ntfs drive an 4 4K signed films on it.Label "LG TV", filesystem: ntfs. I wanted to share this so my hisens 2nd 4K TV could read it as well. Other far common use case: all people exchanging downloaded films (that's bad, but it exists) are doing this with ntfs disks because they often do that from a windows computer.

    So on earth, using ntfs disk on a Linux system which are supposed to be connected most of the time is far from being uncommon. And regarding DLNA streaming usage, it is far sufficient. Reformatting disk using xfs will prevent to unplug the disk and plug it to a windows computer or Mac computer to feed it.

    Of course, regarding storing important data, I would never ever use an ntfs filesystem. it is so fragile and recovery tools will do more damage than effective data recovery.

    Nope. Too tired to repeat myself over and over again so just a quick answer for a potential forum or web search

    • representation of filesystem metadata (so called alternate data streams). Mismatch between NTFS's own implementation and the way OMV's filesharing daemons will do it (Samba, Netatalk, NFS, whatever FTP daemon OMV uses -- no idea)
    • encodings (UTF-16/UCS-2 vs. UTF-8)
    • permission model (POSIX stuff and Unix ACLs vs. NTFS' own concept)

    So this will only 'work' if you live a couple of decades ago when common 'encoding' was plain/primitive ASCII, when filesystem metadata was something only existing on Macs and when the concept of permissions or access restrictions was unknown. Today 'ntfs working fine with OMV' is only a matter of ignorance.

    That's great so why not using those instead?

    You speak about theory, I speak about use case. Who on earth will try to do posix right management on an NTFS usb disk?
    I leave my buffalo because I want something I can tune, something open and the closed buffalo is hardly rootable (need to dismouth it since last FW update),
    My usecase was to have a simple DLNA server (HOME use with a tiny raspberry that can leave within my home patch bay and that I can feed from my linux box or MacOS.
    OMV works perfectly for that purpose. (big thanks to fuse and ntfs driver developpers)
    No need for posix right while the whole disk is shared thru DLNA.
    Accessing it from my Linux box or Macbookpro is easy, I share it thru CIFS (works perfectly) and made some systemd .mount and .automouth files on my linux box that mount it with my feeding user uid/gid..
    Works like a charm, I can see films from My AppleTVs using Infuse, Listen music with itunes. Perfect.
    I can feed it flawlessly and I'm very happy with this solution so far.

    Read problem #2 - https://forum.openmediavault.o…tions-to-common-problems/
    It is disappointing that almost all of your problems are mentioned in the readme at the download of the RPi image or the Solution to common problems announcement at the top of every forum.

    IT's disapointing that you didn't read my posts extensively and reply what you though I would have told.
    Problem #2 states abount avoinding to mount and dismound disk by hand and states that those operations should always be done using web interface.
    Did I ever ever said that I tryed to mount the disk by hand?

    From the post just above:
    OMV 4.1.19-Arrakis on rpi3 Issues and sollutions
    > Unmounting disk from web interface, then issuing
    > ntfslabel /dev/sda1 MyPassport
    > Then remounted via web interface the disk.
    > Now it works, I can select a device.

    More over I gave the solution to help people having the same problem has me which is reproductible and well identified. Your post just reroute the user hitting this BUG to an irrelevant solution to his problem.

    mDNS isn't even involved at all. It's a feature called dynamic DNS updates and I've not encountered a single router (implementing DHCP and DNS at the same time) within the last 5 years that can't cope with this. It's based on which is over 20 years old so it's not that surprising that even the most crappy routers support it in the meantime.
    A simple ping raspberrypi after someone fires up an RPi with a fresh copy of OMV should simply work. Maybe a ping raspberrypi.local (mDNS this time) as well. BTW: mDNS does not need support from the router since mDNS/ZeroConf works without any router at all. It's all about link local addressing here and no central instance needed. Only the capabilities of the involved OS implementations matter (no idea how recent Windows behaves here but in the past it was PITA with Windows)

    OMV is not designed/meant to share NTFS disks anyway but wants a POSIX compliant filesystem.

    thanks for notice about DNS, I'll give a look.
    ping raspberrypi fails on my linux system:
    ping: raspberrypi: Name or service not known
    but ping raspberrypi.local did succeed. It could be a nice addition to the readme.

    Regarding NTFS, it is the basic format of all USB disc you can buy. Linux does support very well these systems. Most of user choosing raspberry based solutions are looking/aiming to use it to read the USB disks they've just bought.
    rejecting this filesystem is, forgive me, just stupid. All NAS like buffalo and such do support those kind of disks.
    I hate this filesystem myself, because if filesystem has a problem, there is no way to recover things; nothing comparable to xfs_repair in anyway. Though, this filesystem is wide spread and apparently, some POSIX conformance test found that ntfs-3g is conformant (

    finaly, as I told: ntfs is perfectly supported by OMV and works flawlessly provided there is no space in the label (and that fuse module is available). It's just a matter of finding where in the OMV code, the path to '/dev/disk/by-label/label with space' lack quote protection.

    I'll tell my fiber provider to change my router then. For sure, this helps people that have no linux knowledge to find their ip when their router has no mdns enabled.

    For point 6: can't select a disk device when I want to share something: Software BUG: OMV doesn't support space in ntfs disk label.
    rename you disk or wait for a fix.
    Unmounting disk from web interface, then issuing
    ntfslabel /dev/sda1 MyPassport
    Then remounted via web interface the disk.
    Now it works, I can select a device.

    For those who want an answer to initial post by navigating to last post:
    nginx doesn't start due to unsupported address family:
    - log in as root
    - type ifconfig
    if you don't see inet6 lines for your main interface, this means that ipv6 is not configured/initialised/supported on your system.

    Possible causes:
    - update (including kernel) is not finished and the original kernel doesn't support ipv6
    Try to wait update process to finish and reboot
    - you still cant have ipv6 (and don't need it) on your system
    Remove ipv6 in nginx config files (/etc/nginx/sites-available/openmediavault-webgui)
    => comment listen line and replace it with listen 80;
    restart nginx with ystemctl restart nginx
    finish debian reconfigure with: apt reconfigure nginx-full

    First and foremost IPv6 is way under developed in most software app's, on nearly any OS.Setting that aside, your post what could only be described as an extended rant, complaining about free software and you expect to get support? Seriously?

    As a suggestion, since it's so flawed (in your mind), don't use OMV. Maybe you should stick with the buffallo chip link station since it seems to work for you.

    I'm not ranting about the software, I'm ranting about stupid answers by people that care more about the post counter than about giving a solution.
    Example: you tell me that ipv6 ix experimental. Are you joking? did you ever read my initial post? I told that because I HAD NO IPV6 (NO IPV6, can you read that?) I had to fix nginx IPV6 that have it enabled by default. it has it enabled by default and you suggest that it's experimental (obviously meaning I shouldn't use it). Does it help original poster?

    I'm developper of many opensource projects, and I consider myself as far from being noob, but when I google for problem, this is the 1st project where 95% of answers are irrelevant to problem.


    Here are some informations to people trying the v4.x on raspberry pi3 for the 1st time.

    1/ After flashing and trying to boot OMV:
    - if the webserver doesn't start du an error like no such adress family:
    => the error is likely related to ipv6 not available in the system and nginx trying to listen (create) an ipv6 socket.
    The solution is to edit /etc/nginx/sites-available/default and /etc/nginx/sites-available/openmediavault-webgui
    and comment lines similar to: listen [::]:80 default_server;
    You should only have: listen 80;
    # listen [::]:80 ipv6only=off;
    in both files.
    then restart nginx (systemctl restart nginx
    then finish debian confioguration apt reconfigure nginx-full

    2/ You don't have an US keyboard and want for example a french keyboard:
    apt-get install console-data
    (and if you want to change: dpkg-reconfigure console-data)

    3/ You can't mount an ntfs file system (fuse error (module missing or bad symbol))
    Update the kernel:
    apt install rpi-update

    => Got 4.14.97-v7+ and worked fine

    4/ changing web admin password:
    It's not in Access Right Management/Users
    Nor it is in a Security section.
    it's hidden in System/General Settings second tab: Web administrator password

    5/ You don't know your IP:
    Method 1:
    Use a console and log in as root (password is the same as web admin user)
    change root password (forced)
    Some system informations are displayed in color. IP is displayed. if it isn't, this means that you didn't get one (either cable not connected or no dhcp answer)

    Method2: (no console)
    use nmap to search for local network port 80 and or port 22 openned and try to guess. (you should better use a screen + kbd for the 1st time ans system may not start nginx if not ipv6 is configured.

    6/ Can't create a share: system won't let chose any device.
    I'm stuck here....
    Also can't share on mini dlna (same issue)
    Disk section sees my ntfs disk and it is mounted and it can compute capacity

    Also got from forum:
    Error Message

    The server encountered an unresolvable problem, please try again later.
    Exception ID: 94a6babfdcb9c7b84aa1c095e8ff5250e1091bfaError Message
    The server encountered an unresolvable problem, please try again later.

    And for the OMV, from webui, disabling and re-eanbling sshd fails and asking for reboot (from web interface) gave me a GRURU MEDITATION. Cool, we have Amiga nostalgic fans.

    So much garbage in threads.... do you really think a good power supply will fix IPV6 issue in nginx config?
    do you think a good sdcard will fix issue of lack of home for admin?


    I'v googled a lot for the nginx issue and found only irrelevant answers like yours about try waiting 30 minutes (magic is in the air), rebooting (like windows solution to any problem), sdcard quality(I have samsung high end, and again,quality issues are not about ip, but about FS errors or at most timeouts or race conditions, not about IP v6 issue: waste reading). Good poser suply, lol. either the card works or not. if its about disk, either it works or it shuts dow due to lack of power (and again: none of issues I've reported can be related to power) ,

    It works for tousand of people who use the V3 on intel PC, that doesn't excuse the fact that basic stuffs are not tested.
    Loads the OMV_4_Raspberry_Pi_2_3_3Plus.img.xz and try the following
    - login as admin on the console => Fail
    - have nginx started on a network that doesn't provide ipv6 adressing => fail
    - plug an ntfs drive => fail.

    And at last, the bonus: posting to this forum gave me this from Firefox: 64.0.2 (thanks fully the message got posted, and thus the original poster may find usefull to know that the issue is related to ipv6)

    Fatal error: An error occured. Sorry.

    ID: 0fc7a94bc45e7a80b34475668c4042c03df6220f
    Please send the ID above to the site administrator.
    The error message can be looked up at “ACP » Logs » Errors”.


    BUG 1 [IPV6] the problem about nginx is not about how to flash, os version hardware or any silly stuff.
    Reading the message is explicit: no such adress familly is typical of IPV6 not available.
    find /etc/nginx |grep listen and you'll find some listen on ipv6.
    replace those listen line with listen 80; and it'll work.

    BUG 2 [admin login] before that you need to login, unfortunately, admin can't login because of missing home dir!!!!
    thanksfully, root login (very bad) is available with admin default password.

    BUG 3 [ask to change pwd before setting up kbd] when login in, it asks to change the password. How do I do that with a non US keyboard!!!! crap!
    used basic letters; worked.

    BUG4 [no alternative kbd available] (loadkey fr: no such keymap)

    BUG5 [no fuse] from web interface, tried to mount a ntfs disk. Failed: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-label/My\x20Passport' 2>&1' with exit code '21': modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.80-v7+/modules.dep.bin'modprobe: FATAL: Module fuse not found in directory /lib/modules/4.9.80-v7+ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root.
    then I wanted to connect via ssh: fail for admin (no home), root: disabled. crap!

    BUG6: web ui fails to restart ssh.

    BUG7: tried many plugins and had buch of stupid errors (missing stuffs (deps problems)...

    That is far far far from being an out of the box NAS solution. and the gui fro flashing? it is even enable to resise the root partition to the full flash size and takes ages! dd is so much faster! (to verify: diff /dev/mmcblk0 flash.img)

    1/ As a sumup
    - if ipv6 is missing: nginx fails to start. so nothing can be done without a screen and kbd
    - ip is not displayed until you login. why?
    - can't login admin in the console because of missing homedir
    - fuse missing / not confiogured
    - missing non us keymap in image. (even initrd on major distro includes that)

    2/ I wanted to replace my buffallo link station LS410D for a more open solution, but unfortunately omv is FAR from being usable. The idea and project is wonderfull, but I wonder if a single component has been tested. honestly, login on console as admin?

    OMV_4_Raspberry_Pi_2_3_3Plus.img.xz (I know it's not the stable version, but I expected a beta. What I saw is not even alpha. Sorry)