I have been trying to install and run Arch on my old Dell Latitude E6410 pc from a USB for the past few days and keep encountering the same issue. The Arch installer is unable to recognize my HDD. The laptop is not secure boot compatible, I am currently running Linux Mint on it, and I have set SATA set to AHCI as many other forums recommended. This is the output of lsblk when I run it in the arch installer:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 794.4M 1 loop /run/archiso/airootfs
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 513M 0 part
└─sda3 8:3 0 232.4G 0 part
sdb 8:16 1 58.6G 0 disk
├─sdb1 8:17 1 954M 0 part
└─sdb2 8:18 1 165M 0 part
sr0 11:0 1 1024M 0 rom
And this is the output of fdisk -l:
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WD2500BEKT-7
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: 63AB5033-8770-49EC-BF7D-8BCD6DA66C37
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 1054719 1050624 513M EFI System
/dev/sda3 1054720 488396799 487342080 232.4G Linux filesystem
Disk /dev/sdb: 58.59 GiB, 62914560000 bytes, 122880000 sectors
Disk model: Flash Disk
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: dos
Disk identifier: 0xf9f63ac3
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 1953791 1953728 954M 0 Empty
/dev/sdb2 1953792 2291711 337920 165M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 794.42 MiB, 833007616 bytes, 1626968 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
Firstly, I am not sure how to go about resolving the message "The backup GPT table is corrupt, but the primary appears OK, so that will be used.", I am not sure if this could be a source of the problem or a symptom. You will also notice that the lsblk command does not recognize the HDD, but the fdisk -l command does.
Any recommendations?
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 794.4M 1 loop /run/archiso/airootfs
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 513M 0 part
└─sda3 8:3 0 232.4G 0 part
sdb 8:16 1 58.6G 0 disk
├─sdb1 8:17 1 954M 0 part
└─sdb2 8:18 1 165M 0 part
sr0 11:0 1 1024M 0 rom
And this is the output of fdisk -l:
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WD2500BEKT-7
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: 63AB5033-8770-49EC-BF7D-8BCD6DA66C37
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 1054719 1050624 513M EFI System
/dev/sda3 1054720 488396799 487342080 232.4G Linux filesystem
Disk /dev/sdb: 58.59 GiB, 62914560000 bytes, 122880000 sectors
Disk model: Flash Disk
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: dos
Disk identifier: 0xf9f63ac3
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 1953791 1953728 954M 0 Empty
/dev/sdb2 1953792 2291711 337920 165M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 794.42 MiB, 833007616 bytes, 1626968 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
Firstly, I am not sure how to go about resolving the message "The backup GPT table is corrupt, but the primary appears OK, so that will be used.", I am not sure if this could be a source of the problem or a symptom. You will also notice that the lsblk command does not recognize the HDD, but the fdisk -l command does.
Any recommendations?