• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 368
  • Last Modified:

kernel poanic...bread failed?

cannot get into linux (I'm anew User)at end of bootup the folowing message appears: attempt to access beyond end of device 03.05 rw=0 want=2 limit=0 ext2-fs; unable to access beyond end of device 3.05 rw=0 want=33 limit=o isofs_read_super bread failed dev.03.05 iso. blk num=16 block 32 kernel panic vfs:unable to mount root f.s.on3.05 what the hell does this mean?
  • 2
1 Solution
For me it meant reinstalling Linux after making some minor changes.  I have a 486 with 80 mb of memory installed but it is flakey. I'm using RH 6.0 so when I got the same message you got I reinstalled it on that box and I sepcified a lower amount of ram each time until I found where it would install reliably. Maybe it was just coincidence, but it seems to work.

When the computer first boots the install (either from the CDrom or boot floppy) you get the "boot" prompt. I typed 'linux mem=72M' or 'linux mem=32M' and so on until I found the upper limit of reliable memory (the box was assembled from scraps and I mixed FP and EDO and you aren't supposed to do that but it sometimes works).  Just trial and error. After you find the right amount of good ram you can enter that on the append line at the lilo bootloader install prompt the same way -- 'linux mem=48M" and then you won't have to type that when you boot the machine.

I got the same message on another box with an AMD6 processor until i disabled cache memory in the bios. Again, Linux appeared to install OK but would never boot up and it would report the same kernel panic, bread etc, when I tried to boot it right after install.

I had the same message (and sometimes the install would exit too with a "signal 7") on my third scrap pile computer with a Cyrix MII300 processor until i quit overclocking it.

So whether it's it's the right thing or not, you might look at your memory, your cache and also whether or not you are deliberately or inadvertently over clocking your processor.
Hi.  You did not mention which kernel version and distribution you are trying to install from.  That would be helpful information for us.

This problem is the result of memory corruption.  Such corruption can occur due to hardware problems OR be the result of a bug that seems to have been introduced in kernel 2.2.10ac12 and carried forward (it has recently been corrected in the 2.3 development kernels).  Hardware is the more likely culprit.

If the distribution you are trying to install uses a fairly current kernel (2.2.10 or later) then the kernel might be responsible.  Note however that the kernel manifestation of this problem is exceedingly rare.

Two suggestions come to mind: 1) make sure your hardware is ok (does the distribution install ok on other machines that you have available?), 2) use a slightly less current distribution (i.e. Red Hat 6.0 rather than 6.1, and so forth with other distributions).

Good Luck!
I remembered one other circumstance that caused this problem:  the wrong boot disk.  I set up one box with such a small hard drive that I didn't want to allocate any space for LILO and was booting from a floppy.  I got mixed up in the clutter of junk on my work bench and put in a boot floppy that instructed Linux to boot hda5 as root instead of hda1 as this particular machine was configured.  It did the same thing yours did.  Since I was in a hurry and didn't want to take the time to rummage around for the proper disk, I rebooted the computer and at the boot prompt I typed "linux mount root=/dev/hda1" -- and that worked fine. So watch the screen while it boots and see if LILO is attempting to mount root on the wrong partition.
normaeonAuthor Commented:
take the points for effort--this problem cleared up due to i dont know what aftter repeated install and right configuration---even so i had an unsupported video card which i have changed.

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now