From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Subject: Switching from (deprecated) IDE driver -> SATA (PATA support)
Date: Sun, 25 Jan 2009 05:56:32 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.0901250553430.2441@p34.internal.lan> (raw)
When switching (removing IDE support) in favor of the new PATA support
under the SATA menu, is there any best practice/or method of knowing what
the new root hdd will be upon reboot?
Example:
If I have 10 sata disks and 2 IDE disks on various cards/controllers, how
do I know /dev/hda will become /dev/sda? In one test on a system I have
here, /dev/hda became /dev/sdb2 after reboot, not an issue if the box is
local, but if the box is remote, how do you cope with this? I ask now
because some IDE drivers have been removed (nvidia I believe? in 2.6.28)
and I cannot upgrade the kernel anymore unless I move to the
PATA-supported SATA driver, but I have no idea what the root disk will be
after a reboot and there is a high probability it will not come back after
a reboot..
Justin.
next reply other threads:[~2009-01-25 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 10:56 Justin Piszcz [this message]
2009-01-25 11:07 ` Alan Cox
2009-01-25 12:09 ` Justin Piszcz
2009-01-25 12:15 ` Justin Piszcz
2009-01-25 12:28 ` Justin Piszcz
2009-01-25 12:41 ` Justin Piszcz
2009-01-25 12:55 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution) Justin Piszcz
2009-01-25 13:08 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution (scratch that)) Justin Piszcz
2009-01-25 13:15 ` Michael Tokarev
2009-01-25 15:45 ` Switching from (deprecated) IDE driver -> SATA (PATA support) Eric Sandeen
[not found] ` <alpine.DEB.1.10.0901250726530.10805__44823.8515914001$1232890466$gmane$org@p34.internal.lan>
2009-01-25 21:13 ` Bill Davidsen
2009-01-25 21:14 ` Justin Piszcz
2009-01-29 23:44 ` Bill Davidsen
2009-01-26 22:02 ` Lennart Sorensen
2009-01-26 23:36 ` Sergei Shtylyov
2009-01-25 18:04 ` Mark Lord
2009-01-25 19:27 ` Bartlomiej Zolnierkiewicz
2009-01-25 21:13 ` Justin Piszcz
2009-01-25 21:39 ` Bartlomiej Zolnierkiewicz
2009-01-29 23:50 ` Bill Davidsen
2009-01-30 3:38 ` david
2009-01-30 10:21 ` Alan Cox
2009-01-30 10:11 ` Alan Cox
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=alpine.DEB.1.10.0901250553430.2441@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--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
all inboxes | Powered by JetHome®