Failed to bind socket: Read-only file system

  • After reboot no web interface access: Failed to connect to socket: No such file or directory


    omv-engined -d -f

    omv-engined[4534]: Failed to bind socket: Read-only file system

    omv-engined[4534]:

    Failed to bind socket: Read-only file system


    I break it to learn.

    Thanks

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • When a filesystem has an issue on boot, sometimes the options will tell it to automatically re-mount readonly. It looks like yours did that. What is the output of mount?

    omv 5.6.13 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • UGH!

    I suspect it is UnionFS

    I have no concern for the data; it is safe. I just want to understand how to get out of the penalty box.


    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • I suspect it is UnionFS

    Nope. Your root filesystem is mounted readonly. sudo mount -o remount,rw / should fix but you should really run an fsck on it. Are you using a usb stick or did you system get shutdown improperly?

    omv 5.6.13 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Code
    root@omvFiveR7515:~# nano /etc/fstab
    Unable to create directory /root/.local/share/nano/: No such file or directory
    It is required for saving/loading search history or cursor positions.
    Press Enter to continue

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • btrfs, huh? You will need to look at syslog to see why it is remounting.

    omv 5.6.13 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • btrfs, huh?

    Experiments look a lot like that. Still gathering info. #NotProductionYet

    Are you using a usb stick or did you system get shutdown improperly?

    mount -o remount,rw / helped.
    Thank you.

    There is more broken, yet I did make headway on my mergerFS concept. #MoreWillBeRevealed

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • You will need to look at syslog to see why it is remounting.

    Jul 6 11:36:31 omvFive systemd[4562]: Listening on GnuPG cryptographic agent (ssh-agent emulation).

    Jul 6 11:36:31 omvFive systemd[4562]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).

    Jul 6 11:36:31 omvFive systemd[4562]: Reached target Paths.

    Jul 6 11:36:31 omvFive systemd[4562]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).

    Jul 6 11:36:31 omvFive systemd[4562]: Reached target Timers.

    Jul 6 11:36:31 omvFive systemd[4562]: Listening on GnuPG cryptographic agent and passphrase cache.

    Jul 6 11:36:31 omvFive systemd[4562]: Reached target Sockets.

    Jul 6 11:36:31 omvFive systemd[4562]: Reached target Basic System.

    Jul 6 11:36:31 omvFive systemd[4562]: Reached target Default.

    Jul 6 11:36:31 omvFive systemd[4562]: Startup finished in 142ms.

    Jul 6 11:36:31 omvFive systemd[1]: Started User Manager for UID 0.

    Jul 6 11:36:31 omvFive systemd[1]: Started Session 1 of user root.

    Jul 6 11:36:34 omvFive kernel: [ 39.581640] BTRFS info (device sdm3): disk space caching is enabled

    Jul 6 11:36:37 omvFive systemd[1]: session-1.scope: Succeeded.

    Jul 6 11:36:47 omvFive systemd[1]: Stopping User Manager for UID 0...

    Jul 6 11:36:47 omvFive systemd[4562]: Stopped target Default.

    Jul 6 11:36:47 omvFive systemd[4562]: Stopped target Basic System.

    Jul 6 11:36:47 omvFive systemd[4562]: Stopped target Sockets.

    Jul 6 11:36:47 omvFive systemd[4562]: dirmngr.socket: Succeeded.

    Jul 6 11:36:47 omvFive systemd[4562]: Closed GnuPG network certificate management daemon.

    Jul 6 11:36:47 omvFive systemd[4562]: gpg-agent-ssh.socket: Succeeded.

    Jul 6 11:36:47 omvFive systemd[4562]: Closed GnuPG cryptographic agent (ssh-agent emulation).

    Jul 6 11:36:47 omvFive systemd[4562]: gpg-agent-browser.socket: Succeeded.

    Jul 6 11:36:47 omvFive systemd[4562]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).

    Jul 6 11:36:47 omvFive systemd[4562]: gpg-agent.socket: Succeeded.

    Jul 6 11:36:47 omvFive systemd[4562]: Closed GnuPG cryptographic agent and passphrase cache.

    Jul 6 11:36:47 omvFive systemd[4562]: Stopped target Timers.

    Jul 6 11:36:47 omvFive systemd[4562]: Stopped target Paths.

    Jul 6 11:36:47 omvFive systemd[4562]: gpg-agent-extra.socket: Succeeded.

    Jul 6 11:36:47 omvFive systemd[4562]: Closed GnuPG cryptographic agent and passphrase cache (restricted).

    Jul 6 11:36:47 omvFive systemd[4562]: Reached target Shutdown.

    Jul 6 11:36:47 omvFive systemd[4562]: systemd-exit.service: Succeeded.

    Jul 6 11:36:47 omvFive systemd[4562]: Started Exit the Session.

    Jul 6 11:36:47 omvFive systemd[4562]: Reached target Exit the Session.

    Jul 6 11:36:47 omvFive systemd[1]: user@0.service: Succeeded.

    Jul 6 11:36:47 omvFive systemd[1]: Stopped User Manager for UID 0.

    Jul 6 11:36:47 omvFive systemd[1]: Stopping User Runtime Directory /run/user/0...

    Jul 6 11:36:47 omvFive systemd[1]: run-user-0.mount: Succeeded.

    Jul 6 11:36:47 omvFive systemd[1]: user-runtime-dir@0.service: Succeeded.

    Jul 6 11:36:47 omvFive systemd[1]: Stopped User Runtime Directory /run/user/0.

    Jul 6 11:36:47 omvFive systemd[1]: Removed slice User Slice of UID 0.

    Jul 6 11:36:54 omvFive monit[3897]: 'omv-engined' failed to start (exit status 0) -- no output

    Jul 6 11:37:24 omvFive monit[3897]: 'rrdcached' process is running with pid 4390

    Jul 6 11:37:24 omvFive monit[3897]: 'rootfs' filesystem flags changed to rw,relatime,space_cache,subvolid=5,subvol=/

    Jul 6 11:37:24 omvFive monit[3897]: 'omv-engined' process is not running

    Jul 6 11:37:24 omvFive monit[3897]: 'omv-engined' trying to restart

    Jul 6 11:37:24 omvFive monit[3897]: 'omv-engined' start: '/bin/systemctl start openmediavault-engined'

    Jul 6 11:37:25 omvFive systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request...

    Jul 6 11:37:25 omvFive systemd[1]: openmediavault-engined.service: Supervising process 4597 which is not our child. We'll most likely not notice when it exits.

    Jul 6 11:37:25 omvFive systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request.

    Jul 6 11:37:25 omvFive monit[3897]: 'omv-engined' started

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • That doesn't have anything helpful. Does it still remount readonly after a reboot?

    omv 5.6.13 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • You will need to look at syslog to see why it is remounting.

    So I rebuilt the box from scratch. Rebooting often. Hangs when I crate a mergerFS that contains a zPool.


    Jul 7 14:01:03 omvFive systemd-sysusers[607]: Creating group systemd-coredump with gid 995.

    Jul 7 14:01:03 omvFive blkmapd[615]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory

    Jul 7 14:01:03 omvFive systemd-sysusers[607]: Creating user systemd-coredump (systemd Core Dumper) with uid 995 and gid 995.

    Jul 7 14:01:03 omvFive systemd[1]: Starting Flush Journal to Persistent Storage...

    Jul 7 14:01:03 omvFive systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] Linux version 5.7.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6), GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30)

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.0-0.bpo.2-amd64 root=UUID=d32290be-f249-4ba2-897b-3731195220f4 ro quiet

    Jul 7 14:01:03 omvFive systemd[1]: Reached target Local File Systems (Pre).

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-provided physical RAM map:

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000008efff] usable

    Jul 7 14:01:03 omvFive systemd[1]: Started udev Coldplug all Devices.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000090000-0x000000000009ffff] usable

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000055d92fff] usable

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000055d93000-0x0000000055db2fff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000055db3000-0x0000000067acefff] usable

    Jul 7 14:01:03 omvFive systemd[1]: Starting Helper to synchronize boot up for ifupdown...

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000067acf000-0x0000000067bcefff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000067bcf000-0x0000000067dcefff] type 20

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000067dcf000-0x000000006dfcefff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000000006dfcf000-0x000000006edfefff] ACPI NVS

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000000006edff000-0x000000006effefff] ACPI data

    Jul 7 14:01:03 omvFive systemd[1]: Started Flush Journal to Persistent Storage.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000000006efff000-0x000000006effffff] usable

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000000006f000000-0x000000006fffffff] ACPI NVS

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000070000000-0x000000008fffffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x00000000aa000000-0x00000000aaffffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x00000000c5000000-0x00000000c5ffffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e0ffffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000027f1fffff] usable

    Jul 7 14:01:03 omvFive systemd[1]: Started Helper to synchronize boot up for ifupdown.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000000027f200000-0x000000027fffffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000010000000000-0x00000100201fffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x000002bf40000000-0x000002bf601fffff] reserved

    Jul 7 14:01:03 omvFive systemd[1]: Started Apply Kernel Variables.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000047e80000000-0x0000047ea01fffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] BIOS-e820: [mem 0x0000063dc0000000-0x0000063de01fffff] reserved

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] NX (Execute Disable) protection: active

    Jul 7 14:01:03 omvFive systemd[1]: Started udev Kernel Device Manager.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] efi: EFI v2.70 by Dell Inc.

    Jul 7 14:01:03 omvFive kernel: [ 0.000000] efi: ACPI=0x6effe000 ACPI 2.0=0x6effe014 MEMATTR=0x61c81aa0 SMBIOS=0x697ab000 SMBIOS 3.0=0x697a9000

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • Without Fuse


    root@omvFive:~# cat /etc/fstab

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # <file system> <mount point>   <type>  <options>       <dump>  <pass>

    # / was on /dev/sda2 during installation

    UUID=d32290be-f249-4ba2-897b-3731195220f4 /               ext4    noatime,nodiratime,errors=remount-ro 0       1

    # /boot/efi was on /dev/sda1 during installation

    UUID=45EF-1513  /boot/efi       vfat    umask=0077      0       1

    # swap was on /dev/sda3 during installation

    #UUID=b197aa8b-ddbc-46ce-a6d2-8ccf5b193303 none            swap    sw              0       0

    # >>> [openmediavault]

    # <<< [openmediavault]

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • With Simple Fuse (this works no RAIDed pools)

    root@omvFive:~# cat /etc/fstab

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # <file system> <mount point>   <type>  <options>       <dump>  <pass>

    # / was on /dev/sda2 during installation

    UUID=d32290be-f249-4ba2-897b-3731195220f4 /               ext4    noatime,nodiratime,errors=remount-ro 0       1

    # /boot/efi was on /dev/sda1 during installation

    UUID=45EF-1513  /boot/efi       vfat    umask=0077      0       1

    # swap was on /dev/sda3 during installation

    #UUID=b197aa8b-ddbc-46ce-a6d2-8ccf5b193303 none            swap    sw              0       0

    # >>> [openmediavault]

    /MZ7LH480HBHQ0D3:/ST8TB188ZR10P2GE:/WDC10TB2YJD8UYD /srv/d3b76cc0-1da9-4609-826e-a53c2ec1ace9 fuse.mergerfs defaults,allow_other,cache.files=off,use_ino,category.create=epmfs,minfreespace=4G,fsname=Store:d3b76cc0-1da9-4609-826e-a53c2ec1ace9,x-systemd.requires=/MZ7LH480HBHQ0D3,x-systemd.requires=/ST8TB188ZR10P2GE,x-systemd.requires=/WDC10TB2YJD8UYD 0 0

    # <<< [openmediavault

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • With RAIDed pools Fused in

    root@omvFive:~# cat /etc/fstab

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # <file system> <mount point>   <type>  <options>       <dump>  <pass>

    # / was on /dev/sda2 during installation

    UUID=d32290be-f249-4ba2-897b-3731195220f4 /               ext4    noatime,nodiratime,errors=remount-ro 0       1

    # /boot/efi was on /dev/sda1 during installation

    UUID=45EF-1513  /boot/efi       vfat    umask=0077      0       1

    # swap was on /dev/sda3 during installation

    #UUID=b197aa8b-ddbc-46ce-a6d2-8ccf5b193303 none            swap    sw              0       0

    # >>> [openmediavault]

    /MZ7LH480HBHQ0D3:/ST8TB188ZR10P2GE:/Vault:/WDC10TB2YJD8UYD:/Wharf /srv/2a5ca469-644e-4829-bc93-13b7ec9b3abd fuse.mergerfs defaults,allow_other,cache.files=off,use_ino,category.create=epmfs,minfreespace=4G,fsname=Store:2a5ca469-644e-4829-bc93-13b7ec9b3abd,x-systemd.requires=/MZ7LH480HBHQ0D3,x-systemd.requires=/ST8TB188ZR10P2GE,x-systemd.requires=/Vault,x-systemd.requires=/WDC10TB2YJD8UYD,x-systemd.requires=/Wharf 0 0

    # <<< [openmediavault]

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • I got it to work; I had to hand-build the fuse.mergerfs. I will dump a bulk of data into it and test it this weekend.

    With RAIDed pools Fused in Hand Built

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # <file system> <mount point>   <type>  <options>       <dump>  <pass>

    # / was on /dev/sda2 during installation

    UUID=d32290be-f249-4ba2-897b-3731195220f4 /               ext4    noatime,nodiratime,errors=remount-ro 0       1

    # /boot/efi was on /dev/sda1 during installation

    UUID=45EF-1513  /boot/efi       vfat    umask=0077      0       1

    # swap was on /dev/sda3 during installation

    #UUID=b197aa8b-ddbc-46ce-a6d2-8ccf5b193303 none            swap    sw              0       0

    # >>> [openmediavault]

    /WDC10TB2YJD8UYD:/ST8TB188ZR10P2GE:/DEL480GB0R402665:/Vault:/Wharf /srv/Store fuse.mergerfs defaults,allow_other,use_ino,dropcacheonclose=true,func.getattr=newest,category.create=epff,minfreespace=77G 0 0

    # <<< [openmediavault]

    Retiring OMV 4.x on intel
    Building OMV 5.x on AMD based Dell R5715

  • I had to hand-build the fuse.mergerfs.

    What do you mean by hand-build? Are you just constructing the fstab entry? If you just want to use different paths, you could use the mergerfsfolders plugin.

    omv 5.6.13 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

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