News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Raid 5 Partition Setting for Data Recovery on Drivestation HD-S4-TSU2/R5

Started by GCKRULL, July 12, 2009, 10:36:35 AM

Previous topic - Next topic

GCKRULL

   

Looks like my Drivestation's MBT just took too many errors and has been corrupted during a Mass Copy of data.   Lost about 2 TB of data and over 300 hours of work.   Spent 100 dollars on a program to recover Raid 5 drives, looks like the program was able to recover 100gb of data but its all corrupted.   Have another program  (Test Trail) which requires the Raid 5 settings of the Drivestation,  anyone know what these setting are - paritylayout - right/left asyncronous/syncronous.   The Stripe Block Size and so forth.    

 

Figured Raid 5 would have been my best backup solution.....should have stuck with Raid 1.   So surprised what issues Raid 5 has after looking it up!

 

Thanks in advance!


Colin137

Sorry for your troubles, GCKRULL. I'll check into those settings for you. RAID isn't a substitute for backups, and if the issue was data corruption, it could have happened on a RAID1 array as well. RAID only protects against single hard disk failure.

 

You may want to consider contacting a data recovery company. We suggest Drivesavers  ( http://www.drivesaversdatarecovery.com/ ).

 

I'm not familiar with that model number... could you post the full model number from the back of the device? Also, where was this device purchased?

Message Edited by Colin137 on 07-13-2009 10:45 PM

Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 129 (show)
Files included: 35 - 1354KB. (show)
Memory used: 999KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]