I have no Boot since updating my BIOS on my X570 Taichi. The Bios P1.80 and AGESA Combo-AM4 1.0.0.3 ABB was supposed to improve Linux compatibility and I upgraded. Now UNRAID won't boot. It now does not even Boot after I downgrade BIOS. I suspect the problem lies in the microcode since the microcode version is not changing after the BIOS downgrade.

 

I've attached my Bootlog.

Also typing out the relevant part so anyone can find this topic if they stumble across it:

clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc-early' as unstable because the skey is too large:

clocksource : 'hpet' wd_now: 1298e98 wd_last 9b0ae7 mask: ffffffff

clocksource: 'tsc-early' cs_now: 2948e64e14 cs_last: 28d6a75fb6 mask: ffffffffffffffff

tsc: Marking TSC unstable due to clocksource watchdog

 

During this message all USB power goes out. The bootlog is visible for like 20 seconds after that and then it just automatically reboots. Infinite loop basically.

 

I am hoping you guys could help me out here. At this point I am willing to try anything to get UNRAID up and running again. I suspect I won't be the only one having problems depending on where the problem in the AMD BIOS is.

 

Any help would be greatly appreciated. Thanks!

Can you boot another OS on this machine, such as a Linux distro?

I tried booting Proxmox and Ubuntu. Both were crashing instantly on startup.

 

But after lots of trial and error I finally found the culprit: The Mellanox ConnectX-2 MNPH29C-XTR is seemingly causing the problem. It was working perfectly before. Now, how a BIOS/microcode update is causing this, I don't know.

 

I might try to update the firmware on the card. That will require some setup since the process is not straightforward. But for now I am happy that I can boot.

Edited August 9, 20196 yr by unbalanced
typo

I also ran into this but mine cut off on the "tsc-early" line - I had to do a hard power down and power back on to get past the boot loop. Im beginning to think theres something about these x570 boards that doesn't reboot like others ive used. It seems like I usually run into problems if I just let it reboot, but things are much more stable with a power down / power on

@unbalanced - How did you figure out what was causing the issue? I do not have any additional network cards, but I am still plagued by this issue, which I only recall happening with 6.8.2... Maybe i'll try to downgrade and see if rebooting works normally.

1 minute ago, johnsanc said:

@unbalanced - How did you figure out what was causing the issue? I do not have any additional network cards, but I am still plagued by this issue, which I only recall happening with 6.8.2... Maybe i'll try to downgrade and see if rebooting works normally.

I figured it out by just unplugging stuff until it worked :P

 

Haven't encountered the error since updating bios and changing network card. I am still on 6.8.1 though...