February 18, 20242 yr Updated from 6.12.6 to 6.12.8 last night and my system will not boot in any option (normal, safe mode, gui, etc). This has been a relatively stable server for the last few years. I have tried different USB ports, different USB drives, backups, fresh USB installs, removing all RAM and trying different sticks (ran a clean memtest a few weeks ago), unplugging everything (GPU, disks, HBA, etc), updating BIOS, downgrading BIOS. It hangs at various points from initialising the USB devices, verifying bzfirmware checksum, verifying bzimage checksum, creating static nodes in /dev, BERT: hardware error, differences between boot sector and its backup. The syslog doesnt write to USB and I am not sure how to enable it. With so many random errors I am leaning towards a motherboard issue but I have no idea. Any help or direction of what to do to provide more information? Edited February 18, 20242 yr by silverrick
February 18, 20242 yr Author Update: got my old computer out of the loft and ran it barebones (CPU, 1x stick RAM, no drives) with my original USB and it boots without issue...I am guessing hardware error but where do I start with this? Don't really fancy buying a new MOBO and its the same issue and nonreturnable once its been opened.
February 18, 20242 yr Author 2 minutes ago, JorgeB said: Does it work again if you revert to v6.12.6? Hi Jorge, Tried installing 6.12.6 on a USB and no boot. Same issues.
February 18, 20242 yr Community Expert That suggest it's not upgrade related, and it can be a hardware issue, start by running memtest.
February 18, 20242 yr Author 8 minutes ago, JorgeB said: That suggest it's not upgrade related, and it can be a hardware issue, start by running memtest. Running Memtest now on one stick of RAM. 6.12.6 and 6.12.8 both boot on the old computer no problems so guessing it is just coincidental timing on the update...how frustrating. If I have trialled it as barebones, is it likely the MOBO is the issue at a guess? Edited February 18, 20242 yr by silverrick Spelling
February 19, 20242 yr Community Expert 19 hours ago, silverrick said: is it likely the MOBO is the issue at a guess? Could be.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.