I am unable to boot from a Ubuntu Live USB stick (current version 20.04 LTS) whatever I try. The boot stops right after the "disk check" completed successfully. When booting without the splash screen (nosplash), I get the following message:
run-init: can't execute 's/sbin/init': No such file or directory Target filesystem doesn't have requested /sbin/init. run-init: can't execute 's/sbin/init': No such file or directory run-init: can't execute 'etc/init': Permission denied Kernel Panic - not syncing: Attempted to kill init! exitcode=0x00000100
Since the boot does not get me even to a command line, I cannot provide a log as text file. However there is a video of the entire boot process. If you think that helps, I can put that somewhere.
I have been researching for days and believe to have tried every last thing that was suggested in any post I could find. Here is a list of all the things I've tried, not necessarily in chronological order:
- Verified downloaded ISO successfully (SHA256 as provided here)
- Tried three different USB sticks, two USB 3, one USB 2, each of which was set up multiple times with the latest version of Rufus (3.10).
- Tried different USB sockets on the computer, from both of the two USB controllers which the mainboard has.
- Played around with the few options my Bios offers regarding booting (e.g. UEFI vs. Legacy+UEFI, Support for Win 7/8 installations on/off, secure boot)
- Updated BIOS
- Tried booting with UEFI and non-UEFI
- Tried all these advanced boot options: nosplash, nomodeset, acpi=off, nolapic
- Disconnected everything from the computer other than Live USB stick, keyboard+mouse dongle and screen
- Checked that my hardware is supported, which seems to be the case for the (presumably most important) Intel Z170 chipset
- MSI Z170A Gaming M5 (MS-7977, specification) (I'm not a gamer, but this model ticked all my boxes at the time...)
- Intel Core i7-6700 CPU (3.40GHz)
- Corsair Vengeance LPX 2x8GB DDR4
- Should not be relevant, but there's a Samsung SSD 950 M.2-drive inside, which houses Windows 10 (which always has been and still is running without issues)
I just don't understand how the kernel (?) cannot access files from an image that it has (presumably) either extracted into memory just a second earlier or at least successfully checked for integrity the moment before. What am I doing wrong??