ardrive unless you specifically mount a partition.
>
> - Bruce
>
> --
> On Mon, 10 Apr 2000, John Kiff wrote:
>
> > Help!!!
> >
> > I got the following messages when I was booting up:
> >
> > "EXT2-fs: group descriptors corrupted:"
> >
>
pted:"
>
> followed a few lines later by:
>
> "kernel panic: unable to mount root fs on 03:02"
>
> after which everything stops. The same thing happened when I tried using my
> boot floppy.
>
> What should I do? My first reaction is to go back to
Help!!!
I got the following messages when I was booting up:
"EXT2-fs: group descriptors corrupted:"
followed a few lines later by:
"kernel panic: unable to mount root fs on 03:02"
after which everything stops. The same thing happened when I tried using my
boot floppy.
That's what the problem was. Thanks for the help.
Kevin
-Original Message-
From: George Bonser [mailto:[EMAIL PROTECTED]
Sent: Monday, April 03, 2000 11:50 PM
To: Kevin
Cc: Debian-User
Subject: Re: Kernel panic: unable to mount root
On Mon, 3 Apr 2000, Kevin wrote:
> I de
and I followed the instructions in the kernel howto. I
compiled and
wessam >installed the kernel, ran lilo, and rebooted. I receive the following
wessam >error:
wessam >
wessam >Kernel panic: VFS: unable to mount root fs on 03:01
wessam >
wessam >my lilo.conf:
wessam >boot=/dev
I decided to compile a new kernel (2.2.1) to upgrade from 2.0.38 for my 486
(slink) and I followed the instructions in the kernel howto. I compiled and
installed the kernel, ran lilo, and rebooted. I receive the following
error:
Kernel panic: VFS: unable to mount root fs on 03:01
my lilo.conf
** On Apr 02, Bob Nielsen scribbled:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing init= option to kernel.
You compiled the kernel with wrong root partition, it happens sometimes. The
best b
On Sun, Apr 02, 2000 at 09:30:07PM -0400, Mike Werner wrote:
> On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> > I have had the same problem as Bob N. and ext2 is IN the kernel, not
> > a module and I have a Pentium III. Is there some bug either in kpkg
> > or latest kernel vers
On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> I have had the same problem as Bob N. and ext2 is IN the kernel, not
> a module and I have a Pentium III. Is there some bug either in kpkg
> or latest kernel version of 2.2.14?
For what it's worth, I'm running 2.2.14 on two of my m
al routine. It just says
it has installed the image and then when I reboot: "kernel panic No init" I
didn't have this problem 2 weeks ago.
I don't seem to be able to revise the kernel.
Eric Wolven
>>>>> "Paul" == Paul Kallstrom <[EMAIL PROTEC
One thing to check: Make sure that you have ext2 support compiled in the
kernel, and not as a module.
Paul
On 02-Apr-2000 Bob Nielsen wrote:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing i
ompiled a new 2.2.14 kernel after doing a new potato
> Bob> install and got the message:
>
> Bob> Kernel panic: No init found. Try passing init= option to
> Bob> kernel.
>
> Bob> Does anyone know what is causing this? The 2.2.14-compact
> Bob&
>>>>> "Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:
Bob> --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii
Bob> I just compiled a new 2.2.14 kernel after doing a new potato
Bob> install and got the message:
Bob> Ker
I just compiled a new 2.2.14 kernel after doing a new potato install and got
the message:
Kernel panic: No init found. Try passing init= option to kernel.
Does anyone know what is causing this? The 2.2.14-compact kernel
installed from the boot-floppies as part of the installation boots
On Sun, Mar 05, 2000 at 08:52:53AM -0800, Mahesh Padmanabhan wrote:
> Hello All,
> The 2.2.14 kernel starts ok but right after :
>
> Freeing unused kernel memory : 36k freed
>
> it says:
>
> Kernel panic. init not found. Pass init= option to the
> kerne
t with the custom
> 2.2.14 kernel I get a kernel panic.
Not familiar with EZ Drive. I don't dual boot my home system, and
manage the rare occasions I dual boot at work largely through VMWare,
else LILO.
You may still have to append a "linear" or disk geometry option to
LOADLIN.EXE.
custom 2.0.36 kernel but with the custom
2.2.14 kernel I get a kernel panic.
I only have one IDE hard drive. The only reason I am
using the Adaptec scsi card is for my scsi scanner. I
am also builing the generic and scsi emulation support
as modules so that I can make the kernel see my CDRW
drive
rts ok but right after :
>
> Freeing unused kernel memory : 36k freed
>
> it says:
>
> Kernel panic. init not found. Pass init= option to the
> kernel.
>
> I tried using rdev on my custom 2.0.36 kernel (which
> works)
>
> rdev linux.20
>
> Root device /de
similar to the one I had
used
for my 2.0.36 kernel.
The 2.2.14 kernel starts ok but right after :
Freeing unused kernel memory : 36k freed
it says:
Kernel panic. init not found. Pass init= option to the
kernel.
I tried using rdev on my custom 2.0.36 kernel (which
works)
rdev linux.20
Root
similar to the one I had
used
for my 2.0.36 kernel.
The 2.2.14 kernel starts ok but right after :
Freeing unused kernel memory : 36k freed
it says:
Kernel panic. init not found. Pass init= option to the
kernel.
I tried using rdev on my custom 2.0.36 kernel (which
works)
rdev linux.20
Root
cial disk from Linux Press)
Description of Partitions:
on dev/hda I have a 2 gig vfat partitions. It is followed by ~26gig of unused
space.
on dev/hdb I have a 2 gig vfat partitions followed by 3 gig of unused space,
followed by ~23 gig NTFS partition.
Problem:
I get a Kernel panic when I boot
Paul McDermott wrote:
>
> Hi Steve, it looks like you might have misconfigured the kernel. did you
> include ext2 filesystem in your configured kernel.
and, steve, the ext2 should no be compiled as module :)
--
hafi
ooting:
>
> Partition check
> hda: driver not present
> VFS: Cannot open root device 03:01
> Kernel panic: VFS: Unable to mount root fs on 03:01
>
> Did I do something wrong with the kernel's IDE configuration (I have a
> IDE 2.5 GB Quantum Bigfoot)? I reran LILO after ins
I just compiled and installed the 2.2 kernel with the debian kernel
package and I got the following error on booting:
Partition check
hda: driver not present
VFS: Cannot open root device 03:01
Kernel panic: VFS: Unable to mount root fs on 03:01
Did I do something wrong with the kernel'
it appears to hit a kernel panic of some kind. I get this
message:
Unable to handle kernel derefence of pointer at address 00
Waiting on processor #0.
And then the entire system hangs, obviously. When my system hangs
(either this problem or hang in general) everything shuts down. I can
gt; and suffenly the system stopped:
>
> Kernel panic: Freeing swap cache page
>
> kern.log says:
>
> Oct 29 11:03:01 convert kernel: VM: read_swap_page: page already in page
> cache!
> Oct 29 11:03:01 convert kernel: Kernel panic: Freeing swap cache page
>
> What does
> From: Noah L. Meyerhans [mailto:[EMAIL PROTECTED]
> On Fri, 29 Oct 1999, Ingo Reimann wrote:
[...]
> > Kernel panic: Freeing swap cache page
[...]
> Well, the kernel hackers will probably tell me that this is insane and
> that it could never possibly make a difference... Des
On Fri, Oct 29, 1999 at 09:03:55AM -0400, Noah L. Meyerhans wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Fri, 29 Oct 1999, Ingo Reimann wrote:
>
> > Kernel panic: Freeing swap cache page
> >
> > kern.log says:
> >
> > Oct 29 11:03:01 convert k
-BEGIN PGP SIGNED MESSAGE-
On Fri, 29 Oct 1999, Ingo Reimann wrote:
> Kernel panic: Freeing swap cache page
>
> kern.log says:
>
> Oct 29 11:03:01 convert kernel: VM: read_swap_page: page already in page
> cache!
> Oct 29 11:03:01 convert kernel: Kernel panic: Fr
ok, things changed
the machine ran stable over night, doing nothing but setiathome. Getting
back to the office, i started
apt-get update && apt-get upgrade
and suffenly the system stopped:
Kernel panic: Freeing swap cache page
kern.log says:
Oct 29 11:03:01 convert ke
Just an idea :)
Its not a scsi CDROM drive is it, have seen similar type problems with NT
booting of
scsi cdrom. If it is does the kernel have support for the scsi controller ???
Syrus Nemat-Nasser wrote:
> Hello folks.
>
> This is not Debian-specific, but my brother-in-law got a ker
Hello around,
i have just installed Debian Slink an my system and wanna try an online
update via isdn. So i installed isdnutils and the newest kernel (2.2.12).
Now, the system gets a kernel panic (killing interrupt handler, it sais, and
a lot of digits).
Whats wrong?
Thanx.
Timo Kabsch
Hello folks.
This is not Debian-specific, but my brother-in-law got a kernel panic
while booting of a Linux installation CD:
>I got the following booting off of a CD while installing on a new
>machine.
>
> VFS: Cannot open root device 08:21
> Kernel panic: VFS: Unable to moun
At 01:54 AM 10/22/99 +0200, Jocke wrote:
>Hi all,
>
>I did something stupid today :(
>While recompiling my kernel to add scsi support for my cdrw I accidently
>forgot some ide stuff and now I can't boot.
If you want to change something important like a...*hmmm*
a kernel or something ALWAYS make li
On 22/10/99 Jocke wrote:
I have 2 debian partitions the one that works are on hda2 and the one
that messed up is on hda5.
I have some old vmlinuz + System.map in /boot
Could anyone guide me thru this so I can get my hda5 debian to boot again ?
Can I fix it from "this" (hda2) partition or do I h
Hi all,
I did something stupid today :(
While recompiling my kernel to add scsi support for my cdrw I accidently
forgot some ide stuff and now I can't boot.
VFS: Cannot open root device 03.05
Kernel panic: VFS: Unable to mount root fs on 03:05
This has been discussed before on this list
oot=/dev/sda
> But when I tried booting the new kernel, I got
>
> VFS: Cannot open root device 08:06
> Kernel Panic: VFS: Unable to mount root fs on 08:06
>
> what should I do now?
>
> -gnana
>
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
ev/sda
> But when I tried booting the new kernel, I got
>
> VFS: Cannot open root device 08:06
> Kernel Panic: VFS: Unable to mount root fs on 08:06
>
> what should I do now?
Compiled ext2 filesystem as module? Make it permanent.
Mirek
08:06
Kernel Panic: VFS: Unable to mount root fs on 08:06
what should I do now?
-gnana
n Oga [mailto:[EMAIL PROTECTED]
Sent: 17. August 1999 09:05
To: [EMAIL PROTECTED]
Subject: Re: Kernel panic!
hi
> VFS: cannot open root device 03:01
> Kernel panic: VFS: Unable to mount root fs on 03:01
i get the same silly error when I tried 2.2.10 on my rh-6.0 box...
( that is /de
it hadn't loaded the IDE drivers yet!! That was what the
kernel panic was all about. :-)
Silly, silly, me... don't know why in the world I would configure the IDE
drivers to be modules rather than compiled-in, but after managing to boot into
the system with the older kernel on my Rescue Di
hi
> VFS: cannot open root device 03:01
> Kernel panic: VFS: Unable to mount root fs on 03:01
i get the same silly error when I tried 2.2.10 on my rh-6.0 box...
( that is /dev/hda1 )
i gave up trying to find out whyand just reverted back to
2.2.5-15 from rh... will try
properly. I used LILO to install the boot sector on /dev/hda and root set
to /dev/hda1, and the kernel seems to boot fine, but after detecting my
Ethernet card, it gives this error:
VFS: cannot open root device 03:01
Kernel panic: VFS: Unable to mount root fs on 03:01
What does this message mean?? Th
> Most of the time when I see this problem, it is because there is no
> support for the drive compiled in the kernel. Did you check the
> following under the Block Device section of menuconfig when compilinf
> the 2.2.10 kernel?
>
> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
> Include IDE
I've installed different board, it's not booting either.
Both boards I've tried had i430VX chipset on them, I'm no longer sure
about the original board (can't get it to boot, sure that it will not work
after picking it up from trash)
Are there any bugs in 2.2.10 connected to VX chipset?
Andrew
-
>
> Andrew;
>
> I suppose that my first thought would be to BIOS differences...
> Have you already checked for "memory holes" and "shadow memory"?
Yep, did that check, everything was ok.
>
> What is the size difference between the two kernels?
>
The 2.0.36 is 406K, 2.2.10 is 495K. Both kern
) and now, for some reason, when I'm trying to boot my 2.2.10
> kernel, I get kernel panic while mounting root fs.
> I can't reproduce the exact message right now, but it seems that while
> booting it's doing a normal partition check and fails then.
> However, I can boo
>
> Andrei Ivanov wrote:
> >
> > Obviosly one of the partitions is not found. Any idea why?
> > Andrew
> >
> Well, I might have spoken too quickly with my last post :-)
> One other thing to check for is that ext2 support is compiled into the
> kernel. It is kinda hard to tell what might be going
egion already allocated at 0x9000.
and then says:
VFS: cannot open root device 08:07
Kernel panic: VFS: Unable to mount root fs on 08:07
And then, everything is stopped, and I have to reboot.
Could someone explain what the problem can b
Andrei Ivanov wrote:
>
> Obviosly one of the partitions is not found. Any idea why?
> Andrew
>
Well, I might have spoken too quickly with my last post :-)
One other thing to check for is that ext2 support is compiled into the
kernel. It is kinda hard to tell what might be going on here without
kno
Most of the time when I see this problem, it is because there is no
support for the drive compiled in the kernel. Did you check the
following under the Block Device section of menuconfig when compilinf
the 2.2.10 kernel?
Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
Include IDE/ATA-2 DISK su
> Have you tried simply running lilo? and/or rdeving the 2.2.10 kernel to
> whatever it
> should point to? Apologies if you've already done all this.
>
> -Aaron Solochek
> [EMAIL PROTECTED]
Yep, I ran lilo (I even recompiled the 2.2.10 kernel and created the boot
disk, still it panics when bo
ad) and now, for some reason, when I'm trying to boot my 2.2.10
> kernel, I get kernel panic while mounting root fs.
> I can't reproduce the exact message right now, but it seems that while
> booting it's doing a normal partition check and fails then.
> However, I can b
> In that case, it looks like a kernel bug in 2.2.* series. What did
> /var/log/kern.log say?? Can you send us the error msg when it is trying
> to mount the harddisk?? use dmesg > error.log
There is no error message through dmesg > error.log because kernel panic
occurs while
>
> just a guess... maybe you have pluged your harddisk into a different slot. it
> might have changed its name from /dev/hda1 to /dev/hdc1
>
>
> Have you tried to use the motherboard bios to re-detect all your harddisk??
> Have you tried to mount the linux root fs when you booted with
> the
??
On Fri, Jul 23, 1999 at 12:51:33AM -0500, Andrei Ivanov wrote:
> I just had to replace a motherboard in my Linux box (floppy controller
> went bad) and now, for some reason, when I'm trying to boot my 2.2.10
> kernel, I get kernel panic while mounting root fs.
> I can't repro
I just had to replace a motherboard in my Linux box (floppy controller
went bad) and now, for some reason, when I'm trying to boot my 2.2.10
kernel, I get kernel panic while mounting root fs.
I can't reproduce the exact message right now, but it seems that while
booting it's
On Sun, Jun 20, 1999 at 10:59:14PM -0500, Brad wrote:
> > I upgraded to 2.2.8
>
> Oddly enough, 2.2.8 had filesystem corruption problems (under very high
> loads) as well! 2.2.9 reverted to 2.2.7's filesystem code, which didn't
> have the problem.
I would have used it but wasn't able to get a tar
On Sun, 20 Jun 1999, Werner Reisberger wrote:
> On Sat, Jun 19, 1999 at 10:57:33AM -0500, Stephen Pitts wrote:
>
> > You shouldn't be running 2.2.3, there are some filesystem corruption
> > problems in the early 2.2.x releases. Upgrade to 2.2.10, that should
> > be better.
>
> I upgraded to 2.2.
On Sat, Jun 19, 1999 at 10:57:33AM -0500, Stephen Pitts wrote:
> > been written to a log file. Below is an excerpt which I found on the
> > console:
> >
> > unable to handle kernel paging request at virtual address e7fde95c
> You shouldn't be running 2.2.3, there are some filesystem corruption
>
On Fri, Jun 18, 1999 at 08:39:11PM +0200, Werner Reisberger wrote:
> I am running a debian machine (PC PII 350 MHZ, 128 MB RAM) as an Internet
> server. Today the server crashed the second times after running one week
> without any problems. The crash was caused by a kernel panic. No
I am running a debian machine (PC PII 350 MHZ, 128 MB RAM) as an Internet
server. Today the server crashed the second times after running one week
without any problems. The crash was caused by a kernel panic. Nothing has
been written to a log file. Below is an excerpt which I found on the
console
33, limit=1
isofs_read_super: bread failed, dev 03:02 iso-blknum 16 block 32
kernel panic: VFS: unable to mount root fs on 03:02
I tried re-installing Linux and Windows. The most recent time I went back
to fdisk and deleted all partitions, then used fdisk to create a primary
partition and
"Camilo Alejandro Arboleda" wrote:
>Thanks to every one for the help with my first problem.
>
>Finaly I could compile the new kernel, but I could not start the system
>with the new kernel.
>
>I get this message:
>'kernel panic: no init found.
Thanks to every one for the help with my first problem.
Finaly I could compile the new kernel, but I could not start the system
with the new kernel.
I get this message:
'kernel panic: no init found. Try passing init = option to kernel'
What is the value of 'option'?
How
Subject: Kernel 2.2.3 & Kernel Panic...
Date: Mon, Apr 05, 1999 at 04:06:55PM -0400
In reply to:Brant Wells
Quoting Brant Wells([EMAIL PROTECTED]):
> Howdy All!
>
> I've been working with installing the Kernel 2.2.3, and I have a
> problem... After I run
On Mon, Apr 05, 1999 at 03:45:15PM -0400, Brant Wells wrote:
> Howdy All...
>
> My Linux box is running on an ext2 partition.
>
> I use 'make install' , because it automatically makes the necessary changes
> for
> me, plus the fact that the last time I tried 'make zImage', it wiped out my
> Hard
make a boot file for the NT Boot Manager...
> When I get the NT Boot Manager to go to Linux, Everything works fine,
> until it comes time to mount the hard drive... I get a MSDOS FAT 12...
> yada yada yada... Then I get:
>
> Kernel Panic. Unable to mount the root partition on 16:05
>
&
Howdy All...
My Linux box is running on an ext2 partition.
I use 'make install' , because it automatically makes the necessary changes for
me, plus the fact that the last time I tried 'make zImage', it wiped out my
Hard Drive when I installed it.
I just went back and looked at the setup in 'menu
rything works fine,
until it comes time to mount the hard drive... I get a MSDOS FAT 12...
yada yada yada... Then I get:
Kernel Panic. Unable to mount the root partition on 16:05
I have DOS Fat support turned on, and the VFAT support is turned on...
The MSDOS Fat is not set (It doesn't wor
kette can be found on any debian ftp site.
> >
> > > I had my system hang last night while running a statistical process. I
> > > used Ctrl-Alt-Delete to
> > > reboot. Now I get a kernel panic.
> > >
> > > UMSDOS: msdos_read_super failed, mount a
d Ctrl-Alt-Delete to
> > reboot. Now I get a kernel panic.
> >
> > UMSDOS: msdos_read_super failed, mount aborted ...
> >
> > HPFS: hpfs_read_super: Not HPFS ...
> >
> > Kernel panic: VFS: Unable to mount root fs on 03:05
> >
>
[EMAIL PROTECTED] wrote:
> I had my system hang last night while running a statistical process. I used
> Ctrl-Alt-Delete to
> reboot. Now I get a kernel panic.
>
> UMSDOS: msdos_read_super failed, mount aborted ...
>
> HPFS: hpfs_read_super: Not HPFS ...
I had my system hang last night while running a statistical process. I used
Ctrl-Alt-Delete to
reboot. Now I get a kernel panic.
UMSDOS: msdos_read_super failed, mount aborted ...
HPFS: hpfs_read_super: Not HPFS ...
Kernel panic: VFS: Unable to mount root fs on 03:05
Does 03:05
Martin Waller wrote:
>
> I've put together an old 486 from bits, and am trying to install Debian
> (hamm) on it.
>
> If I use the boot diskette (doesn't support CD bootup), the bootup stops
> with 'Can't open initial console', and if I try the rescue
Jianming YOU wrote:
>
> Hi, Paul,
>
> Thank you very much.
>
> I followed your suggestion. Here is what I did and what I got:
>
> Boot from a floppy, with kernel 2.0.35
> login as root
>
> > mount /dev/hda2 /mnt
> > cd mnt
> > rm vmlinuz
> > ln -s boot/vmlinuz-2.0.34 vmlinuz
> > ls -l sbin/lil
- James
On Tue, 16 Mar 1999, Paul Miller wrote:
> Jianming YOU wrote:
> >
> > Hi, Experts,
> >
> > I just upgraded my box from 2.0.34 to 2.2.1 and I got
> > "kernel panic, no init found..." when I tried to boot with the new
> > kernel. The proble
Jianming YOU wrote:
>
> Hi, Experts,
>
> I just upgraded my box from 2.0.34 to 2.2.1 and I got
> "kernel panic, no init found..." when I tried to boot with the new
> kernel. The problem have been reported by several people. However, I
> still don't know how
Hi, Experts,
I just upgraded my box from 2.0.34 to 2.2.1 and I got
"kernel panic, no init found..." when I tried to boot with the new
kernel. The problem have been reported by several people. However, I
still don't know how to recover the system after reading those replies,
:(.
I&
I've put together an old 486 from bits, and am trying to install Debian
(hamm) on it.
If I use the boot diskette (doesn't support CD bootup), the bootup stops
with 'Can't open initial console', and if I try the rescue disk, it just
says:
Kernel panic: Free list corrupt
x27;t find valid ramdisk image starting at 0.
[MS-DOS FS Rel. 12,FAT 0,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
[me=0x0,cs=0,fs=0,fl=0,ds=0,de=0,data=0,se=0,ts=0,ls=0,rc=0,fc=4294967295]
Kernel panic: VFS: Unable to mount root fs on 01:00
Any Hints as to why this would happen?
Please CC any replys
make config, make dep, make zImage,
> make modules, make modules_install and lilo (and copying zImage
> to / as vmlinuz), I rebooted the machine.
>
> It booted partially, then stopped with the error message
> "Kernel panic: VFS: Unable to mount root fs on 03:02." C
I just tried to patch the 2.0.35 kernel with Initio SCSI
adapter drivers. After make config, make dep, make zImage,
make modules, make modules_install and lilo (and copying zImage
to / as vmlinuz), I rebooted the machine.
It booted partially, then stopped with the error message
"K
Hello:
Could you help me? I have a message when I boot my Debian Linux
system that says:
kernel panic:EXT2-fs panic(device
03:02):ext2_read_inode:group>=group count
"TONY ANG" <[EMAIL PROTECTED]> writes:
> 1. [ ] text/plain [*] text/html
(Please post just in plain text.)
> Now,I cannot boot from HDD as I did normally. I tried booting from F.Disk but
> I have this Msg" Kernel panic:VFS:Unable to mount root fs on 03:06 " Can you
> please
HI, good-day,
I am Tony from Singapore. I must bought a
Special Edition -Using Linux with 3 CD.
Firstly, I have successful install >From CDs
Linux to run on my New 4.3 G HDD. Because I am a new user, the system got hanged
after a few session of practice.
Now,I cannot boot from HDD as I did
On Sat, Sep 19, 1998 at 11:41:24PM +0200, Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
> > VFS: Can't open root device 03:01
> > Kernel Panic: VFS unable to mount root fs on 03:01
>
> Sounds like you
On Sat, Sep 19, 1998 at 03:41:47PM -0500, Mark Panzer wrote:
> > What do these messages mean, what have I done to myself, and how can I undo
> > it?
> >
>
> Next time also try to use the kpkg utility, all you do is enter the
> source directory enter kpkg and it creates a .deb of the kernel (well
In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
> VFS: Can't open root device 03:01
> Kernel Panic: VFS unable to mount root fs on 03:01
Sounds like you didn't compile in the driver for your harddisk. You
did compile in (not as module) the IDE drive
In article <[EMAIL PROTECTED]>,
Samuel Landau <[EMAIL PROTECTED]> wrote:
>dear mister, that's the orginal doc from de kernel source, not the
>Debianized one.
>well, with Debian there are some more files that are necessary for the
>kernel to work
>(e.g. : /boot/SystemMap)
That's nonsense. I have ne
> VFS: Can't open root device 03:01
> Kernel Panic: VFS unable to mount root fs on 03:01
strange
maybe you compiled the root fs as a module (which is not to be
done), but how would you boot?...
ah there's the answer:
> I installed the 2.0.34 kernel source pa
system won't reboot. The kernel loads, then, after about 3/4 of a
> screen of normal startup messages, the system halts with:
>
> VFS: Can't open root device 03:01
> Kernel Panic: VFS unable to mount root fs on 03:01
>
You might be making your kernel too simple
fter about 3/4 of a screen
of normal startup messages, the system halts with:
VFS: Can't open root device 03:01
Kernel Panic: VFS unable to mount root fs on 03:01
What do these messages mean, what have I done to myself, and how can I undo it?
I installed the 2.0.34 kernel source pa
bread failed
> attempt to access beyond end of device
> 03:03: rw=0, want=2, limit=0
> isofs_read_super: bread failed, de 03:03 iso_blknum 16 block 32
> Kernel panic: VFS: Unable to mount root on 03:03
>
If I booted from floppy everything worked well. Then I tried to copy my
original
Hello:
I recently installed Debian 1.3.1 that I purchased from Linux System
Labs. I have had several problems, and cannot seem to find the
answers.
I installed the system by booting from a floppy and installing the
base system from cdrom. (My cdrom is bootable; the cd is bootable,
but for some
Solved! The problem was a Kernel panic error on startup, just after resetting
the SCSI bus. Many thanks to Peter S. Galbraith, Bob McGowan, and Nathan Norman.
Norman both identified the problem as "the (in)famous AHA-2740/2840 boot
failure". He offered to build me a kernel but said h
r(0x1):
> : Illegal Host Access
> : Kernel panic: scsi0: BRKADRINT, error 0x1, segaddr 0x0.
>
> Hmm, this sounds like the (in)famous AHA-2740/2840 boot failure.
>[...]
> The solution is to use a rescue disk with only the drivers you need.
I'm using Debian 1.3, and had to bu
On 21 May 1998, Paul Mackinney wrote:
: Booting for the first time from recovery disk, I get the following
: error just after it resets the SCSI bus:
:
: aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
: scsi0: BRKADRINT error(0x1):
: Illegal Host Access
: Kernel panic: scsi0
Booting for the first time from recovery disk, I get the following error just
after it resets the SCSI bus:
aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
scsi0: BRKADRINT error(0x1):
Illegal Host Access
Kernel panic: scsi0: BRKADRINT, error 0x1, segaddr 0x0.
The system is an HP
be 0x300...
You're confusing address and device I think. lilo is talking devices:
major 3 minor 0 is hda; i.e. it can't read the partition table on the
1st IDE disk.
In an earlier message, I think you mentioned a kernel panic implying that
your floppy kernel was trying to boot from device 03:0
901 - 1000 of 1036 matches
Mail list logo
