Re: [gentoo-user] udev Migration and SCSI -- SOLVED

[Ian Brandt]

Thanks to Mike and John for all their help.  I learned a lot.

I was able to change my lilo.conf and fstab from the
/dev/scsi/hostW/busX/targetY/lunZ/* scheme to /dev/sdaX instead, and
my 2.4 kernel came back up no problem.  (I wish I could remeber what
forced me into using the /dev/scsi scheme in the first place, but oh
well.)

With that change 2.6 came up as well.

Thanks Again!

Ian

Ian Brandt wrote:
>
> Mike Williams wrote:
>
>>OK great, I'd change my fstab, and reboot to 2.4.X/devfs now, but I'm known
>>for being a little gungho :)
>
>
> Well, guess there's not much more I can do.
>
> Supposing it doesn't come up, would a rescue CD be required to fix it?
>  I left a copy of the old /etc/fstab as /etc/fstab.bak, and setup a
> login with sudo rights to perform the copy, but if the discs don't
> come up, will login be possible?  (I remember the NOC saying there was
> a prompt, "enter the root password for maintenance", or something like
> that after a previous failure to boot the 2.6 kernel where the issue
> was the Adaptec RAID and general kernel I2O drivers clashing.)
>
>
>>BTW, what path for root do you pass to grub?
>>
>
>
> I use lilo actually because it does everything I need, and it doesn't
> care that the discs are on a raid array.  Grub at least used to
> require a special driver.  My lilo.conf is below.  So would I need to
> change my boot and root to the sdaX scheme as well?
>
> # cat /etc/lilo.conf
>
> boot=/dev/scsi/host0/bus0/target0/lun0/disc
> root=/dev/scsi/host0/bus0/target0/lun0/part3
>
> map=/boot/System.map
>
> prompt
> timeout=50
>
> lba32
> vga=normal
>
> default=2.4.25
>
> image=/boot/bzImage-2.4.25
>       label=2.4.25
>       read-only
>
> image=/boot/bzImage-2.4.28-gentoo-r9
>       label=2.4.28
>       read-only
>
> image=/boot/bzImage-2.6.13-gentoo-r3
>       label=2.6.13
>       read-only
-- 
gentoo-user@g.o mailing list