Booting from GRUB to an endless loop after OMV7 installation from scratch.

    I tried "nvme_core.default_ps_max_latency_us=1410" only with the Samsung SSD. (The Transcend SSD was mounted in the bottom M.2 slot because it exclusively supports SATA SSDs. The GRUB default settings have not been touched.)

    I will try the bottom M.2 slot with the Samsung SSD.

    Again no success.

    Quote


    It really looks like this is a dead end for OMV on this hardware combination

    This seems to be true.


    P.S. I did the Transcend SSD test with a default Debian 12.9 installation. So OMV and its host-OS are not running on my Biostar motherboard if a M.2 slot is in use. <X


    Addendum: Now I tried also a FeeBSD based NAS. Its installer was not able to do its work "Waiting for LiveCD retries exhausted! ... The operating system has halted.". This is even less as OMV was doing. Why to hell is MS Windows able to use this HW but "all other" not???

    The board & its firmware are probably only certified for MS Windows and never tested on anything else. Other brands are not much different but the absence of hits on "linux + biostar" is not encouraging as opposed to the likes of ASUS, ASROCK, MSI & GIGABYTE where Linux runs w/out problem. Linux doesn't always work on the latest and greatest hardware, but your combo has been around for awhile although I believed Intel 12th gen has had its problems.


    Yet you know OMV7 installs with the nvme in the m.2 slot, and can boot & run with the nvme drive in an usb enclosure. What's odd is that the installation succeeded. Something I never suggested looking at before is the installer logs that should still be on your nvme in the  /var/log/installer directory.


    Code
    root@ovm-nvme:/var/log/installer# ls -l
total 768
drwxr-xr-x 2 root root   4096 Mar  7 16:45 cdebconf
-rw-r--r-- 1 root root     62 Mar  7 16:45 firmware-summary
-rw-r--r-- 1 root root  33552 Mar  7 16:45 hardware-summary
-rw-r--r-- 1 root root    162 Mar  7 16:45 lsb-release
-rw------- 1 root root 299181 Mar  7 16:45 partman
-rw-r--r-- 1 root root  63454 Mar  7 16:45 status
-rw------- 1 root root 367024 Mar  7 16:45 syslog
root@ovm-nvme:/var/log/installer#


    So if there are no pcieport or other nvme related errors in /var/log/installer/syslog, why is that?


    Looking again at the output you posted in #56 the pcieport complaining is 0000:00:06.0 whereas a later message refers to the nvme on 0000:01:00.0  If you can setup it to boot and check the output oflspcii, it would be useful to eliminate that doubt. The device number [8086:464d] id's as the intel 12th gen pcie 4 controller at 0000:00:06.0

    Around 3.200 rows, see pastebin of syslog; the nvme excerpts are following.

    I searched also for

    1. fail,
    2. error and
    3. warning

    1. : 27 times found

    2.: 10 times found

    3.: 93 times found

    _Michael_


    As I expected, the installer syslog shows none of the pcieport AER errors. The installer probes the hardware differently to the boot kernel and initrd.


    Two thoughts:


    1. Set the pcie link speed of the m.2 slot to gen3 in BIOS rather have it use "auto". Does it make any difference to the boot errors?

    2. Booting from the PM991 in external enclosure, test your other nvme in the m.2 slot can reliably be used as a data disk after wiping, creating and mounting a filesystem on it in OMV7.

    Quote from Krisbee

    ...

    1. Set the pcie link speed of the m.2 slot to gen3 in BIOS rather have it use "auto". Does it make any difference to the boot errors?

    2. Booting from the PM991 in external enclosure, test your other nvme in the m.2 slot can reliably be used as a data disk after wiping, creating and mounting a filesystem on it in OMV7.

    1.: The PCIe link speed is currently set to Gen1. Before (until yesterday) it was auto. I guess "gen3" is therfore don't care?

    2.: I do not have a 2nd NVMe M.2., it is a SATA M.2. In case this is don't care: I still do not exactly know what "wiping" means?

    Final Words

    The Biostar mainboard / motherboard 'Biostar B660T-Silver' is not able to run

    1. some Debian based Linux (tried with openmediavault_7.4.17-amd64.iso and debian-12.9.0-amd64-netinst.iso) and
    2. FreeBSD (tried with XigmaNAS-x64-LiveCD-13.3.0.5.10153.iso)

    if a M.2 NVMe SSD or SATA SSD is in use at its onboard M.2 slots.


    At the end I did this: I used a M.2 SATA SSD in an USB enclosure, it is connected to an internal USB port.


    Addendum 2025-06-28:

    AVOID Biostar motherboards They broke the storage support ...

    Edited once, last by _Michael_: Link about Biostar and Linux storage issue inserted. ().

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login