When I was trying to upgrade from Leap 15.6 to Tumbleweed using the offline method I got a warning saying Cannot upgrade the bootloader because of mismatch of boot technology.
The upgraded system uses GRUB2 for EFI boot while the installation medium has been booted using Systemd boot. This scenario is not supported, the upgraded system may not boot or the upgrade process can fail later.
This is where I stopped and aborted the upgrade. I then accidentally deleted my EFI partition and resized my main Leap partition using the free space. I thought it was related to Windows but it was in fact for Leap. After that I found that my PC didn’t boot anymore because bootloader was gone. And I couldn’t re-install GRUB2 becaue EFI directory was gone too.
So I decided the easiets option was to wipe my whole NVME SSD and install Tumbleweed on it and then just link my exiting 4TB HDD to my /Home directory. On Leap 15.6 I had my /Home folder mounted on separate disk (4TB Toshiba HDD). I also have 500GB SATA SDD for games and 3TB HDD for backup.
So i used the Partitioner in Yast to link my 4TB disk to /Home and it worked but when I restarted my PC and tried to login. It won’t let me in. The login screen doesn’t show any error message it simply flashes for 1 second when I enter my password. I have tried using all 11 snap-shots and none of them let me login. So I cannot use snapper-rollback.
What I discovered is that when I press Ctrl-Shift-F3 or F1 I can login to tty1/tty3 and I can browse my main storage in the terminal. There is an interesting error when I enter my credentials in the tty mode. --dante: /home/dante: change directory failed: Permission denied.
Would someone be able to help me fix this so I can use my computer again? Many Thanks.
You missed showing the directory itself.
What’s the output from
ls -l /home/dante
It shows the same output expect that the 4th column has dante instead of users.
Oops.
I should have asked for:
ls -ld /home/dante
I wanted to see permissions at the top of the home directory tree.
That looks okay.
I have always done fresh installs rather than upgrades – except I had to upgrade to Leap 16.0, because the “agama” installer seems unable to deal with my system.
My guess is that you can ignore that warning about booting.
Right now I am installing Tumbleweed into a VM (a fresh install). And I have told the installer to use grub2 for efi to boot it. The installer has not complained.
Hmm, that install has now finished. And I was able to boot the VM. The installer was booted with “systemd boot” yet can successfully install to use “grub2 efi” for booting. So I am doubting it will have a problem with your system.
While doing the upgrade, I suggest going into the Boot settings, and making sure that you will be using grub2 for EFI. Trying to switch to “systemd booting” might lead to problems.
Okay, now that my newly installed Tumbleweed is running, I am trying to upgrade it to itself using the same offline installer.
Yes, I am getting the same message that you got.
There’s a page with title “Installation Settings”. On that page there is a heading “Booting”. I clicked on that, and got some more warnings. After I closed those warnings, it went to the booting section, where it showed that it was going to boot with “systemd boot”. I switched that to “GRUB2 EFI”. And then all of the warning messages disappeared.
I’ll suggest that you do that – click on Booting, and switch it to GRUB2 EFI.
I have already goten help in different forum. We found that that the error
was caused by some security context label that was missing. This is the command that fixed it.
restorecon -R /home
After that I restarted my PC and upon reboot I was able to login the normal way. Thanks for trying to help. Now I hope that Tumbleweed will not ■■■■ the bed when I run zypper dup with 600+ new packages available.
From what I have seen, Tumbleweed looks pretty stable, although there are occasional glitches.
