Disk drive geometry and partition layouts for well know OS
-
I’m just starting this thread as a place to hang typical disk structures for well known operating systems as viewed by linux.
Commands used:
gdisk,blkid, (lsblk,pvdisplay,vgdisplay,lvdisplay)Update: The developers think they have a moderate understanding of what it takes to identify the US English versions of Win10, and Win7. They have asked if you have installs of Windows 10 in your native languages (not US English) that you also participate in this data collection. They really need to see Windows installs in German, French, Spanish, and the Cyrillic countries to get a good understanding of the disk structure. Also they need to see a few versions of OSX to make sure they are fully supported with these new disk identification routines. Hopefully with this new information they can craft a better multi-language solution for single disk resizable imaging. Also for linux, if you hand craft a specific hard drive layout (not using the automated disk provisioning) they would also like you to provide that information too. The better understanding they can get before any code is rewritten the better the final product will be. To get there they need your help with collecting data.
-
Linux Mint 18.1
In this case I let linux mint choose the disk structure
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.1 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. *************************************************************** Disk /dev/sda: 488397168 sectors, 232.9 GiB Logical sector size: 512 bytes Disk identifier (GUID): 3E9C3EAB-FAA9-46D9-8B58-B08785E0D7AD Partition table holds up to 128 entries First usable sector is 34, last usable sector is 488397134 Partitions will be aligned on 2048-sector boundaries Total free space is 4397 sectors (2.1 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 471818239 225.0 GiB 8300 Linux filesystem 5 471820288 488396799 7.9 GiB 8200 Linux swaplsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232.9G 0 disk ├─sda1 8:1 0 225G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 7.9G 0 part [SWAP] sr0 11:0 1 1024M 0 romblkid/dev/sda1: UUID="7f56bc4d-3e93-43b5-b3d4-88f5b9c5e514" TYPE="ext4" PARTUUID="cb247ec0-01" /dev/sda5: UUID="171606b8-0482-4884-9e1f-00ca49e44e32" TYPE="swap" PARTUUID="cb247ec0-05" -
Raspbian <something>
gdisk -l /dev/mmcblk0GPT fdisk (gdisk) version 0.8.10 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. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/mmcblk0: 60367872 sectors, 28.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 1EC5C2B8-4DA2-48A9-8CFA-D0441073EF09 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 60367838 Partitions will be aligned on 2048-sector boundaries Total free space is 8158 sectors (4.0 MiB) Number Start (sector) End (sector) Size Code Name 1 8192 137215 63.0 MiB 0700 Microsoft basic data 2 137216 60367871 28.7 GiB 8300 Linux filesystemlsblksudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 28.8G 0 disk ├─mmcblk0p2 179:2 0 28.7G 0 part / └─mmcblk0p1 179:1 0 63M 0 part /bootblkid[empty] -
Centos 7.2
gdisk -lGPT fdisk (gdisk) version 0.8.6 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. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/sda: 41943040 sectors, 20.0 GiB Logical sector size: 512 bytes Disk identifier (GUID): FCA9593C-4AE9-4B86-B1F7-33A8DBAD5A37 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 41943006 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 1026047 500.0 MiB 8300 Linux filesystem 2 1026048 41943039 19.5 GiB 8E00 Linux LVMlsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT fd0 2:0 1 4K 0 disk sda 8:0 0 20G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 19.5G 0 part ├─centos-root 253:0 0 17.5G 0 lvm / └─centos-swap 253:1 0 2G 0 lvm [SWAP] sr0 11:0 1 1024M 0 romblkid/dev/mapper/centos-root: UUID="d44b9525-5962-4059-9dd0-475aadea659c" TYPE="xfs" /dev/sda2: UUID="VlX1uI-dwcH-BAPR-Xmjo-iQ98-1evp-yVWZME" TYPE="LVM2_member" /dev/sda1: UUID="dfb28d15-7228-4987-bd8b-732a964488f1" TYPE="xfs" /dev/mapper/centos-swap: UUID="3ec11630-6c88-418e-b2b5-b042f00a973b" TYPE="swap"pvdisplay- LVM Physical volume--- Physical volume --- PV Name /dev/sda2 VG Name centos PV Size 19.51 GiB / not usable 3.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 4994 Free PE 10 Allocated PE 4984 PV UUID VlX1uI-dwcH-BAPR-Xmjo-iQ98-1evp-yVWZMEvgdisplay- LVM Volume Group--- Volume group --- VG Name centos System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size <19.51 GiB PE Size 4.00 MiB Total PE 4994 Alloc PE / Size 4984 / <19.47 GiB Free PE / Size 10 / 40.00 MiB VG UUID jKAdZy-j3ym-Efp8-eIdb-MCBY-BNDv-XLf1xhlvdisplay- LVM Logical Volume--- Logical volume --- LV Path /dev/centos/swap LV Name swap VG Name centos LV UUID ICdNca-Ncxk-oDMb-zOwU-5hkx-9gjT-S46yg6 LV Write Access read/write LV Creation host, time centos025, 2017-03-14 13:29:31 -0400 LV Status available # open 2 LV Size 2.00 GiB Current LE 512 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 8192 Block device 253:1 --- Logical volume --- LV Path /dev/centos/root LV Name root VG Name centos LV UUID 50D90o-oUBd-1nH3-02J3-7gYR-zDUA-2dlJbd LV Write Access read/write LV Creation host, time centos025, 2017-03-14 13:29:31 -0400 LV Status available # open 1 LV Size <17.47 GiB Current LE 4472 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 8192 Block device 253:0 -
Windows XP
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Disk /dev/sda: 20971520 sectors, 10.0 GiB Logical sector size: 512 bytes Disk identifier (GUID): 8E6AF16F-9D5F-47A2-98E1-0C7094DB7863 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 20971486 Partitions will be aligned on 1-sector boundaries Total free space is 22756 sectors (11.1 MiB) Number Start (sector) End (sector) Size Code Name 1 63 20948759 10.0 GiB 0700 Microsoft basic datalsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 10G 0 disk `-sda1 8:1 0 10G 0 partlbkid/dev/sda1: UUID="4C784EA1784E89A2" TYPE="ntfs" PARTUUID="08b508b4-01" -
Ubuntu 16.04
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Disk /dev/sda: 104857600 sectors, 50.0 GiB Logical sector size: 512 bytes Disk identifier (GUID): B8FC208F-1D9C-4E78-9E92-142EA35D83B5 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 104857566 Partitions will be aligned on 2048-sector boundaries Total free space is 6077 sectors (3.0 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 999423 487.0 MiB 8300 Linux filesystem 5 1001472 104855551 49.5 GiB 8E00 Linux LVMlsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 50G 0 disk |-sda1 8:1 0 487M 0 part |-sda2 8:2 0 1K 0 part `-sda5 8:5 0 49.5G 0 partblkid/dev/ram0: UUID="d9d7b22e-186a-4918-821c-c543616297f9" TYPE="ext2" /dev/sda1: UUID="e88cfde7-80b7-4b2d-8f61-288b40016752" TYPE="ext2" PARTUUID="6014c465-01" /dev/sda5: UUID="quIHsI-8NLc-u6Mf-rYlY-qPZc-FovD-SnThF5" TYPE="LVM2_member" PARTUUID="6014c465-05" -
Windows 10 Creators Update Fall 2017
As seen by FOS.
This system arrived with Dell Win10 OEM installed and FOG was used to install Win7 Pro. Then (some time later) Win10 OEM DVD was used to reinstall Dell Win10 OEM, and then was updated to Creator’s update with a forced download from MS. The point being this system was not a clean as delivered install of Win10 OEM.
gdisk -l /dev/sdaPT fdisk (gdisk) version 1.0.0 The protective MBR's 0xEE partition is oversized! Auto-repairing. Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 500118192 sectors, 238.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 27E39075-B7C4-4287-9444-A94B165953C7 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 500118158 Partitions will be aligned on 2048-sector boundaries Total free space is 6411 sectors (3.1 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB EF00 EFI system partition 2 206848 239615 16.0 MiB 0C01 Microsoft reserved ... 3 239616 497422689 237.1 GiB 0700 Basic data partition 4 497424384 499193855 864.0 MiB 2700 5 499195904 500117503 450.0 MiB 2700 Basic data partitionlsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 238.5G 0 disk |-sda1 8:1 0 100M 0 part |-sda2 8:2 0 16M 0 part |-sda3 8:3 0 237.1G 0 part |-sda4 8:4 0 864M 0 part `-sda5 8:5 0 450M 0 partblkid/dev/sda1: LABEL="SYSTEM" UUID="1679-102F" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="a069af86-d72b-45b6-aef4-306cbb829357" /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="ce468e9b-2f1d-49ff-b100-79876caafc87" /dev/sda3: UUID="62347F26347EFBFB" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="47eaa706-b711-46c6-aa49-afb19610f0d4" /dev/sda4: UUID="32D8CAD0D8CA9211" TYPE="ntfs" PARTUUID="f3d1ef6a-104b-4f5f-949e-397f7e9bb713" /dev/sda5: LABEL="Windows RE tools" UUID="66C87BB2C87B7F5D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="47461ac5-019d-4679-9b3b-f8f78c405fdf" -
Windows 10 Creator’s Update Fall 2017
As seen by FOS
This system is a new(ish) remanufactured Dell laptop with a remanufacurers OEM version of Win10 (installed by OEM reman) then upgraded to the latest release of Win10 Fall 2017.
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.0 The protective MBR's 0xEE partition is oversized! Auto-repairing. Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 537234768 sectors, 256.2 GiB Logical sector size: 512 bytes Disk identifier (GUID): 87A12144-5FF9-49F9-87FA-EBA23517B6F8 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 537234734 Partitions will be aligned on 2048-sector boundaries Total free space is 6543 sectors (3.2 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB EF00 EFI system partition 2 206848 239615 16.0 MiB 0C01 Microsoft reserved ... 3 239616 534532989 254.8 GiB 0700 Basic data partition 4 534534144 536309759 867.0 MiB 2700 5 536311808 537233407 450.0 MiB 2700 Basic data partitionlsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 256.2G 0 disk |-sda1 8:1 0 100M 0 part |-sda2 8:2 0 16M 0 part |-sda3 8:3 0 254.8G 0 part |-sda4 8:4 0 867M 0 part `-sda5 8:5 0 450M 0 partblkid/dev/sda1: LABEL="SYSTEM" UUID="7CD5-4E08" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="21f40101-fd5d-42ca-b6f4-bd7e37a432f9" /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="ed528880-5a44-4f85-a0eb-dafaea4c0b42" /dev/sda3: UUID="541AE5961AE57600" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="cc18433b-8ea1-4bd5-80dc-d2902bde9444" /dev/sda4: UUID="7CE46313E462CEC8" TYPE="ntfs" PARTUUID="66b7a3fe-3fb2-418e-af4b-6b245bbcb16a" /dev/sda5: LABEL="Windows RE tools" UUID="DAD4DFF3D4DFD03D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e22ccd88-9c86-4d1d-9b5e-213165371d95"/dev/sda1 “EFI system partition”
# ls -la /mnt total 1 1 drwxr-xr-x 5 root root 1024 Aug 29 06:20 EFI # ls -la /mnt/EFI total 5 drwxr-xr-x 5 root root 1024 Aug 29 06:20 . drwxr-xr-x 3 root root 1024 Jan 1 1970 .. drwxr-xr-x 2 root root 1024 Aug 28 18:27 Boot drwxr-xr-x 3 root root 1024 Aug 29 06:20 Dell drwxr-xr-x 4 root root 1024 Aug 28 18:27 Microsoft # ls -la /mnt/EFI/Microsoft total 9 drwxr-xr-x 4 root root 1024 Aug 28 18:27 . drwxr-xr-x 5 root root 1024 Aug 29 06:20 .. drwxr-xr-x 44 root root 6144 Aug 28 18:27 Boot drwxr-xr-x 2 root root 1024 Aug 28 18:27 Recovery/dev/sda4
# ls -la /mnt total 5 drwx------ 1 root root 4096 Aug 29 04:22 . drwxr-xr-x 18 root root 1024 Nov 9 12:28 .. drwx------ 1 root root 0 Aug 29 08:21 Recovery drwx------ 1 root root 0 Aug 29 04:22 'System Volume Information' # ls -la /mnt/Recovery total 4 drwx------ 1 root root 0 Aug 29 08:21 . drwx------ 1 root root 4096 Aug 29 04:22 .. drwx------ 1 root root 0 Aug 29 04:31 WindowsRE # ls -la /mnt/Recovery/WindowsRE total 509804 drwx------ 1 root root 0 Aug 29 04:31 . drwx------ 1 root root 0 Aug 29 08:21 .. -rw------- 1 root root 1076 Aug 29 04:31 ReAgent.xml -rw------- 1 root root 518864230 Aug 29 08:20 Winre.wim -rw------- 1 root root 3170304 Mar 18 2017 boot.sdi/dev/sda5 “Microsoft reserved partition”
Seems to be a repeat of /dev/sda4, /mnt/Recovery/WindowsRE doesn't contain any files. -
Win10 Fall 2017 upgraded from Win7 Pro
As seen by FOS
This system is a bit of an anomaly. This system had windows 7 pro installed and then was upgraded during the free Windows 10 upgrade program. To complicate things a bit more, this system has 4 hard drives. There are 2 raid arrays using the onboard intel “fake” raid controller. The smaller array is comprised of 2 SSD in a raid 0 configuration. The second array is comprised of 2 465GB hard drives in a raid 1 configuration. Looking at lsblk I can’t really make heads or tails of how the disks are constructed. The 223GB drives are the ssd drives. and the 465GB drives are the rotating hard drives. FWIW: This system is in legacy (bios) mode.
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Warning! Secondary partition table overlaps the last partition by 468849521 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/sda: 468862128 sectors, 223.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): DDC57369-F834-4BBA-8A2F-95AC681F9180 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 468862094 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB 0700 Microsoft basic data 2 206848 936790015 446.6 GiB 0700 Microsoft basic data 3 936790016 937711615 450.0 MiB 2700 Windows REgdisk -l /dev/sddGPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Exact type match not found for type code DE00; assigning type code for 'Linux filesystem' Disk /dev/sdd: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 4082E82F-3643-4773-9E09-C7787CF25435 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 8-sector boundaries Total free space is 8740 sectors (4.3 MiB) Number Start (sector) End (sector) Size Code Name 1 63 128519 62.7 MiB 8300 Linux filesystem 2 129024 4323327 2.0 GiB 0700 Microsoft basic data 3 4323328 976764927 463.7 GiB 0700 Microsoft basic datalsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk |-sda1 8:1 0 100M 0 part `-sda2 8:2 0 223.5G 0 part sdb 8:16 0 223.6G 0 disk sdc 8:32 0 465.8G 0 disk `-sdc1 8:33 0 465.8G 0 part sdd 8:48 0 465.8G 0 disk |-sdd1 8:49 0 62.7M 0 part |-sdd2 8:50 0 2G 0 part `-sdd3 8:51 0 463.7G 0 part sde 8:64 1 29.1G 0 disk `-sde1 8:65 1 121M 0 partblkid/dev/ram0: UUID="3db56938-95cb-4bd6-a325-4ba458198604" TYPE="ext2" /dev/sda1: PARTUUID="c657bdb6-01" /dev/sdb: TYPE="isw_raid_member" /dev/sdd1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07D9-031E" TYPE="vfat" PARTUUID="114116d9-01" /dev/sdd2: PARTUUID="114116d9-02" /dev/sdd3: PARTUUID="114116d9-03" /dev/sde1: SEC_TYPE="msdos" LABEL="GRUB" UUID="367A-397D" TYPE="vfat" PARTUUID="dbbe8098-01" -
Win10 Fall 2017 upgraded from Win7 Pro
This is the second attempt to collect a bit more information on this same system.
https://forums.fogproject.org/topic/11070/disk-drive-geometry-and-partition-layouts-for-well-know-os/9
The issue I was running into is that the computer was running RAID on intel’s “fake raid” (i.e. hardware assisted software raid). When I collected the data the first time I did not take into account I needed to have the RAID kernel drivers enabled using the kernel parametermdraid=trueas outlined in this tutorial: https://forums.fogproject.org/topic/7882/capture-deploy-to-target-computers-using-intel-rapid-storage-onboard-raid So that explains why I had a hard time understanding the disk structure as it was being presented to FOS. I also discovered (for some unknown reason) when I setup this computer I set the data drive up as raid 0 (striping) and not raid 1 (mirroring) like I thought. Hmmmmm…So the following info is being generated with the mdraid kernel parameter enabled.
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Warning! Secondary partition table overlaps the last partition by 468849521 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/sda: 468862128 sectors, 223.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): 824735B4-8872-4BDB-A1EB-AD2E1DC47DBF Partition table holds up to 128 entries First usable sector is 34, last usable sector is 468862094 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB 0700 Microsoft basic data 2 206848 936790015 446.6 GiB 0700 Microsoft basic data 3 936790016 937711615 450.0 MiB 2700 Windows REgdisk -l /dev/md124(the logical array)GPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Disk /dev/md124: 937713664 sectors, 447.1 GiB Logical sector size: 512 bytes Disk identifier (GUID): DD15BBA2-DB04-4CDE-9C39-604AA3A9015F Partition table holds up to 128 entries First usable sector is 34, last usable sector is 937713630 Partitions will be aligned on 2048-sector boundaries Total free space is 4029 sectors (2.0 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB 0700 Microsoft basic data 2 206848 936790015 446.6 GiB 0700 Microsoft basic data 3 936790016 937711615 450.0 MiB 2700 Windows REgdisk -l /dev/sdcGPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Warning! Secondary partition table overlaps the last partition by 976758769 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/sdc: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 77A3546C-A31D-4134-9E04-681DB01678E1 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 1953531903 931.5 GiB 0700 Microsoft basic datagdisk -l /dev/md125(the logical array)GPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Disk /dev/md125: 1953536000 sectors, 931.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 600AE6A8-463C-4363-BC6A-0B1ED148F3A4 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1953535966 Partitions will be aligned on 2048-sector boundaries Total free space is 6077 sectors (3.0 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 1953531903 931.5 GiB 0700 Microsoft basic datalsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk `-md124 9:124 0 447.1G 0 raid0 |-md124p1 259:0 0 100M 0 md |-md124p2 259:1 0 446.6G 0 md `-md124p3 259:2 0 450M 0 md sdb 8:16 0 223.6G 0 disk `-md124 9:124 0 447.1G 0 raid0 |-md124p1 259:0 0 100M 0 md |-md124p2 259:1 0 446.6G 0 md `-md124p3 259:2 0 450M 0 md sdc 8:32 0 465.8G 0 disk `-md125 9:125 0 931.5G 0 raid0 sdd 8:48 0 465.8G 0 disk `-md125 9:125 0 931.5G 0 raid0 sde 8:64 1 29.1G 0 disk `-sde1 8:65 1 121M 0 partblkid/dev/ram0: UUID="3db56938-95cb-4bd6-a325-4ba458198604" TYPE="ext2" /dev/sda: TYPE="isw_raid_member" /dev/sdb: TYPE="isw_raid_member" /dev/sdc: TYPE="isw_raid_member" /dev/sdd: TYPE="isw_raid_member" /dev/sde1: SEC_TYPE="msdos" LABEL="GRUB" UUID="367A-397D" TYPE="vfat" PARTUUID="dbbe8098-01" /dev/md125: PTUUID="5816dc85" PTTYPE="dos" /dev/md124: PTUUID="c657bdb6" PTTYPE="dos" /dev/md124p1: LABEL="System Reserved" UUID="C6E4AA25E4AA1827" TYPE="ntfs" PARTUUID="c657bdb6-01" /dev/md124p2: UUID="D02AAB7A2AAB5BEA" TYPE="ntfs" PARTUUID="c657bdb6-02" /dev/md124p3: UUID="926ACC2A6ACC0D43" TYPE="ntfs" PARTUUID="c657bdb6-03"Here is some additional information the developers asked me to collect.
mount.ntfs-3g /dev/md124p1 /mnt
`ls -la /mnt’rwxrwxrwx 1 root root 4096 Oct 1 21:49 . drwxr-xr-x 18 root root 1024 Nov 9 12:28 .. -rwxrwxrwx 1 root root 1 Jul 16 2016 BOOTNXT -rwxrwxrwx 1 root root 8192 Sep 27 14:52 BOOTSECT.BAK drwxrwxrwx 1 root root 8192 Oct 1 21:49 Boot drwxrwxrwx 1 root root 0 Feb 22 2014 'Program Files' drwxrwxrwx 1 root root 0 Feb 22 2014 ProgramData drwxrwxrwx 1 root root 0 Jul 18 2016 Recovery drwxrwxrwx 1 root root 4096 Jul 17 2016 'System Volume Information' -rwxrwxrwx 1 root root 389328 Sep 7 09:23 bootmgrls -la /mnt/Bootdrwxrwxrwx 1 root root 8192 Oct 1 21:49 . drwxrwxrwx 1 root root 4096 Oct 1 21:49 .. -rwxrwxrwx 1 root root 45056 Nov 12 2017 BCD -rwxrwxrwx 1 root root 51200 Jul 18 2016 BCD.LOG -rwxrwxrwx 2 root root 0 Feb 22 2014 BCD.LOG1 -rwxrwxrwx 2 root root 0 Feb 22 2014 BCD.LOG2 -rwxrwxrwx 1 root root 65536 Sep 27 14:52 BOOTSTAT.DAT drwxrwxrwx 1 root root 4096 Sep 27 14:52 Fonts drwxrwxrwx 1 root root 0 Sep 27 14:52 Resources drwxrwxrwx 1 root root 0 Oct 1 21:50 bg-BG -rwxrwxrwx 1 root root 101728 Jul 16 2016 bootvhd.dll drwxrwxrwx 1 root root 0 Oct 1 21:50 cs-CZ drwxrwxrwx 1 root root 0 Oct 1 21:50 da-DK drwxrwxrwx 1 root root 0 Oct 1 21:50 de-DE drwxrwxrwx 1 root root 0 Oct 1 21:50 el-GR drwxrwxrwx 1 root root 0 Oct 1 21:50 en-GB drwxrwxrwx 1 root root 0 Oct 1 21:50 en-US drwxrwxrwx 1 root root 4096 Oct 1 21:50 es-ES drwxrwxrwx 1 root root 0 Oct 1 21:50 es-MX drwxrwxrwx 1 root root 0 Oct 1 21:50 et-EE drwxrwxrwx 1 root root 0 Oct 1 21:50 fi-FI drwxrwxrwx 1 root root 0 Oct 1 21:50 fr-CA drwxrwxrwx 1 root root 0 Oct 1 21:50 fr-FR drwxrwxrwx 1 root root 0 Oct 1 21:50 hr-HR drwxrwxrwx 1 root root 0 Oct 1 21:50 hu-HU drwxrwxrwx 1 root root 0 Oct 1 21:50 it-IT drwxrwxrwx 1 root root 0 Oct 1 21:50 ja-JP drwxrwxrwx 1 root root 0 Oct 1 21:50 ko-KR drwxrwxrwx 1 root root 0 Oct 1 21:50 lt-LT drwxrwxrwx 1 root root 0 Oct 1 21:50 lv-LV -rwxrwxrwx 1 root root 806752 Sep 7 06:29 memtest.exe drwxrwxrwx 1 root root 0 Oct 1 21:50 nb-NO drwxrwxrwx 1 root root 0 Oct 1 21:50 nl-NL drwxrwxrwx 1 root root 0 Oct 1 21:50 pl-PL drwxrwxrwx 1 root root 0 Oct 1 21:50 pt-BR drwxrwxrwx 1 root root 0 Oct 1 21:50 pt-PT drwxrwxrwx 1 root root 0 Oct 1 21:50 qps-ploc drwxrwxrwx 1 root root 0 Oct 1 21:50 ro-RO drwxrwxrwx 1 root root 0 Oct 1 21:50 ru-RU drwxrwxrwx 1 root root 0 Oct 1 21:50 sk-SK drwxrwxrwx 1 root root 0 Oct 1 21:50 sl-SI drwxrwxrwx 1 root root 0 Oct 1 21:50 sr-Latn-CS drwxrwxrwx 1 root root 0 Oct 1 21:50 sr-Latn-RS drwxrwxrwx 1 root root 0 Oct 1 21:50 sv-SE drwxrwxrwx 1 root root 0 Oct 1 21:50 tr-TR drwxrwxrwx 1 root root 0 Oct 1 21:50 uk-UA drwxrwxrwx 1 root root 0 Oct 1 21:50 zh-CN drwxrwxrwx 1 root root 0 Oct 1 21:50 zh-HK drwxrwxrwx 1 root root 0 Oct 1 21:50 zh-TWls -la /mnt/Recoverydrwxrwxrwx 1 root root 0 Jul 18 2016 . drwxrwxrwx 1 root root 4096 Oct 1 21:49 .. drwxrwxrwx 1 root root 0 Jul 18 2016 Logsmount.ntfs-3g /dev/md124p3 /mnt
ls -la /mntdrwxrwxrwx 1 root root 4096 Sep 27 19:10 . drwxr-xr-x 18 root root 1024 Nov 9 12:28 .. drwxrwxrwx 1 root root 0 Sep 27 19:10 Recovery drwxrwxrwx 1 root root 0 Jul 18 2016 'System Volume Information'ls -la /mnt/Recovery/WindowsRE/drwxrwxrwx 1 root root 0 Sep 27 15:31 . drwxrwxrwx 1 root root 0 Sep 27 19:10 .. -rwxrwxrwx 1 root root 1061 Sep 27 15:31 ReAgent.xml -rwxrwxrwx 1 root root 340406344 Sep 27 19:10 Winre.wim -rwxrwxrwx 1 root root 3170304 Jul 16 2016 boot.sdiHere is what the disk geometry looks like from within windows
<insert picture here> -
Win10 Fall 2017 update
Native UEFI system as seen by FOS
This system is a special case too. In this setup there is the windows disk that is on a pair of SSD drives behind an LSI raid controller, and a pair of HDD behind an Intel “fake raid” controller. AND a M.2 sata high speed scratch disk. This systems is a native uefi system with Dell Win10 OEM as the base OS.
gdisk -l /dev/sdaGPT fdisk (gdisk) version 1.0.0 The protective MBR's 0xEE partition is oversized! Auto-repairing. Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 974651392 sectors, 464.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): C2E38F37-D330-4842-959E-A56B62A8D538 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 974651358 Partitions will be aligned on 2048-sector boundaries Total free space is 5346 sectors (2.6 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB EF00 EFI system partition 2 206848 239615 16.0 MiB 0C01 Microsoft reserved ... 3 239616 972827354 463.8 GiB 0700 Basic data partition 4 972828672 974649343 889.0 MiB 2700gdisk -l /dev/md126GPT fdisk (gdisk) version 1.0.0 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. *************************************************************** Disk /dev/md126: 976766976 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 449912D4-693C-4ABE-984E-87CFF1627C73 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976766942 Partitions will be aligned on 2048-sector boundaries Total free space is 6077 sectors (3.0 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 976762879 465.8 GiB 0700 Microsoft basic datagdisk -l /dev/sddT fdisk (gdisk) version 1.0.0 The protective MBR's 0xEE partition is oversized! Auto-repairing. Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdd: 664212528 sectors, 316.7 GiB Logical sector size: 512 bytes Disk identifier (GUID): 81D8CE84-E6A9-4884-BE68-472663A3D1F5 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 664212494 Partitions will be aligned on 8-sector boundaries Total free space is 3053 sectors (1.5 MiB) Number Start (sector) End (sector) Size Code Name 1 34 262177 128.0 MiB 0C01 Microsoft reserved ... 2 264192 664211455 316.6 GiB 0700 Basic data partitionlsblksda 8:0 0 464.8G 0 disk |-sda1 8:1 0 100M 0 part |-sda2 8:2 0 16M 0 part |-sda3 8:3 0 463.8G 0 part `-sda4 8:4 0 889M 0 part sdb 8:16 0 465.8G 0 disk `-md126 9:126 0 465.8G 0 raid1 `-md126p1 259:0 0 465.8G 0 md sdc 8:32 0 465.8G 0 disk `-md126 9:126 0 465.8G 0 raid1 `-md126p1 259:0 0 465.8G 0 md sdd 8:48 0 316.7G 0 disk |-sdd1 8:49 0 128M 0 part `-sdd2 8:50 0 316.6G 0 part sde 8:64 1 29.1G 0 disk `-sde1 8:65 1 121M 0 partblkid/dev/ram0: UUID="3db56938-95cb-4bd6-a325-4ba458198604" TYPE="ext2" /dev/sda1: LABEL="SYSTEM" UUID="7A1B-7469" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="db0531e2-169c-4622-b701-5bd3af6484d8" /dev/sda3: UUID="404C29F84C29E8FC" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="2e53db12-1913-4a1d-8551-e80a3f386569" /dev/sda4: UUID="4CA2761CA2760AAA" TYPE="ntfs" PARTUUID="4394a9f9-eda8-47ae-a424-1839ae5f0dca" /dev/sdb: TYPE="isw_raid_member" /dev/sdc: TYPE="isw_raid_member" /dev/sdd2: LABEL="Data" UUID="C01033F81033F44E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4e290e9c-4bec-4014-adb6-7fa2cb84e147" /dev/sde1: SEC_TYPE="msdos" LABEL="GRUB" UUID="367A-397D" TYPE="vfat" PARTUUID="dbbe8098-01" /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="61036851-7b86-4a24-9839-40f23ad538b1" /dev/sdd1: PARTLABEL="Microsoft reserved partition" PARTUUID="039d1ad4-887d-4f22-8322-96928e2e0795" /dev/md126: PTUUID="1a088319" PTTYPE="dos" /dev/md126p1: LABEL="Archive" UUID="5AE24617E245F831" TYPE="ntfs" PARTUUID="1a088319-01"attempting to mount any partition on /dev/sda# mount.ntfs-3g /dev/sda1 /mnt NTFS signature is missing. Failed to mount '/dev/sda1': Invalid argument The device '/dev/sda1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? # mount.ntfs-3g /dev/sda2 /mnt NTFS signature is missing. Failed to mount '/dev/sda2': Invalid argument The device '/dev/sda2' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? # mount.ntfs-3g /dev/sda3 /mnt Windows is hibernated, refused to mount. Failed to mount '/dev/sda3': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. # mount.ntfs-3g /dev/sda4 /mnt The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sda4': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.mount.ntfs-3g /dev/md126p1 /mntmount.ntfs-3g /dev/md126p1 /mnt The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/md126p1': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.mount.ntfs-3g /dev/sdd1 /mntNTFS signature is missing. Failed to mount '/dev/sdd1': Invalid argument The device '/dev/sdd1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?mount.ntfs-3g /dev/sdd2 /mntThe disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdd2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.fidsk /dev/sdaisk /dev/sda: 464.8 GiB, 499021512704 bytes, 974651392 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 Disklabel type: gpt Disk identifier: C2E38F37-D330-4842-959E-A56B62A8D538 Device Start End Sectors Size Type /dev/sda1 2048 206847 204800 100M EFI System /dev/sda2 206848 239615 32768 16M Microsoft reserved /dev/sda3 239616 972827354 972587739 463.8G Microsoft basic data /dev/sda4 972828672 974649343 1820672 889M Windows recovery environmentWell that wasn’t very effective. It seems like for half of the partitions FOS could not mount them and the other half FOS thinks they are dirty because I just shut down the computer, but with Win10 shutdown is not shutdown. I’m not too concerned about the dirty bits, since I know those are valid data partitions. I’m more interested in why the gpt boot and recovery partitions are not mountable. I don’t think they are protected by bitlocker, actually the boot partition should never be encrypted by bitlocker anyway since its needed to actually boot the system.
Edit: more info from this mystery machine.
Disk layout according to windows disk manager.
Looking at the disk using Windows diskpart
DISKPART> select part 1 Partition 1 is now the selected partition. DISKPART> detail part Partition 1 Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b Hidden : Yes Required: No Attrib : 0X8000000000000000 Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 3 SYSTEM FAT32 Partition 100 MB Healthy System DISKPART> select part 2 Partition 2 is now the selected partition. DISKPART> detail part Partition 2 Type : e3c9e316-0b5c-4db8-817d-f92df00215ae Hidden : Yes Required: No Attrib : 0X8000000000000000 Offset in Bytes: 105906176 There is no volume associated with this partition. DISKPART> select part 3 Partition 3 is now the selected partition. DISKPART> detail part Partition 3 Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 Hidden : No Required: No Attrib : 0000000000000000 Offset in Bytes: 122683392 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 2 C NTFS Partition 463 GB Healthy Boot DISKPART> select part 4 Partition 4 is now the selected partition. DISKPART> detail part Partition 4 Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac Hidden : Yes Required: Yes Attrib : 0X8000000000000001 Offset in Bytes: 498088280064 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 4 NTFS Partition 889 MB Healthy Hidden DISKPART> select disk 1 Disk 1 is now the selected disk. DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Reserved 128 MB 17 KB Partition 2 Primary 316 GB 129 MB DISKPART> select part 1 Partition 1 is now the selected partition. DISKPART> detail part Partition 1 Type : e3c9e316-0b5c-4db8-817d-f92df00215ae Hidden : Yes Required: No Attrib : 0000000000000000 Offset in Bytes: 17408 There is no volume associated with this partition. -
As @wayne-workman said me, I post the output of my dual system: W10 LTSB 2016 and Ubuntu 16.04
root@U032668:~# gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 500118192 sectors, 238.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 611A1A7F-D5E7-4EB5-87EF-D447B71A8595 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 500118158 Partitions will be aligned on 2048-sector boundaries Total free space is 924269 sectors (451.3 MiB) Number Start (sector) End (sector) Size Code Name 1 923648 1128447 100.0 MiB EF00 EFI system partition 2 1128448 1161215 16.0 MiB 0C01 Microsoft reserved ... 3 1161216 205961215 97.7 GiB 0700 Basic data partition 4 205961216 483586047 132.4 GiB 8300 5 483586048 500117503 7.9 GiB 8200 root@U032668:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 238,5G 0 disk ├─sda1 8:1 0 100M 0 part /boot/efi ├─sda2 8:2 0 16M 0 part ├─sda3 8:3 0 97,7G 0 part ├─sda4 8:4 0 132,4G 0 part / └─sda5 8:5 0 7,9G 0 part [SWAP] sr0 11:0 1 1024M 0 rom root@U032668:~# blkid /dev/sda1: UUID="A47A-9C4F" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="90659379-55aa-43cc-a916-7909278e69d2" /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="ff774eb9-c85f-4dae-aac5-9a8efd46e7b4" /dev/sda3: UUID="385A3AFA5A3AB48A" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="54366076-6bce-46ae-9046-8528edf1876f" /dev/sda4: UUID="e3fa93df-c9a8-4b1c-bcaf-7886256709cb" TYPE="ext4" PARTUUID="c1db2263-cf34-4d82-9954-2484e2c8bdde" /dev/sda5: UUID="c2fec154-bb2c-454c-ad54-8ca7ab1af203" TYPE="swap" PARTUUID="530e6d65-e5d7-4f4c-bb3b-44ccc6305467" root@U032668:~# pvdisplay El programa «pvdisplay» no está instalado. Puede instalarlo escribiendo: apt install lvm2 root@U032668:~# lgdisplay No se ha encontrado la orden «lgdisplay», quizás quiso decir: La orden «lvdisplay» del paquete «lvm2» (main) La orden «vgdisplay» del paquete «lvm2» (main) lgdisplay: no se encontró la orden root@U032668:~# lvdisplay El programa «lvdisplay» no está instalado. Puede instalarlo escribiendo: apt install lvm2
