Weird resurection

English Install/Boot/Login
1

Hello everyone,
it will be long!

On Monday my system started making me troubles - when I have Kmail open and I want to attach a file every second attempt resulted in crashing, which also was crashing the opened LibreOffice. The reverse situation also happened - “saving as” a file in Libreoffice was crashing it and if Kmail was open it also was crashing.

On Tuesday it got very annoying so on Wednesday I decided to do the all packages update if newer version is available in YAST Softaware management.

I got an error that libQt6core was not the proper version to which I gave break dependencies option, since the other choice was to change 460 packages. Well this resulted in not operational VirtualBox, so I made a new update to all packages and this time I chose the first option to change the specified 460 packages. Disaster - I ended in IceWM instead of Plasma X11. Dolphin, KMail and most of the programs that come with Tumbleweed and the ones I installed were missing!

I then decided to do a complete new installation of the system than bother to look how to solve the problems. I chose a Bulgarian locale and regional settings in the installation (the previous installation was in English), formatted the root, boot efi and home directories, deleted all the Repositories and so on.

Yesterday - Thursday, I spent several hours setting printer, Kmail, and some of the things I use. All the programs I used before the formatting were gone. I had to install them again, for which I did not have time and left it for today. Also I had to write a new rows in the fstab file so I have my partitions mounted at startup.

And now the surprise - today on the morning I started the system and it booted like it was on Wednesday before the crash - the English locale version.
All that I have deleted during the formatting, was here like yesterday has never happen (the date and time are accurate!). The home folder was empty yesterday - today it is full with all the files and folders before the formatting. What I saved yesterday is missing.
Yesterday’s setting of Kmail is not present - all my messages are written on a separate partition, which is not formatted, so they are not lost. What I sent yesterday as messages is missing and Kmail appearance is like before the formatting.

My question is how is this possible? I did not backed up anything before the packages update, neither before the new installation. I don’t use Timeshift or similar software.
It all looks like yesterday and the part of the previous day when I made the new installation and formatted the before mentioned partitions has never happen?!

Regards
Stan

2

I have no idea what you think to repair with this. To make a Tumbleweed installation up-to-date the way to go is zypper dup.

3

Can you post the output of sudo fdisk -l?

4

And zypper lr -d ?

5 
Disk /dev/nvme1n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: WDC PC SN720 SDAPNTW-512G-1006          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D1B61019-740B-4E77-AE61-716C5588C693

Device             Start        End   Sectors   Size Type
/dev/nvme1n1p1      2048     206847    204800   100M EFI System
/dev/nvme1n1p2 184526848  394242047 209715200   100G Linux filesystem
/dev/nvme1n1p3    206848  184526847 184320000  87,9G Microsoft basic data
/dev/nvme1n1p4 999127040 1000212479   1085440   530M Windows recovery environment
/dev/nvme1n1p5 394242048  541042687 146800640    70G Linux swap
/dev/nvme1n1p6 541042688  998807551 457764864 218,3G Linux filesystem
/dev/nvme1n1p7 998807552  999127039    319488   156M Microsoft basic data

Partition table entries are not in disk order.


Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: KINGSTON SNV2S1000G                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 31BC0415-0F2E-4996-9EA7-49805AC94E97

Device             Start        End    Sectors   Size Type
/dev/nvme0n1p1      2048  314574847  314572800   150G Linux filesystem
/dev/nvme0n1p2 314574848  734005247  419430400   200G Linux filesystem
/dev/nvme0n1p3 734005248 1953525134 1219519887 581,5G Linux filesystem


Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM048-2E71
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FA9C85CB-9E33-4591-B717-FEC664816F40

Device         Start        End    Sectors   Size Type
/dev/sda1       2048  314574847  314572800   150G Linux filesystem
/dev/sda2  314574848  734005247  419430400   200G Linux filesystem
/dev/sda3  734005248 1953523711 1219518464 581,5G Linux filesystem
6 
#  | Alias                            | Name                                   | Enabled | GPG Check | Refresh | Keep | Priority | Type     | URI                                                                                          | Service
---+----------------------------------+----------------------------------------+---------+-----------+---------+------+----------+----------+----------------------------------------------------------------------------------------------+---------
 1 | Downloads                        | Downloads                              | Yes     | ( p) Yes  | Yes     | -    |   99     | plaindir | dir:/run/media/satco/SSD_Razshiren/Downloads                                                 | 
 2 | NVIDIA:repo-non-free             | repo-non-free                          | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | https://download.nvidia.com/opensuse/tumbleweed                                              | NVIDIA
 3 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)              | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://download.opensuse.org/tumbleweed/repo/non-oss/                                        | 
 4 | download.opensuse.org-oss        | Main Repository (OSS)                  | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://download.opensuse.org/tumbleweed/repo/oss/                                            | 
 5 | download.opensuse.org-tumbleweed | Main Update Repository                 | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://download.opensuse.org/update/tumbleweed/                                              | 
 6 | openSUSE-20250130-0              | openSUSE-20250130-0                    | No      | ----      | ----    | -    |   99     | rpm-md   | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C42568CB2C099734ADE-0:0-part2 | 
 7 | openSUSE:repo-non-oss            | repo-non-oss                           | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://cdn.opensuse.org/tumbleweed/repo/non-oss                                              | openSUSE
 8 | openSUSE:repo-openh264           | repo-openh264                          | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                                      | openSUSE
 9 | openSUSE:repo-oss                | repo-oss                               | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://cdn.opensuse.org/tumbleweed/repo/oss                                                  | openSUSE
10 | openSUSE:repo-oss-debug          | repo-oss-debug                         | No      | ----      | ----    | -    |   99     | N/A      | http://cdn.opensuse.org/debug/tumbleweed/repo/oss                                            | openSUSE
11 | openSUSE:repo-oss-source         | repo-oss-source                        | No      | ----      | ----    | -    |   99     | N/A      | http://cdn.opensuse.org/source/tumbleweed/repo/oss                                           | openSUSE
12 | openSUSE:update-tumbleweed       | update-tumbleweed                      | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://cdn.opensuse.org/update/tumbleweed                                                    | openSUSE
13 | repo-debug                       | openSUSE-Tumbleweed-Debug              | No      | ----      | ----    | -    |   99     | N/A      | http://download.opensuse.org/debug/tumbleweed/repo/oss/                                      | 
14 | repo-openh264                    | Open H.264 Codec (openSUSE Tumbleweed) | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                                      | 
15 | repo-source                      | openSUSE-Tumbleweed-Source             | No      | ----      | ----    | -    |   99     | N/A      | http://download.opensuse.org/source/tumbleweed/repo/oss/                                     |
7

Please, to make the pieces of computer code in your posts better consumable by technical oriented people:

And post as complete as possible. That is starting with the line with the prompt and the command, then all output, and ending with the new prompt line.
When you really feel you need to change anything in such a copy, then in a comment, else we take all characters literally.

8

Next time I’ll do that, but why is there such an option in
YAST >Software management>Package>All packages>Update if newer version is available? Doesn’t it do the same as zypper dup?

9 
satco@localhost:~> sudo fdisk -l
[sudo] password for root: 
Disk /dev/nvme1n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: WDC PC SN720 SDAPNTW-512G-1006          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D1B61019-740B-4E77-AE61-716C5588C693

Device             Start        End   Sectors   Size Type
/dev/nvme1n1p1      2048     206847    204800   100M EFI System
/dev/nvme1n1p2 184526848  394242047 209715200   100G Linux filesystem
/dev/nvme1n1p3    206848  184526847 184320000  87,9G Microsoft basic data
/dev/nvme1n1p4 999127040 1000212479   1085440   530M Windows recovery environment
/dev/nvme1n1p5 394242048  541042687 146800640    70G Linux swap
/dev/nvme1n1p6 541042688  998807551 457764864 218,3G Linux filesystem
/dev/nvme1n1p7 998807552  999127039    319488   156M Microsoft basic data

Partition table entries are not in disk order.


Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: KINGSTON SNV2S1000G                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 31BC0415-0F2E-4996-9EA7-49805AC94E97

Device             Start        End    Sectors   Size Type
/dev/nvme0n1p1      2048  314574847  314572800   150G Linux filesystem
/dev/nvme0n1p2 314574848  734005247  419430400   200G Linux filesystem
/dev/nvme0n1p3 734005248 1953525134 1219519887 581,5G Linux filesystem


Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM048-2E71
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FA9C85CB-9E33-4591-B717-FEC664816F40

Device         Start        End    Sectors   Size Type
/dev/sda1       2048  314574847  314572800   150G Linux filesystem
/dev/sda2  314574848  734005247  419430400   200G Linux filesystem
/dev/sda3  734005248 1953523711 1219518464 581,5G Linux filesystem
satco@localhost:~>
10

I edited your post. Please stop editing it yourself now.

11 
satco@localhost:~> sudo zypper lr -d
[sudo] password for root: 
#  | Alias                            | Name                                   | Enabled | GPG Check | Refresh | Keep | Priority | Type     | URI                                                                                          | Service
---+----------------------------------+----------------------------------------+---------+-----------+---------+------+----------+----------+----------------------------------------------------------------------------------------------+---------
 1 | Downloads                        | Downloads                              | Yes     | ( p) Yes  | Yes     | -    |   99     | plaindir | dir:/run/media/satco/SSD_Razshiren/Downloads                                                 | 
 2 | NVIDIA:repo-non-free             | repo-non-free                          | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | https://download.nvidia.com/opensuse/tumbleweed                                              | NVIDIA
 3 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)              | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://download.opensuse.org/tumbleweed/repo/non-oss/                                        | 
 4 | download.opensuse.org-oss        | Main Repository (OSS)                  | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://download.opensuse.org/tumbleweed/repo/oss/                                            | 
 5 | download.opensuse.org-tumbleweed | Main Update Repository                 | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://download.opensuse.org/update/tumbleweed/                                              | 
 6 | openSUSE-20250130-0              | openSUSE-20250130-0                    | No      | ----      | ----    | -    |   99     | rpm-md   | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C42568CB2C099734ADE-0:0-part2 | 
 7 | openSUSE:repo-non-oss            | repo-non-oss                           | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://cdn.opensuse.org/tumbleweed/repo/non-oss                                              | openSUSE
 8 | openSUSE:repo-openh264           | repo-openh264                          | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                                      | openSUSE
 9 | openSUSE:repo-oss                | repo-oss                               | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://cdn.opensuse.org/tumbleweed/repo/oss                                                  | openSUSE
10 | openSUSE:repo-oss-debug          | repo-oss-debug                         | No      | ----      | ----    | -    |   99     | N/A      | http://cdn.opensuse.org/debug/tumbleweed/repo/oss                                            | openSUSE
11 | openSUSE:repo-oss-source         | repo-oss-source                        | No      | ----      | ----    | -    |   99     | N/A      | http://cdn.opensuse.org/source/tumbleweed/repo/oss                                           | openSUSE
12 | openSUSE:update-tumbleweed       | update-tumbleweed                      | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://cdn.opensuse.org/update/tumbleweed                                                    | openSUSE
13 | repo-debug                       | openSUSE-Tumbleweed-Debug              | No      | ----      | ----    | -    |   99     | N/A      | http://download.opensuse.org/debug/tumbleweed/repo/oss/                                      | 
14 | repo-openh264                    | Open H.264 Codec (openSUSE Tumbleweed) | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md   | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                                      | 
15 | repo-source                      | openSUSE-Tumbleweed-Source             | No      | ----      | ----    | -    |   99     | N/A      | http://download.opensuse.org/source/tumbleweed/repo/oss/                                     | 
satco@localhost:~>
1 Like
12

Now you’ve got it. Can you see that it makes output a lot more readable?

13

Yes, I got wrong the ``` and ‘’’ :grinning:

14

Fom now on use zypper dup. GNOME Software and Discover work fine, as long as there are no conflicts etc

15

I just filtered out all Linux partitions on your system and counted 8 of them:

/dev/nvme1n1p2 184526848  394242047  209715200   100G Linux filesystem
/dev/nvme1n1p6 541042688  998807551  457764864 218,3G Linux filesystem
/dev/nvme0n1p1      2048  314574847  314572800   150G Linux filesystem
/dev/nvme0n1p2 314574848  734005247  419430400   200G Linux filesystem
/dev/nvme0n1p3 734005248 1953525134 1219519887 581,5G Linux filesystem
/dev/sda1           2048  314574847  314572800   150G Linux filesystem
/dev/sda2      314574848  734005247  419430400   200G Linux filesystem
/dev/sda3      734005248 1953523711 1219518464 581,5G Linux filesystem

I am not surprised you are confused.

16

That is equivalent to zypper up and works perfect for Leap. But you are using Tumbleweed ad thus better follow the advises for Tumbleweed.

17

I don’t get your point.
What I did on Wednesday was formatting
/dev/nvme1n1p2 100G partition (this is the root one)
and
/dev/nvme1n1p6 218,3G (this is /home one).
Yesterday /dev/nvme1n1p6 218,3G was completely empty! Today about 30G are filled with old data mostly from February and March 2025 before the formatting of Wednesday.
The rest of the Linux partitions were not formatted and not edited during the new installation on Wednesday.
The two things I don’t understand is:

  1. How a formatted root partition can be recovered to a previous state, when a new installation of Tumbleweed (with different locale settings) is made on it and the same is valid for the /home?
  2. How can I work about 30 hours with the new installation, to be missing all the manually installed programs, to have to set from scratch my mail account in KMail and so on, and then suddenly to “go back in time” like the mentioned 30 hours did not happen?
18

Thank you hcvv, I’ve been using Leap from 42 version until January 2025. Old habits change slow :grinning:

19

One more thing to clear - the new installation was made from an USB flash drive listed in the repo list under No.6.

20

The only plausible explanation is that you are mixing up partitions. Maybe nvme0 and nmve1 were mixed up.