From: "liyu@WAN" <liyu@ccoss.com.cn>
To: rajat.noida.india@gmail.com
Cc: Linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Problem booting 2.6.13 on RHEL 4
Date: Wed, 14 Sep 2005 16:13:47 +0800 [thread overview]
Message-ID: <4327DBBB.7090108@ccoss.com.cn> (raw)
In-Reply-To: <b115cb5f05091321082a3ffc24@mail.gmail.com>
It seem that kernel have no time to probe your disk, and do not
read parttion table.
I use kernel 2.6.12 and SATA disk on FC3, also failed to boot.
but after some experiment, I found if we place 'sleep 5'
statement between insmod commands in linuxrc or init, it will
boot up!
However, this idea is too HACK.
Maybe, I guest, kernel need some time to probe scsi disk?
but I can not explain that kernel say unresoluting symbol XXXXX
use this reason.
May be also, there have one problem in older mkinitrd. but
I looked its source (more roughly), it only include some scriptes.
Any more clear idea on it ??
Rajat Jain wrote:
>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
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
WARNING: multiple messages have this Message-ID (diff)
From: "liyu@WAN" <liyu@ccoss.com.cn>
To: rajat.noida.india@gmail.com
Cc: Linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Problem booting 2.6.13 on RHEL 4
Date: Wed, 14 Sep 2005 16:13:47 +0800 [thread overview]
Message-ID: <4327DBBB.7090108@ccoss.com.cn> (raw)
In-Reply-To: <b115cb5f05091321082a3ffc24@mail.gmail.com>
It seem that kernel have no time to probe your disk, and do not
read parttion table.
I use kernel 2.6.12 and SATA disk on FC3, also failed to boot.
but after some experiment, I found if we place 'sleep 5'
statement between insmod commands in linuxrc or init, it will
boot up!
However, this idea is too HACK.
Maybe, I guest, kernel need some time to probe scsi disk?
but I can not explain that kernel say unresoluting symbol XXXXX
use this reason.
May be also, there have one problem in older mkinitrd. but
I looked its source (more roughly), it only include some scriptes.
Any more clear idea on it ??
Rajat Jain wrote:
>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
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
next prev parent reply other threads:[~2005-09-14 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 4:08 Problem booting 2.6.13 on RHEL 4 Rajat Jain
2005-09-14 4:08 ` Rajat Jain
2005-09-14 8:13 ` liyu@WAN [this message]
2005-09-14 8:13 ` liyu@WAN
2005-09-14 16:20 ` Bill Davidsen
2005-09-14 16:20 ` Bill Davidsen
2005-09-14 16:50 ` Roger Heflin
2005-09-14 16:50 ` Roger Heflin
2005-09-15 15:30 ` Jason Baron
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=4327DBBB.7090108@ccoss.com.cn \
--to=liyu@ccoss.com.cn \
--cc=Linux-newbie@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajat.noida.india@gmail.com \
/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.