Mybook studio raid 0, empty after installing Mavericks

Hi David I try but in my case it renaming everything.

I Use Iskysoft Data Recovery and i find all my folders and file with original name.

I can try your self.

Emi

@davidlach: I couldn't recovery my HFS+ partition using the Kroll/Ontrack Tool. But Prosoft Data Rescue 3 recovered the whole partition (including folder structures and files names). You probably don't need to buy any more storage just to do the scanning of the drive (but probably afterwards).

@ altery: seems like very good news for you! Other people in this thread have had Datarescue 3 being unable to retrieve folder structure and file names...

And in my experience, DR3 really does need newly formatted storage ( as a target disk) at least the size of the storage to be scanned before starting the scan!

➕Recent reports from a computer technician regarding a WD reproduced repartitioning (more than once) involves - "an obvious fault in the node structure where fsck was commanded to diagnose the HFS (OSX ext. journl.) journaled file system" on the WD drive @ corruption.

The very same node structure where the cataloging system that keeps track of where everything was, was then kaput.

If someone could test same: there may be help by the use Single User Mode and fsck to repair a disk after a repartitioning

http://osxdaily.com/2013/08/07/how-to-repair-a-mac-disk-with-fsck-from-single-us er-mode/

If the above reproduced effect is valid and complete (I am sure as he reported it is valid, if not complete) then EITHER Mac OSX is commanding or WD software is commanding the external HD @ which repartitioning is occurring (what the combination is, who is yet to know)

fsck -- filesystem consistency check and interactive repair DESCRIPTION
The first form of fsck preens a standard set of filesystems or the specified filesystems.

It is normally used in the script /etc/rc during automatic reboot. Here fsck reads the filesystem descriptor
table (using getfsent(3)) to determine which filesystems to check. Only partitions that have ``rw,''
``rq'' or ``ro'' as options, and that have non-zero pass number are checked. Filesystems with pass
number 1 (normally just the root filesystem) are checked one at a time. When pass 1 completes, all
remaining filesystems are checked, running one process per disk drive. The disk drive containing each
filesystem is inferred from the shortest prefix of the device name that ends in one or more digits; the
remaining characters are assumed to be the partition designator. In preening mode, filesystems that
are marked clean are skipped. Filesystems are marked clean when they are unmounted, when they have
been mounted read-only, or when fsck runs on them successfully.

It should be noted that fsck is now essentially a wrapper that invokes other fsck_XXX utilities as
needed. Currently, fsck can invoke fsck_hfs, fsck_msdos, fsck_exfat, and fsck_udf. If this underlying
process that fsck invokes encounters serious inconsistencies or the filesystem type is not one of the
above, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected inconsistency

one or more lines will be printed identifying the filesystem on which the correction will take place, and the nature of the correction.

If sent a QUIT signal, fsck will finish the filesystem checks, then exit with an abnormal return status
that causes an automatic reboot to fail. This is useful when you want to finish the filesystem checks
during an automatic reboot, but do not want the machine to come up multiuser after the checks complete.

Without the -p option, fsck audits and interactively repairs inconsistent conditions for filesystems.
It should be noted that some of the corrective actions which are not correctable under the -p option
will result in some loss of data. The amount and severity of data lost may be determined from the
diagnostic output. If the operator does not have write permission on the filesystem fsck will default
to a -n action.

The following flags are interpreted by fsck and passed along to the underlying tool that it spawns.

-f Force fsck to check `clean' filesystems when preening.

-l Limit the number of parallel checks to the number specified in the following argument. By
default, the limit is the number of disks, running one process per disk. If a smaller
limit is given, the disks are checked round-robin, one filesystem at a time.

-p "Preen" mode, described above.

-q Do a quick check to determine if the filesystem was unmounted cleanly.

-y Assume a yes response to all questions asked by fsck; this should be used with great caution

as this is a free license to continue after essentially unlimited trouble has been encountered.

-n Assume a no response to all questions asked by fsck except for `CONTINUE?', which is
assumed to be affirmative; do not open the filesystem for writing.

Peace 😊

No...this did NOT fix anything. any other ideas?

WD has announsed a driver update; for your consideration:

http://community.wd.com/t5/News-Announcements/New-Release-WD-Drive-Manager-for-M ac-Version-3-1-0-11-25-13/m-p/628437#M387

Cheers

thanks for your message however...NO this did not fix anything.

altery Glad that worked for you! I have been running Prosoft Data Rescue 3 on my affected drive (a non WD enclosure configured to hardware RAID 5) and have not been able to recover the lost partitions directly or the original file folder/file stucture. I been able to recover some but not all files. (Luckily I have backups of most of it anyway). Just a general question for anyone here more tech savvy than me - would the fact that the enclosure I have is hardware RAID rather than software RAID and the fact that it's RAID 5 configuration mean it's more difficult (if not impossible) to recover the lost partitions and folder/file structure? I seem remember reading somewhere that RAID 5 configurations can be problematic in the case of recovering lost data in an event such as this WD repartitioning/reformatting fiasco.

Tired and upset of WD's inaction to help with resolution of the situation, I tried to do data recovery on my studio II HDD, hold and behold, I managed to do my recovery from that formatted HDD, all 600GB of photos, raw files or not. Strangely speaking, some files have dates in them, some doesn't...but I guess given how disasterous it has been so far, having the files back is a good thing, many more hours need to put it to rebuild my lightroom library.

And may I say this, the new software released by WD doesn't fix the issue, although they explicitly stated that it fixes the issue. They might have fixed the vulnerability issue but **bleep** no, it doesn't alleviate any of the data loss issue. I wish you folks all the best of luck and may the force be with you.

I asume the single user mode won't work on a disk that has been put back to the empty partition 'MyBook'?

I also found someone telling he 'did it' with migration assistant, but I asume that will only work with corupted Time machine's?

Would there be any chance some genius comes up with a file structure repairing software within a few weeks. Or is the file structure permanently damaged?

Recovering just the files won't do the trick for me since I've lost a few days of work video editing files witch ofc need the references. Stupid as I was, I did not backup those last few days.

Something that might be considered strange though, I thought I allready deleted the WD software a year ago. I heard about the problem but since I allready deleted it I didn't do anything about it. I was allready running Mavericks since it's release date and my drive only got wiped last monday...

The only reason I could think of was that I connected another WD drive with an autorun in it's main folder last weekend. If this caused it, then it is actually no longer safe to connect any new drive without first installing the updated WD software.

darthfroggie

And may I say this, the new software released by WD doesn't fix the issue

Bad news, the new WD software and firmware are causing serious issues from reports.

😟

meurnix wrote:

I asume the single user mode won't work on a disk that has been put back to the empty partition 'MyBook'?

I also found someone telling he 'did it' with migration assistant, but I asume that will only work with corupted Time machine's?

Would there be any chance some genius comes up with a file structure repairing software within a few weeks. Or is the file structure permanently damaged?

Recovering just the files won't do the trick for me since I've lost a few days of work video editing files witch ofc need the references. Stupid as I was, I did not backup those last few days.

Single user mode is to run an fsck, a file system check. The trouble you have is that the file system on disk appears to have no files, you want the file system that existed before the corruption. Personally I don't think an fsck will help, but there are so many different types of potential damage. There are also different ways to try to recover files.

The 'genuises' already have made recovery software, you either need to select the right tool that will repair the disk catalog & partition or you need to send it off to specialists who know how to do this.

Disk Drill has been mentioned as working but you will need to select the correct options, otherwise you simply get 'carved files' e.g no actual folder structure, but the files will contain the same data, just named randomly etc.

The 'folder structure' is stored in the disk catalog, which is a feature of the partition.

In Drill Disk use the popup on the recover button to select 'Scan for lost HFS partition'.

Others have had success with Tech Tool Pro IIRC. Just keep going back through this thread seeing what worked for others.

@Drew Reece. Thanks for your reaction. A few questions. In Disk Drill Pro I can choose search for lost partitions but there's no popup or extra options... And I don't seem to find the things you mention. if I just scan for lost partition it does find some EFI partition which was also shown by the finder when the problem first acured but nothing more...

Is a Deep Scan of any use? I'm now running a deep scan in Prosoft Data Rescue 3. But the deepscans are probably only usefull to get single files?

@Altery, can you specify which steps you took in Prosoft Data Rescue 3 to get everything incl file structures back? I'm now running a deep scan which will take around 36hours. Is it that you've done or should I do something else?

@ Plotinus Veritas what are the issues with the new WD software and firmware?