Beiträge von titango20

  • OMV is suddenly read only

    Trying

    Code
    sudo apt install openmediavault

    gives

    Code
    Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 php-pam : Depends: phpapi-20180731
E: Unable to correct problems, you have held broken packages.

    The idead for reinstallation comes closer :(

  • OMV is suddenly read only

    Something with 5.2x. Unfortunately neither browser works nor omv- commands to ask version. What other command can show me the version?

    Other problems:

    • Commands for upgrade via console not available
    • website not available
    • ip and dns info removed after reboot. Meens file /etc/network/interfaces is empty after reboot.

  • OMV is suddenly read only

    Zitat von Zoki

    your error looks like there is a unknown directive in the profited config file.

    Run

    dpkg --configure

    and post the output

    Error, because

    Code
    -a

    missing


    Code
    -> dpkg --configure -a

    ... says nothing, no message, hidden status.

    Zitat von ElginRoko

    Had this last night. For me the trigger seems to he having mergerfs mounts in my fstab. Fixed with remounting rw, commenting those lines, rebooting, and unticking the fstab checkbox in the mergerfs mount settings in the UI (then applying and rebooting to verify).


    Not sure what changed to cause this. I thought it was that I'd set cache.files=partial in the mergerfs opts, but removing that didn't help. The only relevant looking thing error in dmesg is:

    Code
    [    3.753464] scsi 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
[    3.753476] scsi 2:0:0:1: Failed to get diagnostic page 0x1
[    3.753481] scsi 2:0:0:1: Failed to bind enclosure -19

    Which can supposedly be caused by delays spinning up a sleeping HDD, but no idea why that would suddenly be an issue when it hasn't before

    Good idea. commenting out mergefs line in fstab mounts filesystem with rw. So "success", but doen't help because I need that :(

  • OMV is suddenly read only

    Code
    omv-upgrade

    Found and running.

    Returned code 1 :(


    Code
    dpkg -l | grep openm

    rc omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault

    rc openmediavault 5.6.26-1 all openmediavault - The open network attached storage solution

    rc openmediavault-diskstats 5.1.1-2 all openmediavault disk monitoring plugin

    ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

    rc openmediavault-luksencryption 5.0.2 all OpenMediaVault LUKS encryption plugin

    rc openmediavault-lvm2 5.0.3-1 all openmediavault Logical Volume Manager (LVM2) plugin

    rc openmediavault-mergerfsfolders 5.1.4 all mergerfs folders plugin for openmediavault.

    rc openmediavault-omvextrasorg 5.6.6 all OMV-Extras.org Package Repositories for OpenMediaVault

    rc openmediavault-snapraid 5.0.8 all snapraid plugin for OpenMediaVault.

    rc openmediavault-unionfilesystems 5.1.4 all Union filesystems plugin for OpenMediaVault.


    omv-extras was installed via ppa to use cryptsetup.

    Problem discussed here.

  • OMV is suddenly read only

    From

    Code
    apt --fix-broken


    omv collectd[19285]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)

  • OMV is suddenly read only

    Zitat von Zoki

    can you remount rw?


    I do not think the root cause is rrdcached.

    You will have to digg through the boot logs.

    Yes, but only manually, not after reboot.

    Well that is the first readable problem with journalctl :) Glad to find something.


    Unfortunately the solution reports 2 errors.

    Code
    omv-salt deploy run collectd

    works with 0 errors

    Code
    omv-salt stage run deploy

    works with 2 errors.


    Doing system upgrade doesn't end in omv5 upgrade like omv-5.5.x as discriped on that page :(

    Is there any command like

    Code
    omv-upgrade

    ? I need to look for that later.

  • OMV is suddenly read only

    Changed fstab with

    Code
    UUID=xxx /               ext4    errors=remount-ro

    to

    Code
    UUID=xxx /               ext4    errors=continue

    Nothing else. No success


    Deeper problem with report from journatctl (?) seems this

    Thema
    rrdcached error messages after reboot
    I have set up a completely new x86_64 system including OMV 5.3.2. Everything worked out fine out of the box! :)

    Just one little thing:

    After every reboot I get two mails at the same time:

    (Versteckter Text)


    (Versteckter Text)


    I checked rrdcached with
    systemctl status rrdcached
    Result: Service rrdcached is running.

    syslog:

    (Versteckter Text)


    This just happens on reboot.
    So, is something messed up with the order of starting services on reboot?
    majortim

    and

    Thema
    rrdcached plugin: Failed to connect
    After a new install of OMV5 on an x86 pc , all was going well, when i noticed this in the logs:
    rrdcached plugin: Failed to connect to RRDCacheD at unix:/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)

    I did look through the threads and seems this was an old issue that was fixed.
    Im not smart enough to figure this out, if anyone has some pointers please.
    antcj

    Trying solutions.

  • OMV is suddenly read only

    Same problem here :(

    Debian 10, snapraid, ext4. On some day suddenly readonly after reboot.

    Tried mods from this link with no luck.

    Only foreign mod that I installed is "extras" or something like that to run cryptsetup on omv5.

  • OMV5 not surviving first reboot

    Got late, some other things to do... :(

    So just stop it and accept a "bug" in a big, useful system? Sry, thats not my motivation.


    Btw: One of errors found in my system, so need to apologize on that point.

    After showing my /etc/fstab code to github I realized that the one line potentially crashing the system... didn't have the nofail flag O.o

    After adding it and rebooting, all worked "well".

    But with a new hdd and so system rewriting the line the option again disappeared and system didn't boot :(

    Maybe just a little error in plugin?

  • OMV5 not surviving first reboot

    crashtest Short answer: Yes its worth it. Even for testing whats known to be stable... more or less :/ Whatever I don't have a deadline on that, so its just an experiment until its finished :)


    geaves good. I will look and ask on github for mergefs.


    Zitat
    Quote from titango20 what would the no-fail flag in fstab effect in (in case it works)?

    trapexit says the flag does nothing.

    So why does this flag exist and doesn't show an error warning? Seems like a bug.

    Zitat
    Quote from titango20 how does mergefs work with luks and encrypted devices? In my understanding services like ovpn and luks work like transparent services (osi-layer < 5) meaning other services (mergefs) don't care.

    Mergerfs doesn't know luks exists. It just creates a union of filesystems. If the filesystem is not there (LUKS not unlocked) then it can't create the union and fails. How would you fix that?? mergerfs is not a service. It is a fuse filesystem.

    Either use kind of this flag to tell debian to ignore it (or even dont put to /etc/fstab) or tell mergefs to try mounting devices if user (=omv?) is ready. In omv in file system option there is a button to mount devices. Why not for mergefs = manual ? For me it seems the correct way as I also need to manually mount each device after unlocking (not working for mergefs... weird).

    As of writing this I feel like mergefs service (correct?) tries to run without asking system to be ready or not.

    To repeat: Just my point of view. Pls ignore if totally wrong.

  • OMV5 not surviving first reboot

    Thanks for answers.

    Unfortunately I don't understand mergefs and debian enough.

    Do the devices need to be mount points in fstab? Maybe Im gonna experiment with that.


    Zitat von ryecoaaron

    Linux (not just debian) starts in emergency mode when it can't mount a filesystem unless you pass arguments in fstab to not care. How exactly does Linux know it isn't important?

    Thats the point (Somehow bad jokes). I see an error... Not bad that omv creates moint points for devices, but if using luks maybe the mount point is wrong as for locking and no-fail issues...? Just thoughts.

  • OMV5 not surviving first reboot

    So, to write some thoughts...


    - the problem is mergefs plugin. How far does it pick functions in debian system to block system from booting?

    - what would the no-fail flag in fstab effect in (in case it works)?

    - why does mergefs care for devices to be ready or not? At that point 3rd-party-system (omv) is not loaded at all, right?

    - how does mergefs work with luks and encrypted devices? In my understanding services like ovpn and luks work like transparent services (osi-layer < 5) meaning other services (mergefs) don't care.

    - what error tells debian to start in emergency mode? That mode for not finding an unimportant device sounds like a bad joke, doesn't it?


    Is it possible to tell mergefs to not start after boot automatically?


    I will try mergefsfolder.