Timeline for Where does the "Physical size" information come from?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2024 at 19:08 | vote | accept | Antti Keskinen | ||
| Sep 24, 2024 at 19:08 | comment | added | Antti Keskinen | Alright so, looks like your answer was correct after all, I just did not understand what I was supposed to do first. The solution was to use dd to create the image first, making sure there was ~40 sectors extra in the "count" parameter to extend beyond to last partition, and then use gdisk and its expert menu to fix the partition table on the image file. | |
| Sep 24, 2024 at 9:46 | comment | added | sourcejedi | and hence my answer is to run gdisk to fix the out-of-spec image file, after you created the image file by reading part of the disk | |
| Sep 24, 2024 at 8:13 | comment | added | Antti Keskinen | That "zero sector" was just a term I picked up elsewhere when I was trying to research the issue. If the GPT primary header is at the start of the disk, and the secondary header is at the end then that poses a problem for me. I am not reading the whole disk but just a very limited part of it. So technically the primary header says that the secondary header is in a location which will not be part of the final image. This happens because the gdisk commands are executed before I create the image. | |
| Sep 23, 2024 at 20:00 | history | edited | sourcejedi | CC BY-SA 4.0 | added 810 characters in body |
| Sep 23, 2024 at 19:55 | history | edited | sourcejedi | CC BY-SA 4.0 | added 810 characters in body |
| Sep 23, 2024 at 19:41 | comment | added | sourcejedi | Weird. I do see a second issue. "limit the amount of data read to only extend up to where the second partition ends plus an extra sector to accommodate the "zero sector"". I don't know exactly what you mean by "zero sector", but GPT requires an absolute minimum of two sectors at the end. I think the "w" command should have failed for you with something like "Warning! Secondary partition table overlaps the last partition by 32 blocks! Try reducing the partition table size by 128 entries. (Use the 's' item on the experts' menu.) Aborting write of new partition table." | |
| Sep 23, 2024 at 19:12 | history | edited | sourcejedi | CC BY-SA 4.0 | added 985 characters in body |
| Sep 23, 2024 at 15:49 | comment | added | Antti Keskinen | This does not resolve the issue; after performing the operation and creating a new image file the "Physical size" is still showing a larger value. | |
| Sep 23, 2024 at 15:25 | history | answered | sourcejedi | CC BY-SA 4.0 |