[WORK AROUND] Slackware64-current install fails - packages fail to install.
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
[WORK AROUND] Slackware64-current install fails - packages fail to install.
I tried to install current from DVD and after a few packages get installed, the rest of the packages fail to install with an "error 1". It says the media is corrupt or disk is full.
I "df -h" and the install disk at 0% usage so, I assumed the DVD image was bad.
I downloaded the mini-install disk and used kernel.org's http and it does the same thing. Installs a few packages and then dies with "corrupt media or disk full" error. Again, the install directory is 0% disk usage. I tried a different mirror and the same thing happens.
If you're planning to install Slackware using packages on a local hard disk
partition, or from a NFS/HTTP/FTP server, you don't need a full-blown CDROM
to boot from.
This mini-ISO image of 40 - 70 MB in size contains everything to let you
do the above, and nothing more than that.
The script that was used to create the ISO image can be found here:
Could you post exactly what you have downloaded, how you burned the DVD including the software you used. Did you do a md5sum check on the downloaded .iso file?
AFAIK, the mini install is for current only. Is your intention to install current?
"It sounds like your hard drive, or at least the partition you are installing to is full" - Nope DF shows none of the partitions are full or even close to being full (except SR0).
"Did you do a md5sum check on the downloaded .iso file?" - no because the FTP/HTTP install fails the same way as the DVD install.
"Is your intention to install current?" - yes.
"What is the full url/directory-path your entering for the install?" -
I used setup and chose /dev/sda2 (sda1 is the EFI partition).
For the source on the FTP install, I chose http://mirrors.kernel.org/slackware/...nt/slackware64. The source URL/path is correct becuase it found the packagelists, tag files and installed SOME of the packages.
It's not a hardware problem because Linux Mint and FreeNAS both installed fine.
You are trying to install Slackware from one of AlienBob's liveslack iso's. You need to follow one of the methods described here -->http://docs.slackware.com/slackware:liveslak in order to have success with installing from live Slack.
I have done the method described as PXE booting the Live OS using my Rasberry Pi as a NFS server. I have also done an install using the method "Using the Live OS to install Slackware to hard disk".
Both methods worked for me. You do have to follow the instructions as stated.
I tried to install current from DVD and after a few packages get installed, the rest of the packages fail to install with an "error 1". It says the media is corrupt or disk is full.
I "df -h" and the install disk at 0% usage so, I assumed the DVD image was bad.
I downloaded the mini-install disk and used kernel.org's http and it does the same thing. Installs a few packages and then dies with "corrupt media or disk full" error. Again, the install directory is 0% disk usage. I tried a different mirror and the same thing happens.
Anyone have any ideas about this?
Could it be that by accident you are not installing to your hard drive partition but instead into the RAM disk in which the installer is running? That would explain the fact that after a couple of packages have been successfully installed, the remainder fails - such a thing would happen when the RAM disk capacity is eventually used up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.