From: Francisco Perez <fperez@albrookdata.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Upgrading to Raid
Date: Fri, 02 Sep 2005 20:24:44 -0500 [thread overview]
Message-ID: <4318FB5C.8070307@albrookdata.com> (raw)
In-Reply-To: <4318E87F.1070802@gmx.at>
Correct me if I am wrong since I have yet to have to deal with restoring
failed disk in an array, but in a hardware raid, with my card I would
just enter the card's bios after rebooting and then restore the new
replacement drive from the secondary image (remember I am using raid 10
with 4 disks.) Is there something I'm forgetting?
Frank
Florian D. wrote:
> because there are so many people praising software-raid, you´ll probably
> find this story interesting, which happened to me yesterday (my system
> is -for the biggest part- on a raid5 partition):
>
> while I emerged koffice, played some mp3´s and let matlab calculate sth.
> in the background, I tried to start a windows program with wine. I
> really shouldn´t do that, because Linux crashed and after a hard reboot
> it could not boot any more. It stopped during the execution of the
> init-scripts and i was not able to do anything, thus: 2nd hard reboot. I
> have another(old) gentoo installation on my computer and this time I
> booted into that one. By accident I realized that one of the discs of my
> raid system has been marked as faulty and it was syncing in the
> background. /proc/mdstat said that it would need 20min or so, but after
> 15min it said 200min! After another 10min it was sth >300min (and a lot
> of IO errors). So I rebooted again, this time it synced successfully in
> 12min. Then it was possible to boot and work with my normal system
> without any further difficulties or IO errors.
>
> Summing up, I can say:
>
> + I successfully wrecked my file system, but software raid was able to
> repair it
> - without a second Linux-installation on another partition, you´re lost
> - restoring of a faulty raid disk is not reliable
> - it seems that it is not possible to boot or work with a system, whose
> system disk is being restored at the same time (Linux-2.6.12.6)
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-03 1:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 3:46 [gentoo-amd64] Upgrading to Raid scotthathcock
2005-09-01 3:59 ` Nuitari
2005-09-01 4:18 ` Chris S
2005-09-01 4:34 ` Chris S
2005-09-01 14:54 ` Billy Holmes
2005-09-01 5:29 ` Kyle Liddell
2005-09-01 5:36 ` Francisco Perez
2005-09-02 10:02 ` Joshua Hoblitt
2005-09-02 13:22 ` Matt Randolph
2005-09-02 19:56 ` Joshua Hoblitt
2005-09-03 9:54 ` Florian D.
2005-09-03 20:45 ` Homer Parker
2005-09-04 17:16 ` Florian D.
2005-09-03 0:04 ` Florian D.
2005-09-03 1:24 ` Francisco Perez [this message]
2005-09-03 3:18 ` Nuitari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4318FB5C.8070307@albrookdata.com \
--to=fperez@albrookdata.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox