I just added a second SSD to a Dell M3800 laptop running tumbleweed (20201209) and it now hangs on boot (tumbleweed at the bottom of the screen with the animated circle over it). I can get in recovery mode without a problem and verify that the second SSD gets mounted as setup in the fstab file as follows:
As I mentioned in the original message,the new SSD (sda) gets mounted without a problem.
Now I see that the problem may be that the new SSD is now /dev/sda, while the old SSD is now /dev/sdb. The /boot/efi partition is now in the /dev/sdb1 partition while in the previous configuration it was in the /dev/sda1 partition.
Is there a way to change the bootloader to point at /dev/sdb1, instead of /dev/sda1?
I do not really know if this is the problem but I will investigate in those lines.
hcvv, thank you for your attention to this matter. Any other pointer will be appreciated.
Sorry that I was not clear enough about doing this as root.
And better better use CODE tags then PHP tags. It is the # button, two to the left of the PHP button.
Also, as long as everywhere the UUIDs are used the switching from sda to sdab and v.v. should not matter (and that is done by default on an openSUSE installation).
The information as shown by the OP is certainly not what I would expect from it. I assume that running it as root will provide what we expect. And I see the same on my own 15.2 system: information about file systems is missing when not run as root.
OK, we started this lsblk listing because we wanted to know if the UUID used in fstab is correct. And it is.
We also see that everything you need is mounted. Does no look like recovery mode mode.
Thus back to your report. Did you hit Esc during boot to see what happens?
And maybe a more elaborate description on what you see on the screen until it “hangs” may help to start our imagination.
The last five lines shown afer hitting scape during boot are as follows (I do not know how to capture the screen at that point to share it here)
OK ] Reached target Initrd Root Device.
OK ] Finished dracut initqueue hook.
OK ] Reached target Remote File Systems (Pre.).
OK ] Reached target Remote File Systems.
* ] A start job is running for /dev/sda2 (46s / no limit)
It hangs in there with the time counter increasing indefinitely (I’ve let it go up to 5min+) and the asterisk at the beginning of the line moving back and forth.
That is strange because we know there is no sda2.
But there was before when I understand your story above.
Looks as if still somewhere there is sda2 instead of a UUID. And as now sdb2 is used for Swap, It could be that it is “hardcoded” (as sda2) in the bootstring in the resume= parameter. Can you check that? It is in /boot/grub2/grub.cfg.
Addition. You could in any case check if sda2 is mentioned somewhere in /boot/grub2/grub.cfg at all.
You are welcome. Glad I could analyze it until this. Also note that already in post #5 I hinted that UUIDs should be used everywhere. I also say there that a default installation should do that, thus I wonder why in your case it wasn’t like that.