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.
Is this the same as “live upgrade”?
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?
Thank you!
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:
lsblk -f
and as root:
fdisk -l
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?
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
├─sda2 ntfs Data 6A4AD8C24AD88C67
├─sda3 ext4 1.0 ToshExt4 81a8e23b-d32b-447f-9b34-8a38785f2de8
└─sda4 swap 1 fa294124-86e8-4516-8dfb-4ff53f27ce4d
sdb
├─sdb1 vfat FAT16 0559-0AB6 250.7M 2% /boot/efi
├─sdb2 swap 1 a3b6ed7d-b9be-4a54-b547-33cea812c4d8 [SWAP]
├─sdb3 ext4 1.0 cab07041-6f08-4ba4-9fc0-f93105c10d61
└─sdb4 ext4 1.0 a0e429ae-2f3e-4bd3-bdcf-316d26d2a284 45.5G 39% /
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM CAD2-F52C
├─nvme0n1p2
├─nvme0n1p3 ntfs Windows 5CF2D5B2F2D5911E 93.6G 33% /run/media/theo/Windows
└─nvme0n1p4 ntfs WinRE_DRV FC70D62170D5E286
Another reason why I don’t want to just “skip” this is because I think there will be the same problem with a fresh install.
Thank you!
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.
Thank you!
Unfortunately I can no longer edit the original post, so here is just the command outputs.
> lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
├─sda2 ntfs Data 6A4AD8C24AD88C67
├─sda3 ext4 1.0 ToshExt4 81a8e23b-d32b-447f-9b34-8a38785f2de8
└─sda4 swap 1 fa294124-86e8-4516-8dfb-4ff53f27ce4d
sdb
├─sdb1 vfat FAT16 0559-0AB6 250.7M 2% /boot/efi
├─sdb2 swap 1 a3b6ed7d-b9be-4a54-b547-33cea812c4d8 [SWAP]
├─sdb3 ext4 1.0 cab07041-6f08-4ba4-9fc0-f93105c10d61
└─sdb4 ext4 1.0 a0e429ae-2f3e-4bd3-bdcf-316d26d2a284 45.5G 39% /
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM CAD2-F52C
├─nvme0n1p2
├─nvme0n1p3 ntfs Windows 5CF2D5B2F2D5911E 93.6G 33% /run/media/theo/Windows
└─nvme0n1p4 ntfs WinRE_DRV FC70D62170D5E286
> sudo fdisk -l
Festplatte /dev/nvme0n1: 238.47 GiB, 256060514304 Bytes, 500118192 Sektoren
Festplattenmodell: SKHynix_HFS256GD9TNG-L5B0B
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: F7AC928F-A7CE-48AC-B8B7-FEFFD8E7E27A
Gerät Anfang Ende Sektoren Größe Typ
/dev/nvme0n1p1 2048 534527 532480 260M EFI-System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserviert
/dev/nvme0n1p3 567296 293269503 292702208 139.6G Microsoft Basisdaten
/dev/nvme0n1p4 498069504 500117503 2048000 1000M Windows-Wiederherstellungsumgebung
Festplatte /dev/sdb: 232.89 GiB, 250059350016 Bytes, 488397168 Sektoren
Festplattenmodell: Samsung SSD 860
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: 74DC3FAB-BCC9-432A-BCA6-592DABDA8A9C
Gerät Anfang Ende Sektoren Größe Typ
/dev/sdb1 65535 589814 524280 256M EFI-System
/dev/sdb2 589815 34143734 33553920 16G Linux Swap
/dev/sdb3 34143735 219363327 185219593 88.3G Linux-Dateisystem
/dev/sdb4 219363328 393443327 174080000 83G Linux-Dateisystem
Festplatte /dev/sda: 931.51 GiB, 1000204886016 Bytes, 1953525168 Sektoren
Festplattenmodell: TOSHIBA DT01ACA1
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: DC95F777-0945-4448-BB35-052C63040307
Gerät Anfang Ende Sektoren Größe Typ
/dev/sda1 2048 264191 262144 128M Microsoft reserviert
/dev/sda2 264192 409864191 409600000 195.3G Microsoft Basisdaten
/dev/sda3 409864192 1483606015 1073741824 512G Linux-Dateisystem
/dev/sda4 1483606016 1517160447 33554432 16G Linux Swap
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.
Hmm, It just hangs.
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?
Thank you!
Probably not. I think you need to hold the SHIFT key while clicking “Restart” for this to properly shutdown the file system. But then I’m not a Windows user.
I’m not exactly sure what is “this step”, but I think it is just trying to find all linux system on your disk.
I think you got past the point where UEFI could cause problems.
Thank you.
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”.
When I last tested (several years ago) this only worked when the install media is a CD or DVD. When using a flash drive, it always reported a fail.
Thank you!
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. 
Hmm, now it worked.
I have no idea what is different from yesterday.
New day, new luck.
This time it barely stopped for a second at the drive check.
Strange, but I am happy now. 
Yes, very strange. Congratulation nevertheless.
I suspect that, you may be suffering a little bit of historical partition format – which I must admit, I’m also suffering:
Your UEFI/BIOS seems to be quite new – as is mine also –
Thank you.
In what way is this a problem?
At the moment everything works here.
“If it ain’t broke, then don’t fix it.”
If everything is working, then just enjoy that.