You did mkdir /target
before lsblk
so the /target
directory already exists when you ran mkdir /target
again. So the error message you got at the end of of screenshot is expected.
The solus page asks you about which is your Solus's root partition, and without more info from you, we would not know it just by looking at your screenshot. For example, do you remember how big is your root partition? In you screenshot I see that your /dev/sda1 is about 450G and /dev/nvme0n1 is about 230G. there are also other partitions. You need to know which is your Solus's root partition before you can proceed with the tutorial.
At this point I don't see much that matches the description on the walkthrough
As far as I can see, your output still matches the description on the walkthrough. You just need to replace /dev/sdX#
with your actual root partition, which might be /dev/sda1
, /dev/nvme0n1p1
, or other partition in your screenshot. We would not know which one it is just by looking at your screenshot.
On the other hand, are you sure that boot rescue is the way to fix your issue? This tutorial is for people who's boot process is broken, for example, if your kernel is not found during boot, this can help you. Your case might be other issues, e.g., graphics driver issues can cause a blinking cursor after boot. You can try to check your boot log by going to a tty
terminal and see what went wrong. To go to tty
terminal you can try pressing ctrl
+alt
+f2
after seeing the blinking cursor. If you are able to see the tty
terminal, your boot process completes fine and the boot rescue tutorial will not probably help you.