Why am I seeing an EFI partition when I created a FAT on my external USB hub?Repair or recover seemingly...
What is an informed evaluation of resource availability?
Modeling the Round (Nearest Integer) function
Do proteins interact through classical or quantum mechanics?
Do any languages mark social distinctions other than gender and status?
Was Hitler exclaiming "Heil Hitler!" himself when saluting?
Why can a T* be passed in register, but a unique_ptr<T> cannot?
Should I replace the battery terminal clamp if some material is missing?
How can I seal 8 inch round holes in my siding?
What plausible reasons why people forget they didn't originally live on this new planet?
How were Kurds involved (or not) in the invasion of Normandy?
Options for passes to national parks in Arizona/Utah for 5 people travelling in one car
FPGA starts working after irrelevant changes, why?
As a vegetarian, how can I deal with microwaves smelling of meat and fish?
Are ups & downs/peaks and valleys inherent in piano practice and performance?
C# Toy Robot Simulator
Matrix class in C#
In this day and age should the definition / categorisation of erotica be revised?
LTSpice Zener diode bug?
Why apt asking to uninstall GIMP when installing ardour?
Should I respond to a sabotage accusation e-mail at work?
Repair drywall and protect wires on back of electrical panel
The use of SlotSequence in If[#1 > #2, ##] &
Is the phrase “You are requested” polite or rude?
Why doesn't the nucleus have "nucleus-probability cloud"?
Why am I seeing an EFI partition when I created a FAT on my external USB hub?
Repair or recover seemingly damaged partition on USB external diskwhat does Linux consider connected usb drives and why do they remain as folders when unplugged?Debian boot partition on USB stick, when and how to mountparted created an XFS partition whereas I asked for ext4. Why?Remove stale qgroup entires when incrementally backing up a btrfs partition to an external hddWhy I am getting logged out from gnome session when i insert any usb drive or unmount any usb driveWhen installing Debian it on a USB external hard drive, Can the file system be corrupted during disk shutdown?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{
margin-bottom:0;
}
I am connecting a 4-bay HDD hub (FANTEC QB-35US3-6G) via USB to my Raspberry Pi. I have two disks inside the hub and formated them as FAT.
The formating I did on a Mac because I was not able to see the unformated disks in the hub with blkid when connected to the Raspberry, which is strange.
When sudo blkid I see
/dev/sdc1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="e36842bb-f2a9-4a3e-99b6-bbd4a54f39f6"
/dev/sdc2: LABEL_FATBOOT="WD3" LABEL="WD3" UUID="4568-1704" TYPE="vfat" PARTUUID="576db57a-0543-4f9b-b3e4-4cf452cbdda3"
/dev/sdd1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="c2a64dbc-5b9a-458e-b0a8-04d6f5fd8956"
/dev/sdd2: LABEL_FATBOOT="WD1" LABEL="WD1" UUID="D719-1706" TYPE="vfat" PARTUUID="2cced532-4870-43f1-8226-4f413e513f33"
fdisk -l shows
GPT PMBR size mismatch (4294967294 != 5860533167) will be corrected by write.
Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: EFRX-68AX9N0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BFC5ECE6-8901-4C6C-A2BA-C14DA6AD5890
Device Start End Sectors Size Type
/dev/sdc1 40 409639 409600 200M EFI System
/dev/sdc2 411648 5860532223 5860120576 2.7T Microsoft basic data
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: 01FALS-40Y6A0
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: 9B3E10E4-6E9B-4CE0-A7EF-691A6EA14CC5
Device Start End Sectors Size Type
/dev/sdd1 40 409639 409600 200M EFI System
/dev/sdd2 411648 1953523711 1953112064 931.3G Microsoft basic data
Is this a special thing related to the USB hub? Or is it normal that a FAT partition will also create an EFI System device?
EDIT: Funny, since I just wanted to and did nothing else then to format the disks:
$ sudo mount /dev/sdc2 /mnt
$ ll /mnt
total 132
drwxr-xr-x 4 pi pi 32768 Jan 1 1970 ./
drwxr-xr-x 21 root root 4096 Jul 10 02:41 ../
-rw-r--r-- 1 pi pi 4096 Oct 12 2019 ._.com.apple.timemachine.donotpresent
-rw-r--r-- 1 pi pi 0 Oct 12 2019 .com.apple.timemachine.donotpresent
drwxr-xr-x 2 pi pi 32768 Oct 12 2019 .fseventsd/
drwxr-xr-x 4 pi pi 32768 Oct 12 2019 .Spotlight-V100/
filesystems usb-drive fat
asked yesterday
BenBen
1186 bronze badges
add a comment
|
I am connecting a 4-bay HDD hub (FANTEC QB-35US3-6G) via USB to my Raspberry Pi. I have two disks inside the hub and formated them as FAT.
The formating I did on a Mac because I was not able to see the unformated disks in the hub with blkid when connected to the Raspberry, which is strange.
When sudo blkid I see
/dev/sdc1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="e36842bb-f2a9-4a3e-99b6-bbd4a54f39f6"
/dev/sdc2: LABEL_FATBOOT="WD3" LABEL="WD3" UUID="4568-1704" TYPE="vfat" PARTUUID="576db57a-0543-4f9b-b3e4-4cf452cbdda3"
/dev/sdd1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="c2a64dbc-5b9a-458e-b0a8-04d6f5fd8956"
/dev/sdd2: LABEL_FATBOOT="WD1" LABEL="WD1" UUID="D719-1706" TYPE="vfat" PARTUUID="2cced532-4870-43f1-8226-4f413e513f33"
fdisk -l shows
GPT PMBR size mismatch (4294967294 != 5860533167) will be corrected by write.
Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: EFRX-68AX9N0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BFC5ECE6-8901-4C6C-A2BA-C14DA6AD5890
Device Start End Sectors Size Type
/dev/sdc1 40 409639 409600 200M EFI System
/dev/sdc2 411648 5860532223 5860120576 2.7T Microsoft basic data
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: 01FALS-40Y6A0
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: 9B3E10E4-6E9B-4CE0-A7EF-691A6EA14CC5
Device Start End Sectors Size Type
/dev/sdd1 40 409639 409600 200M EFI System
/dev/sdd2 411648 1953523711 1953112064 931.3G Microsoft basic data
Is this a special thing related to the USB hub? Or is it normal that a FAT partition will also create an EFI System device?
EDIT: Funny, since I just wanted to and did nothing else then to format the disks:
$ sudo mount /dev/sdc2 /mnt
$ ll /mnt
total 132
drwxr-xr-x 4 pi pi 32768 Jan 1 1970 ./
drwxr-xr-x 21 root root 4096 Jul 10 02:41 ../
-rw-r--r-- 1 pi pi 4096 Oct 12 2019 ._.com.apple.timemachine.donotpresent
-rw-r--r-- 1 pi pi 0 Oct 12 2019 .com.apple.timemachine.donotpresent
drwxr-xr-x 2 pi pi 32768 Oct 12 2019 .fseventsd/
drwxr-xr-x 4 pi pi 32768 Oct 12 2019 .Spotlight-V100/
filesystems usb-drive fat
asked yesterday
BenBen
1186 bronze badges
If i comprehend (that SCREEN?) then this is very normal. I was also surprised when I saw all the apple files after copying from a USB. Hidden files also. That is user friendly. Cookies.
– rastafile
yesterday
1
It just looks like Mac defaults to adding ESP with some boot files when you create a gpt partitioned drive. As it says use fdisk & do a write to clean up mismatch. Both Windows & Linux tools start first partition at sector 2048. It looks like Mac uses sector 40 which at least is aligned as it is divisible by 8.
– oldfred
yesterday
I agree, everything OK. Only me I mix up sectors and bytes.
– rastafile
23 hours ago
@oldfred the files are on the second (FAT) partition. the first (EFI) is actually empty. @rastafile SCREEN was just the terminal telling me that I am inscreennumber 0 and could close the terminal without interrupting a process attached. I removed it from the question.
– Ben
22 hours ago
@Ben hey thanks a lot, too.
– rastafile
22 hours ago
add a comment
|
I am connecting a 4-bay HDD hub (FANTEC QB-35US3-6G) via USB to my Raspberry Pi. I have two disks inside the hub and formated them as FAT.
The formating I did on a Mac because I was not able to see the unformated disks in the hub with blkid when connected to the Raspberry, which is strange.
When sudo blkid I see
/dev/sdc1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="e36842bb-f2a9-4a3e-99b6-bbd4a54f39f6"
/dev/sdc2: LABEL_FATBOOT="WD3" LABEL="WD3" UUID="4568-1704" TYPE="vfat" PARTUUID="576db57a-0543-4f9b-b3e4-4cf452cbdda3"
/dev/sdd1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="c2a64dbc-5b9a-458e-b0a8-04d6f5fd8956"
/dev/sdd2: LABEL_FATBOOT="WD1" LABEL="WD1" UUID="D719-1706" TYPE="vfat" PARTUUID="2cced532-4870-43f1-8226-4f413e513f33"
fdisk -l shows
GPT PMBR size mismatch (4294967294 != 5860533167) will be corrected by write.
Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: EFRX-68AX9N0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BFC5ECE6-8901-4C6C-A2BA-C14DA6AD5890
Device Start End Sectors Size Type
/dev/sdc1 40 409639 409600 200M EFI System
/dev/sdc2 411648 5860532223 5860120576 2.7T Microsoft basic data
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: 01FALS-40Y6A0
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: 9B3E10E4-6E9B-4CE0-A7EF-691A6EA14CC5
Device Start End Sectors Size Type
/dev/sdd1 40 409639 409600 200M EFI System
/dev/sdd2 411648 1953523711 1953112064 931.3G Microsoft basic data
Is this a special thing related to the USB hub? Or is it normal that a FAT partition will also create an EFI System device?
EDIT: Funny, since I just wanted to and did nothing else then to format the disks:
$ sudo mount /dev/sdc2 /mnt
$ ll /mnt
total 132
drwxr-xr-x 4 pi pi 32768 Jan 1 1970 ./
drwxr-xr-x 21 root root 4096 Jul 10 02:41 ../
-rw-r--r-- 1 pi pi 4096 Oct 12 2019 ._.com.apple.timemachine.donotpresent
-rw-r--r-- 1 pi pi 0 Oct 12 2019 .com.apple.timemachine.donotpresent
drwxr-xr-x 2 pi pi 32768 Oct 12 2019 .fseventsd/
drwxr-xr-x 4 pi pi 32768 Oct 12 2019 .Spotlight-V100/
filesystems usb-drive fat
asked yesterday
BenBen
1186 bronze badges
I am connecting a 4-bay HDD hub (FANTEC QB-35US3-6G) via USB to my Raspberry Pi. I have two disks inside the hub and formated them as FAT.
The formating I did on a Mac because I was not able to see the unformated disks in the hub with blkid when connected to the Raspberry, which is strange.
When sudo blkid I see
/dev/sdc1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="e36842bb-f2a9-4a3e-99b6-bbd4a54f39f6"
/dev/sdc2: LABEL_FATBOOT="WD3" LABEL="WD3" UUID="4568-1704" TYPE="vfat" PARTUUID="576db57a-0543-4f9b-b3e4-4cf452cbdda3"
/dev/sdd1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="c2a64dbc-5b9a-458e-b0a8-04d6f5fd8956"
/dev/sdd2: LABEL_FATBOOT="WD1" LABEL="WD1" UUID="D719-1706" TYPE="vfat" PARTUUID="2cced532-4870-43f1-8226-4f413e513f33"
fdisk -l shows
GPT PMBR size mismatch (4294967294 != 5860533167) will be corrected by write.
Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: EFRX-68AX9N0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BFC5ECE6-8901-4C6C-A2BA-C14DA6AD5890
Device Start End Sectors Size Type
/dev/sdc1 40 409639 409600 200M EFI System
/dev/sdc2 411648 5860532223 5860120576 2.7T Microsoft basic data
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: 01FALS-40Y6A0
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: 9B3E10E4-6E9B-4CE0-A7EF-691A6EA14CC5
Device Start End Sectors Size Type
/dev/sdd1 40 409639 409600 200M EFI System
/dev/sdd2 411648 1953523711 1953112064 931.3G Microsoft basic data
Is this a special thing related to the USB hub? Or is it normal that a FAT partition will also create an EFI System device?
EDIT: Funny, since I just wanted to and did nothing else then to format the disks:
$ sudo mount /dev/sdc2 /mnt
$ ll /mnt
total 132
drwxr-xr-x 4 pi pi 32768 Jan 1 1970 ./
drwxr-xr-x 21 root root 4096 Jul 10 02:41 ../
-rw-r--r-- 1 pi pi 4096 Oct 12 2019 ._.com.apple.timemachine.donotpresent
-rw-r--r-- 1 pi pi 0 Oct 12 2019 .com.apple.timemachine.donotpresent
drwxr-xr-x 2 pi pi 32768 Oct 12 2019 .fseventsd/
drwxr-xr-x 4 pi pi 32768 Oct 12 2019 .Spotlight-V100/
filesystems usb-drive fat
filesystems usb-drive fat
asked yesterday
BenBen
1186 bronze badges
asked yesterday
BenBen
1186 bronze badges
edited 1 hour ago
Ben
asked yesterday
BenBen
1186 bronze badges
asked yesterday
BenBen
1186 bronze badges
asked yesterday
BenBen
1186 bronze badges
1186 bronze badges
If i comprehend (that SCREEN?) then this is very normal. I was also surprised when I saw all the apple files after copying from a USB. Hidden files also. That is user friendly. Cookies.
– rastafile
yesterday
1
It just looks like Mac defaults to adding ESP with some boot files when you create a gpt partitioned drive. As it says use fdisk & do a write to clean up mismatch. Both Windows & Linux tools start first partition at sector 2048. It looks like Mac uses sector 40 which at least is aligned as it is divisible by 8.
– oldfred
yesterday
I agree, everything OK. Only me I mix up sectors and bytes.
– rastafile
23 hours ago
@oldfred the files are on the second (FAT) partition. the first (EFI) is actually empty. @rastafile SCREEN was just the terminal telling me that I am inscreennumber 0 and could close the terminal without interrupting a process attached. I removed it from the question.
– Ben
22 hours ago
@Ben hey thanks a lot, too.
– rastafile
22 hours ago
add a comment
|
If i comprehend (that SCREEN?) then this is very normal. I was also surprised when I saw all the apple files after copying from a USB. Hidden files also. That is user friendly. Cookies.
– rastafile
yesterday
1
It just looks like Mac defaults to adding ESP with some boot files when you create a gpt partitioned drive. As it says use fdisk & do a write to clean up mismatch. Both Windows & Linux tools start first partition at sector 2048. It looks like Mac uses sector 40 which at least is aligned as it is divisible by 8.
– oldfred
yesterday
I agree, everything OK. Only me I mix up sectors and bytes.
– rastafile
23 hours ago
@oldfred the files are on the second (FAT) partition. the first (EFI) is actually empty. @rastafile SCREEN was just the terminal telling me that I am inscreennumber 0 and could close the terminal without interrupting a process attached. I removed it from the question.
– Ben
22 hours ago
@Ben hey thanks a lot, too.
– rastafile
22 hours ago
If i comprehend (that SCREEN?) then this is very normal. I was also surprised when I saw all the apple files after copying from a USB. Hidden files also. That is user friendly. Cookies.
– rastafile
yesterday
If i comprehend (that SCREEN?) then this is very normal. I was also surprised when I saw all the apple files after copying from a USB. Hidden files also. That is user friendly. Cookies.
– rastafile
yesterday
1
1
It just looks like Mac defaults to adding ESP with some boot files when you create a gpt partitioned drive. As it says use fdisk & do a write to clean up mismatch. Both Windows & Linux tools start first partition at sector 2048. It looks like Mac uses sector 40 which at least is aligned as it is divisible by 8.
– oldfred
yesterday
It just looks like Mac defaults to adding ESP with some boot files when you create a gpt partitioned drive. As it says use fdisk & do a write to clean up mismatch. Both Windows & Linux tools start first partition at sector 2048. It looks like Mac uses sector 40 which at least is aligned as it is divisible by 8.
– oldfred
yesterday
I agree, everything OK. Only me I mix up sectors and bytes.
– rastafile
23 hours ago
I agree, everything OK. Only me I mix up sectors and bytes.
– rastafile
23 hours ago
@oldfred the files are on the second (FAT) partition. the first (EFI) is actually empty. @rastafile SCREEN was just the terminal telling me that I am in
screen number 0 and could close the terminal without interrupting a process attached. I removed it from the question.– Ben
22 hours ago
@oldfred the files are on the second (FAT) partition. the first (EFI) is actually empty. @rastafile SCREEN was just the terminal telling me that I am in
screen number 0 and could close the terminal without interrupting a process attached. I removed it from the question.– Ben
22 hours ago
@Ben hey thanks a lot, too.
– rastafile
22 hours ago
@Ben hey thanks a lot, too.
– rastafile
22 hours ago
add a comment
|
1 Answer
1
active
oldest
votes
You have two GPT formatted "disks". Both have a 200 MB EFI system partition.
sdc has "PMBR size mismatch", meaning protective MBR.
In other words maybe a mess...but the way you tell: with external multi-disk from a different system.
ADDED: I also don't like Start=40. I have 2048. So I have the first MB (?) "out of harms way" (harm=some MBR sector write). But it does say "size mismatch" and "will be corrected".
see comments for how we found the answers. And bottom WHY? for the big Q. I leave it like this. Thanks!
"The formatting I did" -- No joke and less insult: are you sure what you and macos exactly did?
WHY does mac do that?
It is a very good idea to reserve a 200MB (or a bit more even) partition in case you want to make the disk EFI bootable later.
(initrd plus kernel can be 50 MB together as files)
answered yesterday
rastafilerastafile
2046 bronze badges
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
1
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
1
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
1
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
1
hybrid and PMBR are not the same
– rastafile
21 hours ago
|
show 12 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f546485%2fwhy-am-i-seeing-an-efi-partition-when-i-created-a-fat-on-my-external-usb-hub%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have two GPT formatted "disks". Both have a 200 MB EFI system partition.
sdc has "PMBR size mismatch", meaning protective MBR.
In other words maybe a mess...but the way you tell: with external multi-disk from a different system.
ADDED: I also don't like Start=40. I have 2048. So I have the first MB (?) "out of harms way" (harm=some MBR sector write). But it does say "size mismatch" and "will be corrected".
see comments for how we found the answers. And bottom WHY? for the big Q. I leave it like this. Thanks!
"The formatting I did" -- No joke and less insult: are you sure what you and macos exactly did?
WHY does mac do that?
It is a very good idea to reserve a 200MB (or a bit more even) partition in case you want to make the disk EFI bootable later.
(initrd plus kernel can be 50 MB together as files)
answered yesterday
rastafilerastafile
2046 bronze badges
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
1
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
1
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
1
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
1
hybrid and PMBR are not the same
– rastafile
21 hours ago
|
show 12 more comments
You have two GPT formatted "disks". Both have a 200 MB EFI system partition.
sdc has "PMBR size mismatch", meaning protective MBR.
In other words maybe a mess...but the way you tell: with external multi-disk from a different system.
ADDED: I also don't like Start=40. I have 2048. So I have the first MB (?) "out of harms way" (harm=some MBR sector write). But it does say "size mismatch" and "will be corrected".
see comments for how we found the answers. And bottom WHY? for the big Q. I leave it like this. Thanks!
"The formatting I did" -- No joke and less insult: are you sure what you and macos exactly did?
WHY does mac do that?
It is a very good idea to reserve a 200MB (or a bit more even) partition in case you want to make the disk EFI bootable later.
(initrd plus kernel can be 50 MB together as files)
answered yesterday
rastafilerastafile
2046 bronze badges
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
1
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
1
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
1
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
1
hybrid and PMBR are not the same
– rastafile
21 hours ago
|
show 12 more comments
You have two GPT formatted "disks". Both have a 200 MB EFI system partition.
sdc has "PMBR size mismatch", meaning protective MBR.
In other words maybe a mess...but the way you tell: with external multi-disk from a different system.
ADDED: I also don't like Start=40. I have 2048. So I have the first MB (?) "out of harms way" (harm=some MBR sector write). But it does say "size mismatch" and "will be corrected".
see comments for how we found the answers. And bottom WHY? for the big Q. I leave it like this. Thanks!
"The formatting I did" -- No joke and less insult: are you sure what you and macos exactly did?
WHY does mac do that?
It is a very good idea to reserve a 200MB (or a bit more even) partition in case you want to make the disk EFI bootable later.
(initrd plus kernel can be 50 MB together as files)
answered yesterday
rastafilerastafile
2046 bronze badges
You have two GPT formatted "disks". Both have a 200 MB EFI system partition.
sdc has "PMBR size mismatch", meaning protective MBR.
In other words maybe a mess...but the way you tell: with external multi-disk from a different system.
ADDED: I also don't like Start=40. I have 2048. So I have the first MB (?) "out of harms way" (harm=some MBR sector write). But it does say "size mismatch" and "will be corrected".
see comments for how we found the answers. And bottom WHY? for the big Q. I leave it like this. Thanks!
"The formatting I did" -- No joke and less insult: are you sure what you and macos exactly did?
WHY does mac do that?
It is a very good idea to reserve a 200MB (or a bit more even) partition in case you want to make the disk EFI bootable later.
(initrd plus kernel can be 50 MB together as files)
answered yesterday
rastafilerastafile
2046 bronze badges
edited 8 hours ago
answered yesterday
rastafilerastafile
2046 bronze badges
answered yesterday
rastafilerastafile
2046 bronze badges
answered yesterday
rastafilerastafile
2046 bronze badges
2046 bronze badges
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
1
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
1
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
1
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
1
hybrid and PMBR are not the same
– rastafile
21 hours ago
|
show 12 more comments
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
1
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
1
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
1
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
1
hybrid and PMBR are not the same
– rastafile
21 hours ago
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
no, not sure. i did blkid on linux and saw just the PMBR disk as /dev/sdc (without number) and tried to format it with ext4 on the terminal. then it was also not visible any more. then i plugged it into my Mac and both came up for initialisation. because ext4 is not availlable on the Mac i formatted both as FAT with the disk utility GUI. So i think the GUI does a bad job. i might redo the whole thing to ext4 now anyway since i now can See both disks but i need to be sure how to do it.
– Ben
yesterday
1
1
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
MBR partitioning can not be used on the 2.7 TiB disk, it is too big. 2 TiB is the maximum size for a 512 byte / sector disk. This is why you get the Protective MBR size mismatch warning. @rastafile: The disk has 4 k physical sectors, but 512 byte logical sectors, which is what counts in these calculations.
– Johan Myréen
yesterday
1
1
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
@ben but this PMBR is an option you can choose or not. It's how GPT moves it's first sector away from the edge. But sure, once you have it, it might stay. But having a PMBR, even octuple size would not be the problem. Try man wipefs for erasing "signatures"
– rastafile
yesterday
1
1
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
@ben the PMBR is a "protective" MBR. This is added by the GPT partitioning tool, and is supposed to cover the whole disk. It is meant to be a safety measure against old disk partitioning tools which are not aware of GPT. The old tool sees that the disk contains a partition that spans the whole disk, thus the disk has no free space. Without the PMBR, an old fdisk program might fool the user to think the GPT formatted disk does not contain any partitions, i.e. it is empty. The mismatch occurs because you can't have a 2.7 TiB MBR partition.
– Johan Myréen
yesterday
1
1
hybrid and PMBR are not the same
– rastafile
21 hours ago
hybrid and PMBR are not the same
– rastafile
21 hours ago
|
show 12 more comments
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f546485%2fwhy-am-i-seeing-an-efi-partition-when-i-created-a-fat-on-my-external-usb-hub%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If i comprehend (that SCREEN?) then this is very normal. I was also surprised when I saw all the apple files after copying from a USB. Hidden files also. That is user friendly. Cookies.
– rastafile
yesterday
1
It just looks like Mac defaults to adding ESP with some boot files when you create a gpt partitioned drive. As it says use fdisk & do a write to clean up mismatch. Both Windows & Linux tools start first partition at sector 2048. It looks like Mac uses sector 40 which at least is aligned as it is divisible by 8.
– oldfred
yesterday
I agree, everything OK. Only me I mix up sectors and bytes.
– rastafile
23 hours ago
@oldfred the files are on the second (FAT) partition. the first (EFI) is actually empty. @rastafile SCREEN was just the terminal telling me that I am in
screennumber 0 and could close the terminal without interrupting a process attached. I removed it from the question.– Ben
22 hours ago
@Ben hey thanks a lot, too.
– rastafile
22 hours ago