From: Rajat Jain <rajat.noida.india@gmail.com>
To: Linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Problem booting 2.6.13 on RHEL 4
Date: Wed, 14 Sep 2005 13:08:05 +0900 [thread overview]
Message-ID: <b115cb5f05091321082a3ffc24@mail.gmail.com> (raw)
Hi list,
I am using RHEL4 distribution, and am trying to boot with vanilla
2.6.13 stock kernel. My system has two onboard Adaptec SCSI
controllers. I am booting using initrd, and passing the correct
"root=" option. The following message pops up while trying to boot
with 2.6.13:
Loading scsi_mod.ko module
Loading sd_mod.ko module
Loading scsi_transport_spi.ko module
SCSI subsystem initialized
Loading aic7xxx.ko module
Creating root device
umount /sys failed: 16
Mounting root filesystem
Mount: error 6 mounting ext3
Mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
When I boot the default kernel supplied with RHEL 4, it boots successfully:
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading scsi_transport_spi.ko module
Loading aic7xxx.ko module
ACPI: PCI interrupt 0000:05:09.0[A] -> GSI 18 (level, low) -> IRQ 201
ACPI: PCI interrupt 0000:05:09.1[B] -> GSI 19 (level, low) -> IRQ 169
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec aic7899 Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 126, 16bit)
Vendor: HITACHI Model: DK32CJ-18MW Rev: JTN1
Type: Direct-Access ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled. Depth 4
SCSI device sda: 35520512 512-byte hdwr sectors (18187 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec aic7899 Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
Can some one please suggest me what could be the problem? I doubt if
there is any option I need to enable in the kernel configuration?
Any pointers are welcome,
TIA,
Rajat Jain
next reply other threads:[~2005-09-14 4:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 4:08 Rajat Jain [this message]
2005-09-14 8:13 ` Problem booting 2.6.13 on RHEL 4 liyu@WAN
2005-09-14 16:20 ` Bill Davidsen
2005-09-14 16:50 ` Roger Heflin
2005-09-15 15:30 ` Jason Baron
2005-09-28 9:18 ` Rajat Jain
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=b115cb5f05091321082a3ffc24@mail.gmail.com \
--to=rajat.noida.india@gmail.com \
--cc=Linux-newbie@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).