Advice on organizing disks

[Prexy]

One of my computers , the motherboard died. I salvaged the hard drive and memory. I put the hard drive into my other computer. That drive had Tumbleweed, Windows and lots of data on it. I would like advice on how to integrate the “new” drive into my main computer. I jotted down a summary of the disks , without capacity, since I now have a bonus of disk space that I wasn’t looking for. Unless you think it comes into play, here is a breakdown without capacity.

SDA5 - Main linux (Tumbleweed)
SDA7 - appears to be a duplicate of SDA5
SDB6 - linux but “home” directory is empty
SDB7 - old linux data
SDB2 - old windows install
SDA appears to be SATA2
SDB appears to be SATA4

If I left SDB2 as a Windows install, I could recover most of the rest of SDB for data in linux. I suppose I could encrypt the disk for “secret” stuff like bank statements, credit card statements etc.

Also, I need directions on how to get BIOS and grub to recognize whatever the new setup will be. I would rather Tumbleweed start automatically and interrupt when I want to start Windows (which is rarely and becoming less and less important.)

[marel]

I also sometimes tun into the question on how to organize things and like to get a good overview.

I still like the graphical overview of the Yast Partitioner:

But in the end I settled for something better

> lsblk -o  +FSTYPE,PARTLABEL
NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS FSTYPE      PARTLABEL
sda             8:0    0 931.5G  0 disk              crypto_LUKS 
nvme2n1       259:0    0   1.9T  0 disk                          
├─nvme2n1p1   259:1    0     1G  0 part  /boot/efi   vfat        lexar_boot_efi
├─nvme2n1p2   259:2    0     1G  0 part  /boot       ext4        lexar_boot
├─nvme2n1p3   259:3    0   100G  0 part  /           xfs         lexar_root
├─nvme2n1p4   259:4    0   150G  0 part  /data3      xfs         lexar_data
└─nvme2n1p5   259:5    0   1.5T  0 part              crypto_LUKS lexar_home
  └─cr-auto-1 254:0    0   1.5T  0 crypt /home       xfs         
nvme1n1       259:6    0 238.5G  0 disk                          
├─nvme1n1p1   259:7    0   100M  0 part              vfat        EFI system partition
├─nvme1n1p2   259:8    0    16M  0 part                          Microsoft reserved partition
├─nvme1n1p3   259:9    0 237.6G  0 part              ntfs        Basic data partition
└─nvme1n1p4   259:10   0   808M  0 part              ntfs        
nvme0n1       259:11   0 931.5G  0 disk                          
├─nvme0n1p1   259:12   0   512M  0 part              vfat        
├─nvme0n1p2   259:13   0    20G  0 part              ext4        
├─nvme0n1p3   259:14   0   150G  0 part  /data       xfs         crucial_data
├─nvme0n1p4   259:15   0   100G  0 part              xfs         
├─nvme0n1p5   259:16   0   150G  0 part  /pgdata     xfs         crucial_pgsql
└─nvme0n1p6   259:17   0   150G  0 part              xfs

For this to work you need to set “PARTLABELS”, I did that using gdisk:

Using gdisk to set 'partlabels'

sudo gdisk /dev/nvme2n1
GPT fdisk (gdisk) version 1.0.10

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): c
Partition number (1-5): 1
Enter name: boot_efi

Command (? for help): c
Partition number (1-5): 2
Enter name: lexar_boot

Command (? for help): c
Partition number (1-5): 1
Enter name: lexar_boot_efi

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/nvme2n1.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.

[Prexy]

Thanks for alerting me to Yast Partitioner. The warning was scary! But I made no changes. I have to learn how to make safe changes after I decide what the setup should look like.