Hi there,
I just plugged into my computer (via sata on the motherboard) a SSD that was on another computer, and now I can't boot Solus..
I still can choose it from the GRUB menu, and then it goes to a black screen (i waited a lot and nothing happened).
Since this drive was with a Lubuntu install (Swap partition, install partition, an home partition) i thought i could be a conflict between both, so i booted in windows (i'm dual booting) and formated de drive removing all partitions.
Still nothing.
I also tried to do that https://discuss.getsol.us/d/639-a-little-tip-for-troubleshooting-boot-issues, and then nothing happened.. (i pressed f10 after putting the two lines, maybe i was wrong)
Could we have some boot option wich indicate in the terminal what's happening, in order to find what's the problem ? I searched i didn't found anything.
Thank you for any help, and for the second time sorry for any language mistake, english isn't my native language.
Can't boot on Solus after installing a hard drive
[deleted]
- Edited
Flo Remove the resume=long uuid part from boot options
Could we have some boot option wich indicate in the terminal what's happening, in order to find what's the problem ? I searched i didn't found anything.
The link you posted had precisely that.
I couldn't find any resume=long uuid in the boot option (i assume it's the lines appearing after pressing "e" on the boot options in Grub).
And for your systemd.loglevel options of your other post, maybe i put them in a wrong place : i just pressed enter at the end of the last line, put the first. Then enter and put the second.
Anyway thank you for your time 
[deleted]
Flo It's usually at the end. It doesn't say "long uuid", it has a long string of characters, for example resume=ec4dfd3a-5811-4967-a28d-ba76c8ad55a9
- Edited
[deleted] : there's no resume=xxxx in there (checked a lot in order to be shure), the more similar is a root=UUID=XXXX xXXX, but i think it's completely different.
Also i foud an argument wich is system.show_status=false, i changed it to true, and i found an error message that appeared twice -> "Failed to start load Kernel module", i search the web but could only find Debian (ubuntu) related solutions, wich use diferent commands if i'm not wrong.
kyrios I wanted to access fstab from a live usb stick, but I could not get to boot into it neither, with the same error as above "Failed to start load Kernel module" wich make me think that something went wrong not only with Grub.. I also tried to access it via Ext2fsd (windows) but could mount it (ext2fsd thinks it formated as Ext3 wich is wrong, this error exists since quite some time, before my boot problem).
In a last hope i removed the new hard drive, but the problem persist..
Edit : ortograph
[deleted]
- Edited
Flo If you're running Solus 4, the Failed to start load Kernel module message is usually about the virtualbox guest component.
Add the other log level parameters to the boot line and see where it hangs.
I've done so assuming that's those arguments had to be put after the echo "loading solus 4.0 Fortitude 5.0.5..." and linux /boot/com.solus-project.current.5.0.5.113.
The argument loglevel=3 was already on the line, so i didnt put it, and i put a the end the "systemd.loglevel=debug". the text was REALLY quick, but i've made a video if yout want.
Thus, there is 4 time the error "Failed to start load Kernel module", one more or less at the beggining, and three in a raw just before the black screen, just before "Started Load/save RF Kill switch status" (with an OK).
Here's the link for the video (sorry, it's reaally handmade) :
- Edited
Ookay, thus i think the problem just been fixed by himself.. I was trying another reboot, and it worked, i just don't know what happened (neither why i could boot on windows and not on solus before).
Anyway thank you @[deleted] and @kyrios for your time 
I can't find the option to change the subject as resolved :s
I didn't do anything, but I'm glad your problem is solved ! 