The messages you’re getting sound like they’re from the bootloader, so I think secure boot is not causing the problem… Linux should print some stuff right away when it loads, maybe check the architecture of the kernel you’re trying to boot, even an error immediately after loading the kernel should print something unless the architecture is so different that it’s just feeding the CPU bad instructions… Not sure how the bootloader would get installed correctly in that situation though. Is this after installation? Does the system boot from a live USB or cdrom?
Yes this. Imagine posting to a stack themed site, your question would be closed for being incomplete. A screenshot of the failed boot would be great, and some info about the options you chose when installing and the type of machine you’re using.
Yes. But since we’re in Linux land, you may be able to replay the journal and un-dirty your disk by mounting with the ntfs3 driver listed here docs.kernel.org/filesystems/ntfs3.html, or you could try using ‘ntfsfix -d [your device]’ from the ntfs-3g package to clear the journal and the dirty bit, although whatever the last operation was on the filesystem may be left in an incomplete state since the journal is not replayed.
I haven’t done it in a while, but with virtualbox I have used direct disk access by creating a special vmdk with vboxmanage to give a VM access to real partitions.
Lol I don’t know why people are hating this. It’s cool, looks more European. Do you have more for other states? There are some way crazier flags flying in the US.