Fwd: Kernel Panic with SuSE-PPC 7.3
---------- Message transmis ---------- Subject: Kernel Panic with SuSE-PPC 7.3 Date: Fri, 22 Feb 2002 09:51:13 +0100 From: Alain Barthelemy <abarthelemy@sbb.ihe.be> To: suse-ppc@suse.com Hello, Small problem On a PBG3 I have MacOS9.2, MacOSX, SuSE7.3 I had to work on Mac partitions and I changed often Start Disk LinuxBoot <=> MacOS9 <=> MacOSX Then I want to reboot Linux (press space bar OK thus yaboot OK) And it crashes with following message: read_super_block: can't find a reiserfs filesystem on (dev 03.09, block 64, size 1024) Kernel panic: VFS: unable to mount fs on 03:0d I mention that I didn't install reiserfs file system (I stayed with ext2) Thus why is the sustem looking at reiserfs files? BTW I have no problem to boot installed system with CD1 but it is longer. All the partitions are in order. The problem lies only at the boot partition I suppose. Any way to solve the problem or did anybody have the same problem? Thanks -- Alain Barthélemy Section de Biosécurité et Biotechnologie Institut de Santé Publique R. Juliette Wytsman, 14 B-1050 Bruxelles -------------------------------------------------------
Am Freitag, 22. Februar 2002 11:27 schrieb Alain Barthelemy:
---------- Message transmis ---------- Subject: Kernel Panic with SuSE-PPC 7.3 Date: Fri, 22 Feb 2002 09:51:13 +0100 From: Alain Barthelemy <abarthelemy@sbb.ihe.be> To: suse-ppc@suse.com
Hello,
Small problem
On a PBG3 I have MacOS9.2, MacOSX, SuSE7.3 I had to work on Mac partitions and I changed often Start Disk LinuxBoot <=> MacOS9 <=> MacOSX
Then I want to reboot Linux (press space bar OK thus yaboot OK)
And it crashes with following message:
read_super_block: can't find a reiserfs filesystem on (dev 03.09, block 64, size 1024) Kernel panic: VFS: unable to mount fs on 03:0d
This message comes, when you don't give the correct root device to the kernel
I mention that I didn't install reiserfs file system (I stayed with ext2) Thus why is the sustem looking at reiserfs files?
BTW I have no problem to boot installed system with CD1 but it is longer. All the partitions are in order. The problem lies only at the boot partition I suppose.
Any way to solve the problem or did anybody have the same problem?
run pdisk -l to check your partitionnumbers then check /etc/lilo.conf for the correct entries add "copy" to your images like: image = /boot/vmlinux root = /dev/hda13 label = linux append = "" copy and run lilo again. Rolf Schmidt -------------------------------------------------- The light at the end of the tunnel might be an oncoming dragon
participants (2)
-
Alain Barthelemy
-
Rolf Schmidt