From: Ian Brandt <ian@ianbrandt.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev Migration and SCSI -- SOLVED
Date: Fri, 21 Oct 2005 15:29:00 -0700 [thread overview]
Message-ID: <43596BAC.2000801@ianbrandt.com> (raw)
In-Reply-To: <435824A2.5040801@ianbrandt.com>
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@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-21 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 16:50 [gentoo-user] udev Migration and SCSI Ian Brandt
2005-10-19 18:19 ` Mike Williams
2005-10-19 21:00 ` Ian Brandt
2005-10-19 22:46 ` Mike Williams
2005-10-20 16:53 ` Ian Brandt
2005-10-20 16:59 ` John Jolet
2005-10-20 17:05 ` Ian Brandt
2005-10-20 17:28 ` John Jolet
2005-10-20 17:51 ` Ian Brandt
2005-10-20 17:57 ` John Jolet
2005-10-20 18:44 ` Mike Williams
2005-10-20 17:13 ` Mike Williams
2005-10-20 17:51 ` Ian Brandt
2005-10-20 18:41 ` Mike Williams
2005-10-20 23:13 ` Ian Brandt
2005-10-21 22:29 ` Ian Brandt [this message]
2005-10-21 22:42 ` [gentoo-user] udev Migration and SCSI -- SOLVED Mike Williams
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=43596BAC.2000801@ianbrandt.com \
--to=ian@ianbrandt.com \
--cc=gentoo-user@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