OMV 4 problems after install

Hi,

after strarting installation directly from the installation media did not succedd (see thread "Graphics issue when starting install"), I followed the recommended practice:

• install intended system drive in anoither computer
• perform initial install until 1st reboot (worked perfectly)
• re-install the prepared system drive into the NAS box

While this generally worked and resulted in a "somehow" useable system, I faced several problems, which I were not able to solve all, so any help is appreciated..

• Network interface name mismatch, so no network available - solved by manual correction eth0 => eno1
• Missing firmware "kbl_dmc_ver1_04.bin" - solved my manual installation
• always 4 "machiche check events" upon boot, but system is stable ... see below
• systemd timeout because system harddisk does not become available - but afterwards the disk including all partitions is ok, but timeout is 1min 30 seconds ... see below
• boot ends up in "emergency mode" (I assume the result of the above issues 3. and 4.), but if I continue with CTRL-D I end up in an useable system, e.g. webgui working, ...

Concerning the machine check exeptions, this is what the system log reads bootlog.txt:

Aug 18 17:07:51 sal kernel: smpboot: CPU0: Intel(R) Pentium(R) Gold G5420T CPU @ 3.20GHz (family: 0x6, model: 0x9e, stepping: 0xa)
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: Machine check events logged
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae00000000801136
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ff00 MISC 43040000086 
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: Machine check events logged
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee00000000801136
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ff40 MISC 43040000086 
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee00000000801136
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ff80 MISC 43040000086 
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee00000000801136
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ffc0 MISC 43040000086 
Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4

As explained, the messages always appear at the same point on booting and the system runs stable, so I guess that these are no random HW failures ? Can they be ignored ?

Concerning the non-available harddisk, the system log reads bootlog.txt:

Aug 18 17:09:21 sal systemd[1]: dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device: Job dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device/start timed out.
Aug 18 17:09:21 sal systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device.
-- Subject: Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device has failed.
-- 
-- The result is timeout.
Aug 18 17:09:21 sal systemd[1]: Dependency failed for /dev/disk/by-uuid/2f6b6f87-373b-4f83-bbbd-7a0627771193.
-- Subject: Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.swap has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.swap has failed.
-- 
-- The result is dependency.

Additional info:

• systemctrl --type device shows no failing unit, also for all partitions on the system drive (sda1,sda2,sda3) systemctrl-device.txt
• systemd-analyze blame shows 1min 30.397s dev-sda2.device, the other times to init are absolutely acceptable systemd-analyze_blame.txt.

As said, the boot stops in "emergency mode", from which I can continue with CTRL-D which results in an overall running system.

The system is based on a Pentium Gold G5420T ("Coffe Lake") on a Fujitsu D3641-S mainboard, 8G ECC. Maybe that is too new for the underlying Debian "Stretch" ?
I will continue by checking if a plain Debian "Stretch" install succeeds, but any comments or help is highly apprechiated.

Regards, Sven

Quote from Wumpus

The system is based on a Pentium Gold G5420T ("Coffe Lake") on a Fujitsu D3641-S mainboard, 8G ECC. Maybe that is too new for the underlying Debian "Stretch" ?

Well, this seems to be the case.
Just after creating the thread, I relized that OMV 5.0.5 is out, albeit still being a beta (though not indicated as one), so I gave it a try. Result:

• direct booting from installation media worked (no graphical issues)
• installation w/o problems
• at boot, I still have those machine check exceptions - at the same point of time
• no missing firmware
• no hard disk timeouts, very quick booting

Well, so this solves a lot. However, still beta, and all those extra-addons like zfs won't work ?

Regards, Sven

Quote from ryecoaaron

zfs is ported. You can see status of porting at these two links.

Yeap, thanks for the info. However, just trying a plain installation by installing omv-extras and then just selecting the zfs-plugin from the GUI failed, so I think I need to dig in it somewhat deeper; but that is out-of-scope of this thread.

Quote from ryecoaaron

The following should fix it.

Thanx, that did it. . Just spent a like...
Didn't try proxmox yet ... it is 4.15, while I currently have 4.19 (with OMV 5.05) which is long-term maintenance. However lets see when I've got some time I might test that.

Regards, Sven