LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 06-09-2015, 07:33 AM   #1
pzognar
Member
 
Registered: Jun 2015
Distribution: Debian Jessie 64
Posts: 163
Blog Entries: 9

Rep: Reputation: Disabled
Slackware fails to install from USB stick


Slackware 14.1 fails to install from USB stick. It boots from the stick but will not install.

Setup begins as it should. Setting up partitions appears to work fine. Setting target works as it should. The problem is that the installer cannot find the files to install from. Hello, Slackware, that USB you booted off of? You remember that one? Yeah, that one. About that one ... the files you want to install, the ones you can't find? They are there!

So how do I tell Slackware that?

note:

Already tried:

1. Having it automatically search for cdroms. I had figured tht the USB would appear as a large cdrom but apparently not.

2. giving Setup the path to the mounted USB as if it were a hard drive with files to install. That failed. After about one half-second, it claimed that the entire install was all done. Examination after the fact confirmed that nothing was actually copied in.
 
Old 06-09-2015, 10:02 AM   #2
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,656

Rep: Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836
create a new directory such as /usbinstall, mount the usb to new directory, do not use /mnt. select premounted option and path to files during source selection. If the installation files is a iso.file will have to create a second new directory to mount the iso.file on.
 
Old 06-09-2015, 10:56 AM   #3
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,480

Rep: Reputation: Disabled
When you see a dialog box whose title is SOURCE MEDIA SELECTION it displays:

Please select the media from which to install Slackware Linux:

Below it proposes you, among a choice of several sources, this one:

Install from a Slackware USB stick

If you didn't already, try it.

PS: what command did you use to copy the files over the USB stick? And what ISO did you use? That should have been this one:
http://mirrors.slackware.com/slackwa...nstall-dvd.iso for 32-bit
or this other one:
http://mirrors.slackware.com/slackwa...nstall-dvd.iso for 64-bit.

Last edited by Didier Spaier; 06-09-2015 at 11:09 AM.
 
Old 06-09-2015, 12:13 PM   #4
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,656

Rep: Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836
Quote:
Please select the media from which to install Slackware Linux:

Below it proposes you, among a choice of several sources, this one:

Install from a Slackware USB stick
I keep forgetting that the install from usb option was added. lol
 
Old 06-10-2015, 03:19 PM   #5
pzognar
Member
 
Registered: Jun 2015
Distribution: Debian Jessie 64
Posts: 163

Original Poster
Blog Entries: 9

Rep: Reputation: Disabled
1. Install from USB stick fails: it cannot find the stick. The same as it was when telling it to install from usb as cdrom

2. I tried the idea of mounting the boot USB to a director *other* than /mnt and then telling Setup to install from there. Well, that failed, and it managed to fail in an unexpected way. It presented me with a list of ... I guess you would call it categories? I seem to recall that there should be several categories. I was presented with only *one*. The one category was "[*] A Base Linux System".

Now, already I knew it was broken, but I thought I'd play along and see what happens next. I told it to just install all, ("full" I think it was called). The clever Slackare installer then proceded to install every package in a mere half second! Isn't that amazing?

Not.

After exiting the installer, I saw that /mnt had only two directories, the lost+found and the var directories.

So, more fail.

Point of info: my computer is able to install an OS from the just-booted USB, since that is how I got the current distro running on it.
 
Old 06-10-2015, 03:45 PM   #6
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,656

Rep: Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836
How did you put the slackware installer on the usb stick? What method/steps/guide did you use?

Last edited by colorpurple21859; 06-10-2015 at 03:47 PM.
 
Old 06-10-2015, 04:12 PM   #7
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,480

Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
How did you put the slackware installer on the usb stick? What method/steps/guide did you use?
I was about to ask the same question. Please give the exact command you used, and what ISO you used.

Also, to further investigate, please do this:
  • start the installer again
  • go as far as choosing the TARGET
  • When asked for the SOURCE, hit Alt+F2 to open another terminal and type:
    Code:
    lsblk -o name,size,fstype,mountpoint
    Then post the results here. You can mount your other system on a directory that you would create like /other and redirect the output there to spare yourself writing down the results.
 
Old 06-11-2015, 07:52 AM   #8
pzognar
Member
 
Registered: Jun 2015
Distribution: Debian Jessie 64
Posts: 163

Original Poster
Blog Entries: 9

Rep: Reputation: Disabled
I used:

dd if=whereIhavethe.iso of=/dev/sdb bs=2048

That is the same command I used to get a working Mint, Debian, BSD, etc. usb stick.

It will take more time to answer the other questions.

p.s. I have had one idea but implementing it will be shaky and time-consuming: what if the fact of it being a hybrid image is the problem? From other experiments I know that my computer can boot off a USB of a ISO image that is not hybrid (just a pure cd/dvd .iso 9-whatever file system). Maybe there is some file system conflict there?

Last edited by pzognar; 06-11-2015 at 07:55 AM.
 
Old 06-11-2015, 08:17 AM   #9
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,656

Rep: Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836Reputation: 836
The DD command should have worked. Which Iso did you use, where downloaded from? You wouldn't happen to be using the 32bit iso on an efi system? Sometimes that will cause strange issues. You could boot the BzImage and initrd.img that is on the usb from grub or lilo and then before running setup, create a new directory in the root directory and mount the usb to the newly created directory before running setup. Don't use /mnt that is where setup mounts the partition that slackware is to be install on.
 
Old 06-11-2015, 02:44 PM   #10
pzognar
Member
 
Registered: Jun 2015
Distribution: Debian Jessie 64
Posts: 163

Original Poster
Blog Entries: 9

Rep: Reputation: Disabled
All right, have gotten some more info. Tried the suggested lsblk thing and got this output:
Code:
NAME     SIZE FSTYPE      MOUNTPOINT
sda    465.8G             
|-sda1   128G ntfs        
|-sda2     1K             
|-sda5  64.9G vfat        
|-sda6   243M ext2        
|-sda7  15.3G xfs         
`-sda8 257.4G crypto_LUKS 
sdb      7.5G iso9660     
|-sdb1   2.3G iso9660     
`-sdb2   1.4M vfat        
sdc     14.5G             
`-sdc1  14.5G ext2        /mnt
sr0     1024M
sdb was the stick I booted off of. sda is the regular hard drive that the existing OS's are on. sdc1 is where we had intended to install to.

Odd that there appears to be two partitions on the USB stick. I am going to *guess* this is how it is a hybrid, to be bootable as a DVD and also as a USB stick?

I decided to mount sdb1 instead of sdb in an attempt to get a more DVD-like file system. As before, as already described, this involved making a directory off of "/" so *not* anything do do with the "/mnt" directory.

This did have one positive result: instead of only one catagory (the A) I saw several categories. This seems more like how I remember the install of Slackware is supposed to go. So I boldly proceded, telling it to just install everything without prompting.

Fail: as before, after one half second, a claim from Setup that it was all done. Uh huh. I checked and, as before, nothing in /mnt but a lost+found and a var.

I remain perplexed.

Note: This iso I am trying to use is the 64-bit version 14.1 installer, as linked from the Slackware site.
 
Old 06-11-2015, 03:38 PM   #11
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,480

Rep: Reputation: Disabled
Quote:
Originally Posted by pzognar View Post
Odd that there appears to be two partitions on the USB stick. I am going to *guess* this is how it is a hybrid, to be bootable as a DVD and also as a USB stick?
Not at all. /dev/sdb2 is what is called an "EFI system partition" that just contain the EFI boot loader, used in case of an UEFI firmware. But that doesn't hurt at all for machines with a BIOS firmware like yours and has nothing to do with your issue.

Still I don't understand what happens.

Try this:
  • Boot the installer
  • As soon as logged in (before even typing setup) do:
    Code:
    mkdir /slack
    mount /dev/sdb1 /slack
    setup 2>/tmp/errors
  • When asked for the SOURCE, choose "install from a pre-mounted directory"
  • If the installation goes badly as previously, hit "Ctrl+F2" and check the content of the file /tmp/errors. That could give us a clue if it's not empty

PS Before installing the packages you could also check that the directory /slack/slackware64 actually contains the packages, just in case. "du -s /slack/slackware64" should give 2145794.

Last edited by Didier Spaier; 06-11-2015 at 04:40 PM. Reason: PD added.
 
Old 06-11-2015, 08:32 PM   #12
Pednick
Member
 
Registered: Nov 2014
Posts: 80

Rep: Reputation: Disabled
I had that problem then I just figured I choose the harddrive option and type /dev/sdc1, if /dev/sdc1 is where your usb is, that's where mine is uaually and that does the trick.

Just check first with lsblk at the command prompt.

Quote:
Originally Posted by pzognar View Post
Slackware 14.1 fails to install from USB stick. It boots from the stick but will not install.

Setup begins as it should. Setting up partitions appears to work fine. Setting target works as it should. The problem is that the installer cannot find the files to install from. Hello, Slackware, that USB you booted off of? You remember that one? Yeah, that one. About that one ... the files you want to install, the ones you can't find? They are there!

So how do I tell Slackware that?

note:

Already tried:

1. Having it automatically search for cdroms. I had figured tht the USB would appear as a large cdrom but apparently not.

2. giving Setup the path to the mounted USB as if it were a hard drive with files to install. That failed. After about one half-second, it claimed that the entire install was all done. Examination after the fact confirmed that nothing was actually copied in.

Last edited by Pednick; 06-12-2015 at 05:08 AM.
 
Old 06-12-2015, 09:57 PM   #13
pzognar
Member
 
Registered: Jun 2015
Distribution: Debian Jessie 64
Posts: 163

Original Poster
Blog Entries: 9

Rep: Reputation: Disabled
@Didier Spaier:

I did as recommended and ended up with this short output as the "error" file:
Code:
/usr/lib/setup/setup: line 336: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 340: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 342: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 344: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 345: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 346: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 347: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 348: /mnt/etc/fstab: No such file or directory
Very strange, since setup had *claimed* to set up the / directory in the new fstab.
 
Old 06-12-2015, 10:16 PM   #14
j_v
Member
 
Registered: Oct 2011
Distribution: Slackware64
Posts: 364

Rep: Reputation: 67
I wonder if the problem here is the block size given to dd when copying to the usb stick?
The example given in the iso's 'isolinux/README.TXT' uses 'bs=1M'. I seem to remember using
4K, since this is a common default block size these days. YMMV.

Edit: I changed the 4k to 4K... first one is 4000, second one is 4096.

Last edited by j_v; 06-12-2015 at 10:18 PM.
 
Old 06-13-2015, 01:16 AM   #15
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,480

Rep: Reputation: Disabled
Quote:
Originally Posted by pzognar View Post
@Didier Spaier:

I did as recommended and ended up with this short output as the "error" file:
Code:
/usr/lib/setup/setup: line 336: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 340: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 342: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 344: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 345: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 346: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 347: /mnt/etc/fstab: No such file or directory
/usr/lib/setup/setup: line 348: /mnt/etc/fstab: No such file or directory
Very strange, since setup had *claimed* to set up the / directory in the new fstab.
The message that claimed that was displayed after the TARGET step but actually the displayed information (prepared content of /mnt/etc/fstab) was then stored in temporary files whose content should have been later written to /mnt/etc/fstab in the CONFIGURE step.

The line #336 of setup was supposed to create the file /mnt/etc/fstab:
Code:
    cat /dev/null > $T_PX/etc/fstab
The parameter T_PX being set to /mnt the corresponding error message actually indicates that whole directory /mnt/etc does not exist. This directory should have been created by the installation of the first package aaa_base, so that just confirms that this package has not been installed.

That seems to indicate that this package was not found on the installation media.

To check, just mount the USB key from your running system, for instance on /media and post the output of:
Code:
stat /media/slackware64/a/aaa_base-14.1-x86_64-1.txz

Last edited by Didier Spaier; 06-13-2015 at 07:18 AM. Reason: path corrected in the stat command.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
am trying to boot from 1gb usb stick, this fails and windows open Calvince Linux - Newbie 7 09-04-2013 03:47 AM
Install Slackware in a USB Stick Alexvader Slackware 16 07-24-2013 04:06 PM
Install Slackware using a bootable USB stick mariostg Slackware 3 09-22-2012 07:50 AM
[SOLVED] USB stick fails to be detected in debian sarge unev_21 Linux - Hardware 9 08-07-2009 12:09 PM
usb memory stick: chown/chgrp fails pcass Linux - Hardware 2 02-07-2004 10:42 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 03:16 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration