gday-

So, I wanted out of systemd and a flaky e17 install amd I wanted GPT using UEFI, because its there on the laptop, long devoid of windows. Unfortunately, I've had nothing but failures with slackware 14.2, to wit:

(Note: all ISOs md5'd ok.)

-tried an alien bob live stick with current, install went through to end, grub failed, reason unknown, tried configuring elilo, failed. USB boot stick created ok. Odd, it booted with elilo built in - that was the last I saw elilo work. There were errors in the logs indicatiog errors unmounting /sda1 but that was greek to me. Not a good start but I got somewhere - thought it may be better from a DVD, so

-went to a couple dvd installs: tried 2 different ISOs, both burned with brassero. both failed to complete, both with "No space left" errors, both current/huge kernels.

-got a 14.2 ISO from LQ, dd'd it to USB stick - boots but "No space left" errors here as well.

Thats where I'm at right now - at a loss. 2 days googling, answers all over the map, nothing definitive except for being out of inodes (?), all of which were taken by tmp files, but no solutions were offered anywhere in the open.
I'm using GPT with 3 partitions: sda1-EFL/100mg/vfat, sda2-swap/8g, sda3-fs/290g.

I'm figuring if I can't get this far, going the compile route will put me over the edge. There is something I'm missing here which so far is beyond my comprehension. Slackware docs may have something but I haven't found it, google is a nightmare.

So I'm going to bed now but will be back in A.M. with my helmet on in hopes of getting a tow out of this ditch I fell into.

Can someone start me off with what info might be must useful to post here as a starter?

This is stupid...

Hi,

Here is a good source for Slackware-Live; http://bear.alienbase.nl/mirrors/slackware-live/latest/

You probably got an 14.1 ISO with source so that will not fit on DVD. Here is a 14.1 install DVD 2.3GB; https://mirrors.slackware.com/slackw...nstall-dvd.iso

14.1 MD5; https://mirrors.slackware.com/slackw...ll-dvd.iso.md5

14.2 install DVD 2.6GB; https://mirrors.slackware.com/slackw...nstall-dvd.iso

14.2 MD5; https://mirrors.slackware.com/slackw...ll-dvd.iso.md5

When you burn the image, I suggest that you use a speed of X4 and be sure to check the burnt image.

If you want help for Slackware Live then I suggest that you look at docs; https://docs.slackware.com/slackware:liveslak?s

Good Slackware Live download sites; Hope this helps.
Have fun & enjoy!

1 members found this post helpful.

Onebuck replied:

"Here is a good source for Slackware-Live; http://bear.alienbase.nl/mirrors/slackware-live/latest/"

No, I've been there multiple times - I got 14.2-current ISO with a huge kernel, of which there are 2 types but I forget which is which ATM - it ran out of room.

Its the inodes I think but am just getting into that. Maybe an addition to fstab to state volume for tmpfs is the way - just hit that this A.M.

"14.1 MD5; https://mirrors.slackware.com/slackw...ll-dvd.iso.md5"

As stated, all the check sums were fine...

"14.2 install DVD 2.6GB; https://mirrors.slackware.com/slackw...nstall-dvd.iso"

This is one that failed for me as well...

<snip>
"
"When you burn the image, I suggest that you use a speed of X4 and be sure to check the burnt image."

Tad late for that - I used brassero for the burn (could have used dd I think but wasn't into making too many coasters) but that package automagically verifies burns...

"If you want help for Slackware Live then I suggest that you look at docs; https://docs.slackware.com/slackware:liveslak?s[]=slackware&s[]=live"

I wasn't looking for the slack live version - the term live as slack uses it is different than most casual users use of the term "live' - thats OK except I don't need a stick to carry around to show my friends. The live installed - only one that did - but 2 bootloaders failed. It was here I saw the "/sda1 umount" error in logs. I might have persued that but decided to make coasters instead - need 'em for coffee...

"Good Slackware Live download sites; Hope this helps.
Have fun & enjoy!"

Thanks for the links and your help...

The "No space left" errors during installation are an indication of a wrong target. Instead of installing to your harddrive, it looks like you are installing into the installer's RAM drive.
When installing Slackware, and before running the "setup", you are expected to use fdisk or cfdisk or parted to create the partitions on your harddisk that you want Slackware to use (at a miminum that would be one partition for swap, and one partition for the root filesystem). Be sure to assign the proper partition type to the partitions you create or else the installer will not know what partition to use for swap, and what to use for the root filesystem.

Your remark about "errors unmounting /sda1 but that was greek to me" make me think that maybe you are not even aware of disk devices, their names and the fact that you have to create these partitions yourself? No offense meant if I am underestimating your knowledge levels. Yust give us more data to process... what steps did you follow after booting the installation disk, what exact URL did you use to download an ISO, etc...

3 members found this post helpful.

Hi,

Thanks, Eric!

I was thinking about the point; After reading your post then I thought along the lines you pointed out it does make sense.

I think a lot of new Slackware users should learn to rely on; https://docs.slackware.com/start At least the new user who can read!

I also believe new users at LQ should be required to read; https://www.linuxquestions.org/quest...#faq_lqwelcome

Appreciate your feedback.
Have fun & enjoy!

[QUOTE=Alien Bob;
<snip>
"When installing Slackware, and before running the "setup", you are expected to use fdisk or cfdisk or parted to create the partitions on your harddisk that you want Slackware to use (at a miminum that would be one partition for swap, and one partition for the root filesystem). Be sure to assign the proper partition type to the partitions you create or else the installer will not know what partition to use for swap, and what to use for the root filesystem."

I noted in my orig post what my partitions were, set before "setup". But I did wonder when installer says "There don't seem to be any partitions..." when I enter the "Target", it then went on to tell me I have swap and EFI, which I had set already, and REformats what I have already done and then it adds "/dev/sda1 /boot/efi vfat defaults 1 0" to fstab, which sounded right but the venue seemed awkward and my /sda3 wasn't addressed at all, not that it had to be but the installer said I didn't seem to have any linux partitions.

What am I missing there?

"Your remark about "errors unmounting /sda1 but that was greek to me" make me think that maybe you are not even aware of disk devices, their names and the fact that you have to create these partitions yourself?"

see above - I know what a partition is. I have no knowledge of what the /sda1 umount problems in the log were - it was my 1st and only successful install so far (sorta, kudos to alienb) and googling it wasn't fruitful so I tried another venue.

I don't know what installer allows disc space to run out without so much as a never-you-mind.

"No offense meant if I am underestimating your knowledge levels."

none taken but your assumptions are a bit off. I didn't fall off the potato truck last night...

As stated previously, the "live" usb came from aliebbob's site. The 14.2-currents were from here and a mirror I'd have to look up - I don't take notes when I stay in the neighborhood.
I'm perfectly happy to take the blame, I just don't know where my error is. Installing to the installers ramdrive sounds impressive but I'm not that smart

"I was thinking about the point; After reading your post then I thought along the lines you pointed out it does make sense."

I eagerly awaiting your assistance on this - should be illuminating...

"I think a lot of new Slackware users should learn to rely on; https://docs.slackware.com/start At least the new user who can read!

I also believe new users at LQ should be required to read; https://www.linuxquestions.org/quest...#faq_lqwelcome"

I have been there and also to
http://www.therockgarden.ca/aolsfaq.txt

Maybe you could be so kind to point out where in any of those links running out of inodes and/or disc space is addressed.
If you can't add to the solution, why not just leave it there and troll someone else.

HAND

'Here is a good source for Slackware-Live; http://bear.alienbase.nl/mirrors/slackware-live/latest/"

Thats is where I got mine, thanks...

"You probably got an 14.1 ISO with source so that will not fit on DVD."

And you probably skipped reading comprehension in school - that comment really was unnecessary and impossible to do to boot (get it? boot? probably not...)

Maybe something to do with the hardware? What are the hardware specs?

Did you make your /dev/sda3 partition using the Slackware installer and cdfisk, or was it a partition that you already had on the drive? My guess is that it's not tagged as a Linux type partition, and that's why "setup" is rejecting it.

If it's a partition you had before, I'd try running cdfisk, deleting the partition, and making a new one.

lenovo t530 thinkpad corei5 8G ram 300G HD, hybrid Intel/nVidia graphics.
Does what it has to

[QUOTE=volkerdi;5871945]"Did you make your /dev/sda3 partition using the Slackware installer and cdfisk, or was it a partition that you already had on the drive? My guess is that it's not tagged as a Linux type partition, and that's why "setup" is rejecting it."

I used gdisk. What rejection are you referring to??

<snip>

FYI, you're missing your closing quote tag [/quote]

If you didn't set the partition type to Linux, I don't believe the Slackware installer will recognize it (possibly to prevent you from accidentally installing Slackware on an NTFS or some other partition). To do this, you'd open up gdisk, type "t" for partition type, then select your root partition, and then type 8300 to select Linux Filesystem. Finally press "w" to save and exit.

I used type 8304 - linux 86-64 root - I'm calling it /.

Try using type 8300 instead, for all your linux partitions. 8304 has something to do with automounting which is supported by systemd any may be the issue here.