I have a lspro duo with a bad drive. How do we know what drive is bad (in raid 1 configuration)
Remove one of the drives! As you say, it is in RAID1 so it should be able to boot up with just 1 HDD!
I do get the replace with 1 HDD, what I am asking is how does one know
the exact drive that is bad.
- raid1 with hdd1 hdd2
- raid1 get a failure on one of the hdd, lspro shutsdown
- at reboot, lspro works in 1 hdd mode,
at that point how dow I tell what drive is bad
Hello,
have you succeed in changing the bad drive ?
I am about to buy a ls pro duo but i don't if it's possbile to change the drive broken ?
Is anybody have a tutorial to follow ?
Thanks,
Caboche
Yes, I was able to rebuild my array. I bought another sumsung drive (500Gb).
I had to do a full rebuild because I did a manip error. When my array first failed, rather
than simply buying a new drive (I could not find any help on that), I tried to do a
resync, when it failed, I switched the drives.... really bad move.... at that point I
think that the array lost track of the good versus bad drive (I think that the status
is stored in flash and not on the medium, so switching drive arround is a no no)
so at that point I just did a full rebuild with the new drive and I am now back
in business. So as soon as I can get an asnwer on how one know what drive is bad,
then rebuilding is as easy as
. raid1 fails, ls pro shuts down
. reboot, read on the drive management screen which drive is the bad drive
I think that this can be infered by looking the drive that has the check mark,
this is the targeted rebuild drive (source should be greyed out)
. shutdown, take the bad drive out, put the new drive in
(do not move drive arround)
. reboot and resync array.
Thanks for your answer.
I'm sorry but my english is not perfect. I'm french.
I don't understand all what you said.
I want to no if it's possible to change one or two drives of the linkstation pro duo ?
I have read somewhere that part the boot loader is on one of the hd.
Is it possible to make work a LS PRO DUO from scratch when the hd and particulary the hd where is the boot loader are dead.
Thanks for your lignts
Caboche
I am not sure one can recover when both drive go bad. If someone
can point us to how to recover from 2 drive simultaneous failures
that would be great.
for a one drive failure, recovery is possible. I have found that
as long as drive 0 has a an image on it, then the pro station is
bootable. I am not sure if the image needs to be on drive 0 or if it will
boot if the image is only on drive 1.
Thanks for these precisions ?
Paul (the moderator) ca you give us if its possible to recover from 2 drive simultaneous failures or with drive 0 crashed ?
Thanks for your help.
Caboche
If 2 drives crash you lose the RAID and hense your data, as far as im aware there is nothing you can do yourself although a data recovery ajent might be able to get the data off for you.
RAID 5 can only handle one drive going out at a time.
there is 3 different question here.
1. when in a raid1 configuration, a drive goes bad, how do we know
the drive that went bad. (what screen, text ?)
2. if in a raid1 configuration, drive 0 goes bad, can one rebuild the
raid1 by replacing driver 0, or does one need to move the good
drive 1 to drive 0 (physically moving the drive) and then add a new
drive for rebuild
3. if one has to replace the 2 drives at once, is there a way to re-initialize
one of the drive with the boot image (not the data) so we can boot the lspro
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: 95 (
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_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]