Beiträge von wouterve

  • UDEV Failed to query device driver: No such device after update to OMV 6.0.19

    OK guess I've found the problem. I checked with lsusb and my Atolla USB hub does contain a Genesys chip.

    Here is the output of lsusb -t


    Code
    /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 2: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            |__ Port 3: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            |__ Port 4: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
         |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

    and here for lsusb



    So Bus 4 dev 2 points to a Genesys Logic hub after all if I interprett correctly?


    In /etc/udev/rules.d/61-openmediavault-dev-disk-by-id.rules

    I've found the following rule:


    Code
    {ID_VENDOR_ID}=="05e3", \
ENV{ID_MODEL_ID}=="0718", \
IMPORT{program}="serial_id %N", \
ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_$env{ID_SERIAL_SHORT}-$env{ID_INSTANCE}", \
SYMLINK="disk/by-path/$env{ID_PATH}", \
SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"


    So the model n° is 0718 whilst mine is 0616 does this mean I won't be affected by the changes of update 6.0.16?

  • UDEV Failed to query device driver: No such device after update to OMV 6.0.19

    Yesterday I've updated OMV from version 6.0.14 to 6.0.19 and since then I encounter the following problem:


    Boot fails (it goes to emergency mode) with the error Timed out waiting for device /dev/disk/by-uuid/...  & Dependency failed for File system check on /dev/disk/by-uuid/... 

    Strangely it does not always encounter this problem. When I reboot after this message, it often can mount all my disks without any error.


    So I've inspected my journald logs and it seems my Atolla USB 3.0 hub (link) does give some problems with the update UDEV rules.


    FYI I've mounted my disks as a MergerFS pool, hence the errors that the dependenies for the pool fails and why it probably becomes stuck in emergency mode.


    What could I do to solve this problem? AFAIK this does have nothing to do with the warning for update 6.0.16?


    Edit: more information about my setup

    Hardware = Odroid XU4

    Software = Armbian 22.02 bullseye 32-bit using linix kernel 5.4

  • Failed to start Entropy Daemon after update to OMV 6.0.19

    Zitat von macom

    Have a look here:

    https://forum.armbian.com/topi…indComment&comment=134876


    Proposed solution working for me:

    Execute as root these two commands

    Code
    mkdir -p /etc/systemd/system/haveged.service.d
echo -e '[Service]\nSystemCallFilter=uname' > /etc/systemd/system/haveged.service.d/syscall.conf

    Thanks! This solved my problem. I'm running OMV on Odroid XU4 so I might be affected by this bug.


    Another strange thing I noticed is that sometimes a boot fails as it cannot find my file systems. This happens +- every second reboot. So I'm a bit puzzled what could be wrong with my fstab as some boots work and some other not.

    The error I'm receiving is:

    Code
    Time out waiting for device /dev/disk/by-uuid/...
Dependency failed for File System check on /dev/disk/by-uuid/...


    and this for all disks that are attached to my OMV build.

    I've readthis warningupon the update of 6.0.16 but AFAIK none of my drives does have a genesys usb adapter.

    What could be causing this error or do I better start a new thread for this?


    Thanks in advance.

  • Failed to start Entropy Daemon after update to OMV 6.0.19

    Today I updated my OMV 6.0.14 installation to 6.0.19. There were some minor errors during the upgrade process (see attached log) but installation finished OK.


    After reboot however, my server went into emergency mode with the following errors on the screen:


    Code
    Failed to start Entropy Daemon based on the HAVEGE algorithm
See systemctl status haveged.service for details


    Upon second recoot It did get past this error. I checked the status for the service:


    Here is the output from syslog:


    So basically my system is not working now. What can I do to solve this please?

  • OMV5 upgrade to 6 not executed

    Hello,


    I tried to upgrade from 5 -> 6 using the command omv-release-upgrade.

    Ater the command finishes it tells me the upgrade has completed successfully, however the last line of code shows:

    0 upgraded, 0 newly installed, 0 to remove and 726 not upgraded.


    Upon reboot, I'm still on version 5 and debian hasn't upgraded. I'm still able to login and all shares & docker are working.

    However, when performing the command omv-release-upgrade. it hangs after updating the repositories. Also, apt dist-upgrade  hangs.


    What could be the cause? Also, is OMV6 still RC or has it released? In other words, will this probably be resolved in the futures (I'm working with OMV since release 3 and needed to set it up again with each release so probably not)


    Below full output of omv-release-upgrade.


  • Install other version of PHP

    I've been running Apache + Nextcloud for 3 years now without problems (OMV is using Nginx & I'm running that on a different port).

    For other PHP version: a good idea to run that in a container, running another version may be a bridge too far for OMV to run well :)


    Thx for advice

  • Install other version of PHP

    Hello,

    I'm using OMV5 on which I've installed apache2 & Nextcloud as well.

    Some NC apps require newer version of PHP (OMV5 comes with PHP7.3)


    So short question: Is it possible to install PHP7.4 next to the existing 7.3 so that OMV can still keep using that one?

    Or: will I break things and is it wiser to wait for OMV6?

  • 5.5.21-1 HDD serial number replaces by ID_SERIAL_SHORT (JMicron)

    Hello, I havent visited the forum in recent months but I stumbled upon your solution & applied to my installation as well.

    So in /etc/udev/rules.d/61-openmediavault-dev-disk-by-id.rules I've searched for the corresponding vendor_id & model_id & altered the code so it looks like this now:


    Code
    ENV{ID_VENDOR_ID}=="152d", \
ENV{ID_MODEL_ID}=="0567", \
IMPORT{program}="/usr/lib/udev/serial_id %N", \
ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_$env{ID_SERIAL_SHORT}-$env{ID_INSTANCE}", \
SYMLINK="disk/by-path/$env{ID_PATH}", \
SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"


    Code
    IMPORT{program}="serial_id %N", \

    became

    Code
    IMPORT{program}="/usr/lib/udev/serial_id %N", \


    Et voilà, S/N is showing up again :)


    Thanks for your suggestion!

  • 5.5.21-1 HDD serial number replaces by ID_SERIAL_SHORT (JMicron)

    Unfortunately, a reboot does not help.

    Before version 5.5.21 I used these custom udev rules which did help to retrieve the real S/N. With the update it doesn't seem to work anymore.


    I have to add this disk is mounted under /srv/dev-disk-by-uuid-478829cb-d16a-4656-8278-40e4c2fa837c/ so not under this generic S/N.

    What is the implication for not having the real S/N? I use this disk as a backup disk, no shared folders or such are on it.


    kr

    wouter

  • 5.5.21-1 HDD serial number replaces by ID_SERIAL_SHORT (JMicron)

    I've the same problem as the OP. I've deleted the 99-openmediavault-dev-disk-by-id.rules file & executed the omv-salt command. Now I just see a generic serial number:



    Output from udevadm test --action=add /sys/class/block/sdc


    I have updated to 5.22.2-1 but does not make any difference.

  • How to remove failed disk from unionFS

    one problem: I cannot log into omv panel anymore. Here is the error log:


    Code
    OMV\Rpc\Exception: Failed to connect to socket: Connection refused in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(57): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}

    Here is output of systemctl openmediavault-engined.service --no-pager -l


    Code
    omv-engined[6726]: PHP Fatal error: Uncaught OMV\Config\DatabaseException: Fatal error 76: Opening and ending tag mismatch: mntent line 406 and fstab (line=467, column=13); Fatal error 76: Opening and ending tag mismatch: fstab line 393 and system (line=602, column=12); Fatal error 76: Opening and ending tag mismatch: system line 6 and config (line=1070, column=10); Fatal error 77: Premature end of data in tag config line 2 (line=1071, column=1) in /usr/share/php/openmediavault/config/databasebackend.inc:113
omv-engined[6726]: Stack trace:
omv-engined[6726]: #0 /usr/share/php/openmediavault/config/database.inc(34): OMV\Config\DatabaseBackend->load()
omv-engined[6726]: #1 /usr/share/php/openmediavault/config/database.inc(44): OMV\Configomv-engined[6726]: #2 /usr/share/openmediavault/engined/inc/59mergerfs.inc(24): OMV\Config\Database::getInstance()
omv-engined[6726]: #3 /usr/sbin/omv-engined(360): require_once('/usr/share/open...')
omv-engined[6726]: #4 {main}
omv-engined[6726]:   thrown in /usr/share/php/openmediavault/config/databasebackend.inc on line 113
systemd[1]: openmediavault-engined.service: Main process exited, code=exited, status=255/EXCEPTION
systemd[1]: openmediavault-engined.service: Failed with result 'exit-code'.

    Here is my /etc/fstab