If you have a copy, I would do this:
1. run omv-firstaid
2. remove the extra line from cmdline.txt
3. reboot.
4. hope for the best and let us know if that works.
I bricked it previously, then restored the backup, run omv-firstaid, updated to 7.5.0 and it works fine, so the steps above should also work for you.
Display MoreHi, I have the same issue. I updated OMV on my RPi and now the IP address is nothing like my network so can't access it.
I have connected a screen and keyboard and have tried to run omv-firstaid. I can log in and bring up omv-firstaid but it just keeps saying permission denied when I try to do anything from omv-firstaid.
Any ideas?
Thanks
use sudo:
sudo pmv-firstaid
We can merge it with: update from 7.4.17 to 7.5.0 failed
OK Mrbroo , many thanks for the info.
Will try that too.
bballfanatic365 - you should be able to access terminal using a keyboard and monitor.
Hi,
I usually keep my OMV 7 pretty up-to-date.
A 7.5.0 update just appeared on the dashboard. I did the update and lost access to the dashboard, my network drive and SSH access.
Also my router doesn't show up the RPI4 connected any longer.
I will recover my last backup to the SD card, but is there any particular reason why it failed badly?
Was this solved?
I have the same issue. At the moment I just recovered the SD card from the backup, but it would be great to get it sorted.
Cannot exactly remember, but pretty sure I didn't follow the procedure with the the preinstall script.
Is there a way to fix it on the installed OMV?
Can I run the preinstall script now, reboot and then change the hostname?
I did try journal. That was the "dmesg from previous sessions" mentioned in my previous email.
Command journalctl -o short -k -b -1 gives me this result (showing only a few lines):
Mar 15 08:51:19 omv kernel: vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
Mar 15 08:51:19 omv kernel: vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])
Mar 15 08:51:19 omv kernel: vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])
Mar 15 08:51:19 omv kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
Mar 15 08:51:19 omv kernel: vc4-drm gpu: [drm] Cannot find any crtc or sizes
Mar 15 08:51:19 omv kernel: vc4-drm gpu: [drm] Cannot find any crtc or sizes
Mar 15 08:51:19 omv kernel: vc4-drm gpu: [drm] Cannot find any crtc or sizes
Mar 15 08:51:20 omv kernel: Bluetooth: hci0: BCM: features 0x2f
Mar 15 08:51:20 omv kernel: Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+-0190
Mar 15 08:51:20 omv kernel: Bluetooth: hci0: BCM4345C0 (003.001.025) build 0382
Mar 30 12:58:15 omv systemd-journald[283]: /var/log/journal/104fcb2b14ab4bf4a6df289113fe6cbb/system.journal: Journal file has been deleted, rotating.
Mar 30 12:58:15 omv systemd-journald[283]: Failed to write entry to /var/log/journal/104fcb2b14ab4bf4a6df289113fe6cbb/system.journal (27 items, 663 bytes), rotating before retrying: Identifier removed
Mar 30 12:58:15 omv kernel: watchdog: watchdog0: watchdog did not stop!
Mar 30 12:58:15 omv systemd-shutdown[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog0
Mar 30 12:58:15 omv systemd-shutdown[1]: Watchdog running with a timeout of 10min.
Mar 30 12:58:15 omv systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 30 12:58:15 omv systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 30 12:58:15 omv systemd-journald[283]: Received SIGTERM from PID 1 (systemd-shutdow).The alert was from the 29th of March, but nothing in the log above as you can see.
Thank you. Yes, noticed the description. Which log would it be? Syslog or kernel log available from the admin panel doesn't have anything around that date. I SSHed and checked older logs (kern.log.1, faillog, dmesg from previous sessions) and also couldn't find anything from that date. All I can find is either today's reboot or a previous boot weeks ago.
Hi,
I received a notification email from OMV yesterday:
Subject:
[omv] Monitoring alert -- Filesystem flags changed filesystem_srv_dev-disk-by-uuid-9b905237-9d8a-4a60-b86a-8eab1bce9483
Body:
The system monitoring needs your attention.
Host: omv
Date: Fri, 29 Mar 2024 09:07:42
Service: filesystem_srv_dev-disk-by-uuid-9b905237-9d8a-4a60-b86a-8eab1bce9483
Event: Filesystem flags changed
Description: filesystem flags changed from 'rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group' to 'ro,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group'
This triggered the monitoring system to: alert
After the alert email the filesystem became Read-Only.
This is a LUKS partition. No other issues were detected. No recent reboots or a power issues. No recent SMART alerts.
A reboot helped to solve the problem, but can someone explain why it happened and how to avoid this kind of issues in a future?
I use OMV since version 5.x (use LUKS since ver 6.x - around 1.5-2 years) and it has never happened to me before.
Many thanks
The person I mentioned earlier is also from New Zealand. Must be something to do with PayPal in your country.
On another forum I am someone just posted that his donation via PayPal to a different Open Source project was also rejected (not supported in his country), so it may be a PayPal thing...
BernH - as posted above - I've already tried "omv" and "omv.local". Also "omv.broadband". No luck.
Just noticed in the router status that it restarted at night due to an automatic upgrade from my ISP just before the OMV kernel log reported Link Down / Link Up.
It may be related to that.
Restarted it manually again. Disabled and re-enabled IP4 and IP6 DNS in a local network (The DNS is provided by the router). No luck.
Will investigate. If no solution then I'll live with it. No problem. It's funny that it's only 1 of my two RPI4s I have in a local network.
Hi all,
I have a weird problem this morning:
Cannot access the OMV dashboard and SSH using a hostname. I have it bookmarked, so always use the same link. I tired omv and omv.local - none of them work.
It works fine with IP.
Using SSH I have an error message:
ssh: Could not resolve hostname omv: Temporary failure in name resolution
when SSH using the IP the prompt reports as:
pi@omv:~ $
so with the hostname
I have another RPI in a home network (running something else, not OMV) and it works fine.
There were some automatic updates running yesterday evening (docker-compose-plugin, openmediavault-resetperms, rpi-eeprom).
Also yesterday I opened raspi-config, disabled predictable network interface names, but it asked me to restart, so I enabled it again.
Any suggestions?
Many thanks.
EDIT: found that in kernel.log if it helps:
28/02/2024, 04:47:22 kernel: bcmgenet fd580000.ethernet end0: Link is Up - 1Gbps/Full - flow control off
28/02/2024, 04:46:07 kernel: bcmgenet fd580000.ethernet end0: Link is Down
28/02/2024, 04:45:39 kernel: bcmgenet fd580000.ethernet end0: Link is Up - 1Gbps/Full - flow control off
28/02/2024, 04:45:32 kernel: bcmgenet fd580000.ethernet end0: Link is Down
Same things on RPI4. I did a fresh OM7 install a month ago (previously OMV6 32-bits, but wanted 64-bits, thus the fresh OMV7 install) and only eth0 shows up in the performance statistics.
The error says:
wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
What is the filesystem type on your disk?
Is it ext4 or something else which Linux supports natively?
Run the below command on the client machine and let us know what the output is:
showmount -e <omv_server_hostname_or_ip>
PS. Remember that for NFS4 you skip "export" bit when mounting, so something which looked like this in NFS3: "/export/my_disk" will become "/my_disk" in NFS4.
Login via SSH and follow the steps described on the Tailscale website:
Hi all,
While sorting out some issues with OMV recently I realized I run 32-bit version.
I want to upgrade to 64-bit soon.
Is there any option I can backup all or most of my configuration which I can restore after the new 64-bit installation?
(either via web dashboard or manually copying / backing up files)
Many thanks for your advice.
Just to let you all know - when I've been asked to apply the changes again I clicked cancel or revert (cannot remember how it is called) and it doesn't show the notification any longer. Also the /var/lib/openmediavault/dirtymodules.json file is empty. And the hostname is the new hostname I set up a few days ago. So I guess all is as it should be.
Tailscale. Can be run as a docker container, and does not need an open port in the router.
Or wireguard, available as an OMV plugin. It requires to open a port in the router.
You can install Tailscale directly in the OMV. This is what I use.
You don't need Docker for one package.
