I had the same problem just now trying to boot the gparted live ISO from Grub (on OMV7) using the instructions provided by gparted (https://gparted.org/livehd.php). I gave up and booted it from a USB stick instead.
Posts by hmoff
-
-
Active: active (exited) since Sat 2025-11-22 04:00:49 CET; 7h ago
Check postfix's logs and/or journal to see why it's not running.
-
Yes, indeed. I thought I wrote from the beginning, that the problem is only with the pcie x1 slot
You said the NVMe was also affected though, I am not seeing any disruption to that when the ethernet is down.
-
OK, nothing interesting in there unfortunately. It's just full of virtual interfaces going up and down which is all due to starting and stopping Docker containers usually. It's a general linux issue not OMV specific from what I see so you might be better off asking in a general linux questions Reddit for example.
-
There's nothing interesting in there yet, but does more appear when the slowdowns start? The log only shows the first 14 seconds after booting.
-
I'm a bit of a noob, not really sure what I am looking for. Lots of messages about devices being renamed, entering different states and leaving promiscuous mode.
I was wondering if there are any errors. But it sounds like you didn't see any. Feel free to post the logs, there's nothing sensitive in the kernel log generally.
-
Maybe hmoff You can just Yours cat /etc/default/grub if You have that option also in Your grub setting - this would explain, why You didn't have such problem
No I only have the default. But I don't have anything in the PCIe x1 slot currently so maybe that is the difference.
-
As the problem started after I rebooted OMV I now think the HDD has failed. I popped in another SD card with a new OMV7 installation and it initially recognised sda1 but then it disappeared.
The kernel logs should give you some idea what is going on here.
-
Are there any relevant messages in the kernel log? From a terminal (ssh) run dmesg.
-
For the A+E Key (Wlan + BT) m.2 slot, there are also SATA cards with two SATA ports. Maybe it's better to use one in your case.
I'm using a 2-port JMB58x card in the E key (Wifi) slot. I have a 4-port ASMedia card to go in the x1 slot but haven't installed it yet as I don't need the extra ports right now. So maybe my test wasn't helpful for you anyway.
Can You please tell me what version of BIOS do You have? And when You bought the mobo, where and model of Your expansion pcie card?
I bought it from Amazon.de last December. For the BIOS version `dmidecode` says
CodeHandle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: 0405 Release Date: 12/13/2023The other decode says
Code
Display More# dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 3.5.0 present. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: PRIME N100I-D D4 Version: Rev 1.xx Serial Number: 240639649200789 Asset Tag: Default string Features: Board is a hosting board Board is replaceable Location In Chassis: Default string Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x001D, DMI type 41, 11 bytes Onboard Device Reference Designation: Onboard IGD Type: Video Status: Enabled Type Instance: 1 Bus Address: 0000:00:02.0 Handle 0x0020, DMI type 10, 6 bytes On Board Device Information Type: Video Status: Enabled Description: Onboard IGD -
Just tried left it for 90 minutes and it worked perfectly.
-
The Host OMV tagged interface esp1.50 doesn't seem to have an acquired an ip address these should have been served to this VLAN via the pfSense DHCP server.
Acquired inside the Docker container or outside? I was reading about Docker MACVLAN just recently. It doesn't have a DHCP client. Don't expect containers to get an IP address allocated by an external DHCP server. Docker will allocate IP addresses from a reserved range you configure.
-
I use ZFS for encryption on my NAS, because it also has RAID and compression and snapshots built-in - perfect for backups. Plus you can have a mix of encrypted and unencrypted datasets.
-
My assumption is that OMV only works one way: from the webUI ---> to the os files, but not the other way, so a modification in fstab does not launch a modification in config.xml
Yes, OMV is the master of the config files (via Salt), don't edit the config files directly. They are either entirely or partially owned by OMV, in the case of fstab you can see there is a section that is maintained by OMV but the rest of the file is editable.
-
They'll be in /etc/openmediavault/config.xml.
-
I'm not sure if 15second is enought.
Hmm. The kernel logged that the link was down. I will try longer.
-
I unplugged the ethernet from the N100I-D and reconnected it 15 seconds later - no other messages from the kernel, all working fine.
-
I'm using the standard Debian kernel - 6.12.43+deb12-amd64. I use Jellyfin but I don't care about transcoding, so I don't know if the hardware acceleration works. But 6.12 is newer than the 6.8 you're using.
-
I see the same PCI tree (I have the same board). I will try disconnecting the network cable when I can and see if that upsets the SATA controller for me too.
Do you have the backports kernel installed - 6.12?
-
After I bought this mobo I launched memtest for 24h (as always do for new hardware) to make sure that everything works smooth.
And after a long period of time I see, that the problems occurs only in specific situation:
Link down or unplugged cable RJ45 -> NIC is propagating this on the PCie bus and (I don't understand why) stuff connected to the Pcie x1 bus is going to D3Cold state from which it can't come back to live.
Uh, maybe the NIC is behaving badly and killing the PCIe bus. I see that the on-board Realtek NIC, the NVMe and the SATA controller I have in the WiFi slot (m.2 e-key) are all on the same PCI bus.
I haven't had the issue you mentioned but also my network link stays up always. I can't try disconnecting it right now deliberately.
You could get another NIC for the x1 slot, or an e-key NIC, or even USB.
