Editing Harddrive
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
<div style="float:right">[[File: | <div style="float:right">[[File:CECHC04_NAND-system.jpg.JPG|200px|thumb|left|Most of the system software is on the harddrive, without one you get this error instead of XMB]]<br />[[File:No-HDD-on-NOR-consoles-Cannot start. The appropriate system storage was not found.jpg|200px|thumb|left|No-HDD on NOR-consoles - Cannot start. The appropriate system storage was not found.]]<br />[[File:PS3-Reserved-Area.png|200px|thumb|left|PS3 % Reserved Area<br />(system files {dev_flash}; {dev_flash2}; {dev_flash3}, game data {dev_hdd0}, system cache {dev_hdd1} etc]]</div> | ||
== Internal harddrive == | == Internal harddrive == | ||
All HDD models used in retail PS3's are 2.5" size and 9.5 milimeters height max, with 1 platter (and 1 or 2 heads), the platter has a rotational speed of 5.400 rpm and 512 bytes per sector | All HDD models used in retail PS3's are 2.5" size and 9.5 milimeters height max, with 1 platter (and 1 or 2 heads), the platter has a rotational speed of 5.400 rpm and 512 bytes per sector | ||
Is connected internally to [[South Bridge]] wich contains [[Hypervisor_Reverse_Engineering#ENCDEC_device|ENCDEC device]] to manage AES-CBC-128/AES-CBC-192/XTS-AES-128 encryption/decryption, and a SATA-150 controller with a maximum transfer speed of 1.5 | The maximum capacity supported by PS3 is 1TB (TeraBytes) ''note: this ''seems'' untrue as there are several people posting pictures of their external to internal drive mod with a size of 2TB, but so far no one has been able to confirm that, only to debunk it as fake''. See/use the [[Talk:Harddrive|talk page]] for discussions/testreports | ||
Is connected internally to [[South Bridge]] wich contains [[Hypervisor_Reverse_Engineering#ENCDEC_device|ENCDEC device]] to manage AES-CBC-128/AES-CBC-192/XTS-AES-128 encryption/decryption, and a SATA-150 controller with a maximum transfer speed of 1.5 Gb/s. | |||
*GameOS partition | *GameOS partition | ||
**Is an UFS2 256-bit file system with a sectorsize of 512 bytes (4096 bits). | **Is an UFS2 256-bit file system with a sectorsize of 512 bytes (4096 bits). | ||
**Because | **Because is perconsole encrypted, it is not possible to read out the data on it with another console (it will just ask to reformat it, to set it to its own perconsole encryption, hence emptying the drive) | ||
To read/write data out in Linux, BSD, Windows, | To read/write data out in Linux, BSD, Windows, Mac OS X its needed to use the specific perconsole "ATA tweak" and "ATA data" keys. See [[Harddrive#Harddrive_encryption|Harddrive encryption]] and [[HDD_Encryption]] | ||
*In some newer PS3 models (like [[CECH-40xx]]A 12GB) the internal harddrive has been replaced by a [[Flash_(Hardware)|Flash]] | *In some newer PS3 models (like [[CECH-40xx]]A 12GB) the internal harddrive has been replaced by a [[Flash_(Hardware)|Flash]] | ||
=== Harddrive Model info === | === Harddrive Model info === | ||
The data in this table has been copied from manufacturer documents (datasheets or productsheets) | The data in this table has been copied from manufacturer documents (datasheets or productsheets) availables at his support webs. See links at bottom of the page | ||
*A collection of productsheets/datasheets of the HDD models used in PS3, renamed by manufacturer/series: [[http://www.multiupload.nl/V3ISMS6Q80 Download]] (fujitsu series are missing) | *A collection of productsheets/datasheets of the HDD models used in PS3, renamed by manufacturer/series: [[http://www.multiupload.nl/V3ISMS6Q80 Download]] (fujitsu series are missing) | ||
Line 56: | Line 58: | ||
! colspan=21 {{cellcolors|lightgrey}} | ! colspan=21 {{cellcolors|lightgrey}} | ||
|- | |- | ||
! rowspan= | ! rowspan=4 | Hitachi | ||
! Travelstar 5K160 | ! Travelstar 5K160 | ||
| [[HTS541640J9SA00]] || 40 GB || 5400rpm (1/1) || 8 MB || SATA-150 | | [[HTS541640J9SA00]] || 40 GB || 5400rpm (1/1) || 8 MB || SATA-150 | ||
Line 82: | Line 84: | ||
| 0.9 A || 0.80 W || 1.4 W || 1.4 W | | 0.9 A || 0.80 W || 1.4 W || 1.4 W | ||
! {{cellcolors|lightgrey}} | ! {{cellcolors|lightgrey}} | ||
| 55 ºC || 2.9 bels || [[CECH-20xx]]A | | 55 ºC || 2.9 bels || [[CECH-20xx]]A | ||
|- | |- | ||
! Travelstar Z5K500 | ! Travelstar Z5K500 | ||
Line 92: | Line 94: | ||
! {{cellcolors|lightgrey}} | ! {{cellcolors|lightgrey}} | ||
| 60 ºC || 2.1 bels || [[CECH-40xx]]C | | 60 ºC || 2.1 bels || [[CECH-40xx]]C | ||
|- | |- | ||
! colspan=21 {{cellcolors|lightgrey}} | ! colspan=21 {{cellcolors|lightgrey}} | ||
Line 160: | Line 144: | ||
! colspan=21 {{cellcolors|lightgrey}} | ! colspan=21 {{cellcolors|lightgrey}} | ||
|- | |- | ||
! rowspan= | ! rowspan=8 | Toshiba | ||
! rowspan=2 | MKxx52GSX | ! rowspan=2 | MKxx52GSX | ||
| [[MK8052GSX]] || 80 GB || 5400rpm (1/1) || 8 MB || SATA-300 | | [[MK8052GSX]] || 80 GB || 5400rpm (1/1) || 8 MB || SATA-300 | ||
Line 195: | Line 179: | ||
| 55 ºC || 2.0 bels || [[CECH-20xx]]B <!-- also the [[CECH-21xx]]B and [[CECH-25xx]]B probably goes here --> | | 55 ºC || 2.0 bels || [[CECH-20xx]]B <!-- also the [[CECH-21xx]]B and [[CECH-25xx]]B probably goes here --> | ||
|- | |- | ||
! rowspan= | ! rowspan=2 | MKxx65GSX | ||
| [[MK1665GSX]] || 160 GB || 5400rpm (1/1) || 8 MB || SATA-300 | | [[MK1665GSX]] || 160 GB || 5400rpm (1/1) || 8 MB || SATA-300 | ||
! {{cellcolors|lightgrey}} | ! {{cellcolors|lightgrey}} | ||
Line 211: | Line 187: | ||
! {{cellcolors|lightgrey}} | ! {{cellcolors|lightgrey}} | ||
| 55 ºC || 20 dBA || [[CECH-25xx]]A | | 55 ºC || 20 dBA || [[CECH-25xx]]A | ||
|- | |- | ||
| [[MK3265GSX]] || 320 GB || 5400rpm (1/2) || 8 MB || SATA-300 | | [[MK3265GSX]] || 320 GB || 5400rpm (1/2) || 8 MB || SATA-300 | ||
Line 254: | Line 222: | ||
**There is no conversion formula between "bels" (sound power) and "dBA" (sound pressure)... are different meassure concepts and cant be compared | **There is no conversion formula between "bels" (sound power) and "dBA" (sound pressure)... are different meassure concepts and cant be compared | ||
{{Boxframe0|content=''' | {{Boxframe0|content='''Temporal notes (this is missing info that needs to be moved to the table)''' | ||
*[[CECHMxx]] 80GB <--- Toshiba [[MK8052GSX]], or fujitsu [[MHZ2080BH]], or hitachi [[HTS542580K9SA00]] ? | *PS3 models missing in the table: | ||
*[[CECH- | **[[CECHMxx]] 80GB <--- Toshiba [[MK8052GSX]], or fujitsu [[MHZ2080BH]], or hitachi [[HTS542580K9SA00]] ? | ||
*[[CECH- | **[[CECH-21xx]]A 120GB <--- toshiba [[MK1255GSX]] ? | ||
* | **[[CECH-21xx]]B 250GB <--- toshiba [[MK2555GSX]] ? | ||
**[[CECH-25xx]]A 120GB <--- toshiba [[MK1255GSX]] ? | |||
*[[CECH- | **[[CECH-25xx]]B 250GB <--- toshiba [[MK2555GSX]] ? | ||
**[[CECH-40xx]]A 12GB <---- internal flash storage (no HDD) | |||
* | **[[CECH-40xx]]B 250GB <--- hitachi Travelstar (Z5K500 series) - [[HTS545025A7E380]] (1 head), or toshiba [[MK2555GSX]] (old) ? | ||
*[[CECH- | |||
}} | }} | ||
==== Harddrive Speed Tests ==== | ==== Harddrive Speed Tests ==== | ||
Line 533: | Line 497: | ||
*There is no HDD speed test tool for PS3 GameOS, in PS3 OtherOS/linux hdparm can be used for a simple speed test | *There is no HDD speed test tool for PS3 GameOS, in PS3 OtherOS/linux hdparm can be used for a simple speed test | ||
*There is a '''Speed Tests (PS3)''' table in [[Talk:Harddrive#Experimental_Tables|Talk Page]] ready to include this speed tests made in PS3, feel free to add your results or/and copy the whole table here when needed | *There is a '''Speed Tests (PS3)''' table in [[Talk:Harddrive#Experimental_Tables|Talk Page]] ready to include this speed tests made in PS3, feel free to add your results or/and copy the whole table here when needed | ||
=== Harddrive info From software === | === Harddrive info From software === | ||
Line 644: | Line 563: | ||
'''About not-backuped files''' | '''About not-backuped files''' | ||
Savegames in PS3 format and trophies are linked to the console/user by using | Savegames in PS3 format and trophies are linked to the console/user by using his PARAM.SFO... if you look in this table [http://www.psdevwiki.com/ps3/PARAM.SFO#SFO_Requirements_for_HDD_contents|SFO Requirements for HDD contents] in his respective columns, the critical param_keys that needs to be taken in consideation when importing/exporting to another account or console are: ACCOUNTID, ACCOUNT_ID, PARAMS, and SAVEDATA_LIST_PARAM | ||
There are several scenarios for importing exporting in the same or other console, between accounts, between registered and not registered PSN accounts, etc... One scenario that deserves a mention because the simplicity is when you replace the HDD, your account is not registered in PSN, and your PS3 uses a NOR flash | There are several scenarios for importing exporting in the same or other console, between accounts, between registered and not registered PSN accounts, etc... One scenario that deserves a mention because the simplicity is when you replace the HDD, your account is not registered in PSN, and your PS3 uses a NOR flash | ||
PS3 accounts not registered in PSN | PS3 accounts not registered in PSN uses an account id filled with zeroes (thats normal, and is taken as a real number by the system), and trophies are only linked to ACCOUNTID !!!. If your source and target accounts are not registered in PSN you can simply paste the old trophy folders in the new account (dev_hdd0/home/<any_user_id_here>) in your new HDD and "rebuild database", thats all. You can use the same "trick" to transfer trophies between accounts in the same or other console if none of them are registered in PSN (yes, all the PS3 CFW users of the world not registered in PSN can share his trophies just by copypasting files) | ||
For gamesaves the ACCOUNT_ID is also used, but like explained above (because in this example the source and target accounts are not registered in PSN) this is not a problem, the problem here are the contents of PARAMS and SAVEDATA_LIST_PARAM | For gamesaves the ACCOUNT_ID is also used, but like explained above (because in this example the source and target accounts are not registered in PSN) this is not a problem, the problem here are the contents of PARAMS and SAVEDATA_LIST_PARAM | ||
Line 653: | Line 572: | ||
Actually, are not a problem in all cases because chances are high that all values matches, but usually what changes is the "User ID" assigned to the account the first time it was created (you know... this 00000001 folder that was assiged to the first user you created inside dev_hdd0/home/<user_id_here>/), This number is a counter that always increases (even when you erase users it will not decrease) is stored inside xregistry.sys, and inside the gamesaves in the PARAMS | Actually, are not a problem in all cases because chances are high that all values matches, but usually what changes is the "User ID" assigned to the account the first time it was created (you know... this 00000001 folder that was assiged to the first user you created inside dev_hdd0/home/<user_id_here>/), This number is a counter that always increases (even when you erase users it will not decrease) is stored inside xregistry.sys, and inside the gamesaves in the PARAMS | ||
Probably you need to change this number to match the new account, so after replacing the HDD and creating a new account | Probably you need to change this number to match the new account, so after replacing the HDD and creating a new account is a good moment to keep this account number 00000001 and modify all the saves to match the 00000001 inside his PARAM. The other known values inside PARAM doesnt need to be changed (because we are importing/exporting in the same console, so "PS3 console ID" is the same)... only is needed to change this when moving the save to another console | ||
All this tasks are simple edits in the PARAM.SFO file... you could even make it with a | All this tasks are simple edits in the PARAM.SFO file... you could even make it with a hexeditor if you are used to .SFO format, to simplify it you can use some .SFO editor (one that allows to change this values) or one gamesave editor | ||
Trophies and PS3 saves are protected by .PFD files so in case you | Trophies and PS3 saves are protected by .PFD files so in case you modifyed one of the .SFO then you need to "update" the list of protected files inside the .PFD (because PARAM.SFO is always in the list). When you update the .PFD the new PARAM.SFO is added to the list and this makes the whole gamesave folder/files "valid" and ready to be copyed in PS3. Is also needed to use the option "rebuild database" at the end of the process | ||
The PFD "update" is one of the commands inside "flatz pfd tools", it returns some info about the protected files inside the table with an "OK" at the end of each line when everything is fine. | The PFD "update" is one of the commands inside "flatz pfd tools", it returns some info about the protected files inside the table with an "OK" at the end of each line when everything is fine. | ||
Line 663: | Line 582: | ||
*Notes | *Notes | ||
**Part of the contents of PARAMS and SAVEDATA_LIST_PARAM are still unknown, ( | **Part of the contents of PARAMS and SAVEDATA_LIST_PARAM are still unknown, (is awesome how some people that uses/codes savegame cheat apps are still ignoring this... and im not talking about flatz, his purpose was to break the .pfd security to unlocking/transfering protected user files between legit offline accounts and no cheating purposes) --[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 02:40, 28 January 2014 (EST) | ||
**About NAND or NOR consoles... xregistry.sys contains "Account ID" and "User ID" | **About NAND or NOR consoles... xregistry.sys contains "Account ID" and "User ID" | ||
***Is PS3's with NOR xregistry.sys is stored in "Virtual flash" (a partition in HDD) | ***Is PS3's with NOR xregistry.sys is stored in "Virtual flash" (a partition in HDD) | ||
Line 693: | Line 612: | ||
===== Economic contemplation ===== | ===== Economic contemplation ===== | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- |