Well, I'm going to close this thread, as things are still working, but there was no real solution to the problem.
Posts by TheLostSwede
-
-
No, that's normal and that is the reason why Linux mounts the drive's by UUID instead of dev.
When a PC boots, it reads and assigns the drive letters as "first come, first serve" which means that it willl never be the same drive to the same letter.
You probably are thinking "Windows" that always assigns a drive to a letter (because it's done under the hood).
Just check your fstab and you see what this is all about:
cat /etc/fstab
You mean this soup?
Code
Display More# /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). # # systemd generates mount units based on this file, see systemd.mount(5). # Please run 'systemctl daemon-reload' after making changes here. # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sde2 during installation UUID=45631327-7283-45c7-8cc9-99a6182da008 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sde1 during installation UUID=9CAD-DB4C /boot/efi vfat umask=0077 0 1 # swap was on /dev/sde3 during installation UUID=37b25def-093a-4884-a2c8-5c14865b5965 none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-uuid/4e2840af-9b3c-44f4-b54a-7cc8091bcc70 /srv/dev-disk-by-uuid-4e2840af-9b3c-44f4-b54a-7cc8091bcc70 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-uuid/2f19e3a4-88ed-4ee3-8c21-0f8bc593a2b7 /srv/dev-disk-by-uuid-2f19e3a4-88ed-4ee3-8c21-0f8bc593a2b7 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-uuid/c69d16fb-9343-4111-9a09-1eaaec7317e2 /srv/dev-disk-by-uuid-c69d16fb-9343-4111-9a09-1eaaec7317e2 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-uuid/4908162a-9784-44cc-8ad1-d71be0a9b289 /srv/dev-disk-by-uuid-4908162a-9784-44cc-8ad1-d71be0a9b289 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /srv/dev-disk-by-uuid-4e2840af-9b3c-44f4-b54a-7cc8091bcc70:/srv/dev-disk-by-uuid-2f19e3a4-88ed-4ee3-8c21-0f8bc593a2b7:/srv/dev-disk-by-uuid-c69d16fb-9343-4111-9a09-1eaaec7317e2 /srv/mergerfs/jbod fuse.mergerfs category.create=epmfs,minfreespace=4G,fsname=jbod:fdd1b0fb-366a-44da-876e-a9b101ae71e7,defaults,allow_other,cache.files=off,use_ino,x-systemd.requires=/srv/dev-disk-by-uuid-4e2840af-9b3c-44f4-b54a-7cc8091bcc70,x-systemd.requires=/srv/dev-disk-by-uuid-2f19e3a4-88ed-4ee3-8c21-0f8bc593a2b7,x-systemd.requires=/srv/dev-disk-by-uuid-c69d16fb-9343-4111-9a09-1eaaec7317e2 0 0 # <<< [openmediavault]
-
I still seem to have write access, but why are my drives jumbled again?
The OS drive is now sdd again after another reboot. This can't be right, can it?
I thought these things were static.
Code
Display MoreNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.6T 0 disk └─sda1 8:1 0 3.6T 0 part /srv/dev-disk-by-uuid-2f19e3a4-88ed-4ee3-8c21-0f8bc593a2b7 sdb 8:16 0 3.6T 0 disk └─sdb1 8:17 0 3.6T 0 part /srv/dev-disk-by-uuid-4e2840af-9b3c-44f4-b54a-7cc8091bcc70 sdc 8:32 0 3.6T 0 disk └─sdc1 8:33 0 3.6T 0 part /srv/dev-disk-by-uuid-c69d16fb-9343-4111-9a09-1eaaec7317e2 sdd 8:48 0 55.9G 0 disk ├─sdd1 8:49 0 512M 0 part /boot/efi ├─sdd2 8:50 0 54.4G 0 part / └─sdd3 8:51 0 976M 0 part [SWAP] sde 8:64 0 3.6T 0 disk └─sde1 8:65 0 3.6T 0 part /srv/dev-disk-by-uuid-4908162a-9784-44cc-8ad1-d71be0a9b289
-
-
Clear your browser cache or force reload with Ctrl+Shift+R
Oh boy, that's embarrassing. Thanks.
-
Different bug now.
I guess I should report this in a separate thread though?
Had this happen before as well.
Clicking on storage, I get thrown here and no matter what I do, I can't get in to any of the sub-categories outside of system or users, as I just get kicked back to this screen. Rebooting doesn't solve it.
-
-
Run omv-upgrade from CLI.
Yeah, I've done that before, just wasn't sure if that was part of what caused the OS drive to be read only.
Just updated to see, but I doubt that's it.
All good so far, time to install OMV-Extras.
-
Ok, clean install, everything looks right.
Code
Display Moreroot@OMV:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.6T 0 disk └─sda1 8:1 0 3.6T 0 part sdb 8:16 0 3.6T 0 disk └─sdb1 8:17 0 3.6T 0 part sdc 8:32 0 3.6T 0 disk └─sdc1 8:33 0 3.6T 0 part sdd 8:48 0 3.6T 0 disk └─sdd1 8:49 0 3.6T 0 part sde 8:64 0 55.9G 0 disk ├─sde1 8:65 0 512M 0 part /boot/efi ├─sde2 8:66 0 54.4G 0 part / └─sde3 8:67 0 976M 0 part [SWAP]
Installing updates.
For some reason, linux-image-5.16.0-0.bpo.4-amd64 5.16.12-1~bpo11+1 and linux-image-amd64 5.16.12-1~bpo11+1 never wants to install.
Besides that, all updates install just fine.
System rebooted and working as intendend so far.
-
Something really odd is going on, as the drives change name/mount points.
The OS SSD is normally sde, but today it came up as sdd.
I could mount it now, but the last command still failed.
Different failure message though.
Code
Display Moreroot@OMV:~# systemctl status openmediavault-engined.service ● openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2022-04-15 07:39:38 BST; 3min 6s ago Main PID: 1177 (code=exited, status=1/FAILURE) CPU: 63ms Apr 15 07:39:37 OMV systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request... Apr 15 07:39:38 OMV systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request. Apr 15 07:39:38 OMV omv-engined[1177]: Failed to bind socket: Address already in use Apr 15 07:39:38 OMV omv-engined[1177]: Apr 15 07:39:38 OMV systemd[1]: openmediavault-engined.service: Main process exited, code=exited, status=1/FAILURE Apr 15 07:39:38 OMV systemd[1]: openmediavault-engined.service: Failed with result 'exit-code'.
After a reboot, the OS SSD is back as sde and the filesystem is read only.
-
Nope, not working. I tried remounting the OS drive, which is sde2 for some reason now.
Could it have something to do with folder2ram? I forgot I had installed that.
Code
Display Moreroot@OMV:~# systemctl status openmediavault-engined.service ● openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2022-04-14 16:50:50 BST; 38s ago Main PID: 2261 (code=exited, status=1/FAILURE) CPU: 48ms Apr 14 16:50:50 OMV systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request... Apr 14 16:50:50 OMV systemd[1]: openmediavault-engined.service: Supervising process 2261 which is not our child. We'll most likely not > Apr 14 16:50:50 OMV systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request. Apr 14 16:50:50 OMV omv-engined[2261]: Failed to bind socket: Read-only file system Apr 14 16:50:50 OMV omv-engined[2261]: Apr 14 16:50:50 OMV systemd[1]: openmediavault-engined.service: Main process exited, code=exited, status=1/FAILURE Apr 14 16:50:50 OMV systemd[1]: openmediavault-engined.service: Failed with result 'exit-code'.
-
Did you try to fix the mount of the mergerfs? This is a storage device and it can not be mounted according to the logs.
But a so much of the log file is missing, one can only guess.
I wouldn't have the first clue how to do that. I'm not a Linux expert.
I've reinstalled OMV about half a dozen times by now and this happens every time after I update OMV and installed mergerfs.
Going to reinstall again tomorrow and we'll see what happens.
-
It tells you the config inside the systemd unit is wrong. Does not tell you anything about files in the merger fs.
Use the search engine. This has been an issue here before.
Or do you mean, your problem is solved?
No, the problem isn't solved, as I don't know why or how the drive goes into read only mode.
I thought that was due to something on the storage drives.
-
I do not know if this is the reason:
CodeApr 9 00:09:08 OMV systemd[1]: local-fs.target: Cannot add dependency job, ignoring: Unit srv-mergerfs-jbod.mount failed to load properly: File name too long.
but try to fix it (by editing /etc/fstab) after you remount the os disk rw.
If the system crashes, before the flashmemory plugin writes the logs back to the hard disk, these logs are lost.
The drives are empty now, so that's something old from before I wiped them.
I thought the old unionfs install was part of the problem.
I would guess this is no longer an issue, since I changed to mergerfs.
-
You need to check the syslog. If the kernel decides to remount the root file system as read-only, you will find a log entry.
Will the attached do?
I've installed OMV Extras and Mergerfs as well as SnapRAID, but beyond that, I haven't installed anything else.
-
Did you check your filesystem?
How? I mean, I don't have a clue what has gone wrong and keeps going wrong.
Every single time I've installed OMV 6 and after the first reboot, this happens.
Code
Display Moreroot@OMV:~# fsck fsck from util-linux 2.36.1 e2fsck 1.46.5 (30-Dec-2021) /dev/sdd2: clean, 43241/3571712 files, 852181/14272512 blocks e2fsck 1.46.5 (30-Dec-2021) /dev/sda1 is mounted. e2fsck: Cannot continue, aborting. e2fsck 1.46.5 (30-Dec-2021) /dev/sdc1 is mounted. e2fsck: Cannot continue, aborting. e2fsck 1.46.5 (30-Dec-2021) /dev/sde1 is mounted. e2fsck: Cannot continue, aborting. e2fsck 1.46.5 (30-Dec-2021) /dev/sdb1 is mounted. e2fsck: Cannot continue, aborting.
-
anything in the nginx logs?
In a recent thrad the directory /run/php was missing, can you check that
ls -l /run/php
Coderoot@omv:~# ls -l /run/php/ insgesamt 4 srw------- 1 www-data www-data 0 2. Apr 13:55 php7.4-fpm-openmediavault-webgui.sock -rw-r--r-- 1 root root 4 2. Apr 13:55 php7.4-fpm.pid srw-rw---- 1 www-data www-data 0 2. Apr 13:55 php7.4-fpm.sock lrwxrwxrwx 1 root root 30 2. Apr 13:55 php-fpm.sock -> /etc/alternatives/php-fpm.sock
-
Code
Display More● php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-04-12 19:57:46 BST; 1min 43s ago Docs: man:php-fpm7.4(8) Process: 1434 ExecStartPost=/usr/lib/php/php-fpm-socket-helper install /run/php/php-fpm.sock /etc/php/7.4/fpm/pool.d/www.conf 74 (c> Main PID: 1346 (php-fpm7.4) Status: "Processes active: 0, idle: 2, Requests: 0, slow: 0, Traffic: 0req/sec" Tasks: 3 (limit: 19002) Memory: 16.4M CPU: 46ms CGroup: /system.slice/php7.4-fpm.service ├─1346 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf) ├─1432 php-fpm: pool www └─1433 php-fpm: pool www Apr 12 19:57:45 OMV systemd[1]: Starting The PHP 7.4 FastCGI Process Manager... Apr 12 19:57:46 OMV systemd[1]: Started The PHP 7.4 FastCGI Process Manager.
-
Code
Display Moreroot@OMV:~# systemctl status openmediavault-engined.service ● openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-04-12 18:47:19 BST; 59s ago Process: 2009 ExecStart=/usr/sbin/omv-engined (code=exited, status=0/SUCCESS) Main PID: 2011 (code=exited, status=1/FAILURE) CPU: 48ms Apr 12 18:47:19 OMV systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request... Apr 12 18:47:19 OMV systemd[1]: openmediavault-engined.service: Supervising process 2011 which is not our child. We'll most likely not not> Apr 12 18:47:19 OMV systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request. Apr 12 18:47:19 OMV omv-engined[2011]: Failed to bind socket: Read-only file system Apr 12 18:47:19 OMV omv-engined[2011]: Apr 12 18:47:19 OMV systemd[1]: openmediavault-engined.service: Main process exited, code=exited, status=1/FAILURE Apr 12 18:47:19 OMV systemd[1]: openmediavault-engined.service: Failed with result 'exit-code'.
-
Ok, I have no idea what's going on, but I keep running into this issue after I reboot my NAS with OMV 6.
It prevents me from logging in through the web UI and I have no idea why it's happening.
It seems like the file system goes into read only mode by itself and this has happened several times in a row and keeps happening.
Yes, I'm aware this is a pre-release OS, but I wasn't going to install 5.x again after my NAS trashed itself for some weird reason explained in a different thread.
Any suggestions would be welcome.
Coderoot@OMV:~# dpkg -l | grep openm ii openmediavault 6.0.21-1 all openmediavault - The open network attached storage solution ii openmediavault-flashmemory 6.1 all folder2ram plugin for openmediavault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-mergerfs 6.1.1 all mergerfs plugin for openmediavault. ii openmediavault-omvextrasorg 6.0.8 all OMV-Extras.org Package Repositories for OpenMediaVault ii openmediavault-snapraid 6.0.4 all snapraid plugin for OpenMediaVault. ii openmediavault-usbbackup 6.0-10 all openmediavault USB/eSATA backup plugin