Hi,
I have installed the SLES8.0 on a LX50 server. The installation went
fine. While coming up the kernel panics with the below message.
kernel panic: VFS: Unable to mount root fs on 08:03
I have tried the workaround by give mem=2048M for boot options . This
does not work and give the same problem.
Can anyone of you throw light on this?
Your help is highly appreciated.
--
Regards,
P.S.M.Swamiji
Hi,
The follwing are the detailed messages while kernel panic.
------
Pending list:
Kernel Free SCB list: 3 1 0
DevQ(0:0:0): ) waiting
DevQ(0:0:0): ) waiting
aic7xxx_abort returnss 0x2002
scsi: device set offline - not ready or command retry failed after bus
reset: ho
st 1 channel 0 id 15 lun 0
Loading module ext3 ...
Using /lib/modules/2.4.19-64GB-SMP/kernel/fs/ext3/ext3.0
kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "sda2" or 08:02
Please append a correct "root=" boot option
kernel panic: VFS: Unable to mount root fs on 08:03
--------
The system has three partitions.
1. /dev/sda1 /boot 125 MB ext3
2. /dev/sda2 / 30.5 GB ext3
3. /dev/sda3 swap 3.5 GB swap
And the RAM is 2048MB.
Boot options used : root=/dev/sda2 mem=2048M.
Any clues?
Thanks,
P.S.M.Swamiji
Sesha Muneendra Swameejee Panda wrote:
> Hi,
>
> I have installed the SLES8.0 on a LX50 server. The installation went
> fine. While coming up the kernel panics with the below message.
>
> kernel panic: VFS: Unable to mount root fs on 08:03
>
> I have tried the workaround by give mem=2048M for boot options . This
> does not work and give the same problem.
>
> Can anyone of you throw light on this?
>
> Your help is highly appreciated.
>
--
Regards,
P.S.M.Swamiji
Ph:2298989 x 27566
"LIFE IS ALREADY SHORT, DONT MAKE IT SHORTER by SMOKING OR
ARGUING."
On Mit, 2004-03-10 at 21:05, Sesha Muneendra Swameejee Panda wrote:
[...]
> Sesha Muneendra Swameejee Panda wrote:
[...]
> > I have installed the SLES8.0 on a LX50 server. The installation went
You should probably go to SuSE with the bug report since it is theirs
product.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
Hi Bernd,
Bernd Petrovitsch wrote:
> On Mit, 2004-03-10 at 21:05, Sesha Muneendra Swameejee Panda wrote:
> [...]
>
>>Sesha Muneendra Swameejee Panda wrote:
>
> [...]
>
>>>I have installed the SLES8.0 on a LX50 server. The installation went
>>
>
> You should probably go to SuSE with the bug report since it is theirs
> product.
As I am a new bite to linux world , I don't know the procedure to file bugs.
Can you please give the procedure or contact info of Suse to file the
bug report.
--
Regards,
P.S.M.Swamiji
Ph:2298989 x 27566
On Don, 2004-03-11 at 08:34, Sesha Muneendra Swameejee Panda wrote:
> Bernd Petrovitsch wrote:
> > On Mit, 2004-03-10 at 21:05, Sesha Muneendra Swameejee Panda wrote:
> > [...]
> >>Sesha Muneendra Swameejee Panda wrote:
> > [...]
> >>>I have installed the SLES8.0 on a LX50 server. The installation went
> >>
> >
> > You should probably go to SuSE with the bug report since it is theirs
> > product.
>
> As I am a new bite to linux world , I don't know the procedure to file bugs.
First I assume that SLES-8.0 means "Suse Linux Enterprsie Server 8.0".
> Can you please give the procedure or contact info of Suse to file the
> bug report.
Their website is http://www.suse.com/. I don't know where exactly you
are expected to ask that kind of questions or file bug reports.
In the current case the kernel is not able to mount the root file system
(where pretty much the very important executables and libraries are
around).
This problem has actually nothing to do with the kernel per se since he
simply reports that (which is actually the second reason why the
question is somewhta off-topic on the LKML).
Usually that means that at least one of the follwoign does not work:
-) the driver for IDE, SCSI or wherever the root filesystem is to be
found is not available
-) the driver of the filesystem which is used on the root filesystem is
not available.
-) some part of the hardware is broken - this can be the SCSI/IDE/...
controller itself, the disk, cables in between, etc.
The list is not complete - just what I would primarily expect.
Especially the
---- snip ----
aic7xxx_abort returnss 0x2002
scsi: device set offline - not ready or command retry failed after bus
reset: ho
---- snip ----
make me think that either the Adaptec controller or the disk (or the
cable in between) have a serious hardware problem. But I'm no export in
that area ....
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services