Am 21.02.20 um 10:20 schrieb zb4ng:
Please note, that the problem at hand is already solved, but the underlying issue gets in my way from time to time, so I wanted to tell (or rant 😉) about it.
Two days ago, I wasn't able to boot my system (LEAP 15.1): X-Server didn't start and I could only log into maintenance mode with no network either. First, I suspected a botched update, but the kernel-firmware was updated a couple of days before and I had successfully booted in the mean time. So, I was dumbfounded, but then I remembered to look into /etc/fstab and found an entry of a USB drive that I had plugged in and removed. I deleted said entry and LEAP booted just fine.
My point is: maybe the maintainers could help to avoid this situation: Please, don't break the boot process if some malfunctioning but unimportant entry in fstab doesn't work! Or at least, make it easier for the user to find out what is going wrong. I had similar issues multiple times over the past years and sometimes it took me quite a time to figure them out.
Regards.
Just wanted to add that Ubuntu has the same behaviour. 1. create new partition in OpenSuSE 2. add partition to fstab in Ubuntu 3. delete partition in OpenSuSE 4. Ubuntu fails to boot -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org