So i got an secondhand Gigabyte X299 Designare EX flashed the BIOS to the latest available on Gigabyte website.
After installing the latest version of OpenSUSE on an new Kingston NV2 M.2 SSD always get this spam of errors during booting for less than a half-a-sec:
After that, OpenSUSE Boot Menu appears, like nothing happened. and can boot OpenSUSE normally but slower than it should, i can run the same distro with an basic SATA SSD and a AMD FM2+ machine way faster than this.
System Specs:
Gigabyte Designare X299 EX motherboard, (Latest BIOS)
Boot Drive: Kingston NV2 1TB - Formatted as XFS.
Kingston Fury DDR4-3200 32GB
Intel Core i7-9800X.
I’ve reading in the Manjaro forums seems like Grub has an history of not liking booting XFS partitions, So i want to consider my choices before nuking the partition and reinstall Tumbleweed but to ext4 instead.
To add more issues: i’ve getting weird ACPI errors reported in the dmesg logs,i’m believing the Gigabyte X299 workstation boards had sketchy UEFI BIOS implementations, and sometimes if i plug an ethernet cable after booting causes the system to freeze.
I’ve never had an XFS filesystem. ISTR before BTRFS became default that openSUSE defaults were EXT4 for / and if a separate /home/, XFS for it. I’m sure Google could find you an explanation why. I don’t know, and have only ever used EXTx on my hundreds of Linux native filesystems. I suggest to install again and not use XFS for /. I’m writing this from a GA-B250M-D3H (Kaby Lake, i3-7100T, ZTC M.2 128GB NVME).
As the messages say, grub gets request to read outside of partition boundaries. It could be due to filesystem corruption, it could be due to grub misinterpreting data on the partition in question. You need to find out what triggers it. Go to grub CLI, try to access each partition (e.g. listing it contents).
Decided reinstall OpenSUSE Tumbleweed again, but this time i choose EXT4 as my main partition instead, not longer i have those “attempt to read or write outside of partition” error spam anymore.
Still have the ACPI BIOS errors, but i think i have to live with it, my main suspicion is at the time of X299 BIOS were just bad, and Gigabyte being the worst.
