I am attempting to install a dualboot (Ubuntu on top of Windows 10) to a PC I have just built myself. I have no problem installing Ubuntu, its just I am unable to setup my computer to boot into it afterwards. During the instalation I am told that the GRUB does not install properly and I also hit errors when trying to run a boot repair program in terminal. I am creating the installation using Rufus, and making use of the MBR parition scheme. The Disk I am creating it on is GPT, but when I try use this partition scheme in Rufus an error scheme comes up when I try boot this from a USB stick. This is shown in the next image (and note my bios mode is set to UEFI). For reference my motherboard is a "MSI B450 TOMAHAWK MAX Motherboard ATX". What is the best course of action to take? I found some videos that showed how to convert my from UEFI to legacy boot and to change my disk to a MSB partition, would this be the best solution or will this create further problems down the line?

I bought a brand new 4TB Western Digital Blue HDD, which is connected to my NAS running Debian via usb with an external HDD enclosure. I used the following commands to setup the drive: (parted) mklabel gpt (parted) mkpart primary 0% 100% sudo mkfs.exfat -n 4tbBackup /dev/sdc It seemed to work okay on the Linux machine, but when I plugged it into my Windows PC, it showed up under Disk Management as an unallocated 2048GB partition and another unallocated partition with the rest of the disk on it. I tried switching to gdisk, and it immediately gave me this error: GPT fdisk (gdisk) version 1.0.6 Warning: Partition table header claims that the size of partition table entries is 0 bytes, but this program supports only 128-byte entries. Adjusting accordingly, but partition table may be garbage. Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) How can I totally reset the drive so that I can clear all of this header corruption out and reformat it safely to exFAT?

While trying to install Kali Linux as a secondary OS with Windows 11(primary OS), the partition created for Kali is not visible during the Graphical Install. The hard drive I'm trying to install kali on is of size 1 TB. Even after making a partition of 150 GB, the disk partition menu in the graphical install of kali is not showing the partitions rather showing the disk with one partition of size 932 GB Upon initial research, I tried fixing the partition table using gdisk (since my system has GPT disks), but that didn't help. Primary OS: Windows 11 Disk Type: GPT Image Used: kali-linux-2021.4a-installer-amd64 **EDITED:** Disk Management: Partition Not Visible:

I have a 6TB disk in Debian Linux 12, let's say the disk is /dev/sdd. It's just for data; no parts of the OS are on it. Now I’m trying to use it as a normal disk with the full space in a single partition. If I try to create the partition, fdisk tells me that the max size with a DOS partition is 2TB. If I create that, I get a new device /dev/sdd1, but the size is limited to 2TB, not what I want. To have a single 6TB partition, I need to use a GPT partition table instead of DOS. If I do that, I can create a single partition with fdisk. But then I don’t get a device node for the partition (/dev/sdd1), which I need later for things like formatting. Any ideas? **EDIT** I create the partition that way. fdisk /dev/sdd Tells me then: *The size of this disk is 6 TiB (6597069766656 bytes). DOS partition table format cannot be used on drives for volumes larger than 2199023255040 bytes for 512-byte sectors. Use GUID partition table format (GPT).* Commands are then: g n w That creates a GPT partition table and a new partition with full size and writes it down.

I have 8GB flash memory stick. Sometimes ago I formatted it to be able to install Windows from it. I can't remember what exactly I did but I think I wanted to be able to install Win 7 64-bit to boot in EFI mode. Now I can't reformat it nor in Windows nor in Linux. I tried to convert it to MBR from GPT with gdisk by gdisk /dev/sdc, then w (to write GPT from memory to the drive as the tool reported "Found invalid GPT and valid MBR; converting MBR to GPT format in memory"). Then gdisk /dev/sdc again: # gdisk /dev/sdc GPT fdisk (gdisk) version 0.8.8 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if you don't want to convert your MBR partitions to GPT format! *************************************************************** , opened expert tools with x, z (to destroy GPT). Here is the output: Expert command (? for help): z About to wipe out GPT on /dev/sdc. Proceed? (Y/N): Y GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Blank out MBR? (Y/N): Y # then tried to delete a partition with fdisk # fdisk /dev/sdc Command (m for help): p Disk /dev/sdc: 8086 MB, 8086618112 bytes 249 heads, 62 sectors/track, 1023 cylinders, total 15794176 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 identifier: 0x000a07ca Device Boot Start End Blocks Id System /dev/sdc1 * 62 15793073 7896506 7 HPFS/NTFS/exFAT Command (m for help): d Selected partition 1 Command (m for help): p Disk /dev/sdc: 8086 MB, 8086618112 bytes 249 heads, 62 sectors/track, 1023 cylinders, total 15794176 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 identifier: 0x000a07ca Device Boot Start End Blocks Id System Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Error closing file After this I tried to pull out and plug in the stick again but NTFS mount error window appeared each time. I also tried to rewrite an initial drive area with a test content with badblocks sudo badblocks -w -s -o /tmp/usbstick.log /dev/sdc and with dd sudo dd if=/dev/zero of=/dev/sdc bs=1024k count=2 but I couldn't reformat it to usable state. Is there a way I can restore its factory state? My system: Linux Mint 17.3 **UPDATE** # blkid /dev/sdc1: UUID="675599A00CE338FC" TYPE="ntfs" # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1307 ProdID=0190 Rev=01.00 S: Manufacturer=USBest Technology S: Product=USB Mass Storage Device S: SerialNumber=00000000000004 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=98mA I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

I've installed Arch on a partition, and installed grup as the wiki says grub-install /dev/sda grub-mkconfig -o /boot/grub/grub.cfg Now I only get Archlinux and Advanced options and no Windows. Here's my parted -l output: Model: ATA Hitachi HTS54757 (scsi) Disk /dev/sda: 750GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 135MB 134MB bios_grub 2 135MB 269MB 134MB Mi msftres 3 269MB 86.2GB 85.9GB ntfs Ba msftdata 4 86.2GB 129GB 43.2GB ext4 misc 6 129GB 236GB 107GB ntfs msftdata 7 236GB 343GB 107GB ntfs msftdata 5 343GB 394GB 50.8GB ext4 8 394GB 403GB 9000MB linux-swap(v1) 9 403GB 507GB 103GB ext4 And lsblk -f : NAME FSTYPE LABEL UUID MOUNTPOINT sda |-sda1 |-sda2 |-sda3 ntfs Windows 02F00D3CF00D3785 /media/Windows |-sda4 ext4 25bc874b-1a89-4ff9-a01e-ca39e28155d9 |-sda5 ext4 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 / |-sda6 ntfs Programming 01CE50F6C84EAFE0 /media/Programming |-sda7 ntfs Entertainment 01CE50F6CC660CE0 /media/Entertainment |-sda8 swap 374052bf-9a06-4c34-a1dc-616967b6fe4f [SWAP] `-sda9 ext4 misc2 15b7261e-39a6-4668-9f22-a7c3096a6af5 /media/misc2 sr0 My /boot/grub/grub.cfg content: # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### insmod part_gpt insmod part_msdos if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_gpt insmod ext2 set root='hd0,gpt5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 else search --no-floppy --fs-uuid --set=root 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 fi font="/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_US insmod gettext fi terminal_input console terminal_output gfxterm if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-342ebed5-9592-4246-bdc2-4cd5c5ee92d5' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 else search --no-floppy --fs-uuid --set=root 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 fi echo 'Loading Linux linux ...' linux /boot/vmlinuz-linux root=UUID=342ebed5-9592-4246-bdc2-4cd5c5ee92d5 rw quiet echo 'Loading initial ramdisk ...' initrd /boot/intel-ucode.img /boot/initramfs-linux.img } submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-342ebed5-9592-4246-bdc2-4cd5c5ee92d5' { menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-342ebed5-9592-4246-bdc2-4cd5c5ee92d5' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 else search --no-floppy --fs-uuid --set=root 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 fi echo 'Loading Linux linux ...' linux /boot/vmlinuz-linux root=UUID=342ebed5-9592-4246-bdc2-4cd5c5ee92d5 rw quiet echo 'Loading initial ramdisk ...' initrd /boot/intel-ucode.img /boot/initramfs-linux.img } menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-342ebed5-9592-4246-bdc2-4cd5c5ee92d5' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 else search --no-floppy --fs-uuid --set=root 342ebed5-9592-4246-bdc2-4cd5c5ee92d5 fi echo 'Loading Linux linux ...' linux /boot/vmlinuz-linux root=UUID=342ebed5-9592-4246-bdc2-4cd5c5ee92d5 rw quiet echo 'Loading initial ramdisk ...' initrd /boot/intel-ucode.img /boot/initramfs-linux-fallback.img } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### Content of /etc/default/grub: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Arch" GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="" # Preload both GPT and MBR modules so that they are not missed GRUB_PRELOAD_MODULES="part_gpt part_msdos" # Uncomment to enable Hidden Menu, and optionally hide the timeout count #GRUB_HIDDEN_TIMEOUT=5 #GRUB_HIDDEN_TIMEOUT_QUIET=true # Uncomment to use basic console GRUB_TERMINAL_INPUT=console # Uncomment to disable graphical terminal #GRUB_TERMINAL_OUTPUT=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE=auto # Uncomment to allow the kernel use the same resolution used by grub GRUB_GFXPAYLOAD_LINUX=keep # Uncomment if you want GRUB to pass to the Linux kernel the old parameter # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries GRUB_DISABLE_RECOVERY=true # Uncomment and set to the desired menu colors. Used by normal and wallpaper # modes only. Entries specified as foreground/background. #GRUB_COLOR_NORMAL="light-blue/black" #GRUB_COLOR_HIGHLIGHT="light-cyan/blue" # Uncomment one of them for the gfx desired, a image background or a gfxtheme #GRUB_BACKGROUND="/path/to/wallpaper" #GRUB_THEME="/path/to/gfxtheme" # Uncomment to get a beep at GRUB start #GRUB_INIT_TUNE="480 440 1" #GRUB_SAVEDEFAULT="true"

I have a laptop, with installations of Ubuntu 12.10, and Windows 8. Windows 8 was first installed on the system, and Ubuntu was installed afterwards. During the Ubuntu installation, the installer recognized that there are existing partitions, but failed to see any OS on them. I created another ext4 partition in the free space, and installed Ubuntu. Initially grub only added the entry for Ubuntu, and Ubuntu works ok. Now I wanted to enter w8 settings to Grub manually, and modified /etc/grub.d/40_custom: #!/bin/bash exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry "Windows 8" { insmod part_gpt insmod fat insmod search_fs_uuid insmod chain #set root='(hd0,gpt1)' search --fs_uuid --no-floppy --set=root --hint-bios=hd0,gpt2 --hint efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 chainloader /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi } The search string (second to last) I found with this command: sudo grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi Now after updating grub config, rebooting and selecting windows 8 entry, it complains: error: unspecified search type error: file '/boot/efi/EFI/Microsoft/Boot/bootmgfw.efi' not found Press any key to continue In Ubuntu however, if I do ls /boot/efi/EFI/Microsoft/Boot/b* /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi /boot/efi/EFI/Microsoft/Boot/bootmgr.efi /boot/efi/EFI/Microsoft/Boot/boot.stl /boot/efi/EFI/Microsoft/Boot/bg-BG: bootmgfw.efi.mui bootmgr.efi.mui Now, if I press e to edit the Windows 8 entry, and then select F2 to enter grub shell, indeed if I try to run ls /boot/efi, no files are shown. Funnily enough, if at this point I just type exit, windows 8 will boot up. fdisk -l gives me that it recognizes /dev/sda1 as GPT partition Any ideas what I should do to get grub working "right out of the menu"?

Recently I bought new sshd to replace my old one on my notebook, but I have problem. I installed Ubuntu 15.10 on new one and put the old on usb case I have, but the disk on USB doesnt have partition (I screamed for 5 minutes because I can't lose data). So I moved back my old disk inside the disk bay and put the new on usb case, and all my data was here intact but the disk on usb shows no partition. Both of disks when in usb case show the model and factory correctly but not the partitions. The case is OK, tested with old HDD that doesn't have GPT/EFI partition. How can I mount the external disk so I can transfer my files? Ouput of commands: $ sudo blkid /dev/sdb /dev/sdb: PTTYPE="PMBR" $ sudo parted /dev/sdb print Error: /dev/sdb: unrecognised disk label Model: ST1000LM 014-1EJ164 (scsi) Disk /dev/sdb: 1000GB Sector size (logical/physical): 4096B/4096B Partition Table: unknown Disk Flags: $ sudo gdisk /dev/sdb GPT fdisk (gdisk) version 1.0.0 Partition table scan: MBR: protective BSD: not present APM: not present GPT: not present

I'm having problems with booting a Debian 8 system on which I migrated the root partition from a single hard drive to a RAID1 (mdraid). On every boot, I get the following grub error: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/2ab18cb4-a23d-4e5c-b37d-cbd3077b878c does not exist. Dropping to a shell! modprobe: module ehci-orion not found in modules.dep (initramfs) _/dev/md0_ is not started, so it can't find the root partition: (initramfs) ls /dev/md* ls: /dev/md*: No such file or directory (initramfs) I can, however, start the raid manually just fine: (initramfs) mdadm --assemble --scan mdadm: /dev/md0 has been started with 2 drives. (initramfs) ls /dev/md* /dev/md0 The system will only boot if I manually create the directory _/dev/disk/by-uuid_ and link _md0_: (initramfs) mkdir /dev/disk/by-uuid (initramfs) ln -s /dev/md0 /dev/disk/by-uuid/2ab18cb4-a23d-4e5c-b37d-cbd3077b878c I hope someone can help me figure out why grub doesn't start the md device by itself. I searched the internet and tried about everything I could find but no luck. I'm really lost right now. I want to boot via _BIOS-legacy_, not _UEFI_. The only two connected hard drives (SSD!) are formatted with a _GPT_ partition table and the following partitions (exactly the same): 1 1049kB 2097kB 1049kB bios_grub 2 2150MB 12,9GB 10,7GB ext4 raid (_grub-pc_ needs the first partition to boot from _GPT_ drives) The Raid1 (v0.90 metadata) is formatted directly as _ext4_. Through a live system chroot, I installed _grub-pc_ to _/dev/sda_ and _/dev/sdb_, changed my _fstab_, ran update-grub andupdate-initramfs -u -k all. blkid: /dev/sda2: UUID="b59d3baf-346b-568d-03a2-8b26060640c5" TYPE="linux_raid_member" PARTUUID="0609ba5b-9065-41f8-80ed-6832e3236ec9" /dev/sdb2: UUID="b59d3baf-346b-568d-03a2-8b26060640c5" TYPE="linux_raid_member" PARTUUID="24ee1040-02dd-4867-b4da-5be11d59bdcd" /dev/md0: UUID="2ab18cb4-a23d-4e5c-b37d-cbd3077b878c" TYPE="ext4" /dev/sda1: PARTUUID="df5161cf-b5b3-422c-9ed2-90a7750ac265" /dev/sdb1: PARTUUID="7d20b55b-ba50-4187-b05e-ae1f18b21de3" _mdadm.conf_ contains (only!) the content from mdadm --detail --scan: ARRAY /dev/md0 metadata=0.90 UUID=b59d3baf:346b568d:03a28b26:060640c5 Here is an excerpt from my _/boot/grub/grub.cfg_: load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod part_gpt insmod diskfilter insmod mdraid09 insmod ext2 set root='mduuid/b59d3baf346b568d03a28b26060640c5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/b59d3baf346b568d03a28b26060640c5' 2ab18cb4-a23d-4e5c-b37d-cbd3077b878c else search --no-floppy --fs-uuid --set=root 2ab18cb4-a23d-4e5c-b37d-cbd3077b878c fi echo 'Linux 3.16.0-4-amd64 wird geladen …' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=2ab18cb4-a23d-4e5c-b37d-cbd3077b878c ro rootdelay=20 echo 'Initiale Ramdisk wird geladen …' initrd /boot/initrd.img-3.16.0-4-amd64

I am currently considering moving to UEFI/GPT on my system. I plan to install Windows first and use the ESP created by Windows. My first major question is this: Will Windows automatically use the GPT scheme when installing when it detects that that the system is booted in UEFI? Or will it force using MBR? I read [here](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Microsoft_Windows) that Windows supports booting from disks larger than 2TB, one of the features of GPT, but not that it supports GPT necessarily. My second question is this: The Arch Wiki tells me to mount the ESP at /boot, but where is this supposed directory? Is it the /boot dir of the Arch install? If so, should I after installing chroot into the system and mount the ESP at /boot manually, or should I allow the refind-install script to automatically detect and mount my ESP when I install rEFInd?. Thanks for your help.

When opening GParted on my Fedora 32 system, I receive the following message: I'm not sure what exactly is going wrong here. The system boots fine. I tried running fsck (via adding file /forcefsck and rebooting) but it didn't change anything. EDIT: Partition table is GPT, that's probably relevant eh.

My current idea is to create one software array, class RAID-6, with 4 member drives, using mdadm. Specifically, the drives would be 1 TB HDDs on SATA in a small server Dell T20. Operating System is GNU/Linux Debian 8.6 (later upgraded: Jessie ⟶ Stretch ⟶ Buster ) That would make 2 TB of disk space with 2 TB of parity in my case. *** I would also like to have it with GPT partition table, for that to work, I am unsure how to proceed specifically supposing I would prefer to do this purely over the terminal. As I never created a RAID array, could you guide me on how I should proceed? *** Notes: - This array will serve for the sole data only. No boot or OS on it. - I opted for RAID-6 due to the purpose of this array. Two drive failures the array must be able to survive. Since I am limited by hardware to 4 drives, there is no alternative to RAID-6 that I know of. (However ugly the RAID-6 slowdown may seem, it does not matter in this array.)

I followed the very detailed guide for making hybrid MBR record (GPT/MBR) taken from here Now, gdisk says I have hybrid mbr. But I can only boot in UEFI and cannot do that in BIOS (I use external hard drive). Seems that simple execution of grub-install installs only uefi part. I saw the discussion about requirement for protective entry to be the first on the disk, so I made it the first and that is not the root cause. So the question is how to install GRUB so it would boot OS both being started from BIOS/MBR and UEFI/GPT? **$ sudo gdisk /dev/sdd** GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: hybrid BSD: not present APM: not present GPT: present Found valid GPT with hybrid MBR; using GPT. Command (? for help): r Recovery/transformation command (? for help): o Disk size is 468862128 sectors (223.6 GiB) MBR disk identifier: 0x7213C4A0 MBR partitions: Number Boot Start Sector End Sector Status Code 1 1 208895 primary 0xEE 2 * 208896 1196031 primary 0x83 3 1196032 135413759 primary 0x83 4 200425472 468860927 primary 0x83 Recovery/transformation command (? for help): p Disk /dev/sdd: 468862128 sectors, 223.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): 21773ad9-3d43-4832-85b7-6c841d20ce75 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 468862094 Partitions will be aligned on 1-sector boundaries Total free space is 62183 sectors (30.4 MiB) Number Start (sector) End (sector) Size Code Name 1 63 80324 39.2 MiB EF00 Basic data partition 2 208896 1196031 482.0 MiB 8300 Basic data partition 3 1196032 135413759 64.0 GiB 8300 4 135413760 168968191 16.0 GiB 0700 Basic data partition 5 168968192 200425471 15.0 GiB 0700 Basic data partition 6 200425472 468860927 128.0 GiB 8300 7 81920 149503 33.0 MiB EF02 **$ sudo parted /dev/sdd** GNU Parted 3.2 Using /dev/sdd Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA OCZ-VECTOR150 (scsi) Disk /dev/sdd: 240GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 32.3kB 41.1MB 41.1MB fat32 Basic data partition boot, esp 7 41.9MB 76.5MB 34.6MB bios_grub 2 107MB 612MB 505MB ext4 Basic data partition 3 612MB 69.3GB 68.7GB ext4 4 69.3GB 86.5GB 17.2GB linux-swap(v1) Basic data partition msftdata 5 86.5GB 103GB 16.1GB ntfs Basic data partition msftdata 6 103GB 240GB 137GB ext4 **$ sudo grub-install** Installing for x86_64-efi platform. Installation finished. No error reported.

I have a Dell Latitude 7390 2-in-1 with a 256Gb NVMe installed with dual boot Win10 and Deb12. All working fine. Just running out of space so planned to clone to bigger drive. From Dell site and Crucial upgrade site concluded a 2Tb NVMe M.2 PCIe 4.0 should work. Bought a Kingston of that spec. I have attempted to clone the 256Gb to the 2Tb using, Clonezilla, dd, AOMEI Backupper and Macrium Reflect X Home (Free trial). Both via direct clone with the 2Tb in a USB-C housing or via backup to image file and restore. After replacing the 256Gb with the 2Tb in the Dell, ALL methods of cloning fail to boot. The Kingston is listed in BIOS but I just get a spinning white circle and unit eventually rebooting and repeating. If I boot the Dell from GParted live, clonezilla, or attempt to install a fresh Debian 12, ALL fail to find/list the 2Tb NVME drive, despite it showing in BIOS. If I swap back to the 256Gb the Dell boots fine and from Windows it will see the 2Tb from windows though it marks as offline as it has same disk signature ... all the partitions look as expected from the clone. If I connect to a separate unit running Debian 11 it shows as expected and I can mount the partitions and read write. So this maybe more a Dell question, but any thoughts or knowledge? Have I bought the wrong spec of NVME for that Dell or is there a BIOS setting I need to tweak? More info, the old drive is a "SK hynix SC311 SATA 256Gb" if that is an M2 SSD not NVMe would that prevent the cloning? Also in addition to software already previously listed above, have also now tried Boot-Repair that @oldfred suggested. It lists the 2Tb NVMe like BIOS does, but as per other software it then has no mention of it in the rest of the log Thank you to @oldfred, his comments were main part of answer. Per his comments, I had to put the old drive back in. Apply the AHCI change, then re clone it. I used Macrium and both created an image and also did a direct clone to the new 2Tb NVMe in a USB caddy. Then swapped the 2Tb for the old 256Gb drive, rebooted, which failed. I ran Macrium's boot repair option on the 2Tb but all the blue screen options failed to do anything apart from accessing UEFI settings failed. So option 2 was I booted Macrium's USB recovery media and used it to restore the image to the 2Tb, on rebooting the 2Tb said "Preparing Automatic Repair" and "Diagnosing PC" rebooted did again, but I could select Advanced and enter Safe Mode...which ran fine. Rebooted and finally all good.

We experienced a power outage last Thursday morning. Luckily the OMV server is on battery backup, so I was able to shut the server down. Once power was restored, I restarted the server and the RAID drive is Missing. From what I can tell, during the reboot, a BIOS autorecovery setting applied GPT to 3 of my RAID drives, as seen in the blkid output below. Looking for options to recover this system. Thanks in advance for any assistance. **uname -a** > Linux omvnas 6.1.0-30-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.124-1 > (2025-01-12) x86_64 GNU/Linux **lsblk** NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdb 8:16 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdc 8:32 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdd 8:48 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sde 8:64 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdf 8:80 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdg 8:96 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdh 8:112 0 10.9T 0 disk sdi 8:128 0 10.9T 0 disk └─md0 9:0 0 0B 0 raid6 sdj 8:144 0 10.9T 0 disk sdk 8:160 0 10.9T 0 disk nvme0n1 259:0 0 476.9G 0 disk ├─nvme0n1p1 259:1 0 512M 0 part /boot/efi ├─nvme0n1p2 259:2 0 475.5G 0 part /var/folder2ram/var/cache/samba │ /var/folder2ram/var/lib/monit │ /var/folder2ram/var/lib/rrdcached │ /var/folder2ram/var/spool │ /var/lib/containers/storage/overlay │ /var/folder2ram/var/lib/openmediavault/rrd │ /var/folder2ram/var/tmp │ /var/folder2ram/var/log │ / └─nvme0n1p3 259:3 0 976M 0 part [SWAP] **blkid** /dev/sdf: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="bde193d0-b68d-c1d5-11ed-5f8275a4a220" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/nvme0n1p3: UUID="2bb7348b-aa0a-42a1-af4b-f4ee684c78ba" TYPE="swap" PARTUUID="d804df87-8bf9-45bd-9cb5-da32f39fee2a" /dev/nvme0n1p1: UUID="4647-262F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="8aa9ef68-1a9f-4d0e-a27b-afc72cc70946" /dev/nvme0n1p2: UUID="82bb97eb-6acc-4de0-8361-09b220ad4041" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="537d3034-7576-44ea-a8e8-ccce3d33c1b8" /dev/sdd: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="3017eba0-37a3-83ff-202c-dd24668b7223" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sdb: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="792c5ef1-7fb7-335c-6f63-b5a835548740" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sdi: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="ee6cdfb3-c66c-013a-0918-1573a1f32bfd" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sdg: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="711a8d42-424e-f6f6-9ff4-60cc2bee0cb9" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sde: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="8955e286-76c7-a860-7421-928527ed2f2e" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sdc: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="04f481c7-5f9f-d02b-a759-61d0b880c975" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sda: UUID="cbcc5712-da6b-1419-139a-de9757c7348b" UUID_SUB="8440a728-ed6c-82a2-bbcf-2b533cc73f22" LABEL="omvnas:0" TYPE="linux_raid_member" /dev/sdk: PTUUID="5066a101-8bc4-412b-8c31-9989f6114efe" PTTYPE="gpt" /dev/sdj: PTUUID="0543fe2c-2926-4428-a9bb-4d8478340340" PTTYPE="gpt" /dev/sdh: PTUUID="bed11372-978a-482f-8eff-9d94f18c9b61" PTTYPE="gpt" **mdadm --detail /dev/md0** /dev/md0: Version : 1.2 Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Used Dev Size : 18446744073709551615 Raid Devices : 11 Total Devices : 8 Persistence : Superblock is persistent Update Time : Thu Feb 6 05:21:31 2025 State : active, FAILED, Not Started Active Devices : 8 Working Devices : 8 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 512K Consistency Policy : unknown Name : omvnas:0 (local to host omvnas) UUID : cbcc5712:da6b1419:139ade97:57c7348b Events : 260594 Number Major Minor RaidDevice State - 0 0 0 removed - 0 0 1 removed - 0 0 2 removed - 0 0 3 removed - 0 0 4 removed - 0 0 5 removed - 0 0 6 removed - 0 0 7 removed - 0 0 8 removed - 0 0 9 removed - 0 0 10 removed - 8 64 2 sync /dev/sde - 8 32 0 sync /dev/sdc - 8 0 1 sync /dev/sda - 8 80 9 sync /dev/sdf - 8 48 4 sync /dev/sdd - 8 16 3 sync /dev/sdb - 8 128 5 sync /dev/sdi - 8 96 7 sync /dev/sdg **cat /etc/mdadm/mdadm.conf** # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST # definitions of existing MD arrays ARRAY /dev/md0 metadata=1.2 name=omvnas:0 UUID=cbcc5712:da6b1419:139ade97:57c7348b cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : inactive sdi(S) sde(S) sdg(S) sdf(S) sdd(S) sda(S) sdc(S) sdb(S) 93750140928 blocks super 1.2 unused devices: **mdadm --examine /dev/sd[a-k]** /dev/sda: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : 8440a728:ed6c82a2:bbcf2b53:3cc73f22 Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : aa6cf6bd - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 1 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdb: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : 792c5ef1:7fb7335c:6f63b5a8:35548740 Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : a0a64df4 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 3 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdc: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : 04f481c7:5f9fd02b:a75961d0:b880c975 Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : a3552017 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 0 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdd: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : 3017eba0:37a383ff:202cdd24:668b7223 Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : 52962446 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 4 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sde: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : 8955e286:76c7a860:74219285:27ed2f2e Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : 524ddf1 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 2 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdf: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : bde193d0:b68dc1d5:11ed5f82:75a4a220 Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : b32fb355 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 9 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdg: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : 711a8d42:424ef6f6:9ff460cc:2bee0cb9 Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : 28c8fdd9 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 7 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdh: MBR Magic : aa55 Partition : 4294967295 sectors at 1 (type ee) /dev/sdi: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : cbcc5712:da6b1419:139ade97:57c7348b Name : omvnas:0 (local to host omvnas) Creation Time : Sun Sep 3 15:35:48 2023 Raid Level : raid6 Raid Devices : 11 Avail Dev Size : 23437535232 sectors (10.91 TiB 12.00 TB) Array Size : 105468811776 KiB (98.23 TiB 108.00 TB) Used Dev Size : 23437513728 sectors (10.91 TiB 12.00 TB) Data Offset : 235520 sectors Super Offset : 8 sectors Unused Space : before=235440 sectors, after=21504 sectors State : clean Device UUID : ee6cdfb3:c66c013a:09181573:a1f32bfd Internal Bitmap : 8 sectors from superblock Update Time : Thu Feb 6 05:21:31 2025 Bad Block Log : 512 entries available at offset 56 sectors Checksum : c7f997b8 - correct Events : 260594 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 5 Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdj: MBR Magic : aa55 Partition : 4294967295 sectors at 1 (type ee) /dev/sdk: MBR Magic : aa55 Partition : 4294967295 sectors at 1 (type ee)

I'm partitioning a non-SSD hard disk with *parted* because I want a GPT partition table. parted /dev/sda mklabel gpt Now, I'm trying to create the partitions correctly aligned so I use the following command to know where the first sector begins: parted /dev/sda unit s p free Disk /dev/sda: 488397168s Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 34s 488397134s 488397101s Free Space We can see that it starts in sector 34 (that's the default when this partition table is used). So, to create the first partition I tried: parted /dev/sda mkpart primary 63s 127s to align it on sector 64 since it's a multiple of 8 but it shows: **Warning: The resulting partition is not properly aligned for best performance.** The logical and physical sector sizes in my hard disk are both 512 bytes: cat /sys/block/sda/queue/physical_block_size 512 cat /sys/block/sda/queue/logical_block_size 512 How do I create partitions correctly aligned? What am I doing wrong?

I keep receiving this error: > Warning!! Unsupported GPT (GUID Partition Table) detected. Use GNU Parted I want to go back to the normal MBR. I found some advice [here](http://lukas.zapletalovi.com/2011/12/how-to-get-rid-of-guid-partition-table.html) and did: parted /dev/sda mklabel msdos quit But when I get to the mklabel option it spits out a warning that I will lose all data on /dev/sda. Is there a way to get the normal MBR back without formatting the disk?

I need to extend the size of the logical volumes in a CentOS 7 system and noticed that the current partition table cannot handle the updated disk size, which is around 5TB: Disk /dev/sda: 5497.6 GB, 5497558138880 bytes, 10737418240 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 label type: dos Disk identifier: 0x000bc7c4 Device Boot Start End Blocks Id System /dev/sda1 * 2048 2099199 1048576 83 Linux /dev/sda2 2099200 2147483647 1072692224 8e Linux LVM I know that I have to use parted along with GPT but couldn't find a guideline on how to first change the partition table and then expand the volumes accordingly. Could you please help me with this?

One of my disk (nvme0n1) fails, so it was replaced. Now lsblk shows

nvme0n1     259:0    0 476.9G  0 disk
├─nvme0n1p1 259:5    0   511M  0 part
├─nvme0n1p2 259:6    0 475.9G  0 part
│ └─md2       9:2    0 475.8G  0 raid1 /
└─nvme0n1p3 259:7    0   512M  0 part
nvme1n1     259:1    0 476.9G  0 disk
├─nvme1n1p1 259:2    0   511M  0 part  /boot/efi
├─nvme1n1p2 259:3    0 475.9G  0 part
│ └─md2       9:2    0 475.8G  0 raid1 /
└─nvme1n1p3 259:4    0   512M  0 part  [SWAP]

But I'm afraid that nvme0n1p3 is not mounted as SWAP as nvme1n1p3, and the same situation is with nvme0n1p1. What I do after replacing disk is:

sgdisk --backup=nvme1n1.sgdisk /dev/nvme1n1
sgdisk --load-backup=nvme1n1.sgdisk /dev/nvme0n1
sgdisk -G /dev/nvme0n1
mdadm --manage /dev/md2 --add /dev/nvme0n1p2

Is that correct configuration? If nvme1n1 will fail, system will boot correctly?

I've got a disk image that I need shortened slightly (long story - but it deals with variances in flash drive sizes). The partitions are *already* short enough, but the drive size is not. Basically, I have a disk image that is 15678308352 bytes (30621696 sectors). I'm wanting to reduce the disk image size to 15678292992 bytes (30621666 sectors). The last sector being used by any "real" partition is 30621662 (I'm fine ending there, too, but I padded it by 4 sectors just to be safe). In any case, I'm wanting to resize the partition tables, but I don't really know how, especially since the GPT table is inside a "protected MBR". Here's the output of fdisk showing the protected MBR:

fdisk mydisk.img 
Disk: mydisk.img	geometry: 1906/255/63 [30621696 sectors]
Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
 1: EE    0   0   2 - 1023 255  63 [         1 -   30621695] 
 2: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 3: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused

Here's the output of gdisk showing the GPT info:

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): p
Disk mydisk.img: 30621696 sectors, 14.6 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): BD99B4B8-8070-0648-AEA4-B28BCD949EB7
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30621662
Partitions will be aligned on 2048-sector boundaries
Total free space is 18398 sectors (9.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            8192          249855   118.0 MiB   8300  primary
   2          260096        30621662   14.5 GiB    8300  primary

As you can see, I have plenty of room to shrink the disk but I just don't know how. I tried manually editing the MBR partition size in hexedit, but then I got all sorts of warnings on the GPT partition. Any ideas?