From: Hans Kristian Rosbach <hk@isphuset.no>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Kernel upgrade, need workaround for libata detection
Date: Mon, 18 Oct 2004 12:30:46 +0200 [thread overview]
Message-ID: <1098095446.21895.129.camel@linux.local> (raw)
I forget the kernel numbers (around 2.6.5 I think), but those
are not important in this matter.
I have installed linux on a few computers with an old 2.6 kernel,
they both have sata disks recogniced as hda and hdc. But a problem
arises when I try to upgrade to a newer kernel (FC2 kernels), the
disks are then sda and sdb.
Now this is fine with me, but the big problem here is that these
disks are in a raid. So I need to find a solution for booting and
finding root on these disks.
I'm thinking about the following solutions:
1. Is there any kernel parameter to disable libata, so that it
will revert to good old hda and hdc?
2. Can I reconfigure the raid to use hda,hdc,sda,sdb even if only
hda and hdc is available while reconfiguring?
Will it work correctly when I reboot and they are sda and sdb
instead? Any hints as to how to do this safely?
3. Any way to make the kernel know that hda==sda ?
I apologise for my bad wording today, It's not a good day (flu).
-HK
reply other threads:[~2004-10-18 10:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1098095446.21895.129.camel@linux.local \
--to=hk@isphuset.no \
--cc=linux-kernel@vger.kernel.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