Re: Installer and installed system differ in disk enumeration
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
Reply to: