From: Keith Mannthey <kmannth@gmail.com>
To: "Srinivasan, Usha" <Usha.Srinivasan@unisys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.3 boot problem
Date: Mon, 15 Aug 2005 10:41:22 -0700 [thread overview]
Message-ID: <a762e240508151041597c84fc@mail.gmail.com> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F601F9A9B1@USTR-EXCH5.na.uis.unisys.com>
On 8/15/05, Srinivasan, Usha <Usha.Srinivasan@unisys.com> wrote:
> Hello,
>
> I have been successfully running 2.6.11 under Red Hat RHEL4 environment
> with no problems at all. I needed to switch to 2.6.12 and chose
> 2.6.12.3. However, I am having problems booting 2.6.12.3. My SCSI HBAs
> & disks are not being found at boot time and I see these errors during
> boot:
The 2.6.11 tree is a kernel.org tree?
Are you using LVM or regular partitions?
> Red Hat nash version 4.1.18 starting
> Mkrootdev: label / not found
> Umount /sys failed: 16
> Mount: error 19 mounting ext3
> Mount: error 2 mounting none
> Switchroot: mount failed: 22
> Umount /initrd/dev failed: 2
Do you see the scsi driver find the disks?
I work around I use some times is to change my root line in the
bootloader to root=/dev/(your disk). Lables can cause confusion.
> After trying many many things I have figured out what works and what
> doesn't.
>
> Works:
> If I build scsi_mod, sd_mod, scsi_transport_spi and aic7xxxx drivers as
> built into the kernel, 2.6.12.3 boots fine.
>
> Doesn't work:
> If I build scsi_mod, sd_mod, scsi_transport_spi and aic7xxxx drivers as
> Modules, 2.6.12.3 fails to boot.
The modules are put into an initrd correct? You need their
functinality to boot.
Keith
prev parent reply other threads:[~2005-08-15 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 17:00 2.6.12.3 boot problem Srinivasan, Usha
2005-08-15 17:41 ` Keith Mannthey [this message]
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=a762e240508151041597c84fc@mail.gmail.com \
--to=kmannth@gmail.com \
--cc=Usha.Srinivasan@unisys.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.