From: "Mathias Burén" <mathias.buren@gmail.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: "Keld Jørn Simonsen" <keld@keldix.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Performance question, RAID5
Date: Sun, 30 Jan 2011 19:46:46 +0000 [thread overview]
Message-ID: <AANLkTinnc9V8bZWaF+8JEXgAzxUVieiaiH4Fad5FERjJ@mail.gmail.com> (raw)
In-Reply-To: <4D45BF84.7030706@hardwarefreak.com>
On 30 January 2011 19:44, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> Mathias Burén put forth on 1/30/2011 6:12 AM:
>
>> Thanks to mdadm, and /dev/disks/by-label/ I should be fine with just
>> swapping the SATA cables around actually, without having to change any
>> configs. I'll try that later on and let you know if it affects
>> performance anything. Good catch!
>
> Be sure to change the mobo and PCIe card BIOS boot order after moving the SSD
> cable to the PCIe card or the machine won't boot. Also, before swapping cables,
> make sure you have the PCIe card chipset driver built into your kernel or
> properly built into your initrd image. If not you still won't boot.
>
> --
> Stan
>
I forgot to mention it, but I already swapped the cables. I had to
change a few things (reinstall GRUB, change menu.lst) but otherwise I
was OK. Strange thing is that my mainboard doesn't seem to want to
boot off a drive that's connected to the Highpoint controller. Just
sits there. However, using GRUB from a USB stick enables me to just do
root (hd2,0), then chainload + and load the GRUB of the SSD. Not
elegant, but it works (for now). Will investigate more later...
// Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-30 19:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 22:48 Performance question, RAID5 Mathias Burén
2011-01-29 22:53 ` Roman Mamedov
2011-01-29 23:44 ` Mathias Burén
2011-01-29 23:57 ` Roman Mamedov
2011-01-30 0:15 ` Stan Hoeppner
2011-01-30 0:33 ` Mathias Burén
2011-01-30 0:27 ` Mathias Burén
2011-01-30 1:52 ` Keld Jørn Simonsen
2011-01-30 1:54 ` Mathias Burén
2011-01-30 5:56 ` Keld Jørn Simonsen
2011-01-30 12:12 ` Mathias Burén
2011-01-30 19:44 ` Stan Hoeppner
2011-01-30 19:46 ` Mathias Burén [this message]
2011-02-01 11:37 ` John Robinson
2011-02-01 13:53 ` Roberto Spadim
2011-02-01 14:02 ` Mathias Burén
2011-02-01 14:32 ` Roberto Spadim
2011-01-29 23:26 ` CoolCold
2011-01-30 0:18 ` Mathias Burén
2011-01-30 4:44 ` Roman Mamedov
2011-01-30 12:09 ` Mathias Burén
2011-01-30 12:15 ` Roman Mamedov
2011-01-30 19:41 ` Mathias Burén
2011-01-30 19:54 ` Roman Mamedov
2011-01-30 19:58 ` Mathias Burén
2011-01-30 20:03 ` Stan Hoeppner
2011-01-30 21:43 ` Mathias Burén
2011-01-31 3:39 ` Stan Hoeppner
2011-01-31 3:54 ` Roberto Spadim
2011-01-31 8:52 ` Keld Jørn Simonsen
2011-01-31 9:37 ` Mathias Burén
2011-01-31 13:11 ` Keld Jørn Simonsen
2011-01-31 14:43 ` Roberto Spadim
2011-01-31 18:44 ` Keld Jørn Simonsen
2011-01-31 20:42 ` NeilBrown
2011-01-31 21:41 ` Keld Jørn Simonsen
2011-01-31 21:43 ` Roberto Spadim
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=AANLkTinnc9V8bZWaF+8JEXgAzxUVieiaiH4Fad5FERjJ@mail.gmail.com \
--to=mathias.buren@gmail.com \
--cc=keld@keldix.com \
--cc=linux-raid@vger.kernel.org \
--cc=stan@hardwarefreak.com \
/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;
as well as URLs for NNTP newsgroup(s).