You might want to try HDL Salvage Tools as they were designed to help salvage/repair problems like this.
Printable View
You might want to try HDL Salvage Tools as they were designed to help salvage/repair problems like this.
I'm sorry this happened, but you really should be more careful about such commands.
I have made it a point to always mention the fact that it does format the entire HDD, whenever I have mentioned the HddManager "Format" command at all, so I am very certain that nothing I ever wrote could have misled you into thinking of it as a PC-style single-partition format, which does not exist for a PS2 HDD. On the PS2 such single-partition formatting is implicit in the act of creating new partitions, which is done by the separate "Create" command in the uLE HddManager.
Reformatting a partition without creating it is simply not possible with the PS2 HDD system. (It would have to be simulated by low-level sector writes in a custom program.) So the correct action for such cases is to remove the misbehaving partition and then create it anew.
There is one, although minimal in size.Quote:
I wished there would prompt a requester telling me that this command will format the entire HDD instead of the selected partition;
When in the HddManager you open the R1 menu and give the "Format" command you get a popup dialog box containing this:
This clearly states that it is the HDD which is about to be formatted if you proceedCode:Format HDD ?
>OK CANCEL
and not just some specific partition, since no such partition is mentioned.
That is the point where you should have canceled the operation, instead of proceeding.
I'm afraid I don't know any sure way to help you. Most of the various methods others have suggested for recovering original content have a common flaw: For perfect success they need all sectors that were in use for such content before the formatting to remain free and unaltered after it, which is not likely to be the case.Quote:
That was a long story for today, I hope you people didn't got bored because of it. Thanks in advance for any help, if any. :rolleyes:
Best regards: dlanor
Of course you didn't misled me, it's just my fault I didn't read through the forums or the uLE readme file at all. I'm just one of those guys who kill first and asks questions later. :D
I didn't know that, I thought it's like in PC's. :(Quote:
Reformatting a partition without creating it is simply not possible with the PS2 HDD system. (It would have to be simulated by low-level sector writes in a custom program.) So the correct action for such cases is to remove the misbehaving partition and then create it anew.
You're right, but you know, sometimes people understand what they want to understand, and not what it's meant to be. :)Quote:
There is one, although minimal in size.
When in the HddManager you open the R1 menu and give the "Format" command you get a popup dialog box containing this:
This clearly states that it is the HDD which is about to be formatted if you proceedCode:Format HDD ?
>OK CANCEL
and not just some specific partition, since no such partition is mentioned.
That is the point where you should have canceled the operation, instead of proceeding.
Thanks for help to all you guys. I've only tried WinHiip. It rescued the HDL games only, not the "__common" directory or partition (whatever). So all my MC backups are gone. :( All other files didn't mean much, they just need to be copied over again. Though all the PS2 HDD directories are still in their default sizes and I can't alter them. I would like to make them bigger again. Is there a way? I even don't remember how I made them bigger a few years ago. :DQuote:
I'm afraid I don't know any sure way to help you. Most of the various methods others have suggested for recovering original content have a common flaw: For perfect success they need all sectors that were in use for such content before the formatting to remain free and unaltered after it, which is not likely to be the case.
Best regards: dlanor
I don't understand why you would want to make the Sony 'standard' partitions larger, when no homebrew software is intended to use them, at all... (Except possibly for Dev1 use of "__boot")
Since you have a 160GB HDD you should not be able to use Sony software for the PS2 HDD, and that is the only software I know of which can use those partitions for their originally intended purpose.
The Sony HDD drivers have a limit of 128 binary GB (1GB == 2^30 Bytes) which is appx 137 decimal GB (1GB == 10^9 Bytes), so they do not work right with a 160 GB HDD (if they work at all, they are likely to corrupt a large disk).
Like you, I and some others still use the "__common" partition for MC backups (as does Sony software), but most of the others are just unused, so there would be no advantage in making them bigger.
You are well advised to keep homebrew applications and their data in user-type partitions, such as uLE can create for you, as this will allow you more control in HddManager than the other partition types allow. The exception is with applications that create their own partitions, as those partitions are of course what you should then use.
Best regards: dlanor
I use __common for all my homebrew, perhaps I should stop doing that?
I see no real problem with doing so.
It is only if you use the Sony HDD setup and their HDD browser etc that anything you do can come in conflict with the original purpose of their HDD partitions. But if you don't use their HDD software then you (like me) are immune to any such conflicts.
Except of course if some new software starts to use that folder for some new purpose...
Best regards: dlanor
@CaptainHIT;
Sorry to hear about that. I know you're not the only one to suffer a similar fate. Sometime after the development of HDDmanager, another bloke did the same thing. Some users think that they are formatting a single selected partition when it in actuality it formats the entire drive.
I really don't think that will help completely, as some people just use every OK button in sight, or keep hitting the Enter key on keyboard, thinking (if at all) that this gets the job done faster. And those people will get this kind of problem anyway. There is no way to guard against that kind of usage.
I might still consider adding an extra warning to the "Format" command in future, just to end the discussion, but it is not the kind of thing that merits a full release for that single change.
So it will have to wait until we make a new release to include other changes too.
Best regards: dlanor
Oh, of course, no amount of coding in warnings will avoid that. :D
Also agree that it certainly doesn't merit a release just for it's inclusion.
BTW, it might be enough to just add the warning to the "Format" prompt, don't really see a need for having to hit OK again? Or maybe it should, to be real sure, since it's pretty final...