Hi,
let me explain the title. I installed OMV on my designated mainboard
https://www.aliexpress.com/ite…VGA-HDMI/32574624109.html
which a friend brought from China. So I though I'd replace my aging Qnap with some DIY NAS.
I install from USB to a 1TB mSATA (Samsung EVO 850) on the board
The 1st install went fine, I could boot the mSATA, configure the web frontend, conect via ssh.. all well.
Then I got bold and did apt update && apt upgrade
The machine continued to work for a while, then I lost contact. Since then it never booted from mSATA again.
I installed OMV to it - now for the 7th time. WIthout any problems, the installation goes through, no errors,
the mSATA is there, fdisk sees it, tells me there is a dos boot sector.
But all I get when booting is a screen with a blinking cursor after a while the machine reboots.
When I boot some rescue disk, and then try to boot existing OS, that fails too.
When I boot into a rescue system, mount the /dev/sda1 partition (with OMV on it), that works, FS seems to not have any errors whatsoever, everything looks right.
chrooting into that is impossible, suddenly binaries are missing, but not the corrupted kind of missing, it just looks as if I was on a totally different disk.
I've been doing Linux now since 1995 but I never ever experienced something like this.
And honestly I'm out of ideas. Maybe you got some for me.
pre-edit:
What I did and didn't write up above (because 2 days aren't written in a few lines)
Because I thought I might have done something to the BIOS settings, I popped out the 2032 battery for a couple of minutes - which by the way didn't seem to have any effect on the BIOS settings. Battery back.
Of course I revised BIOS settings like 50 times now. I almost feel at home in the American Megatrends BIOS there...
edit:
Installing the system on a Seagate IronWolf 10TB on SATA port 1 yields exactly the same result - blank screen with a blinking cursor - after reboot and trying to boot from it.
Next try: simply try to install Jessie