Return to Answer

• The partition table at the front, in purple. As mentioned above, it informs the OS where the partitions logically are in the storage device.
• Partition #1 starts at location 8, and runs through to location 456 (i.e: it's 448 units in size).
• Unused space
• Partition #2 starts at location 504, and runs through to location 904 (i.e: it's 400 units in size).
• Unused space

• The partition table at the front, in purple. As mentioned above, it informs the OS where the partitions logically are in the storage device.
• Partition #1 starts at location 8, and runs through to location 456 (i.e: it's 449 units in size).
• Unused space
• Partition #2 starts at location 504, and runs through to location 904 (i.e: it's 401 units in size).
• Unused space

With solid-state storage like SSDs and SD cards, this concept is taken to the next level, with logical blocks assigned to physical storage in a way that is completely out of the control of the user and even Operating System - the main reason for this being wear levelling. In addition to this, a growing number of SSDs will encrypt their entire contents, so it the data isn't accessible to you at a physical level anyway.

With solid-state storage like SSDs and SD cards, this concept is taken to the next level, with logical blocks assigned to physical storage in a way that is completely out of the control of the user and even Operating System - the main reason for this being wear levelling. In addition to this, a growing number of SSDs will encrypt their entire contents, so the data isn't accessible to you at a physical level anyway.