Skip to main content
Inline image, minor grammar, corrected code blocs
Source Link
 root@mint:/home/mint# gdisk /dev/sda GPT fdisk (gdisk) version 1.0.8 Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: ERROR Main partition table: OK Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** 
 root@mint:/home/mint# gdisk /dev/sda GPT fdisk (gdisk) version 1.0.8 Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: ERROR Main partition table: OK Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** 
Inline image, minor grammar, corrected code blocs
Source Link

https://i.sstatic.net/d1REs.pnghttps://i.sstatic.net/d1REs.png Trying

Trying to install mintLinux Mint to dual-boot with Windows 11, but i I always get the above (linked image) error, i`m. I`m not sure what is wrong, drive works perfectly on windowsWindows and when iI format it to ntfs, fat32, ext2, etc... it works perfectly as well. I cannoutcannot mount it either, please help me, (the. The device iI want to install it to is /dev/sda, a SSD of 250gb) and my installation device is a 16gb pen-drive. Also, fdisk -l

fdisk -l yields this=:

root@mint:/home/mint# fdisk -l Disk /dev/loop0: 2.34 GiB, 2515390464 bytes, 4912872 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/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SSSTC CL1-4D256 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: 5AEAC324-E073-45E4-A1E5-7FFB0E9C35DB Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 498065776 497498481 237.2G Microsoft basic data /dev/nvme0n1p4 498069504 500117503 2048000 1000M Windows recovery environment Disk /dev/sdb: 14.32 GiB, 15376318464 bytes, 30031872 sectors Disk model: Cruzer Blade 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: 07896644-3E61-4841-B41A-CA3F44823CCE Device Start End Sectors Size Type /dev/sdb1 64 5228883 5228820 2.5G Microsoft basic data /dev/sdb2 5228884 5237379 8496 4.1M EFI System /dev/sdb3 5238784 30031808 24793025 11.8G Linux filesystem The backup GPT table is corrupt, but the primary appears OK, so that will be used. Disk /dev/sda: 234.38 GiB, 251658240000 bytes, 491520000 sectors Disk model: SD/MMC/MS PRO 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: 1D9ED2E0-08EC-4B50-BA77-FDDE180000F0 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 491517951 490467328 233.9G Linux filesystem``` Also, after doing mkdir.ext4 on sda=filesystem ```root@mint

After doing mkdir.ext4 on /dev/sda:

root@mint:/home/mint# mkfs.ext4 /dev/sda mke2fs 1.46.5 (30-Dec-2021) Found a gpt partition table in /dev/sda Proceed anyway? (y,N) y Creating filesystem with 61440000 4k blocks and 15360000 inodes Filesystem UUID: 72493794-1b54-4809-9d60-d28eff016d6a Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done``` I thought this would have fixed it but now it gave me done 

I thought this would have fixed it but now it gave me

https://i.sstatic.net/d1REs.png Trying to install mint to dual-boot with Windows 11, but i always get the above (linked image) error, i`m not sure what is wrong, drive works perfectly on windows and when i format it to ntfs, fat32, ext2, etc... it works perfectly as well. I cannout mount it either, please help me, (the device i want to install it to is /dev/sda, a SSD of 250gb) and my installation device is a 16gb pen-drive. Also, fdisk -l yields this=

Disk /dev/loop0: 2.34 GiB, 2515390464 bytes, 4912872 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/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SSSTC CL1-4D256 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: 5AEAC324-E073-45E4-A1E5-7FFB0E9C35DB Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 498065776 497498481 237.2G Microsoft basic data /dev/nvme0n1p4 498069504 500117503 2048000 1000M Windows recovery environment Disk /dev/sdb: 14.32 GiB, 15376318464 bytes, 30031872 sectors Disk model: Cruzer Blade 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: 07896644-3E61-4841-B41A-CA3F44823CCE Device Start End Sectors Size Type /dev/sdb1 64 5228883 5228820 2.5G Microsoft basic data /dev/sdb2 5228884 5237379 8496 4.1M EFI System /dev/sdb3 5238784 30031808 24793025 11.8G Linux filesystem The backup GPT table is corrupt, but the primary appears OK, so that will be used. Disk /dev/sda: 234.38 GiB, 251658240000 bytes, 491520000 sectors Disk model: SD/MMC/MS PRO 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: 1D9ED2E0-08EC-4B50-BA77-FDDE180000F0 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 491517951 490467328 233.9G Linux filesystem``` Also, after doing mkdir.ext4 on sda= ```root@mint:/home/mint# mkfs.ext4 /dev/sda mke2fs 1.46.5 (30-Dec-2021) Found a gpt partition table in /dev/sda Proceed anyway? (y,N) y Creating filesystem with 61440000 4k blocks and 15360000 inodes Filesystem UUID: 72493794-1b54-4809-9d60-d28eff016d6a Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done``` I thought this would have fixed it but now it gave me  

https://i.sstatic.net/d1REs.png

Trying to install Linux Mint to dual-boot with Windows 11 I always get the above error. I`m not sure what is wrong, drive works perfectly on Windows and when I format it to ntfs, fat32, ext2, etc... it works perfectly as well. I cannot mount it either. The device I want to install it to is /dev/sda, a SSD of 250gb and my installation device is a 16gb pen-drive.

fdisk -l yields:

root@mint:/home/mint# fdisk -l Disk /dev/loop0: 2.34 GiB, 2515390464 bytes, 4912872 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/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SSSTC CL1-4D256 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: 5AEAC324-E073-45E4-A1E5-7FFB0E9C35DB Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 498065776 497498481 237.2G Microsoft basic data /dev/nvme0n1p4 498069504 500117503 2048000 1000M Windows recovery environment Disk /dev/sdb: 14.32 GiB, 15376318464 bytes, 30031872 sectors Disk model: Cruzer Blade 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: 07896644-3E61-4841-B41A-CA3F44823CCE Device Start End Sectors Size Type /dev/sdb1 64 5228883 5228820 2.5G Microsoft basic data /dev/sdb2 5228884 5237379 8496 4.1M EFI System /dev/sdb3 5238784 30031808 24793025 11.8G Linux filesystem The backup GPT table is corrupt, but the primary appears OK, so that will be used. Disk /dev/sda: 234.38 GiB, 251658240000 bytes, 491520000 sectors Disk model: SD/MMC/MS PRO 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: 1D9ED2E0-08EC-4B50-BA77-FDDE180000F0 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 491517951 490467328 233.9G Linux filesystem 

After doing mkdir.ext4 on /dev/sda:

root@mint:/home/mint# mkfs.ext4 /dev/sda mke2fs 1.46.5 (30-Dec-2021) Found a gpt partition table in /dev/sda Proceed anyway? (y,N) y Creating filesystem with 61440000 4k blocks and 15360000 inodes Filesystem UUID: 72493794-1b54-4809-9d60-d28eff016d6a Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done 

I thought this would have fixed it but now it gave me

Source Link

Error resizing partition (Linux Mint Installer error)

https://i.sstatic.net/d1REs.png Trying to install mint to dual-boot with Windows 11, but i always get the above (linked image) error, i`m not sure what is wrong, drive works perfectly on windows and when i format it to ntfs, fat32, ext2, etc... it works perfectly as well. I cannout mount it either, please help me, (the device i want to install it to is /dev/sda, a SSD of 250gb) and my installation device is a 16gb pen-drive. Also, fdisk -l yields this=

Disk /dev/loop0: 2.34 GiB, 2515390464 bytes, 4912872 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/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SSSTC CL1-4D256 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: 5AEAC324-E073-45E4-A1E5-7FFB0E9C35DB Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 498065776 497498481 237.2G Microsoft basic data /dev/nvme0n1p4 498069504 500117503 2048000 1000M Windows recovery environment Disk /dev/sdb: 14.32 GiB, 15376318464 bytes, 30031872 sectors Disk model: Cruzer Blade 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: 07896644-3E61-4841-B41A-CA3F44823CCE Device Start End Sectors Size Type /dev/sdb1 64 5228883 5228820 2.5G Microsoft basic data /dev/sdb2 5228884 5237379 8496 4.1M EFI System /dev/sdb3 5238784 30031808 24793025 11.8G Linux filesystem The backup GPT table is corrupt, but the primary appears OK, so that will be used. Disk /dev/sda: 234.38 GiB, 251658240000 bytes, 491520000 sectors Disk model: SD/MMC/MS PRO 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: 1D9ED2E0-08EC-4B50-BA77-FDDE180000F0 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 491517951 490467328 233.9G Linux filesystem``` Also, after doing mkdir.ext4 on sda= ```root@mint:/home/mint# mkfs.ext4 /dev/sda mke2fs 1.46.5 (30-Dec-2021) Found a gpt partition table in /dev/sda Proceed anyway? (y,N) y Creating filesystem with 61440000 4k blocks and 15360000 inodes Filesystem UUID: 72493794-1b54-4809-9d60-d28eff016d6a Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done``` I thought this would have fixed it but now it gave me