OMV 4 problems after install

    • OMV 4.x
    • Resolved
    • 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:
      1. install intended system drive in anoither computer
      2. perform initial install until 1st reboot (worked perfectly)
      3. 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..
      1. Network interface name mismatch, so no network available - solved by manual correction eth0 => eno1
      2. Missing firmware "kbl_dmc_ver1_04.bin" - solved my manual installation
      3. always 4 "machiche check events" upon boot, but system is stable ... see below
      4. 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
      5. 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 (full log attached):

      Source Code

      1. Aug 18 17:07:51 sal kernel: smpboot: CPU0: Intel(R) Pentium(R) Gold G5420T CPU @ 3.20GHz (family: 0x6, model: 0x9e, stepping: 0xa)
      2. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: Machine check events logged
      3. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae00000000801136
      4. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ff00 MISC 43040000086
      5. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
      6. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: Machine check events logged
      7. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee00000000801136
      8. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ff40 MISC 43040000086
      9. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
      10. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee00000000801136
      11. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ff80 MISC 43040000086
      12. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
      13. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee00000000801136
      14. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: TSC 0 ADDR 8f27ffc0 MISC 43040000086
      15. Aug 18 17:07:51 sal kernel: mce: [Hardware Error]: PROCESSOR 0:906ea TIME 1566140868 SOCKET 0 APIC 0 microcode b4
      Display All
      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 (full log attached):

      Source Code

      1. 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.
      2. Aug 18 17:09:21 sal systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device.
      3. -- Subject: Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device has failed
      4. -- Defined-By: systemd
      5. -- Support: https://www.debian.org/support
      6. --
      7. -- Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.device has failed.
      8. --
      9. -- The result is timeout.
      10. Aug 18 17:09:21 sal systemd[1]: Dependency failed for /dev/disk/by-uuid/2f6b6f87-373b-4f83-bbbd-7a0627771193.
      11. -- Subject: Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.swap has failed
      12. -- Defined-By: systemd
      13. -- Support: https://www.debian.org/support
      14. --
      15. -- Unit dev-disk-by\x2duuid-2f6b6f87\x2d373b\x2d4f83\x2dbbbd\x2d7a0627771193.swap has failed.
      16. --
      17. -- The result is dependency.
      Display All
      Additional info:
      • systemctrl --type device shows no failing unit, also for all partitions on the system drive (sda1,sda2,sda3) (output attached)
      • systemd-analyze blame shows 1min 30.397s dev-sda2.device, the other times to init are absolutely acceptable (output attached).
      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
    • Wumpus wrote:

      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
    • Wumpus wrote:

      all those extra-addons like zfs won't work ?
      zfs is ported. You can see status of porting at these two links.
      forum.openmediavault.org/index…?postID=186122#post186122
      bintray.com/openmediavault-plugin-developers/usul
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Wumpus wrote:

      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.
      The plugin can't fix this. zfs-dkms builds the zfs module and depends on linux-headers. But apt installs the headers after zfs-dkms sometimes causing the module compiling to fail. The following should fix it.

      apt-get -f install (might fail but that is ok because it should finish compiling the zfs module)
      modprobe zfs (load the zfs module so the other zfs packages can finish installing)
      apt-get -f install

      -or-

      You can install the proxmox kernel from the omv-extras kernel tab which eliminates the need to build the zfs module. This will also use the newer 0.8.1 version of zfs that includes encryption.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Wumpus wrote:

      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.
      The proxmox kernel on OMV 5.x is 5.0 (from proxmox 6.x).
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Users Online 1

      1 Guest