newbie issues....kernel panic...desparatly in need of assistance...
full installed slackware ISO cd with all packages, no errors.
previous OS: WinMe, WinXP hard drive: IDE, 30gig: /dev/hda1 - swap, 1gb /dev/hda2 - root, 29gb, ext2. upon reboot, after the boot menu, i get pages and pages of junk, too fast to read. the last screen, where it freezes, displays all this (without the line breaks): EXT3-fs: unable to read superblock hda1: bad access: block=2 count=2 end_request: I/O error, dev 03:01 (hda), sector 2 EXT2-fs: unable to read superblock hda1: bad access: block=0 count=1 end_request: I/O error, dev 03:01 (hda), sector 0 FAT: unable to read boot sector UMSDOS: msdos_read_super failed, mount aborted. hda1: bad access: block=0 count=1 end_request: I/O error, dev 03:01 (hda), sector 0 FAT: unable to read boot sector hda1: bad access: block=0, count=1 end_request: I/O error, dev 03:01 (hda), sector 0 FAT: unable to read boot sector hda1: bad access: block=64, count=2 end_request: I/O error, dev 03:01 (hda), sector 64 isofs_read_super: bread failed, dev=03:01, iso_blknum=16, block=32 hda1: bad access: block=128, count=2 end_request: I/O error, dev 03:01 (hda), sector 128 read_super_block: bread failed (dev=03:01, block 64, size 1024) hda1: bad access: block=16, count=2 end_request: I/O error, dev 03:01 (hda), sector 16 read_super_block: bread failed (dev=03:01, block 6, size 1024) Kernel panic: VFS: Unable to mount root fs on 03:01 i tried all three lilo locations, still the same error after boot menu. |
did you install lilo in the mbr
|
yes.
|
ide-kernel on a SCSI-box? =)
Cheers, Tink |
nope, i don't have anything that's scsi.
|
for it to go through the filesystems like that it is just not seeing a linux filesystem on there.
maybe use lba32 in lilo.conf |
umm...not to be retarded but...im totally new to linux, how do i do that?
|
first you will need to access it, since it's not booting you may need to get a root boot disk so you can boot it up and make some changes.
try this first... hit tab at the boot menu, if it does not show the command promt and a list of images then hit ctrl_x then using an image name from the list do this... imagename root=/dev/hda1 if that fails try it with hda? until you have tried several of them if you have another drive try it starting with /dev/hdb1 |
Which drive is the swap ?
|
okay. i repartitioned to remove the swap, and ran
fsck -y -v -f /dev/hda1 which a friend suggested. there have been like a million errors so i hope it fixes them... current config: /dev/hda1 = / |
once this finishes, i'm probably going to repartition it again to add the swap again, then re-run fsck and e2fsck. (i removed the swap in the first place because fsck had alotta problems checking it)
here will be the configs: /dev/hda1 - swap - 1gb /dev/hda2 - / - 29gb |
is the hard drive bad? linux is not very forgiving on bad hard drives.
|
the hd was working just fine before i installed linux, and the check/format didnt report any errors.
okay, finished all the fsck runs....one directory kept on being corrupt though, so i went ahead and repartitioned as stated in my above post, then ran fsck -y -v -f /dev/hda1 and got this: the filesystem size (according to the superblock) is 7474233 blocks the physical size of the device is 248999 blocks Either the superblock or the partition table is likely to be corrupt! Abort? yes (back to prompt) suggestions? |
my guess is you need to turn of drive translations in the bios
|
full installed slackware ISO cd with all packages, no errors.
previous OS: WinMe, WinXP hard drive: IDE, 30gig: /dev/hda1 - swap, 1gb /dev/hda2 - root, 29gb, ext2. upon reboot, after the boot menu, i get pages and pages of junk, too fast to read. the last screen, where it freezes, displays all this (without the line breaks): EXT3-fs: unable to read superblock hda1: bad access: block=2 count=2 end_request: I/O error, dev 03:01 (hda), secto It looks like the kernel / lilo is trying to mount your swap instead of your root drive. |
try this
linux root=/dev/hda2 |
okay, with a little help, i finally got it working.
i had to use several instances of fsck, e2fsck, and cfdisk to repartition and wipe the errors from the hd (there were hundreds...) and reinstall slack. finally got it working! thanx! :) |
All times are GMT -5. The time now is 07:12 PM. |