SlackwareThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I dont know how much help I can be here but 1 thing:
Stay away from the floppies if you can. You dont need them. This will only frustrate you more.
When you format the linux partition I hope you do a full format not just a quickie.
Post your system spec.
I also hope you are not doing an expert install. You may leave out dependencies if you do this.
Go with a complete user friendly install.
Also, please use this time to re-evaluate your partition size.
You have the time now to reconcider this as you have not installed and set up your system fully yet. 5GB is more than enough, but if you want to install lots of 3rd party apps, games etc....
you should make this partition bigger.
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
Well, since the partition can't be mounted, try putting a filesystem it and mounting it manually before running setup:
mke2fs /dev/hdb1
mount /dev/hdb1 /mnt
Do the errors still persist?
Btw, installing in the expert mode won't hurt. I did it the first time and whenever I'm missing a dependency I just put the CD in the drive and installed the corresponding package
ok.
paulinimus -
my sys specs are: AMD Duron 1GHz, 60GHz hdd running XP, 20 GHz hdd for slackware, 256MB RAM as posted in the initial post.
I will do everything I can to stay far, far away from the floppy install disks as I can =)
I have tried both the quick format and the more thorough format.
I have tried full install, and newbie install.
My choice of partition sizes is based on the fact that this install was meant to be proctice for a later install I plan on doing on an old laptop (Compaq Armada 1120T)
wpyh -
I tried your commands. After typing in the first command (mke2fs /dev/hdb1) I got a response. The second command... should it be mount /dev/hdb1<space>/mnt or mount /dev/hdb1/mnt? I tried both. When entered with the space, I got an error message that said that it could not find mount in etc/fstab (or similar...It's a little hazy now). when entered with a space, I got no response, just a new prompt. Either way, it didn't work. When reaching the install portion of the setup I still start getting fatal errors almost immediately.
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
Well, what response did you get after "mke2fs /dev/hdb1"? Was it some numbers etc? If yes then it should be right... Anyway, can you post it here? This command is for putting a filesystem on the partition /dev/hdb1 (DOS/Windows-speak: format).
The second command is "mount /dev/hdb1 /mnt". There is a space in between, as we are telling the system to mount the filesystem in /dev/hdb1 to the directory /mnt. If there's no response and you get back at the prompt it should mean that the mount is successful. To verify it, type "mount" with no parameters. It should say something like:
/dev/hdb1 on /mnt type ext2 (rw)
If after all these, you still get the errors... well, why not try repartitioning your disk? I mean, do a:
dd if=/dev/zero of=/dev/hdb
(this will wipe everything in /dev/hdb!!!)
Then use fdisk to partition it:
fdisk /dev/hdb
(fdisk will complain about invalid partition table and such, but don't worry, it will automatically build a partition table)
If you don't know how to use fdisk, it should be pretty straightforward: it tells you to give the 'm' command for help.
ok, so...
when I used themke2fs/dev/hdb command i got:
mke2fs 1.34 (25 - Jul-2003)
Filesystem
OS type Linux
Blocksize = 4096 (log = 2)
and so on regarding superblocks and such...that command worked and so did the mount command...however...
I tried reformatting the drive using fdisk and then running setup...no luck
tried reburning the ISO as the slowest speed possible...no luck
<sigh>
The real depressing part is...I haven't even started trying to tweak my hardware settings yet =)
any and all theories welcome as to why this is happening.
Thanks
melee
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
Cedrik:
Boot floppies won't help. This user has a problem with installation, not with booting.
melee:
Anyway, what are those errors? Please take a look at them more closely. Are they along the lines of "No space left on device" or such?
Maybe your disks are bad... You can actually check the isos with md5sums:
2464f68acde7b4ad197e2a77a5ac5dc9 slackware-10.0-install-d1.iso
39517cd115ef8cd0a4d56d21cd6266de slackware-10.0-install-d2.iso
51896df07759e240b612aa526be099c4 slackware-10.0-source-d3.iso
53ad523e79fe422b43bbe3637030baed slackware-10.0-source-d4.iso
wpyh -
My checksum is identical to the one you posted (I only checked checksum for disc 1 as I haven't even gotten to disc 2 yet) The errors that i am recieving are as follows:
There was a fatal error attempting to install /var/log/mount/slackware/a/aaa_elflibs-9.2.0-i486-1.tgz 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 may hit enter to continue if you wish, but if this is an important required package then your installation may not work as-is.
and the same for:
/var/log/mount/slackware/a/apmd-3.0.2-i386-1.tgz
I'm sorry for bringing my story here but I have the similar problem as the melee so I decided to post here insted of to open a new topic.
Here is my situation:
HD = 120GB and I have Xp and some remains of Yoper 2.0 installed.
There is no way I could back-up the files even right now I think that hd format is the only way to solve the problem.
So I had Yoper 2.0 installed and decided to change and work on Slackware. So, I deleted ext2 partition where Yoper was installed and i made it again.
During the installation I get this error:
"Installpkg error #1
There was a fatal error attempting to install
/var/log/mount/slackware/a/coreutils-5.2.1-i486-1.tgz
..."
When I press enter, new error wil pop-up.
The thing is, when I reboot, I still get Lilo askong me to chose Yoper / win2k.
So does anyone have any idea how could I solve my problem? Hd format is not an option for now.
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
Um... ok, so do you two know how to configure a Linux system? If you do, you can just install the packages by hand...
But if you don't (I don't :P) I think you should try this:
1. Boot from the CD
2. Mount /dev/hdb1 (or whatever partition it is) on /mnt
3. Mount /dev/hdc (the cdrom, or whatever else it is) on /cdrom
4. Go to /cdrom (it will go to /var/log/mount instead because /cdrom points to /var/log/mount and the shell doesn't hide this)
5. Go to directory slackware
6. Here you will find a few directories like a, ap, d, e, ... These are the package directories.
7. I presume you have at least 3 GB on your partition. cd to each directory and install the packages found there. This is a long job, especially since the shell is so stupid that I can't figure out how to do a loop :P for each package, do a:
installpkg -root /mnt <pkgname>
(Replace <pkgname> with the package name, which should end in .tgz)
8. Go to the root directory again, and run setup. Go through the install steps, but don't format your partition :P and don't install any packages, i.e. use the 'expert' mode but deselect all packages.
Please note that you should run the configuration step in the setup program
well.. I got to step 3 before seeing an error message...seems like a new record for me. When trying step 3 I got the error message that the cdrom was mounted as read only. When I tried step 4 it said that I didn't have permission to access /cdrom. I'm starting to think that this wasn't meant to be.
melee
Distribution: Slackware 9.1 but FUBAR with packages I compile myself, and OpenBSD (not exactly a distro) on QEMU
Posts: 153
Rep:
Well, so you got this:
mount: block device /dev/hdc is write protected, mounting read-only
(or whatever you got for /dev/hdc)
It's not an error, just a warning. Of course it's read-only, it's a CD
But you can't access the /cdrom directory? Weird... Did you log in as root, by the way? I mean, when prompted login: then you should press [Enter]...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.