No, I mean “online upgrade”.
It is documented, I guess on the same place where your method is described.
In short, it uses the 15.5 repositories to update (almost) all of the openSUSE provided packages that are on the system to those of 15.5. LIke i gigantic update and a bit like Tumbleweed does on every new TW snapshot (but thes are mostly not that large).
Many use this already for several openSUSE version upgrades (from maybe even 42).
I think the same. The installer simply inspects the disks. How many are there, what is their partitioning, is it possible to detect what file system are there, is it possible to decide what those file systems are for.
Then, I assume that for an upgrade it will (try to) find the root partition of the system that should be upgraded.
(And for a fresh install it will check how many free space there is, but that is unneeded in case of an Upgrade I guess.)
When the system runs without problem until that upgrade is tried, I do not feel it very likely that a hardware problem now all of a sudden emerges.
There is written in " SDB:Offline upgrade" Offline upgrade: It is safer and more versatile than the live upgrade, because the system is taken offline, the upgrade is done from a small live system running off the DVD.
I have upgraded four notebooks before with this USB Stick (offline image 15.5) and had no problems.
Should I try to physically remove the Toshiba HDD first?
I would say, when you are used to ding it your way, then carry on using this method instead of going for something new.
And about removing one of the disks. That requires knowledge of what is on it. And we do not know. When there are no openSUSE system file systems on there ( most often: when the root partition is not on it), it is not needed during the upgrade. If it is easy to do, you could try without and see what happens.
And when you want that we know like you what is on the disks, then please show:
The Toshiba HDD contains only data (sda)
I separated Windows10 on the NVME (nvme0n1 )and Linux on the Samsung SSD (sdb),
There is also an older 15.3 OpenSuse on the SSD (sdb3).
I haven’t had a problem with multi-booting so far.
Can it be that it hangs because of Windows/NVME?
Please, help people to understand computer text better by using the </> button and not the " button on the selected text.
Also please always include the line withe prompt-command at the beginning and the new prompt at the end. It is only two lines more with the copy/paste and it will tell your helpers often a lot of information.
Also, please talk about sda, adb and nvme0n1 and not about Samsung or Toshiba whatever brand. Else we have to scroll back all the time to undrstand about what disk you are talking.
Also, the fdisk -l is missing.
In any case, nvme0n1 does not even have any Linux file system on it, thus removing it during the upgrade might be save.
I believe the answer could easily be yes, if Windows wasn’t completely shut down, but instead hibernated by having fast boot enabled, or specifically hibernated, both of which leave its filesystems open and inaccessible from Linux.
I booted into Windows and got out with Reboot.
Afair this should disable the fastboot.
I removed the HDD (/dev/sda).
I tried the installer without a network connection.
What exactly does the installer do in this step?
How long can the “hard disk check” take?
As I said, I’ve already tried it for 20 minutes. But everything gets hot, including the USB stick.
I’m a bit hesitant to remove the main drive on the MB ( /dev/nvme0n1) for a test.
What could happen?
Can it be reinstalled afterwards without any problems and then everything is the same as before?
No problems with UEFI?
With “This step” I mean what you see in the first screenshot of this tread.
At 40% of “Systemüberprüfung” (System check) it says “Festplatten werden überprüft” (Checking disks).
It hangs there and I wonder how long you should wait for it to finish or if it really crashed.
In any case, the buttons don’t work there.
To reduce the number of possible causes, it may also be worthwhile, since it only takes a few seconds, to check the installation media (pendrive in your case).
From the initial menu (the grub menù with “install” , “upgrade” …) select “more” and then “check installation media”.
I tested the pendrive in a different way.
I started another computer with it to see how it behaves.
There, too, it stopped at 40% (checking disks), but the installer continued after about 2 minutes.
So the pendrive shouldn’t be the problem.
Maybe I’ll install an external fan against the heat and just wait an hour.