- 1 Internal harddrive
- 1.1 Harddrive Model info
- 1.2 Internal Harddrive maximum capacity
- 1.3 Harddrive info From software
- 1.4 Harddrive encryption
- 1.5 Firmware harddrive tools
- 1.6 Harddrive replacements, modifications, expansion parts
- 1.6.1 Replacing the internal harddrive
- 1.6.2 Internal SATA to External drive/cradle
- 1.6.3 CECH-40xx : External harddrive expansion for internal storage
- 1.6.4 CECH-4000B only : Internal harddrive
- 2 External storage
- 3 Tools, HDD manufacturers support webs, Documentation, etc
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 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 Gbit/s.
- GameOS partition
- Is an UFS2 256-bit file system with a sectorsize of 512 bytes (4096 bits).
- Because it is per-console 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 per-console encryption, hence emptying the drive)
Harddrive Model info
The data in this table has been copied from manufacturer documents (datasheets or productsheets) available at support sites found at the links at bottom of the page
- A collection of productsheets/datasheets of the HDD models used in PS3, renamed by manufacturer/series: [Download] (fujitsu series are missing)
|Buffer||Interface||Seek Speeds||Power Requirements||Operating
|Used in PS3 Models|
|Fujitsu||MHW||MHW2040BH||40 GB||5400rpm (1/1)||8 MB||SATA-150||1.5 ms||5.56 ms||12 ms||14 ms||1.0 A||0.60 W||1.9 W||1.9 W||55 ºC||2.0 bels||CECHJxx|
|MHZ||MHZ2080BH||80 GB||5400rpm (1/1)||8 MB||SATA-300||1.5 ms||5.56 ms||12 ms||14 ms||1.0 A||0.60 W||1.9 W||1.9 W||55 ºC||2.4 bels||CECHKxx, CECHLxx|
|MHZ2160BH||160 GB||5400rpm (1/2)||8 MB||SATA-300||1.5 ms||?.?? ms||?? ms||?? ms||1.0 A||0.60 W||2.1 W||2.1 W||55 ºC||2.0 bels||CECHPxx, CECHQxx|
|Hitachi||Travelstar 5K160||HTS541640J9SA00||40 GB||5400rpm (1/1)||8 MB||SATA-150||2.2 ms||5.50 ms||14 ms||15 ms||1.0 A||0.85 W||1.8 W||1.8 W||55 ºC||2.7 bels||CECHHxx|
|Travelstar 5K250||HTS542580K9SA00||80 GB||5400rpm (1/2)||8 MB||SATA-150||2.2 ms||5.50 ms||14 ms||15 ms||1.0 A||0.85 W||1.8 W||1.8 W||55 ºC||2.7 bels||CECHLxx|
|Travelstar 5K500||HTS545012B9SA00||120 GB||5400rpm (1/1)||8 MB||SATA-150||2.2 ms||5.50 ms||14 ms||15 ms||0.9 A||0.80 W||1.4 W||1.4 W||55 ºC||2.9 bels||CECH-20xxA|
|Travelstar Z5K500||HTS545050A7E380||500 GB||5400rpm (1/2)||8 MB||SATA-300||2.2 ms||5.50 ms||13 ms||13 ms||0.9 A||0.55 W||1.6 W||1.6 W||60 ºC||2.1 bels||CECH-40xxC|
|Travelstar Z5K320-160||HTS543216A7A384||160 GB||5400rpm (1/?)||?||?||?||?||?||?||?||?||?||?||?||?||CECH-30xxA|
|Travelstar Z5K320-250||HTS543225A7A384||250 GB||5400rpm (1/?)||?||?||?||?||?||?||?||?||?||?||?||?||CECH-40xxB|
|Seagate||Momentus 5400.2||ST96812AS||60 GB||5400rpm (1/2)||8 MB||SATA-150||1.5 ms||5.56 ms||12 ms||14 ms||1.1 A||0.99 W||1.9 W||2.3 W||55 ºC||3.1 bels||CECHAxx, CECHCxx|
|Momentus 5400.3||ST980811AS||80 GB||5400rpm (1/2)||8 MB||SATA-150||1.5 ms||5.56 ms||11 ms||13 ms||1.0 A||0.75 W||1.9 W||1.8 W||60 ºC||3.2 bels||CECHExx|
|LD25 SATA||ST920217AS||20 GB||5400rpm (1/1)||2 MB||SATA-150||2.0 ms||5.60 ms||16 ms||16 ms||1.0 A||?.?? W||2.3 W||2.3 W||55 ºC||2.7 bels||CECHBxx|
|ST9402115AS||40 GB||5400rpm (1/2)||2 MB||SATA-150||2.0 ms||5.60 ms||16 ms||16 ms||1.0 A||2.00 W||2.3 W||2.3 W||55 ºC||2.7 bels||CECHGxx, CECHHxx, and probably in CECHJxx|
|LD25 5400.2||ST940210AS||40 GB||5400rpm (1/2)||2 MB||SATA-150||1.5 ms||5.60 ms||15 ms||15 ms||1.0 A||2.50 W||2.3 W||2.3 W||60 ºC||2.6 bels||CECHGxx, CECHJxx, and probably in CECHHxx|
|Toshiba||MKxx52GSX||MK8052GSX||80 GB||5400rpm (1/1)||8 MB||SATA-300||2.0 ms||?.?? ms||12 ms||12 ms||0.9 A||0.85 W||2.0 W||2.0 W||55 ºC||25 dBA||CECHLxx|
|MK1652GSX||160 GB||5400rpm (1/2)||8 MB||SATA-300||2.0 ms||?.?? ms||12 ms||12 ms||0.9 A||0.85 W||2.0 W||2.0 W||55 ºC||25 dBA||CECHPxx, and probably in CECHQxx|
|MKxx55GSX||MK1255GSX||120 GB||5400rpm (1/1)||8 MB||SATA-300||2.0 ms||5.55 ms||12 ms||12 ms||0.9 A||0.85 W||1.4 W||1.4 W||55 ºC||2.0 bels||CECH-20xxA|
|MK2555GSX||250 GB||5400rpm (1/2)||8 MB||SATA-300||2.0 ms||5.55 ms||12 ms||12 ms||0.9 A||0.85 W||1.4 W||1.4 W||55 ºC||2.0 bels||CECH-20xxB|
|MKxx65GSX||MK1265GSX||120 GB||5400rpm (1/1)||8 MB||SATA-?||?.? ms||?.?? ms||? ms||? ms||?.? A||?.?? W||?.? W||?.? W||?? ºC||?? dBA||CECH-21xxA|
|MK1665GSX||160 GB||5400rpm (1/1)||8 MB||SATA-300||2.0 ms||?.?? ms||12 ms||12 ms||0.9 A||0.75 W||1.5 W||1.5 W||55 ºC||20 dBA||CECH-25xxA|
|MK3265GSX||320 GB||5400rpm (1/2)||8 MB||SATA-300||2.0 ms||?.?? ms||12 ms||12 ms||0.9 A||0.75 W||1.5 W||1.5 W||55 ºC||20 dBA||CECH-25xxB|
|MKxx76GSX||MK1676GSX||160 GB||5400rpm (1/1)||8 MB||SATA-300||2.0 ms||5.55 ms||12 ms||12 ms||0.9 A||0.55 W||1.5 W||1.5 W||55 ºC||20 dBA||CECH-30xxA|
|MK3276GSX||320 GB||5400rpm (1/2)||8 MB||SATA-300||2.0 ms||5.55 ms||12 ms||12 ms||0.9 A||0.55 W||1.5 W||1.5 W||55 ºC||20 dBA||CECH-30xxB|
- Meassure units conversions:
- Watts = Amps * volts (or... Amps = Watts / Volts)
- There is no conversion formula between "bels" (sound power) and "dBA" (sound pressure)... are different meassure concepts and cant be compared
Harddrive Speed Tests
This speed tests are only orientative because was made in PC's with different motherboards, and the results can be different in a PS3
- 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 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
Internal Harddrive maximum capacity
When talking about compatibility is important to keep in mind the PS3 firmware could be partially "broken" by using a large capacity, most specifically the filesystem manteinance functions that are the resposibles to run the filesystem checks (and repair the posible filesystem problems if needed), the filesystem manteinance functions runs in the background while on XMB (periodically?), and additionally the PS3 firmware runs a "filesystem check" under 2 conditions: after a firmware crash (in other words, after a shutting down the device without the proper filesytem "unmount"), and when we use the option 3 from Recovery Menu named 3. Restore File System
There are some harddrive capacities (in between 1TB and 2TB) where the PS3 formats it correctly, allows to install games, and could potentially run fine for a few months but "breaks" the filesystem manteinance functions. In this case what happens is every little filesystem error (caused by firmware freezes/crashes or interrumpted file transfers from FTP/USB) are going to stay forever in the filesystem gets cummulated with other filesystem errors up to a point where the whole filesystem collapses and you are welcomed with a warning screen where the only option is to format it (in other words, is imposible to restore it). When this happens you lost all his contents, and the last hope to recover some files from it is by using the "EID root key" to decrypt his contents in a PC
|unknown||The exact limit where the filesystem check functions gets broken is unknown|
|2,147,483,647||1,099,511,627,264||1024-(1 sector)||~1099||Yes||No||32bit integer limit|
|unknown||The exact limit where the formatting functions gets broken is unknown|
Harddrive info From software
Harddrive info in Flash
- In NOR flash
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00F201F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F20200 00 00 00 01 48 69 74 61 63 68 69 20 48 54 53 35 ....Hitachi HTS5 00F20210 34 31 36 34 30 4A 39 53 41 30 30 20 20 20 20 20 41640J9SA00 00F20220 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00F20230 20 20 53 42 32 41 38 31 53 4B 48 33 4E 36 55 53 SB2A81SKH3N6US 00F20240 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
- In GameOS
See DeviceID ext_nor_flash
Harddrive info in xregistry.sys
In path: dev_flash2/etc/XRegistry.sys
The entry: setting/system/hddSerial contains the "HDD model" + "HDD Serial"
Harddrive info from SCSI/atapi commands in GameOS
Normally on PC, you would use:
sg_logs SCSI LOG SENSE -t command
Not much specific to hdd temperature on ps3 in gameos documented yet
PS3 uses XTS-AES-128 to encrypt the internal HDD drive on SLIM consoles and AES-CBC-128/AES-CBC-192 on PHAT consoles.
Good paper about XTS-AES: http://ntnu.diva-portal.org/smash/get/diva2:347753/FULLTEXT01
XTS-AES-128 means that there are 2 keys of size 128bit actually, the one for tweak encryption and the other for data encryption. Both keys are different on each PS3 console and can be easily dumped e.g. with modified sb_iso_spu_module.self. These 2 keys are sent to ENCDEC device which performs HDD encryption/decryption. HDD keys are NOT stored in EID4.. On PHAT consoles the only data key is used with zeroed IV.
Currently i'm able to decrypt my PS3 HDD on PC and i can also talk to the ENCDEC device without isolated SPU modules.
To be able to talk to the ENCDEC device, you have to extract 2 AES-CBC keys and one magic e.g. from sb_iso_spu_module.self . First, the 2 AES-CBC are used to establish a secure session between the host and the ENCDEC device. The host and the ENCDEC device exchange 2 random numbers and derive a session key from these random numbers. The session key is then used to encrypt the actual command sent to the ENCDEC device from the host. A command can e.g. set ATA keys.
Dumping ATA keys (128bit tweak and 128bit data key) is easy, i did it on PS3 Linux with my spuisofs driver and a modified version of sb_iso_spu_module.self. ATA keys are passed as parameters to this module and i just copied them with MFC DMA to PPU memory and stopped the execution of the SPU.
Firmware harddrive tools
About not-backuped files
Savegames in PS3 format and trophies are linked to the console/user by using their PARAM.SFO... if you look in this table Requirements for HDD contents in their 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
PS3 accounts not registered in PSN use an account id filled with zeroes (that's 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", that's 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 their trophies just by copy-pasting 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
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, it's a good time to keep this account number 00000001 and modify all the saves to match the 00000001 inside their PARAM. The other known values inside PARAM doesn't need to be changed (because we are importing/exporting in the same console, so "PS3 console ID" is the same)... you only need 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 hex editor 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 modified 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 copied in the PS3. You will also need to "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.
- Part of the contents of PARAMS and SAVEDATA_LIST_PARAM are still unknown, (it's awesome how some people that uses/codes savegame cheat apps are still ignoring this... and I'm 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) --Sandungas (talk) 02:40, 28 January 2014 (EST)
- 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)
- In the case of NOR when replacing/formatting the HDD you are deleting the file, so is generated at next boot (and filled with the user info the first time you create a new user, that will be assigned the "account id" 00000001). This is not bad, actually is a good way to "cleanup" the xregistry.sys because the PS3 will generate a "fresh one" from scratch (usually xregistry.sys contains lot of areas marked as "not used" from old users that was erased, other old data, the annoying user counter that always increases, and even errors)
- Is PS3's with NAND xregistry.sys is stored in "NAND flash"
- In the case of NAND when replacing/formatting the HDD you keep the file with the old users info, the user counter increasing, etc... i dont know a good/efective/simple way to regenerate it --Sandungas (talk) 02:15, 28 January 2014 (EST)
Data Transfer Utility
Harddrive replacements, modifications, expansion parts
Replacing the internal harddrive
For compatibility, if you have a SATA-300 (sometimes called SATA-II or SATA2) or SATA-600 (sometimes called SATA-III or SATA3) harddrive, you should sometimes set the harddrive via jumper to enforce the slower SATA-150 speed, instead of default 3 Gb/s of SATA-300 / 6Gb/s of SATA-600.
|This article is marked outdated.|
|3.5" 7200 rpm HDD||0,048||90.6|
|3.5" 5400 rpm HDD||0,049||92.5|
|2.5" 5400 rpm HDD||0,053||100|
|2.5" 7200 rpm HDD||0,061||115.1|
|3.5" 7200 rpm SSHD||0,071||134|
|2.5" 5400 rpm SHDD||0,076||143.4|
|2.5" 1TB SSD||0,358||675.5|
|2.5" 7200 rpm SSHD||N / A||N / A|
|3.5" 5400 rpm SHDD||N / A||N / A|
|3.5" 1TB SSD||N / A||N / A|
Exchanging the internal drive to a 7200RPM model doesn’t do much for your loading times (shaves off a second or 2), hybrid SSHD are a bit more future proof while still lowcost, but upgrading to SSD/Flash Drives is almost insane considering the prices you pay per GB. Any modern larger drive is always faster than the older default smaller drive. Some people are arguing that SSD/Flash Drives produce "much less heat" but consider this: a very good/efficient one uses 5V 0.35A 1.75 Watt while a harddrive uses 5V 0.85A 4.25 Watt. A difference of 2.5W less on a total of 225Watt is not something you would see prominently back on your electric bill or thermometer.
There is even report of SDD's sometimes having a negative impact on performance, compared to the original PS3 harddrive. Example: Corsair CSSD F240GBGT BK - which seem to have 4KB sectors (cause?)
Because of the low price/ high storage capacity I personally always go for SATAII/300 7200rpm drives (if internal, maximum height is 9.5mm, 12 or 12.5mm doesn’t fit) and if modified to external via eSATA you can even use cheaper/faster 3.5″ drives (but you’ll need them to have their own powersupply because the internal PS3 powersupply can’t power that safely).
Original vs Replacement Drives speed comparison
|Original 2.5"||SATA1 150||5400||60 GB||Seagate Momentus 5400.2 ST96812A S||25 MB/s||24.4 MB/s||28.5 MB/s||17.4ms|
|New (A) 2.5"||SATA1 150||5400||160GB||Samsung HM160HI HH100-06||70 MB/s||54.9 MB/s||115.4 MB/s||22.4ms|
|New (B) 2.5"||SATA2 300||7200||500GB||Samsung HM500JI 2AC101C5||95 MB/s||71.5 MB/s||219.3 MB/s||21.4ms|
|New (C) 3.5"||SATA2 300||7200||2TB||Samsung HD203WI 1AN10003||115 MB/s||85.6 MB/s||252.5 MB/s||23.6ms|
Replacement Internal HDDs for PS3
for a more updated table with 1TB 2.5" SSHD's, see Psdevwiki.com/PS4 Harddrive page
Internal SATA to External drive/cradle
You can also convert the internal SATA to an external eSATA port, to which you can connect a eSATA cradle or eSATA harddrive. Example of such a cable : http://www.cutedigi.com/images/sata_2_esata_cable.jpg
More solutions are listed here: Solutions for swapping / externalise the harddrive
- Vertical Stand with Storage attachement (CECH-4000A only)
- Hard Disk Drive (HDD) Mounting Bracket (CECH-ZHD1)
- Hard Disk Drive (HDD) Mounting Bracket including 250GB drive (CECH-ZS1)
CECH-4000B only : Internal harddrive
5400rpm Hitachi hard drive
- Z5K500 HTS545050A7E380 (500GB)
- Z5K500 HTS543225A7A384 (250GB)
The PS3 also supports external harddrives connected to the USB port (identified as USB Mass Storage device) using only FAT12/16/32 file systems format. File systems like UFS/UFS2, EXT3/EXT4, which are natively used on internal harddrive cannot be used on external on a non-modified system. You can format it to any size up to 8TB *, which is the theoretical drive size limit of FAT32. There have been verified success of 2TB external harddrives working with the PS3. The whole drive needs to be formatted into a single 2TB FAT32 partition using special software tools like fat32format.exe that can handle large drives. Note that FAT32 supports a maximum file size of 4GB.
- *FAT32 restrictions:
- max amount of files: 268,173,300
- max filesize: 4,294,967,295 Bytes
- max cluster size: 32K practical, 64K with high incompatibility (PS3 and Xbox360 will accept it, but most applications will not).
- max sector size: 512 Bytes (4096 sectorsize is not compatible)
- max amount of clusters per volume: 268,435,445 (2^28)
- max volume size because of cluster limit: 8,796,093,022,208 Bytes (~8TB)
- max volume size because of compatibility: 2TB-1 @ 512B sectors, 32KB allocation unit or 4TB-1 @ 512B sectors, 64KB allocation unit (not recommended) / absolute limit would be 16 TB for 4096 byte sectors, which is incompatible with PS3
- *FAT32 restrictions:
- performance consideration: with a 8TB volumesize, the file allocation table itself will be 1GB, not really practical (it is 256MB at a 2TB volumesize, which is still a lot larger than ps3 memory thus negatively impacting on performance).
Tools, HDD manufacturers support webs, Documentation, etc
Sometimes you just need to be sure that harddrive is still working in crisp condition. All harddrive manufacturers have special low level diagnostics tool for that purpose.
Low level diagnostic tools
- Some of this wikipage is also in User Manual (e.g. Page 36 and further: CECH-2001A_2001B-2.85_2.pdf)
HDD Manufacturers support and info webs
http://storage.toshiba.eu/cms/en/support_services/faq.html (fujistsu storage products model numbers)
M=fujitsu, H=HNfamily, Z=series, 2=2.5", 040=40GB, BH=interface
H=HGST, T=Travelstar, S = Standard, 54=5400rpm, 16 =topcapacity, 40=model capacity, J=Generation, 9=9mm form factor, SA=sata150 (or E3 = SATA 3Gb/s), 8=Feature code (8MB cache), 0=Unique code
ST=brand(seagate) 9=form factor(2.5") 6=size(60GB) 8=cache(8mb) 12=identifier AS=interface(SATA)
Toshiba Europe Products - Client Hard Disk Drives: http://storage.toshiba.eu/cms/en/hdd/hard_disk_drives/index.jsp#