Slackware Installation Problems


Recommended Posts

Ok, im a noob but i wanna have a go at slackware. My partitions are: 1gig swap, 10 gig /, 10 gig /home, 10gig /opt... hehe lotsa room on hard drive. During installation, it either:

1) freezes at a random package

2)gives me a segmentation fault at random, or

3) gives me installpkg error #39 /var/log/mount/slackware/*/* The package may be corrupt, the installation media may be bad, or something else has caused the package to be unable to be read without error. You man hit enter to continue if you wish, but if this is an important required package then your installation may not work as-is. again at random

(at least i think its all random) im installing from cd drive, and i checked the md5 sums and they match. ive tried at least 7 times!!

Link to comment
Share on other sites

sounds like a hardware failure. From your description I'd either blame it on insufficient power supply, or dying cd-rom. Course it could also be ram, cpu, mobo or hard disk, but I'd test those last.

Link to comment
Share on other sites

Fdisk is okay to partition, but did you fsck your partitions? maybe they are corrupt.

Maybe you should try simplifying your partitions scheme and seeing if that works.

Link to comment
Share on other sites

Is that a complete list of your partitions?

Also, 1G is excessive for a swap, I would recommend about 300-600MB for most modern systems. Not sure what (if any) ill side effects you will have for a 1G swap.

And, there really is no need to separate each directory into its own parition. /boot and / and swap are common. I also see /home set apart by people who like to load a lot of different distros and other major changes. A separate /home allows the Linux install to format everything else and load, and leave /home untouched. Cool trick! :cool:

I think that separating all of your directories can lead to problems should you end up putting more in one than anticipated, and the system cannot just float that space from another partition/directory. Having a very large / directory will allow you to share all the space wherever is needed.

As for your problem (yes, I am getting to that...), try running memtest86. It will run and test your memory chips. You have to boot into it (and it may be included on your CDs, so you can boot off of CD, and run memtest86. It is a cyclical program that never terminates on its own. Let it run for quite a while and see what it turns up (overnight is good).

Link to comment
Share on other sites

As for your problem (yes, I am getting to that...), try running memtest86.  It will run and test your memory chips.  You have to boot into it (and it may be included on your CDs, so you can boot off of CD, and run memtest86.  It is a cyclical program that never terminates on its own.  Let it run for quite a while and see what it turns up (overnight is good).

so do i just boot the slackware cd and then type it into where it says boot kernel or something? cause i cant get it to work

and for the fsck it says that the superblock could not be read or does not describe a correct ext2 file system.

Link to comment
Share on other sites

so do i just boot the slackware cd and then type it into where it says boot kernel or something? cause i cant get it to work

and for the fsck it says that the superblock could not be read or does not describe a correct ext2 file system.

Personally, I have never had a hard drive problem (so far!), but if I did, I imagine it would sound like "the superblock could not be read or does not describe a correct ext2 file system". :pinch:

As for memfree86, when you boot off your CD1, there should be an option for 'help' or maybe 'more info', or something like that. It may list some of the utilities that can be run from the CD.

Link to comment
Share on other sites

im gonna try again, i took out 2 sticks of ram since i mixed and matched them. (i know thats bad) so i only have a 256 stick now. hope this works

Link to comment
Share on other sites

im gonna try again, i took out 2 sticks of ram since i mixed and matched them. (i know thats bad) so i only have a 256 stick now. hope this works

Did you do anything about your suspect hard drive?

Perhaps repartition and format, then fsck them again.... I think your problem is in the drives, based on your earlier message about the superblock.

Link to comment
Share on other sites

Yippie!!!!!!!!!!!!!!!!!! Im so happy!!!!! after replacing the ram, the installation worked!!!! thank you very much for your time, and ill check my hard drives now. ugh... when i load up my computer, grub loads up but i thought i set up lilo

Link to comment
Share on other sites

grub loads up? Slackware 9.1 installs Lilo. Are you sure you installed lilo to the MBR?

I can't seem to get LILO install it always say edit the /etc/lilo.conf But it's not there. Don't know what the problem.

Link to comment
Share on other sites

Make sure you follow the install steps, Alvin. Install the header, install your linux partition(s) then your DOS partitions. then Install Lilo to the MBR. Also, make sure you don't have spaces in the label names.

Example:

Don't use "Slackware 2.6.4"

Use "Slackware2.6.4" instead

Link to comment
Share on other sites

running /sbin/lilo wouldn't work anyway if you had spaces.

just make sure you run it after editing your lilo.conf and most likely, all images will be added to the mbr.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.