Nothing works.... :(

  • Hello,


    I'm working for several days on it. First I installed OMV on my Raspberry 4b and it worked more or less. I set up everything the way I need it and thought it could run like that. But some days later - without changes it displayed "bad gateway nginx" when I wanted to log in by browser. I tried several browsers, cleared the browser cache, tried to reinstall according to some hints here in the forum. Nothing helped.


    So I installed OMV again that way:


    1) Raspberry PI OS Lite on an Intenso 8 GB, Class 10 Card

    2) Made some changes in the raspi-config (Language settings, Fan settings, SSH enabled, changes the password)... Then.....

    3) "sudo apt update && sudo apt upgrade -y"

    4) "sudo rm -f /etc/systemd/network/99-default.link"

    5) "sudo reboot"

    6) after reboot "wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash"


    Then in the browser (I tried several browsers like Firefox, Edge, Chrome and cleard the browser's cache) i logged in. I changed my password and the host name. I clicked "Save" and after that "Apply Settings".... Normally not a big deal.... but I always get stuck by waiting for the settings to be applied. I waited at least 45 Minutes but nothing happened.....


    In addition....When I click on "Disks" and "File Systems" I only get the message "Waiting"...... And I waited....yesterday 2 hours. But nothing happened.

    Sometimes I also get a "communication failure" Error by klicking on menu items.


    So this morning I performed a fresh install again on another SD Card (SanDick 32 GB, Class 10) but I have the same issues. Anyone here knows where the problem is and what I could do?


    By the way: I have 4 x 4TB hard disks from WD attached and that worked before. Also the file systems are created....so they must be there....


    Best regards

    Manuel

    • Official Post

    How old is the SD card? Do you have the output from the install script?

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hello ryecoaaron,


    The SD Cards are maybe 3....4 weeks old. Never used 'em before. Where to find the output from the install script?

    Just recognized when I switch off another Raspberry (Z-Wave) just 2...3 inch away from the NAS Raspberry I can access the file systems and all file systems are shown. At least one more step.... :)

    But when I wanna mount it (doesn't matter which file system) I get the following error:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': raspberrypi:
    ---------- ID: create_filesystem_mountpoint_c7166338-341c-4358-8867-1c057f640adb Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_c7166338-341c-4358-8867-1c057f640adb for file /etc/fstab was charged by text Started: 14:10:02.406112 Duration: 2.306 ms Changes:
    ---------- ID: mount_filesystem_mountpoint_c7166338-341c-4358-8867-1c057f640adb Function: mount.mounted Name: /srv/dev-disk-by-uuid-68E0E42BE0E3FD66 Result: False Comment: ntfs-3g: Failed to access volume '/dev/disk/by-uuid/68E0E42BE0E3FD66': No such file or directory
    ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on
    Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2017 Jean-Pierre Andre Copyright (C) 2009 Erik Larsson
    Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
    Options: ro (read-only mount), windows_names, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g).
    Example: ntfs-3g /dev/sda1 /mnt/windows
    News, support and information: http://tuxera.com Started: 14:10:02.410595 Duration: 198.91 ms Changes:
    ---------- ID: create_filesystem_mountpoint_69eaf734-08bb-4d3b-b137-b27e5f530da4 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_69eaf734-08bb-4d3b-b137-b27e5f530da4 for file /etc/fstab was charged by text Started: 14:10:02.610278 Duration: 3.098 ms Changes:
    ---------- ID: mount_filesystem_mountpoint_69eaf734-08bb-4d3b-b137-b27e5f530da4 Function: mount.mounted Name: /srv/dev-disk-by-uuid-409EECAE9EEC9DA2 Result: False Comment: ntfs-3g: Failed to access volume '/dev/disk/by-uuid/409EECAE9EEC9DA2': No such file or directory
    ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on
    Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2017 Jean-Pierre Andre Copyright (C) 2009 Erik Larsson
    Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
    Options: ro (read-only mount), windows_names, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g).
    Example: ntfs-3g /dev/sda1 /mnt/windows
    News, support and information: http://tuxera.com Started: 14:10:02.613755 Duration: 116.684 ms Changes:
    ---------- ID: create_filesystem_mountpoint_9fd5f2b3-7e9d-46e1-b43a-d3465b902158 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_9fd5f2b3-7e9d-46e1-b43a-d3465b902158 for file /etc/fstab was charged by text Started: 14:10:02.731196 Duration: 3.123 ms Changes:
    ---------- ID: mount_filesystem_mountpoint_9fd5f2b3-7e9d-46e1-b43a-d3465b902158 Function: mount.mounted Name: /srv/dev-disk-by-uuid-9b345f25-089c-4f5f-962b-f67f6ab4d678 Result: True Comment: Target was already mounted Started: 14:10:02.734702 Duration: 180.022 ms Changes: ---------- umount: Forced remount because options (user_xattr) changed
    ---------- ID: create_filesystem_mountpoint_37206656-8ee3-40a2-be29-b94f412a11f8 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_37206656-8ee3-40a2-be29-b94f412a11f8 for file /etc/fstab was charged by text Started: 14:10:02.915527 Duration: 3.52 ms Changes:
    ---------- ID: mount_filesystem_mountpoint_37206656-8ee3-40a2-be29-b94f412a11f8 Function: mount.mounted Name: /srv/dev-disk-by-uuid-18671922-8858-4501-a8f8-b2c8e4b567e0 Result: True Comment: Target was already mounted Started: 14:10:02.919567 Duration: 178.628 ms Changes: ---------- umount: Forced remount because options (user_xattr) changed
    ---------- ID: create_filesystem_mountpoint_db55fa6a-3b71-41a8-836a-df100e87f917 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_db55fa6a-3b71-41a8-836a-df100e87f917 for file /etc/fstab was charged by text Started: 14:10:03.098899 Duration: 3.708 ms Changes:
    ---------- ID: mount_filesystem_mountpoint_db55fa6a-3b71-41a8-836a-df100e87f917 Function: mount.mounted Name: /srv/dev-disk-by-uuid-d4163e7c-a5d8-46ad-8d1f-5be705ab6113 Result: True Comment: Target was successfully mounted Started: 14:10:03.103024 Duration: 8395.423 ms Changes: ---------- mount: True
    ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: Changes were made Started: 14:10:11.504577 Duration: 21.078 ms Changes: ---------- diff: --- +++ @@ -8,4 +8,5 @@ /dev/disk/by-uuid/409EECAE9EEC9DA2
    /srv/dev-disk-by-uuid-409EECAE9EEC9DA2 ntfs defaults,nofail,big_writes 0 2 /dev/disk/by-uuid/9b345f25-089c-4f5f-962b-f67f6ab4d678
    /srv/dev-disk-by-uuid-9b345f25-089c-4f5f-962b-f67f6ab4d678 ext4
    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
    0 2 /dev/disk/by-uuid/18671922-8858-4501-a8f8-b2c8e4b567e0
    /srv/dev-disk-by-uuid-18671922-8858-4501-a8f8-b2c8e4b567e0 ext4
    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
    0 2 +/dev/disk/by-uuid/d4163e7c-a5d8-46ad-8d1f-5be705ab6113
    /srv/dev-disk-by-uuid-d4163e7c-a5d8-46ad-8d1f-5be705ab6113 ext4
    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
    0 2 # <<< [openmediavault]

    Summary for raspberrypi
    ------------
    Succeeded: 9 (changed=4)
    Failed: 2
    ------------
    Total states run: 11
    Total run time: 9.107 s


    Restarted several times. But that doesn't help.... :(


    Best regards

    Manuel

    • Official Post

    Where to find the output from the install script?

    The screen when you run it is the only place.

    Restarted several times. B

    Restarting won't help that error. It looks like you have old entries from previously mounting those disks? What is the output of:


    sudo omv-showkey mntent

    sudo blkid

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hello again and thanks for your answer...... :)


    The output of sudo omv-showkey mntent is:


    pi@NAS:~ $ sudo omv-showkey mntent

    <mntent>

    <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>

    <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>

    <dir>/xxx/yyy/zzz</dir>

    <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>

    <opts></opts>

    <freq>0</freq>

    <passno>0|1|2</passno>

    <hidden>0|1</hidden>

    </mntent>

    <mntent>

    <uuid>c7166338-341c-4358-8867-1c057f640adb</uuid>

    <fsname>/dev/disk/by-uuid/68E0E42BE0E3FD66</fsname>

    <dir>/srv/dev-disk-by-uuid-68E0E42BE0E3FD66</dir>

    <type>ntfs</type>

    <opts>defaults,nofail,big_writes</opts>

    <freq>0</freq>

    <passno>2</passno>

    <hidden>0</hidden>

    </mntent>

    <mntent>

    <uuid>69eaf734-08bb-4d3b-b137-b27e5f530da4</uuid>

    <fsname>/dev/disk/by-uuid/409EECAE9EEC9DA2</fsname>

    <dir>/srv/dev-disk-by-uuid-409EECAE9EEC9DA2</dir>

    <type>ntfs</type>

    <opts>defaults,nofail,big_writes</opts>

    <freq>0</freq>

    <passno>2</passno>

    <hidden>0</hidden>

    </mntent>

    <mntent>

    <uuid>6fc4d38d-0230-4678-a571-bc20cc772284</uuid>

    <fsname>/dev/disk/by-uuid/18671922-8858-4501-a8f8-b2c8e4b567e0</fsname>

    <dir>/srv/dev-disk-by-uuid-18671922-8858-4501-a8f8-b2c8e4b567e0</dir>

    <type>ext4</type>

    <opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>

    <freq>0</freq>

    <passno>2</passno>

    <hidden>0</hidden>

    </mntent>

    pi@NAS:~ $



    .... and the output of is:


    pi@NAS:~ $ sudo blkid

    /dev/mmcblk0p1: LABEL_FATBOOT="boot" LABEL="boot" UUID="5DE4-665C" TYPE="vfat" P ARTUUID="f2322557-01"

    /dev/mmcblk0p2: LABEL="rootfs" UUID="7295bbc3-bbc2-4267-9fa0-099e10ef5bf0" TYPE= "ext4" PARTUUID="f2322557-02"

    /dev/sda1: LABEL="DATA1" UUID="18671922-8858-4501-a8f8-b2c8e4b567e0" TYPE="ext4" PARTUUID="e3a88bf5-2ff2-4544-8be3-328b8fd7fa6c"

    /dev/sdb1: LABEL="DATA2" UUID="a23aa0e3-e449-4c88-85d9-6004852b361b" TYPE="ext4 " PARTUUID="4461dfd0-87f4-4079-9156-60e02da5c660"

    /dev/sdc1: LABEL="DATA3" UUID="9b345f25-089c-4f5f-962b-f67f6ab4d678" TYPE="ext4 " PARTUUID="e1515239-0ad6-4c02-ba7e-bdde078eb0da"

    /dev/sdd1: LABEL="DATA4" UUID="d4163e7c-a5d8-46ad-8d1f-5be705ab6113" TYPE="ext4" PARTUUID="04988b48-e440-4efa-a0ee-95ac4000051e"

    /dev/mmcblk0: PTUUID="f2322557" PTTYPE="dos"

    pi@NAS:~ $


    Hope that helps.... :)


    Best regards

    Manuel

    • Official Post

    I see two ntfs drives in there that don't seem to be connected to the system anymore. If you wiped them and formatted ext4, you should have unmounted them in the Filesystems tab first. Do you still see the two missing ntfs filesystems in the Filesystems tab? If so, will it let you delete them? If not, you will need to manually remove the entries from /etc/openmediavault/config.xml (make a backup first).

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hey ryecoaaron,


    Thanks for the hint. I was not able to delete the ntfs drives by the easy way - so I edited /etc/openmediavault/config.xml and deleted it. That worked fine and now I got no more error messages....till now. :) right now I'm creating a new file system for another (5th) hard drive and there are about 15 minutes left. After that I'll configure the rest. I'll keep u updated.


    Thanks again! :)

    Best regards

    Manuel

    • Official Post

    Good to hear.

    omv 7.7.9-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.2


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • votdev

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!