Difference between revisions of "Partitions"
|Line 149:||Line 149:|
| Main OS partition, contains kernel [[Modules
| Main OS partition, contains kernel [[Modules|]]
Revision as of 14:44, 21 August 2018
All devices on the Vita are partitioned the same way. Logical block size is 512 bytes and the first logical block is the master block which defines the partition table along with other information. Because of block level encryption, the master block is also encrypted along with everything else and cannot be seen if the device is dumped from an external dumper.
The first block (512 bytes) provides a partition table as well as auxiliary information to the block management drivers.
|0x0||0x20||Magic string "|
|0x20||0x4||Version ? (0x3)|
|0x24||0x4||Size of device in blocks (ex: 0x71A000 blocks -> * 0x200 bytes per block = 0xE3400000 = 3 812 622 336 bytes = 3.81 GB)|
|0x28||0x8||full of zeroes - maybe padding|
|0x30||0x4||Second Loader offset in blocks (ex: 0x6070 -> * 0x200 bytes per block = 0xC0E000 bytes = 12 MB from MBR start)|
|0x34||0x4||Second Loader size in blocks (ex: 0x6F -> * 0x200 bytes per block = 0xDE00 bytes = 56kB)|
|0x38||0x4||? (ex: 0x600)|
|0x3C||0x4||? (ex: 0x400)|
|0x40||0x4||? (ex: 0x600)|
|0x40||0x4||? (ex: 0x10000)|
|0x48||0x8||full of zeroes - maybe padding|
|0x50||0x110 (0x11 per partition * 10 partitions)||Partition entries (there are 0x10 partitions at most (derived from code and data structure of SdStor driver))|
|0x1BE||0x10||unknown (may contain some data) (In standard MBR this area corresponds to Partition Entry)|
|0x1CE||0x10||unknown (must contain zeros) (In standard MBR this area corresponds to Partition Entry)|
|0x1DE||0x10||unknown (must contain zeros) (In standard MBR this area corresponds to Partition Entry)|
|0x1EE||0x10||unknown (must contain zeros) (In standard MBR this area corresponds to Partition Entry)|
Each partition entry is 17 bytes long. Offset 0x0 means end of table.
|0x0||0x4||Partition offset (blocks)|
|0x4||0x4||Partition size (blocks)|
|0xB||0x4||Flags ? seen: |
The partition code uniquely identifies the partition to its function. It is related to SceKernelModulemgr#Partition Code.
|0x1||Internal||first eMMC partition, some data, IdStorage|
|0x2||Internal||SLB2 Boot loaders|
|0x3||os0||Internal||Main OS partition, contains kernel modules|
|0x4||vs0||Internal||system applications & libraries|
|0x5||vd0||Internal||Registry and error history|
|0x6||tm0||Internal||NpDrm, Marlin and DevKit/TestKit activations files|
|0x7||ur0||Internal||User resources, LiveArea cache, database, & other stuff|
|0x8||ux0||Memory Card||Memory Card|
|0x9||gro0||Game Card||Game Card read-only area|
|0xA||grw0||Game Card||Game Card writable area|
|0xB||ud0||Internal||Updater application and PUP copied here before reboot|
|0xC||sa0||Internal||Dictionary and font data|
|0xD||External||Some data on Memory Card & Game Card|
|0xE||pd0||Internal||Welcome Park and welcome video|
The partition type code indicates the file system used or if there is no file system (for example, in the case of a SLB2 archive).
Some partitions (specifically
os0 and the boot loaders) have a shadow redundant copy. On update, only the inactive partition is written to and finally the active partition is swapped. For partitions that do not use this feature, this value is ignored.