We had a power cut today and when I powered up the RAID 5 drive the following came up:
Raid Error E13 Array1 Error
HD Error E23 HD3 is Faulty
Operational Mode I12 Degrade Mode
Can I have some advice how to resolve this please?
Replace the HDD and restructure the array
Question...
I have 4 x 500GB drives at the moment, can I replace the dead drive with a 1TB HD restructure the array and then replace the other 500GB HD restructuring the array as I do one drive swap at a time.
There is virtually no difference in price between 500Gb and 1Tb drives so It would be a good opportunity to upgrade the drive storage.
If you replace the 500GB drive with a 1 TB and resynch it into the array it will scale the drive down to 500 GB. I would just replace all of the drives and TFTP the firmware back on to it.
I have a similar problem on my Terastation (HS-DH0.0TGL/R5).
Raid Error E13 Array 1 Error
Operational Mode I12 Degrade Mode
HD1 Error E23 HD1 is faulty
Several months ago, I replaced a drive in this Terastation and everything went well. At that time, I purchased two new drives, keeping one as a spare. These drives were IDENTICAL to the drives installed on the Terastation (Samsung Model HD501LJ, 500Gb).
I replaced HD1 with the remaining new drive I had, but am still getting the same messages. I've done some reseach on other users with the same experience and many are now saying that Buffalo Technologies is suggesting it's a faulty raid controller. If this is the case, is it possible to change the raid controller? I am about to order several Terastation Pro II units for my business, but am alarmed about how many instances of raid controller failures I've seen. I would just like to know if there is any recourse in the event the HDs are not the problem.
Thanks!
I have been living with this error (E13) for quite some time and would like to have it resolved. I have replaced the faulty drive, re-structured the array, and reset to factory defaults. Nont of these seem to work, and I am in an endless loop of resetting.
I REALLY don't want to wipe the drive and reload my data.
Does anyone have a solution?
PS: TeraStation Pro iSCSI TS-IGL/R5
After you did that have you tried to Reinit the unit through the user interface?
Log into the Web Admin then go to Maintenance>initialization>restore.
The terastation pro II hasn't been manufactured in nearly a decade so I doubt its them that you are ordering.
Either way the RAID controller is software based, its not a hardware component.
Browser ID: smf
(is_webkit)
Templates: 1:
Printpage (default).
Sub templates: 4:
init,
print_above,
main,
print_below.
Language files: 1:
index+Modifications.english (default).
Style sheets: 0:
.
Hooks called: 80 (
showintegrate_autoload, integrate_pre_load, integrate_load_session, integrate_verify_user, integrate_pre_load_theme, integrate_user_info, integrate_load_board, integrate_board_info, integrate_pre_load_theme, integrate_allowed_to_general, integrate_simple_actions, integrate_allowed_to_general, integrate_load_theme, integrate_pre_log_stats, integrate_actions, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_codes, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_word_censor, integrate_word_censor, integrate_pre_parsebbc, integrate_bbc_print, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_pre_parsebbc, integrate_smileys, integrate_smileys, integrate_post_parsebbc, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general, integrate_menu_buttons, integrate_current_action, integrate_theme_context, integrate_allowed_to_general, integrate_allowed_to_general, integrate_allowed_to_general)
Files included: 27 - 1055KB. (
show./index.php, ./Settings.php, (Cache)/db_last_error.php, (Sources)/QueryString.php, (Sources)/Subs.php, (Sources)/Subs-Auth.php, (Sources)/Errors.php, (Sources)/Load.php, (Sources)/Security.php, (Sources)/Subs-Compat.php, (Sources)/Subs-Db-mysql.php, (Sources)/Cache/CacheApi.php, (Sources)/Cache/CacheApiInterface.php, (Sources)/StopForumSpam.php, (Sources)/Subs-Charset.php, (Sources)/Unicode/Metadata.php, (Sources)/Unicode/QuickCheck.php, (Sources)/Session.php, (Sources)/Logging.php, (Sources)/Class-BrowserDetect.php, (Sources)/Unicode/RegularExpressions.php, (Sources)/Unicode/CaseUpper.php, (Sources)/Unicode/CaseTitle.php, (Current Theme)/languages/index.english.php, (Current Theme)/languages/Modifications.english.php, (Sources)/Printpage.php, (Current Theme)/Printpage.template.php)
Memory used: 733KB.
Tokens:
post-login.
Queries used: 10.
[Show Queries]