When You setting up HPA, fw expecting LBA number which is max sector number. If You choose number for target disk size and indeed it become that size, then You should know what sector size You type and which was used by firmware. You couldn't get the same disk size using the same max LBA for two different physical sector size.
In example 1,5TiB (1649267441664 bytes) is equally to:
3221225472 sectors if sector size = 512 bytes (or so called e512, "split" on fw side 4K to 8 slices end exposing each as single LBA number for higher layers)
402653184 sectors if sector size = 4096 bytes (so called 4K)
I've been doing some further testing and investigation of this fsbtodb value in the UFS superblock.
Edit: I've removed this post for now as I've realised there was a mistake in how I was doing the testing (the fsbtodb value seems to change based on whether the filesystem is little-endian vs big-endian, not between BSD variants as I originally suggested). I will re-post once I've tested further.
From further testing I've got a bit more insight into things now...
The reason I couldn't mount the PS3 partition in NetBSD 6 was because "FFS Endian Independent support" was not enabled in the kernel in the amd64 release. Although the utilities like fsck_ffs, tunefs and resizefs supported both little-endian and big-endian without this; mount_ffs did not. Once I re-compiled the kernel with "options FFS_EI" enabled then I can mount the PS3 partition.
A secondary issue when trying to use NetBSD is that they removed support for "soft updates" in NetBSD 6. This is a UFS feature that the PS3 requires, and if you mount the partition in NetBSD 6+ it automatically disables this making the PS3 unable to mount it: https://www.netbsd.org/changes/changes-6.0.html#softdep
NetBSD 5.2 is the latest release which retains soft updates support; but you still must be careful. You have to specifically mount the partition with this option enabled otherwise it will automatically turn it off. If that has happened then there is no way I can find from within NetBSD to turn this feature back on. The option is missing from their tunefs application. You can fix it and turn it back on by using tunefs from FreeBSD (they don't seem to have ever removed this from their implementation, and you're at no risk of turning it off accidentally when your mount your partition there).
The mount command for NetBSD 5.2 and earlier would be:
Code:
mount -o softdep /dev/ld1d /cell_mw_cfs/
Lastly on the PS3 setting the UFS superblock fsbtodb to 0 - seemingly - when a 512e disk drive is being used. A value of 0 is telling you the disk logical sector size is 4096, and a value of 3 is telling you the logical sector size is 512.
I'm almost certain the PS3 shouldn't be doing this. The only way I can replicate this behaviour when creating UFS partitions is if I'm explicitly passing the -S option to newfs and setting it to 4096.
The fact that the PS3 is creating a UFS file system based on a logical disk sector size of 4096 makes me think that it is producing a fundamentally flawed file system on these drives (even though it appears to work fine). I can only imagine you are going to run into issues at some point, most likely as the drive fills up.
Running fsck from NetBSD and FreeBSD on such a drive that the PS3 has just formatted, they both agree that the partition is in need of repair. This does not happen on a 512n drive that the PS3 has correctly formatted with fsbtodb set to 3 - that file system is clean.
Code:
# fsck_ffs -fn /dev/ld1d
** /dev/rld1d (NO WRITE)
** Swapped byte order
** File system is already clean
** Last Mounted on /cell_mw_cfs
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=2 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547584 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547585 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547586 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547587 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547588 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547589 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547590 (4 should be 32)
CORRECT? no
INCORRECT BLOCK COUNT I=6547591 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547592 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=6547593 (6 should be 48)
CORRECT? no
INCORRECT BLOCK COUNT I=9469952 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=9469953 (144 should be 1152)
CORRECT? no
INCORRECT BLOCK COUNT I=9469954 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=9469955 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=9469956 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=9469957 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=9469959 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337088 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337089 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337090 (2564 should be 20512)
CORRECT? no
INCORRECT BLOCK COUNT I=27337092 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337093 (132 should be 1056)
CORRECT? no
INCORRECT BLOCK COUNT I=27337094 (260 should be 2080)
CORRECT? no
INCORRECT BLOCK COUNT I=27337095 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337096 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337097 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337098 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337099 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337100 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337101 (304 should be 2432)
CORRECT? no
INCORRECT BLOCK COUNT I=27337102 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337103 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337104 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337105 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337106 (304 should be 2432)
CORRECT? no
INCORRECT BLOCK COUNT I=27337107 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337108 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337109 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337110 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337111 (304 should be 2432)
CORRECT? no
INCORRECT BLOCK COUNT I=27337112 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=27337113 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=31591168 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=31591169 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=31591170 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=31591171 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=43613568 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=43613569 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=43613571 (72 should be 576)
CORRECT? no
INCORRECT BLOCK COUNT I=43613572 (72 should be 576)
CORRECT? no
INCORRECT BLOCK COUNT I=43613573 (72 should be 576)
CORRECT? no
INCORRECT BLOCK COUNT I=43613575 (25 should be 200)
CORRECT? no
INCORRECT BLOCK COUNT I=43613577 (25 should be 200)
CORRECT? no
INCORRECT BLOCK COUNT I=43613580 (1284 should be 10272)
CORRECT? no
INCORRECT BLOCK COUNT I=62738432 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=62738433 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=62738434 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=62738435 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=62738436 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=82936064 (1 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=82936065 (122944 should be 983552)
CORRECT? no
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
63 files, 128562 used, 235823183 free (31 frags, 58955788 blocks, 0.0% fragmentation)
***** UNRESOLVED INCONSISTENCIES REMAIN *****
It's unclear to me if allowing fsck to repair it would be enough to fix the partition; I suspect not given it's been explicitly created based on a 4096 logical sector size. What I do know is that the PS3s own file system restore function does not repair these errors.
------
Edit: I tested repairing it via fsck from NetBSD, and as soon as the PS3 mounts the drive again it introduces new inconsistencies, according to a subsequent fsck.
------
I have limited disk drives I can test against, so I'm curious if this is an isolated case or if the PS3 makes this mistake with all 512e drives (ie. drives that present to the hardware as 512 logical / 4096 physical). If anyone wants to share their UFS superblocks from such a drive:
You can use this command to manually set fsbtodb to 3, which then allows FreeBSD and NetBSD to mount the drive. But this value is reset to 0 when the PS3 next mounts it.
I have a PS3 HDD that was initialized (killed) by Windows. After a lot of attempts with the <PS3 HDD Mounter (Missing PS3PT).sh>, it was finally able to mount my HDD. (sincerally, yesterday it didn't work out by any means, but today it finally was able to mount my HDD (I'm so happy I could cry actually!))
I guess there were some problems with the sectors, so I flashed my backup image again into the HDD. Also, I don't know if this influenced also, but the second time it asked me about which sector to initiate from (first one is asking about the flash, second one about the HDD), I pressed enter by mistake. Then, coincidence or not (probably not) the next attempt to run the program it ran smoothly and mounted the HDD without any more problems.
My doubt now is: I want to backup and save my Save Game Data and Media. The media I'm pretty sure how to do it, but how am I supposed to backup the saves? Can I just copy them to my USB over PS3->SAVEDATA, format my HDD, reinstall the system and them get them back? Or do I need something like Multiman to get them back?
Also, is the save data location ps3/storage/hdd/dev_hdd0/home/0000000x/savedata, being x the user?
The games I'm most concerned about are Gran Turismo 5, Gran Turismo 6, Minecraft to get the saves. Also, I do have more then one user. (1 or 2 didn't have PSN accounts if I'm not wrong)
Also, can I fix my HDD with this toolbox or do I need to retry doing a partition table transplant?
I would still like to game with this HDD installation
My doubt now is: I want to backup and save my Save Game Data and Media. The media I'm pretty sure how to do it, but how am I supposed to backup the saves? Can I just copy them to my USB over PS3->SAVEDATA, format my HDD, reinstall the system and them get them back? Or do I need something like Multiman to get them back?
Also, is the save data location ps3/storage/hdd/dev_hdd0/home/0000000x/savedata, being x the user?
Also, can I fix my HDD with this toolbox or do I need to retry doing a partition table transplant?
I would still like to game with this HDD installation
Not sure what you mean by "fix the HDD". The best solution is to backup all the important data (media, savefiles, configs, PKGs, licences, etc)., then make the PS3 format the HDD to start clean and finally restore all the data back.
I know it's a pain to reinstall everything, but it's the best option in the long run as it avoids lots of problems.
Oh, and by fixing, as I mentioned, I accidentally initialized the HDD in my Windows. I didn't want it to initialize, but yes... So as the PS3 partition is gone, the system can't properly recognize the disk anymore.
Also, if I copy the media, savefiles, configs, PKGs, licences (are there any more important things? I don't have any idea), can I just copy then to the newly and fresh installed HDD using multiman? Like, bluntly copying them in the right paths
Oh, and by fixing, as I mentioned, I accidentally initialized the HDD in my Windows. I didn't want it to initialize, but yes... So as the PS3 partition is gone, the system can't properly recognize the disk anymore.
Also, if I copy the media, savefiles, configs, PKGs, licences (are there any more important things? I don't have any idea), can I just copy then to the newly and fresh installed HDD using multiman? Like, bluntly copying them in the right paths
Of course!, that's the way to do it. Once you've placed all the files in their respective places, you shoud be able to run and use them.
Remember, copy the act.dat and all the RIF files in order to run all your games. If you lose them, you will have to extract the RAF files from the RIF in order to generate new licences.
I see! Gracias compa! But I don't have any clue though about what are these RIF and RAF things lol
Is there a guide or tutorial that I could read?
I do agree that starting fresh would be great, even more now that I managed to get my precious data back (I literally cried lol) but I lack any sense about what to copy, what not to copy, or even how to copy. If it is just the HDD0 than I could just cntrl c cntrl v, but if it gets to the flash and etc then I'm totally lost
For data gathering record: which values You've chose? And what model exactly You have (CECHxx?/CECH-xxxx)? Maybe models correlating, or maybe not. Worth to note for us for analysis and other people from the future.
My doubt now is: I want to backup and save my Save Game Data and Media. The media I'm pretty sure how to do it, but how am I supposed to backup the saves? Can I just copy them to my USB over PS3->SAVEDATA, format my HDD, reinstall the system and them get them back? Or do I need something like Multiman to get them back?
No, because some saves have COPY PROHIBITED parram set in PARAM.SFO, preventing copy them from/to USB in XMB. So You need use FTP Client, filemanager eg. build-in multiMAN, or PC (if You want next fight round with ufs.ko module (the one from script work but for unknown reason, compiler ignoring my ".config" so results end with read only ufs like original...) or setting up FreeBSD or NetBSD in VM on Linux (yes, "We need to go deeper")) to restore them. And of course do rebuild database from recovery menu or else none of content will appear in XMB.
Also, is the save data location ps3/storage/hdd/dev_hdd0/home/0000000x/savedata, being x the user?
So You should also copy not only saves but their damn cache. Because patching from scratch is around 8h for GT6 due to broken by design way those games doing it (patches in PKG are used only as delivery for patches which those games applying later).
Also, can I fix my HDD with this toolbox or do I need to retry doing a partition table transplant?
I would still like to game with this HDD installation
If You are feel that You have time for it, why not. None option in toolbox can do that, only to backup it but restoring You need to do manually, in which I can help.
However, Guilotte Tesla have right. Best would be start clean. Especially that we later discovered that not always PS3PT are the same and we do not know yet why and in what circumstances exactly. In theory always the same on the same HDD and the same model. But that's theory and it is possible this is the reason why some people report that method not works for them, while works for others including me. This would be explanation of that phenomena.
RIF files are the license files attached to your PSN account and console, via act.dat (that's why it's important to save it). They are unique, non-transferable files located in /dev_hdd0/home/0000000x/exdata folder.
RAF files are license activation files used to activate content (can be games, DLCs, themes, movies, etc.). Think of them as templates that are used to generate the RIF files attached to your console and PSN account.
If you happen to reinstall everything and create a new act.dat file, you can extract the RAF files from the RIF files using some tools in order to reactivate your content.
That's why RAF files are valuable as they can be used to activate virtually any content on any console for everyone. Thus, asking for RAF files is considered piracy.
@Berion first I'm sorry, I got mixed up. I meant to put a custom value, but instead pressed enter by mistake. I do not know if this is related (probably not cause I know this sound very weird/dumb but), well: as I mentioned in the other thread, I reburned the image and then got back to linux. Then, the first try was a failure, in the second one I meant to put a custom value (it was option 'a' I think) 524288, but instead I pressed enter by mistake. Also went in failure. But then, the third try it worked (I select b for both again, just like in the 1st try). Really, I didn't do any unmounting or anything different between them, but only worked at the third try. Or maybe I'm confused, can't be like that
The third try wen like this: (I actually forgot it open, so that's why I managed to save it)
Code:
PS3 HDD Mounter (Missing PS3PT) v1.0 by Berion
Script allows to mount UserData and 3rd VFlash partitions.
This script is only for people which overwritten PS3PT by MBR/GPT in Windows.
In other words: disk initialized by Windows.
Confirm root permissions everytime You will be asked for!
[sudo] password for vfransant:
STEP 1: Devices
Choose your HDD from PS3 (type eg: /dev/sdx) from below device list:
MODEL SIZE NAME
4K /dev/fd0
ST9160821AS 149,1G /dev/sda
489M ├─/dev/sda1
489M ├─/dev/sda2
148,1G └─/dev/sda3
SAMSUNG HD102UJ 931,5G /dev/sdb
398,1G ├─/dev/sdb1
1K ├─/dev/sdb2
133,4G ├─/dev/sdb5
400G └─/dev/sdb6
Generic 298,1G /dev/sdc
/dev/sdc
Ok, so You've chose: "/dev/sdc".
Press any key to continue.
STEP 2: Mounting
Choose WISELY:
1. Mount HDD came from Fat with NAND memory.
2. Mount HDD came from Fat with NOR memory.
3. Mount HDD came from Slim with NOR memory.
3
Choose sector of "dev_flash2" partition:
a. user defined LBA
b. LBA 439816
b
Choose sector of "dev_hdd0" partition:
a. user defined LBA
b. LBA 524304
c. LBA 524312
d. LBA 524320
b
WARNING: Device /dev/sdc already contains a 'dos' partition signature.
WARNING!
========
Detected device signature(s) on /dev/sdc. Proceeding further may damage existing data.
Are you sure? (Type 'yes' in capital letters): YES
NAME
sdc
└─ps3hdd-bs
└─ps3hdd
└─ps3vflash
NAME MOUNTPOINT
loop40 /home/vfransant/ps3/storage/hdd/dev_flash2
NAME MOUNTPOINT
loop41 /home/vfransant/ps3/storage/hdd/dev_hdd0
"/dev/loop40":
00000000 e9 00 00 20 20 20 20 20 20 20 20 00 02 04 10 00 |... .....|
00000010 02 00 02 00 80 f8 20 00 00 00 00 00 00 00 00 00 |...... .........|
00000020 00 00 00 00 00 00 29 00 00 00 00 4e 4f 20 4e 41 |......)....NO NA|
00000030 4d 45 20 20 20 20 46 41 54 31 36 20 20 20 00 00 |ME FAT16 ..|
"/dev/loop41":
00000000 b0 06 cc 10 79 9f 20 77 6d e4 53 8e 18 31 1d 5a |....y. wm.S..1.Z|
00000010 3b b7 ba 8a 44 79 d3 33 3e af a4 9a 8b 25 ed 1e |;...Dy.3>....%..|
00000020 de ee 39 8e 2e 69 49 32 58 df 3a 80 09 d7 b1 01 |..9..iI2X.:.....|
00000030 6d 44 77 bf 2c ce cf d7 5f 98 28 6e 3b f2 a2 fc |mDw.,..._.(n;...|
00000040 aa 5c 79 65 fb 8e 46 21 3b 2f 94 9c a8 d1 18 fc |.\ye..F!;/......|
00000050 b1 be 16 a2 c6 d6 0a ba d6 bd b3 cc f0 8e 04 92 |................|
00000060 05 a0 22 eb 2d 5c d4 eb bc fb e0 0f c5 5e 28 90 |..".-\.......^(.|
00000070 b8 48 79 2c 11 64 4a f9 2a 43 76 00 a8 f4 fe d8 |.Hy,.dJ.*Cv.....|
00000080 16 0b 39 b5 58 6e 37 a6 e8 a9 ac 07 91 4e 3a df |..9.Xn7......N:.|
00000090 ee 33 3e 42 e1 21 92 c9 28 b9 a4 1f 4f 7d 91 32 |.3>B.!..(...O}.2|
000000a0 9e 04 c3 b8 39 12 62 40 3c f1 f8 25 43 72 63 15 |....9.b@<..%Crc.|
000000b0 49 e9 f9 3a 9a d9 d2 d2 7a ea a6 6a f5 71 f1 f5 |I..:....z..j.q..|
000000c0 2d c5 bf 47 05 5e 32 84 40 27 eb 38 94 68 72 4f |-..G.^2.@'.8.hrO|
000000d0 91 78 14 a7 b4 17 0b d3 38 0e 15 2b e1 98 bb ec |.x......8..+....|
000000e0 a6 32 f0 c9 56 0f ea e7 f5 a1 4d df ba dd b8 20 |.2..V.....M.... |
000000f0 bd c6 2f 44 9a 1c 8b e5 db 89 94 b5 d0 14 02 cc |../D............|
All done. Press any key to exit.
And what model exactly You have (CECHxx?/CECH-xxxx)? Maybe models correlating, or maybe not. Worth to note for us for analysis and other people from the future.
I have a CECH-2501B PS3 Slim and the HDD is a Toshiba 320GB
No, because some saves have COPY PROHIBITED parram set in PARAM.SFO, preventing copy them from/to USB in XMB. So You need use FTP Client, filemanager eg. build-in multiMAN, or PC (if You want next fight round with ufs.ko module (the one from script work but for unknown reason, compiler ignoring my ".config" so results end with read only ufs like original...) or setting up FreeBSD or NetBSD in VM on Linux (yes, "We need to go deeper")) to restore them. And of course do rebuild database from recovery menu or else none of content will appear in XMB.
I could try if needed to use a VM since I kinda like that stuff, but I would prefer to use Multiman if possible. Can I copy the save data from my USB to the PS3 HDD (freshly installed CFW) using Multiman? And I know there is this account thing, so I just got to test Apollo to test if I could use my Gran Turismo 5 save, and it worked after patching it (thanks god)
x is not sufficient. xxxx or xxx is (I reached once ~300 users created, not at once of course but count not resetting but incrementing).
So You should also copy not only saves but their damn cache. Because patching from scratch is around 8h for GT6 due to broken by design way those games doing it (patches in PKG are used only as delivery for patches which those games applying later).
So it will be more of a pain in the ass to get GT6 savedata working? What would I need to do
If You are feel that You have time for it, why not. None option in toolbox can do that, only to backup it but restoring You need to do manually, in which I can help.
Well, let's start fresh then, why not. I think I'll just buy a 480GB SSD or something like this to use. I know the PS3 doesn't have the latest SATA protocol but anyways, upgrade is upgrade, and droping a SSD is fine... Also, I did got some errors of denied access, so I would like some future help if possible
RIF files are the license files attached to your PSN account and console, via act.dat (that's why it's important to save it). They are unique, non-transferable files located in /dev_hdd0/home/0000000x/exdata folder.
RAF files are license activation files used to activate content (can be games, DLCs, themes, movies, etc.). Think of them as templates that are used to generate the RIF files attached to your console and PSN account.
If you happen to reinstall everything and create a new act.dat file, you can extract the RAF files from the RIF files using some tools in order to reactivate your content.
That's why RAF files are valuable as they can be used to activate virtually any content on any console for everyone. Thus, asking for RAF files is considered piracy.
From non-transferable files you mean between people or like, read/write blocked? And if I get those files in /dev_hdd0/home/0000000x/exdata folder to my new fresh install, when I get a content that need those then it will use them and will work? Like, if I get the files prepared for GT6, then try to play GT6, simple as that or I actually didn't understand shit? lol
If you happen to reinstall everything and create a new act.dat file, you can extract the RAF files from the RIF files using some tools in order to reactivate your content.
@Victor França
Thanks for the explanation of actions taken.
Ok, so for Yours CECH-2501 works:
dev_flash2: LBA 439816
dev_hdd0: LBA 524304
I made so many user accounts because many games not offering saving on "different slots" but one or just using autosave. So for me easier to make quick backups was just creating new user and copy save to it (it is not modified in any way) than copying to eg. USB. After reaching maximum number of users, I deleted oldest. That's why I have reached so high count number.
Saves backup is one thing. Cache (vel installation) is another. And I mentioning about it, to safe Your time. GT6 have broken by design patching system because for some reason, Sony don't follow their own rules here. Normally patches ready to use are delivered inside *.pkg. But in this specific game case, PKG contains patches which game applies by itself, I dunno, maybe xdelta or similar solution (to limiting package size I suppose?), and this taking ages. A lot longer than could user downloading patches if they would be in normal form. What is funny, it is possible to wait eg. 7h and near the end seeing an error and starting all of this again...
Do not use SSD. It is lottery which works fine and which doesn't. Cause is unknown.
You didn't change console and users so act.dat + *.rif's transplantation are fine, but after that, still, export them to *.raf on USB by Apollo to free Yourself from user and console tide up.
As I said in guide, You need operate on those partitions as root (let's call him the administrator, You will notice it by red ribbon on top in Nemo) because such permissions was set by CellOS. Normal limited user, don't have access to every place. If You are running Nemo as root and still cannot read some data from somewhere, it means that UFS2 is broken. Your best approach then, would be try fsck on FreeBSD, but that is very invasive and can make things worst instead fix anything. Details on earlier pages related to UserData partition expanding (use PS3 HDD Expander script, just ignore everything except how to expose not mounted mappers, install needed software (in commented section in script is how) and choose option to run FreeBSD, all the rest like qemu setup and images download is handled by script).
Non-transferable meaning between people. Think it this way: you reactivate your PS3 with your PSN account, and you generate a new act.dat file. This action will render your old savefiles and RIF files useless because the console "thinks" content belongs to another user.
Hi, could you help me? I followed your tutorial "HDD mounting and decryption on Linux"
but without success. I'm new to Linux. I use linux mint 19.2 and my ps3 is slim CECH2101A. I'm using a formatted hdd as a test, and I made a backup by copying the sectors of the hdd that was booted by windows MBR.
Cannot read requested amount of data.
failed to stat() /dev/mapper/ps3hdd
Device /dev/mapper/ps3hddl doesn't exist or access denied.
failed to stat() /dev/mapper/ps3vflash
mount: /home/mint/ps3/storage/hdd/dev_hdde: special device /dev/mapper/ps3hdd2 does not exist. mount: /home/mint/ps3/storage/hdd/dev hdd1: special device /dev/mapper/ps3hdd3 does not exist.
mount: /home/mint/ps3/storage/hdd/dev flash: special device /dev/mapper/ps3vflash2 does not exist.
mount: /home/mint/ps3/storage/hdd/dev flash2: special device /dev/mapper/ps3vflash3 does not exist.
mount: /home/mint/ps3/storage/hdd/dev_flash3: special device /dev/mapper/ps3vflash4 does not exist.
/usr/bin/crc32: Cannot open /tmp/ps3pt oos.bin: No such file or directory
xxd: /tmp/ps3pt oos.bin: No such file or directory
/home/mint/ps3/PS3 HDD Mounter (Read Only).sh: line 129: printf: 0x: invalid hex number mount: /home/mint/ps3/storage/hdd/dev_hdd2: special device /dev/loop90p1 does not exist.
NAME
SIZE FSTYPE MOUNTPOINT
Loop90 160040802816
NAME
SIZE
Loop91 4194304
NAME
SIZE FSTYPE MOUNTPOINT
160040802816
sdc
Lps3hdd-bs 160040802816
@RyanPPss
You cannot link image to place on Your computer. Upload it somewhere and paste link to the post (if You will be unable to, cut https/www stuff from it) or attach it to the post.
Not sure if I understood You well in post no.336. So few control questions on start:
1. Do You have EID Root Key from this console and did You calculate needed keys for it as in the tutorial (first pasted line telling us that disk mapper with decrypted disk hasn't been created; all the rest errors are consequence of that)?
2. Is this HDD which was formatted by PS3?
3. If yes, does this HDD was later: formatted (quick format option) or initialized by Windows?
I use linux mint 19.2 and my ps3 is slim CECH2101A
Mint 19.2 is very old now, I suggest to switch to 21 or 21.1 (You don't need to install it of course).
For Your model, all options in Keygen and Mounter must be for Slims.
I have the root key. the HDD was formatted on PS3 4.90. At first my ps3 HDD suffered windows MBR initialization, I followed your tutorial "Fixing Windows disk initalization" but in the end the ps3 asked to update and froze at 98%. I still have the ps3 160gb HDD sectors saved in a .bin file. I will try Linux 21 to read HDDps3
Upload it somewhere and paste link to the post (if You will be unable to, cut https/www stuff from it) or attach it to the post.
