How to find out where debian is being loaded from? How to merge partitions and not overwrite the boot sector?

Question

Debian

There are two 3.84TB ssd drives in the raid and an 8 TB HDD. Initially, on the hezner machine, as far as I remember, the system was installed on the HDD, then reinstalled on the SSD. Below is what's left. How to find out where debian is being loaded from? How to merge partitions and not overwrite the boot sector? I see the BIOS boot on /dev/sda5 as well - and this is the HDD. The ultimate goal is to mount the HDD to a folder. To do this, as I understand it, it is necessary to merge all partitions / dev / sda?

fdisk -l
Disk /dev/nvme0n1: 3.5 TiB, 3840755982336 bytes, 7501476528 sectors
Disk model: SAMSUNG MZQLB3T8HALS-00007
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: C3D50790-812F-4B14-9AA0-A57AA316DD24

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1    4096    1052671    1048576  512M Linux RAID
/dev/nvme0n1p2 1052672 7501476494 7500423823  3.5T Linux RAID
/dev/nvme0n1p3    2048       4095       2048    1M BIOS boot

Partition table entries are not in disk order.


Disk /dev/nvme1n1: 3.5 TiB, 3840755982336 bytes, 7501476528 sectors
Disk model: SAMSUNG MZQLB3T8HALS-00007
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: 7CCCAAEA-4191-4261-9324-9E5270CAF93D

Device           Start        End    Sectors  Size Type
/dev/nvme1n1p1    4096    1052671    1048576  512M Linux RAID
/dev/nvme1n1p2 1052672 7501476494 7500423823  3.5T Linux RAID
/dev/nvme1n1p3    2048       4095       2048    1M BIOS boot

Partition table entries are not in disk order.


Disk /dev/md0: 511 MiB, 535822336 bytes, 1046528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md1: 3.5 TiB, 3840081723392 bytes, 7500159616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: HGST HUH721008AL
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: D89378D7-4DA0-4619-9379-3942FD7E44D6

Device          Start         End     Sectors  Size Type
/dev/sda1        4096     8392703     8388608    4G Linux RAID
/dev/sda2     8392704     9441279     1048576  512M Linux RAID
/dev/sda3     9441280  2121273343  2111832064 1007G Linux RAID
/dev/sda4  2121273344 15628053134 13506779791  6.3T Linux RAID
/dev/sda5        2048        4095        2048    1M BIOS boot
/dev/sda6          34        2047        2014 1007K Linux filesystem

Partition 6 does not start on physical sector boundary.
Partition table entries are not in disk order.


Disk /dev/mapper/vg0-root: 3.5 TiB, 3822898380800 bytes, 7466598400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg0-swap: 16 GiB, 17179869184 bytes, 33554432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Answer 1

According to the screenshots, you have a working system both on the raid and on a single disk, in order to make sure that data is "killed" on a single screw, order a lara and disable the sata port in the BIOS where the single screw sits. You should be able to boot from the raid without any problems. And you will be sure that when formatting or re-partitioning the disk, the system will not do anything