From: "David Pyke" <dpyke@researchdimensions.com>
To: <gentoo-amd64@lists.gentoo.org>
Subject: RE: [gentoo-amd64] Re: Drive asignments for sata drives
Date: Tue, 13 Mar 2007 16:04:31 -0400 [thread overview]
Message-ID: <008c01c765aa$d0b09e70$6f0a0a0a@RDLaptop3> (raw)
In-Reply-To: <20070313195906.GH29939@v.igoro.us>
It may be that your SATA drive has moved from sda to hda. Trying changing it
in your fstab and see if it works. (boot using the live CD and mount the
drive, etc.)
-----Original Message-----
From: dustin@v.igoro.us [mailto:dustin@v.igoro.us]
Sent: Tuesday, March 13, 2007 3:59 PM
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Drive asignments for sata drives
On Tue, Mar 13, 2007 at 08:53:13PM +0100, ducasse.isidore@gmail.com wrote:
> Just to mention, I did activate the SCSI drivers for my hd in the new path
in menuconfig manually.
>
> By the way, while trying latest 2.6.20 kernel, my machine couldn't mount
my SCSI drive as sda2 anymore...
> I swear I didn't plug/unplug any device in the meanwhile.
>
> Got any clue? Is there a magic option to get in a shell and check with
genkernel made kernels for the correct device node? Or a udev initramfs with
just a prompt available?
It's always frustrating to diagnose things like that, without being able to
effectively pause and restart the kernel messages. Booting with a serial
console is, I think, the preferred solution.
One thing you could do is put in an IDE drive and put a basic root partition
on it -- at least enough to boot into a recovery shell. Then you can look
around at dmesg, etc.
It's not elegant, but it's an idea.
Dustin
--
gentoo-amd64@gentoo.org mailing list
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-03-13 20:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 16:39 [gentoo-amd64] Drive asignments for sata drives P.V.Anthony
2007-03-12 16:52 ` Olivier Crête
2007-03-12 17:00 ` Bob Sanders
2007-03-12 17:11 ` Marcus D. Hanwell
2007-03-12 17:21 ` dustin
2007-03-12 18:16 ` Marcus D. Hanwell
2007-03-12 17:53 ` [gentoo-amd64] " Bernhard Auzinger
2007-03-13 9:08 ` P.V.Anthony
2007-03-13 14:06 ` dustin
2007-03-13 17:31 ` Peter Humphrey
2007-03-13 18:33 ` dustin
2007-03-13 18:45 ` Duncan
2007-03-13 19:48 ` ducasse.isidore
2007-03-13 20:07 ` Thomas Rösner
2007-03-15 1:35 ` Florian D.
2007-03-15 2:18 ` ducasse.isidore
2007-03-13 19:53 ` ducasse.isidore
2007-03-13 19:59 ` dustin
2007-03-13 20:04 ` David Pyke [this message]
2007-03-12 17:42 ` [gentoo-amd64] [OT] " Bob Slawson
2007-03-12 17:50 ` Bob Sanders
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='008c01c765aa$d0b09e70$6f0a0a0a@RDLaptop3' \
--to=dpyke@researchdimensions.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