Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3395

[Testing - Trixie] Can't mount proper /home, /boot partitions back in place using 'Calamares'

$
0
0
Hello Community!
Got rid off LVM partitions from both of my HDD and SDD recently. Which can be seen in my older posts.
Used 'Calamares' from LiveDebian - Trixie release:

Code:

Architectures: amd64Codename: trixieComponents: main non-free-firmwareDate: Mon, 27 Jan 2025 08:21:22 +0000Description: Last updated: Mon, 27 Jan 2025 08:21:22 +0000Label: DebianOrigin: DebianSuite: trixie
I was not able to solve network card auto identification and setting during 'Install' and had to pass to 'Live Debian' feature instead. From where my trouble comes.
Could not pass over to 'Calamares' a proper partitioning sequence so that newly created partitions were distributed as per my wish between /, /home, /boot and /boot/efi accordingly.
I'm talking about these disks:

Code:

kojibka@sheldon:~$ lsblkNAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTSsda       8:0    0 238,5G  0 disk ├─sda1    8:1    0   500M  0 part /boot/efi├─sda2    8:2    0    40M  0 part ├─sda3    8:3    0   128M  0 part ├─sda4    8:4    0   750M  0 part ├─sda5    8:5    0 115,4G  0 part ├─sda6    8:6    0   906M  0 part ├─sda7    8:7    0  97,4G  0 part /├─sda8    8:8    0  14,4G  0 part [SWAP]├─sda9    8:9    0   8,5G  0 part └─sda10   8:10   0   500M  0 part sdb       8:16   0 931,5G  0 disk ├─sdb1    8:17   0   128M  0 part ├─sdb2    8:18   0 497,1G  0 part /media/kojibka/DATA└─sdb3    8:19   0 434,3G  0 part sdc       8:32   1   3,8G  0 disk ├─sdc1    8:33   1   3,6G  0 part /media/kojibka/d-live testing gn amd64└─sdc2    8:34   1   3,2M  0 part sdd       8:48   1   7,7G  0 disk └─sdd1    8:49   1   7,7G  0 part /media/kojibka/HOMEBKPsr0      11:0    1  1024M  0 rom 
in such evironment:

Code:

kojibka@sheldon:~$ sudo fdisk -l[sudo] password for kojibka: Sorry, try again.[sudo] password for kojibka: Disk /dev/sda: 238,47 GiB, 256060514304 bytes, 500118192 sectorsDisk model: SAMSUNG SSD PM85Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: gptDisk identifier: 614E5657-54FD-494E-BA31-A0D10A332F8BDevice         Start       End   Sectors   Size Type/dev/sda1       2048   1026047   1024000   500M EFI System/dev/sda2    1026048   1107967     81920    40M unknown/dev/sda3    1107968   1370111    262144   128M Microsoft reserved/dev/sda4    1370112   2906111   1536000   750M Windows recovery environment/dev/sda5    2906112 245005083 242098972 115,4G Microsoft basic data/dev/sda6  245006336 246861823   1855488   906M Windows recovery environment/dev/sda7  246861824 451192831 204331008  97,4G Linux filesystem/dev/sda8  451192832 481292287  30099456  14,4G Linux swap/dev/sda9  482316288 500116143  17799856   8,5G Windows recovery environment/dev/sda10 481292288 482316287   1024000   500M EFI SystemPartition table entries are not in disk order.Disk /dev/sdb: 931,51 GiB, 1000204886016 bytes, 1953525168 sectorsDisk model: ST1000LM024 HN-MUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisklabel type: gptDisk identifier: 9FE9A6C6-64B0-4B78-B862-B6C0FE93E480Device          Start        End    Sectors   Size Type/dev/sdb1        2048     264191     262144   128M Microsoft reserved/dev/sdb2      264192 1042657279 1042393088 497,1G Microsoft basic data/dev/sdb3  1042657280 1953523711  910866432 434,3G Linux homeDisk /dev/sdc: 3,75 GiB, 4026531840 bytes, 7864320 sectorsDisk model: Flash Disk      Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0x923181b4Device     Boot Start     End Sectors  Size Id Type/dev/sdc1  *       64 7554623 7554560  3,6G  0 Empty/dev/sdc2        6628   13155    6528  3,2M ef EFI (FAT-12/16/32)Disk /dev/sdd: 7,68 GiB, 8242855936 bytes, 16099328 sectorsDisk model: Flash Disk      Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0x0d28befeDevice     Boot Start      End  Sectors  Size Id Type/dev/sdd1        2048 16099327 16097280  7,7G  c W95 FAT32 (LBA)
I was trying to do a lot of monkey business with encryption and hiding '/' and '/home' so in the end it became over complicated for 'Calamares' to manage. Most possibly I've screwed it over in attempt to hide partitions behind 'luks'. Instead I got Debian installed on SSD in only one 'ext4' partition. SWAP was mounted by installation process and '/boot' was lost in the middle on the SSD. '/home' was missed out from istallation as it is placed on HDD which is managed from the 'Calamares' partition management in segregated window. Thus making it even harder to assemble in single install.
Here comes my partitioning table given by 'GParted as it is formatted for the moment, let's start with SSD on /sda:

Code:

Device InformationModel: ATA SAMSUNG SSD PM85Serial:Size: 238.47 GiBPath: /dev/sdaPartition table: gptHeads: 255Sectors/track:2Cylinders:980623Total sectors:500118192Sector size:512PartitionNameFile SystemMount PointLabelSizeUsedUnusedFlags/dev/sda1EFI system partitionfat32/boot/efiESP500 MiB37.48 MiB462.52 MiBboot, esp/dev/sda2! Basic data partitionfat32DIAGS40.00 MiB------hidden/dev/sda3! Microsoft reserved partitionunknown128.00 MiB------msftres/dev/sda4Basic data partitionntfsWINRETOOLS750.00 MiB440.55 MiB309.45 MiBhidden, diag/dev/sda5Basic data partitionntfsOS115.44 GiB113.20 GiB2.24 GiBmsftdata/dev/sda6ntfs906.00 MiB589.20 MiB316.80 MiBhidden, diag/dev/sda7 [locked] rootext4/97.43 GiB13.95 GiB83.48 GiB/dev/sda8[locked] swaplinux-swapSW14.35 GiB0.00 B14.35 GiBswap/dev/sda10bootext4BOO500.00 MiB260.60 MiB219.40 MiBboot, esp/dev/sda9Microsoft recovery partitionntfsPBR Image8.49 GiB7.76 GiB741.33 MiBhidden, diagunallocatedunallocated1.00 MiB------
Continue with HDD on /sdb:

Code:

Device InformationModel: ATA ST1000LM024 HN-MSerial:Size: 931.51 GiBPath: /dev/sdbPartition table: gptHeads: 255Sectors/track:2Cylinders:3830441Total sectors:1953525168Sector size:512PartitionNameFile SystemMount PointLabelSizeUsedUnusedFlags/dev/sdb1! Microsoft reserved partitionunknown128.00 MiB------msftres/dev/sdb2[locked] Basic data partitionntfs/media/kojibka/DATADATA497.05 GiB359.96 GiB137.09 GiBmsftdata/dev/sdb3homeext4434.33 MiB1.94 GiB432.39 GiBlinux-home
While initial attempts to manage everything from within 'Calamares' I got several middle results starting from the last:

Code:

## FOURTH iteration - manualDeleting partition '/dev/sda7'...Create new 99771MiB partition on '/dev/sda' (SAMSUNG SSD PM851 2.5 7mm 256GB)Set flags on 99771MiB 'luks' partition to 'root'Deleting partition '/dev/sda10'...Create new 500MiB partition on '/dev/sda' (SAMSUNG SSD PM851 2.5 7mm 256GB)Set flags on 500MiB 'luks' partition to 'boot'Deleting partition '/dev/sdb3'...Create new 444759MiB partition on '/dev/sdb' (ST1000LM024 HN-M101MBB)Set up fat32 partition '/dev/sda1' with mount point '/boot/efi'...Install Debian on 'new' ext4 system partition # !!! # - Some error is below that line !!!Set up 'new' ext4 partition with mount point '/boot'Set up 'new' ext4 partition with mount point '/home'## THIRD iteration made by CALAMARES REPLACEMENTDeleting partition '/dev/sda7'...Create new 99771MiB partition on '/dev/sda' (SAMSUNG SSD PM851 2.5 7mm 256GB) with entries 'root'Set up fat32 partition '/dev/sda1' with mount point '/boot/efi'...Install Debian on 'new' ext4 partition### SECOND iteration which I didn't started to use due to the last couple linesDeleting partition '/dev/sda7'...(ST1000LM024 HN-M101MBB)Create new 99771MiB partition on '/dev/sda' (SAMSUNG SSD PM851 2.5 7mm 256GB)Set flags on 99771MiB 'luks' partition to 'root'Deleting partition '/dev/sda8'...Create new 14697MiB partition on '/dev/sda' (SAMSUNG SSD PM851 2.5 7mm 256GB)Set flags on 14697MiB 'luks' partition to 'swap'Deleting partition '/dev/sda10'...Create new 500MiB partition on '/dev/sda' (SAMSUNG SSD PM851 2.5 7mm 256GB)Set flags on 500MiB 'luks' partition to 'bootDeleting partition '/dev/sdb3'...Create new 444759MiB partition on '/dev/sdb (ST1000LM024 HN-M101MBB)Set up fat32 partition '/deb/sda1' with mount point '/boot/efi'...Install Debian on 'new' luks system partitionSet up 'new' luks partition with mount point '/boot'Set up 'new' luks partition with mount point '/home'### FIRST iteration MANUAL which ended with errorFormat 99754 MiB partition '/dev/sda7' with file system 'luksSet filesystem label 'RT' to partition '/dev/sda7'Deleting partition '/dev/sda10'...Create new 500 MiB partition on '/dev/sda (SAMSUNG SSD PM851 2.5 7mm 256GB)Set flags on 500 MiB 'luks' partition to 'boot'Format 14697 MiB partition '/dev/sda8' with file system 'linuxswap'# Format 444759 MiB partition '/dev/sdb3' with file system ext4 ### Commented out for editing purposesFormat 444759 MiB partition '/dev/sdb3' with file system 'luks'Set filesystem label 'HM' to partition '/dev/sdb3'Set up fat32 partition '/dev/sda1' with mount point '/boot/efi'...Install Debian on luks system partition '/dev/sda7'Set up 'new' luks partition with mount point '/boot'Set up ext4 partition '/dev/sdb3' with mount point '/home'...
How to get attached '/boot' and '/home' partition back to use?

Statistics: Posted by nikobit — 2025-02-16 11:14 — Replies 0 — Views 16



Viewing all articles
Browse latest Browse all 3395

Trending Articles