I installed another Arch OS on an Sdc disk (because SSD on which Solus resides is taken up entirely by Solus) in order to check it out (archcraft with openbox defaulted), and mistakenly put its boot loader on the Solus's Sda disk. So now Solus doesn't boot when I boot up into the Sda disk (via the (F12) Boot Manager, though it was written into the (not relevant) BIOS boot script after an update-grub.
I followed the following instructions from the Solus Support area but got to early dead end:
"First we need to be root as the user. Type: sudo su
Next we make a directory where we will mount our local Solus system: mkdir /target
Now, using lsblk, determine the /dev/sdX# partition of the Solus system. We recommend checking the size of the partition listed and if it matches the size of your Solus install, use that. It will likely be something along the lines of /dev/sdb# or /dev/sda#.
Once found, replace the “sdX#” in the following command with the partition and mount to the target directory we created: mount /dev/sdX# /target"
I did mkdir /target. It is there (in editor) though I do not see it listed.
lsblk reveals that sda2 is the location of Solus - both Swap and Main as lvms.
Results of inputting "mount /dev/sda2 /target" :
mount: /target: unknown filesystem type 'LVM2_member'.
Do not know how to proceed with rest of instructions...
Are there other instructions, or have I irretrievably lost access to the installation?
If have to install again, is there any way to do so without SOLUS taking up an entire 240GB SSD?
PS I don't know if this is helpful, but:
/dev/sda1: UUID="b5edca1b-4a54-4fbb-adb7-4b66ba4588b9" BLOCK_SIZE="1024" TYPE="ext4" PARTUUID="4b1bf7db-01"
/dev/sda2: UUID="Jh7iV6-AUGy-WZnU-e9oj-1cr0-46N1-hdh047" TYPE="LVM2_member" PARTUUID="4b1bf7db-02"
/dev/sdb: LABEL="2TBDrive" UUID="2f7a73d6-6375-4f34-9db4-d35bdcff72b1" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc1: LABEL="HOME" UUID="d3de515e-ed19-4e8e-9669-aa8383f8be07" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="039bfffc-01"
/dev/sdc2: LABEL="4GB" UUID="3e5d8abf-dd1c-4076-9a33-0dc4aba25f8b" UUID_SUB="c6dc94bb-126c-48f6-8353-991421be5439" BLOCK_SIZE="4096" TYPE="btrfs" PTTYPE="dos" PARTUUID="039bfffc-02"
/dev/sdc3: LABEL="SYS1" UUID="965d63f8-2088-4c0e-a53e-446e4ad75c74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="039bfffc-03"
/dev/mapper/SolusSystem-Swap: UUID="d7073d80-3a6e-43bd-b226-b329c0b40335" TYPE="swap"
/dev/mapper/SolusSystem-Root: UUID="83b22cbc-673f-45c7-be5f-466b4a0b82a9" BLOCK_SIZE="4096" TYPE="ext4"
It seems that SOLUS is seen both as LVM and as something in dev/mapper