From: Joe Bormolini <lordjoe@bigfoot.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] two suggestions (hpt370 woes)
Date: Tue Sep 4 23:43:01 2001 [thread overview]
Message-ID: <20010904224209.627d55b8.lordjoe@bigfoot.com> (raw)
In-Reply-To: <000501c135ca$2c54b7a0$12710404@black>
On Tue, 4 Sep 2001 22:18:17 -0700
"Darren Twa" <twa@headthirst.com> wrote:
> 2. This is more important. My system is one that has an onboard
Highpoint
> RAID controller (Abit KT7-RAID). In the install when you must chroot
after
> mounting the cd image I was unable to follow the instructions further
> because there were not devices for hard drives e,f,g,h only a,b,c,d. To
> install I was forced to move the drive I wanted to install to the other
> controller because I didn't know how to create the necessary devices at
that
> point. This just made the disk disappear and I had to install LILO
because
> Grub was totally lost.
>
> Thanks for Gentoo. It looks like the Linux I've been looking for.
>
> Darren
>
Ohhhhhhh boy :p I have a highpoint 370 controller on my mobo (epox 8k7a+)
and the RAID support is only present in the alan cox kernel releases. It
took some time before I figured out how to get the kernel I compiled to
boot the root image off the disk (lol... hint "rdev" and linuxdoc.org). So
when I did get it booting properly, I mounted devfs and hurrah there was
/dev/ataraid/disc0. The only way I got grub to install was from a bootdisk
- installing from linux seemed to mess up my array... YMMV :p I'm
proud to say that everything is running quite nicely now =) good luck!
Also keep in mind any /dev/hd(e,f,g,whatever) will NOT be the raid array
and WILL screw stuff up if you try to format it, write to it, etc.
--lordjoe
prev parent reply other threads:[~2001-09-05 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 23:19 [gentoo-dev] two suggestions Darren Twa
2001-09-04 23:43 ` Joe Bormolini [this message]
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=20010904224209.627d55b8.lordjoe@bigfoot.com \
--to=lordjoe@bigfoot.com \
--cc=gentoo-dev@cvs.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