| 1 |
It may be that your SATA drive has moved from sda to hda. Trying changing it |
| 2 |
in your fstab and see if it works. (boot using the live CD and mount the |
| 3 |
drive, etc.) |
| 4 |
|
| 5 |
-----Original Message----- |
| 6 |
From: dustin@×××××××.us [mailto:dustin@×××××××.us] |
| 7 |
Sent: Tuesday, March 13, 2007 3:59 PM |
| 8 |
To: gentoo-amd64@l.g.o |
| 9 |
Subject: Re: [gentoo-amd64] Re: Drive asignments for sata drives |
| 10 |
|
| 11 |
On Tue, Mar 13, 2007 at 08:53:13PM +0100, ducasse.isidore@×××××.com wrote: |
| 12 |
> Just to mention, I did activate the SCSI drivers for my hd in the new path |
| 13 |
in menuconfig manually. |
| 14 |
> |
| 15 |
> By the way, while trying latest 2.6.20 kernel, my machine couldn't mount |
| 16 |
my SCSI drive as sda2 anymore... |
| 17 |
> I swear I didn't plug/unplug any device in the meanwhile. |
| 18 |
> |
| 19 |
> Got any clue? Is there a magic option to get in a shell and check with |
| 20 |
genkernel made kernels for the correct device node? Or a udev initramfs with |
| 21 |
just a prompt available? |
| 22 |
|
| 23 |
It's always frustrating to diagnose things like that, without being able to |
| 24 |
effectively pause and restart the kernel messages. Booting with a serial |
| 25 |
console is, I think, the preferred solution. |
| 26 |
|
| 27 |
One thing you could do is put in an IDE drive and put a basic root partition |
| 28 |
on it -- at least enough to boot into a recovery shell. Then you can look |
| 29 |
around at dmesg, etc. |
| 30 |
|
| 31 |
It's not elegant, but it's an idea. |
| 32 |
|
| 33 |
Dustin |
| 34 |
-- |
| 35 |
gentoo-amd64@g.o mailing list |
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-amd64@g.o mailing list |
Archives