Fwd: Installer and installed system differ in disk enumeration
Forgot to CC the list.
---------- Forwarded message ----------
From: John Baab <john.baab@gmail.com>
Date: Apr 12, 2005 8:37 AM
Subject: Re: Installer and installed system differ in disk enumeration
To: A E Lawrence <A.E.Lawrence@lboro.ac.uk>
I have had a similiar problem while using a pata and a sata drive. I
wanted to use the pata drive as the secondary drive and the sata drive
as the primary, installer goes through fine, but grub would always be
pointing to the wrong place (HD1,1 instead of HD0,1). At points I
think the installer was actually writing grub to the pata hd's mbr.
So I had to edit the grub menu and everything boots fine now.
On Apr 12, 2005 7:48 AM, A E Lawrence <A.E.Lawrence@lboro.ac.uk> wrote:
> Toshikazu Aiyama, Ph.D. wrote:
> > A.E.Lawrence wrote:
>
> > I have a similar set up with you:
> > ASUS a8n-sli Deluxe mbrd populated with 5 hard disks:
> >
> > a) 1 scsi MO on adaptec 2940UW
> > b) 1 PATA primary master
> > c) 4 sata on nv_sata, none on sil_SATA
> >
> > In addition, I have 1 DVD-RAM, and 1 CD-RW on PATA secondary.
>
> Mine is pretty similar, but my pata drive is on the ide1 channel, and it
> is not the boot disc.
>
> > I do not use grub becasue it uses a kind of relative disk assignment: 1st disk
> > is hdd0, and 2nd disk is hdd1, and so on; thus if I change the disk
> > configurations, there is no easy way to boot the system, at least, to
> > grub-ignorant people like me.
>
> It just uses Bios enumeration.
>
> > If you are using an installer, the steps are as follows, I think. After a
> > chosen kernel is installed, we can choose a boot loader: grub or lilo. I
> > believe grub or lilo is a mutually exclusive options; thus since you are
> > talking about grub, you are in the position to follow my suggestions. Of
> > course, you can simply ignore me.
>
> The problem is that the installer then wrote the wrong root=drive
> parameter for the kernel. I could fix that with the grub edit.
>
> > If I use non-default pre-compiled image, disk on 2940UW is recognized as scsi4
> > by the installer kernel, and the same disk is recognized as scsi0 by the
> > installed kernel. But if I use non-default image, the SATA2 disk on nv_sata is
> > recognized as scsi0 by both installer kerenel and the installed kernel.
>
> Maybe that is another way I could have solved my problem.
>
> Anyway, I am up and running now. Thanks for the comments. Let's hope
> that these entries in the archive will be useful for anyone else who has
> these sorts of problems.
>
> ael
>
>
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--
Useful Software:
Mozilla Firefox ->
http://www.spreadfirefox.com/?q=affiliates&id=15270&t=1
Mozilla Thunderbird -> http://www.mozilla.org/products/thunderbird/
OpenOffice.org(OOo) -> http://www.openoffice.org/
Gaim -> http://gaim.sourceforge.net/
7-Zip -> http://www.7-zip.org/
http://clusty.com/ -> "The David that takes down Goliath" -Bartos
Reply to: