yea i set up my external drives to mount on /mnt/ in seperate folders in yast partitioner after driver installation which might of caused the issue also journalctl is reaaally long and kind of hard to understand
i might just reinstall again at this point
Fair enough, you can trying passing '# journalctl -xb | grep 'error\|warn\|fail' - with quotes. It may shorten the output up some. Or even pipe systemd journal through less > # journalctl -xb | grep 'error\|warn\|fail' | less then you can use up and down arrow to navigate.
-Great Hopes
tried this and what caught my interest is this line
It may be of considerable interest to start a new thread about this problem.
Off Topic:
A thought of mine though would be /dev/sda3 is a block device containing the operating system? Are you able to get to a prompt? If so what is the output of lsblk -o +FSTYPE? Maybe perform a chroot by using openSUSE Rescue CD and editing fstab or something could repair the machines OS to a bootable state.
okay i might not migrate to another thread because im having the same issue on the installer, it displays the initial selection but it wont display the installer when going into it
Off Topic:
Looks like a mountpoint is set on the /dev/sda2 partition of drive. That could be what is jamming boot up. what is the output of cat /etc/fstab?
Perhaps try selecting the nvme0n1 specifically at BIOS boot menu. /dev/sdb1 has mountpoint also set. You need to try and remove these mountpoints on /dev/sda2 and /dev/sdb1 as they are not implemented correctly is what I think.
New thread will help.
-Best Hopes
made a new thread Thread migration, mounting issues
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
