Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
11-27-2002, 07:51 PM
|
#1
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Rep:
|
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.
Last edited by Rio Nishida; 11-28-2002 at 05:53 PM.
|
|
|
|
11-27-2002, 07:53 PM
|
#2
|
|
Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,154
Rep:
|
did you install lilo in the mbr
|
|
|
|
11-27-2002, 07:56 PM
|
#3
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Original Poster
Rep:
|
yes.
|
|
|
|
11-27-2002, 09:32 PM
|
#4
|
|
Moderator
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,903
|
ide-kernel on a SCSI-box? =)
Cheers,
Tink
|
|
|
|
11-27-2002, 10:23 PM
|
#5
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Original Poster
Rep:
|
nope, i don't have anything that's scsi.
|
|
|
|
11-28-2002, 02:38 AM
|
#6
|
|
Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,154
Rep:
|
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
|
|
|
|
11-28-2002, 11:55 AM
|
#7
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Original Poster
Rep:
|
umm...not to be retarded but...im totally new to linux, how do i do that?
|
|
|
|
11-28-2002, 12:57 PM
|
#8
|
|
Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,154
Rep:
|
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
|
|
|
|
11-28-2002, 04:31 PM
|
#9
|
|
Member
Registered: Nov 2002
Distribution: Slackware
Posts: 155
Rep:
|
Which drive is the swap ?
|
|
|
|
11-28-2002, 04:51 PM
|
#10
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Original Poster
Rep:
|
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 = /
|
|
|
|
11-28-2002, 04:54 PM
|
#11
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Original Poster
Rep:
|
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
Last edited by Rio Nishida; 11-28-2002 at 04:55 PM.
|
|
|
|
11-28-2002, 05:25 PM
|
#12
|
|
Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,154
Rep:
|
is the hard drive bad? linux is not very forgiving on bad hard drives.
|
|
|
|
11-28-2002, 05:41 PM
|
#13
|
|
LQ Newbie
Registered: Nov 2002
Location: Nowhereville, Kentucky
Distribution: Slackware...if i can get it to work.
Posts: 10
Original Poster
Rep:
|
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?
|
|
|
|
11-28-2002, 10:16 PM
|
#14
|
|
Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,154
Rep:
|
my guess is you need to turn of drive translations in the bios
|
|
|
|
11-28-2002, 11:21 PM
|
#15
|
|
Member
Registered: Nov 2002
Distribution: Slackware
Posts: 155
Rep:
|
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.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 04:16 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|