LinuxQuestions.org
Help answer threads with 0 replies.
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 05-17-2017, 10:21 AM   #16
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146

I cannot see why that is not working. You've already been how long in days not being able to experience the greatness of Slackware?

Personally the way I do this is very simple. If I install Slackware second. I let it take over by installing LILO. then Install Slackware grub, to elevate the figuring out how to get LILO to boot other systems minus Windows.

I do this with every second or more install of an operating system. If they use grub then I have that install of Linux install its Grub and take over the boot process.

This way I know that it has been installed in working order, then I go into change it to how I want it to be booted up and by which system being the main system in control of it all.

This is my logic behind this type of situation. I could spend hours, (others days even) on trying to get that (an) install to finally work. Whereas with most even Slackware doing a complete install takes less time then time spent on trying to trouble shoot it to get it to work.

Code:
if [ time spent trying to get it to work > a new fresh install ]] then 
just install it again
that is my quick fix.
Benefits - practice installing and configuring a Linux system.

In most cases what is all that is needed to be done. Let the new install take care of any discrepancies that may have occurred that are now preventing it from booting.

On the other side. Spending hours, days, weeks even hacking away at it until you finally get it to boot. Teaches you patience and whatever else one may learn from that experience.

Last edited by BW-userx; 05-17-2017 at 10:23 AM.
 
Old 05-17-2017, 10:55 AM   #17
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
thanx BW-userx for the support. Well, I am trying to do something different thus the long time of trying and error. I wanted to install slackware on an external hdd (that already has another linux on it) through virtualbox. The installation process actually went OK. It is in the boot face I am having these problems of kernel crash. Anyway, I had slackware before (v12) so I had experienced the greatness of it

In the end I 'm gonna install it in a clean disk and install Antergos afterwords...
 
Old 05-17-2017, 11:02 AM   #18
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by apmount View Post
thanx BW-userx for the support. Well, I am trying to do something different thus the long time of trying and error. I wanted to install slackware on an external hdd (that already has another linux on it) through virtualbox. The installation process actually went OK. It is in the boot face I am having these problems of kernel crash. Anyway, I had slackware before (v12) so I had experienced the greatness of it

In the end I 'm gonna install it in a clean disk and install Antergos afterwords...
well that explains a lot. lol

you're using Vbox to install a Linux system somewhere else? Why not use the hardware what VBox is installed on?

nevertheless, that process is (should be) the same. just have Slackware install lilo. then boot into Slackware first before doing anything else.
 
Old 05-17-2017, 12:05 PM   #19
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
i am going to try this also. but in the process of installing lilo, the installer says that it will install lilo in the "first" hd whereas i want it to be installed on the second (sdb as it is known the external usb hd to virtualbox).
what actually bothers me is that i can not find a way to review the massages when the kernel crashes. is there a way to run the boot process in a debug mode?
but as i see it, i will end up installing slackware on a clean disk . i tried the vbox method just to see if there is a transparent way of installing a linux from a windows machine to an external hd without using the native windows hd or any usb stick, just the iso image and a virtual machine. it worked with arch and anyergos, it installed slack, i am just having problem booting slack.
 
Old 05-17-2017, 12:13 PM   #20
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by apmount View Post
i am going to try this also. but in the process of installing lilo, the installer says that it will install lilo in the "first" hd whereas i want it to be installed on the second (sdb as it is known the external usb hd to virtualbox).
what actually bothers me is that i can not find a way to review the massages when the kernel crashes. is there a way to run the boot process in a debug mode?
but as i see it, i will end up installing slackware on a clean disk . i tried the vbox method just to see if there is a transparent way of installing a linux from a windows machine to an external hd without using the native windows hd or any usb stick, just the iso image and a virtual machine. it worked with arch and anyergos, it installed slack, i am just having problem booting slack.
1. what do you have installed on that first drive?
2. I just remember/thought about this one. you can use your install USB Stick to boot your Slackware install.

I just got a remember how that is done. lol

let me pull my USB Stick out and do this to refresh my memory. hold on brb.

Back:
ok it was easy enough. when you boot using your USB Stick you get your boot: prompt.
Code:
boot: huge.s root=/dev/sdb3 rdinit=ro
give that a try, remembering your system is using the kernel on the USB Stick. you can then use Slackware grub

Code:
# grub-install /dev/sdb3
# grub-mkconfig -o /boot/grub/grub.cfg
https://docs.slackware.com/howtos:sl..._first_install

Last edited by BW-userx; 05-17-2017 at 12:23 PM.
 
1 members found this post helpful.
Old 05-17-2017, 12:43 PM   #21
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
but i am not using a usb stick !
i am using vdox to run the iso image. sdb3 in my case is the third partition on the external hd that has the slackware installed on it. i will try though to run again the virtual machine up to the point of boot:
now that i mention this, the physical order of the partitions on the disk is not the same as the logical one! due to the way i have created them, sdb1 (antergos) is the first partition on the disk, sdb2 is the swap and physically is placed at the end of the disk and sdb3 is the slackware partition and is second in physical order just after the sdb1. does this play any role?
 
Old 05-17-2017, 12:47 PM   #22
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by apmount View Post
but i am not using a usb stick !
i am using vdox to run the iso image. sdb3 in my case is the third partition on the external hd that has the slackware installed on it. i will try though to run again the virtual machine up to the point of boot:
now that i mention this, the physical order of the partitions on the disk is not the same as the logical one! due to the way i have created them, sdb1 (antergos) is the first partition on the disk, sdb2 is the swap and physically is placed at the end of the disk and sdb3 is the slackware partition and is second in physical order just after the sdb1. does this play any role?
that is worth investing that is for sure. I am still trying to wrap my head around how you're using a VBox to run an ISO and install that on to an external HDD. and the why the hell would you even want to do that. lmao (no offense)
 
Old 05-18-2017, 12:41 PM   #23
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
OK, after some more efforts I managed finally to get Slackware started from the external hdd but... on the virtualbox! I use the hdd as a raw device defined to a virtual machine and I can start from there both Antergos and Slackware. But I can not yet boot it directly from the external hdd (attached to a usb port) whereas Antergos starts OK. In case of Slackware I have to enter to the grub2 menu and modify the root to point to /dev/sda1 instead of /dev/sdb1 because when I installed these OSes the hdd was the sdb device where now it is the sda.

The message I am getting for Slackware now has something to do with init parms "kernel panic - not syncing: no working init found..." I am using huge-4.4.14. I suspect some modiles may be missing regarding the usb (?). Because otherwise it is the same exactly option on grub menu that starts Slackware sucessfully under vbox.

I tried to make an initrd but cannot run mkinitrd since it cannot find the command. Still on the search...
 
Old 05-18-2017, 12:47 PM   #24
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by apmount View Post
OK, after some more efforts I managed finally to get Slackware started from the external hdd but... on the virtualbox! I use the hdd as a raw device defined to a virtual machine and I can start from there both Antergos and Slackware. But I can not yet boot it directly from the external hdd (attached to a usb port) whereas Antergos starts OK. In case of Slackware I have to enter to the grub2 menu and modify the root to point to /dev/sda1 instead of /dev/sdb1 because when I installed these OSes the hdd was the sdb device where now it is the sda.

The message I am getting for Slackware now has something to do with init parms "kernel panic - not syncing: no working init found..." I am using huge-4.4.14. I suspect some modiles may be missing regarding the usb (?). Because otherwise it is the same exactly option on grub menu that starts Slackware sucessfully under vbox.

I tried to make an initrd but cannot run mkinitrd since it cannot find the command. Still on the search...
this is why you change it everywhere you can to UUID grub and fstab
 
1 members found this post helpful.
Old 05-18-2017, 07:01 PM   #25
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,316

Rep: Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023Reputation: 5023
Quote:
Originally Posted by apmount View Post
OK, after some more efforts I managed finally to get Slackware started from the external hdd but... on the virtualbox! I use the hdd as a raw device defined to a virtual machine and I can start from there both Antergos and Slackware. But I can not yet boot it directly from the external hdd (attached to a usb port) whereas Antergos starts OK. In case of Slackware I have to enter to the grub2 menu and modify the root to point to /dev/sda1 instead of /dev/sdb1 because when I installed these OSes the hdd was the sdb device where now it is the sda.

The message I am getting for Slackware now has something to do with init parms "kernel panic - not syncing: no working init found..." I am using huge-4.4.14. I suspect some modiles may be missing regarding the usb (?). Because otherwise it is the same exactly option on grub menu that starts Slackware sucessfully under vbox.

I tried to make an initrd but cannot run mkinitrd since it cannot find the command. Still on the search...
Have a look at my article on SlackDocs on how to convert your system to UUIDs. With bootloaders, it only covers lilo since I have no experience with grub, but you should be able to get the gist of it and edit your grub config.

With mkinitrd, make sure you are chrooting into the root Slackware partition so all the commands and kernels are where it expects. Also, don't forget to pass the kernel version of Slackware to mkinitrd (the -k option), otherwise it will use the one you're currently running (probably on Antergos, which likely doesn't match Slackware's and would cause an error). You might also want to check out /usr/share/mkinitrd/mkinitrd_command_generator.sh to help you generate a proper command (if you're not very familiar with mkinitrd).
 
1 members found this post helpful.
Old 05-19-2017, 01:52 AM   #26
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
@bassmadrigal

many many thanx! In fact I came across this document while trying to make it work and helped me a lot to clear out some things.

Basically the problem I have right now is that when I boot my laptop directly from the external hdd (attached as USB device), it stops the boot process and says that it can not sync due to the fact that no working init is found and I should have passed parameter on the init process by myself. However, this does not happen when I boot Slackware from this hdd when it is attached to a virtual box machine (as a raw device). There, everything works fine. I am searching on this right now.

Now, on why the hell I am doing all this mess and not using directly the laptop (without the use of a virtual box) to install slackware, arch, any other distro to the external disk, or even better to the internal hdd. Well, mainly it is for the fun of it. Secondly, I want to leave the internal hdd of the laptop untouched as possible. And thirdly, this way (using virtual box to install distros on external hdd) I can install a number of distros on a disk without having to ipl each time the laptop and insert a new usb stick each time for any new distro. I can just boot it from virtual box and install it on the external hdd, which by the way with some small changes on the grub menu could be used on any other pc/laptop (my intentions, not that it will certainly be functioning).

Well, basically it is for the fun of it

Regards, Apostolos

edit: forgot about the initrd recommendation. It is one of the things I will try next

Last edited by apmount; 05-19-2017 at 01:53 AM. Reason: initrd
 
Old 05-20-2017, 09:02 AM   #27
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
Ok, so after trying with initrd i am now getting the attached errors. Any hints on those? I am getting these when i boot from the external hdd. When i boot this drive from within virtual box it works fine. kernel is huge.
Attached Thumbnails
Click image for larger version

Name:	IMG_0295.jpg
Views:	12
Size:	255.6 KB
ID:	25053  
 
Old 05-20-2017, 09:36 AM   #28
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by apmount View Post
Ok, so after trying with initrd i am now getting the attached errors. Any hints on those? I am getting these when i boot from the external hdd. When i boot this drive from within virtual box it works fine. kernel is huge.
It might be that it is pointing to the wrong drives -- this It where you had to changeover to UUID yes?

if the correct UUID was in fact used in the grub on the external drive that boots whatever OS's are installed on them, and the correct UUID is again used in your fstab on that external drive OS. I have no idea.

the messages are indicating it cannot find things
what is

jbd2:
dup symbols ..jbd2_journal_restart ...
do you have that in your system twice, being called from two separate or twice? So the second one errors out because of it.

mbcache : same error mesage here just for mb_cache...(can't make it out glaring)

they both have exec(able) format errors. if scripts something within them is not written correctly so they are not getting executed. would be my guess.

fstab:
look like somewhere it is calling to maybe mount something in /mnt
but cannot find it in fstab

fstab issues last line. no /sbin/init found. do you even have an "/sbin/init" directory on that system?

if not check fstab paths statements or any script that maybe telling Linux to look for something that is not there.

So yeah looks like you have to fiddle with it beings that you are trying to get it to work by two separate means (methods) of connections.

The exec format errors:

maybe having somewhere within that init process processes being called twice.

Ownership has already been taken by the Kernel one starting it the first time, then it is being called to restart, maybe from somewhere else(another script) or restart the very same again. (without shutting it down first to relinquish ownership) the Kernel still has it (and does not want it again?).

That is my educated guesses

Last edited by BW-userx; 05-20-2017 at 09:39 AM.
 
1 members found this post helpful.
Old 05-20-2017, 11:03 AM   #29
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,122

Rep: Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972Reputation: 6972
The attached picture just shows that you are using an initrd.gz image together with the "huge" kernel instead of the recommended "generic" kernel. The "huge" kernel has the modules already built-in which are then again attempted to load from the initrd. Hence the "duplicate symbols" and the module load error. That is not bad, it just looks ugly, and that should not be the reason why your computer subsequently fails to boot.
 
1 members found this post helpful.
Old 05-21-2017, 10:07 AM   #30
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
OK, I think I understand where the error is but I have no clue on how to fix it. First of all as Alien Bob said it is not the duplicate load of modules because of the huge kernel plus the initrd. It is that exactly after that point it tries to mount /dev/sda1 to /mnt but /dev/sda1 is the windows hard drive (the internal one) and NOT the external usb drive from where the boot process is happening! My fstab is like:

#/dev/sda1 / ext4 defaults 1 1
UUID=16e87207-f7c1-472a-8505-6af3dd72e2a8 / ext4 defaults,noatime,discard 1 1
#/dev/sda2 swap
UUID=8d53e91b-bf37-49b5-8779-4676683e05a8 none swap defaults,discard 0 0
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0

so I expected to see something like a uuid on the boot. But this is not happening. It tries to mount /dev/sda1 and as /dev/sda1 is the internal hdd and not the external one. This is not happening when I boot this disk from virtual box, neither with some other distros I tried (antergos, arch, debian). All other distros were able to boot directly from the external hdd.

When I do a ls /dev/sd* at the emergency shell I only see the /dev/sda and /dev/sda1 devices. So, I guess that somewhere in the boot process there might be a hardcoded value of /dev/sda1 and not a search for the uuid. I believe this is so because of the init script uses for rootdev the value /dev/sda1. But although the boot is happening from the external usb hdd, still /dev/sda1 has the contents of the internal drive and not the usb drive.

If this is the case, I think I hit a wall here. I do not know how to overcome this.

Regards, Apostolos.

UPDATE: I tried to modify the rootdev value and to put the UUID there without success. Still when booting directly from the external hdd, rootdev value is /dev/sda1. I suspect that the same is happening also when I boot this drive from the virtual box, only in this case the /dev/sda1 is correctly identified as the disk where slackware is (the external one). So, the difference between booting directly from external hdd and booting form within virtual box is which hard drive the system considers the /dev/sda1 to be. In the first case the system considers as /dev/sda1 the internal drive (windows), in the second case the external usb drive (slackware). I still can not figure out why this is not happening in the other distros.

UPDATE2: OK, I just made another discovery. Antergos lists that the external disk is the /dev/sdb* when I boot directly from it (when I boot from within the virtual box, the disk is identified as /dev/sda*)! So I suppose it is correct that the internal windows disk is the /dev/sda and the external the sdb. But how can I make the slackware init script to consider /dev/sdb as rootdev instead of /dev/sda?

UPDATE3: Well, I think the problem is that I am building the grub from antergos and when I issue the command grub-mkconfig there, although for all other distributions the entries are generated as "root=UUID=..." for Slackware the entries are generated for example as "linux /boot/vmlinuz-huge-4.4.38 root=/dev/sda1" for the last line. So it is something on the generation of the grub menu. I thought that an alteration could be OK but I read that one should not edit this cfg file. So, it seems that I can not generate grub for Slackware to have uuids instead of /dev/sd...Slowly but gradually I find myself of coming back to the original suggestion by BW-userx: use UUIDs instead of /dev/sdxx...

Last edited by apmount; 05-21-2017 at 12:10 PM. Reason: update
 
  


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
AryaLinux installation USB external HDD failed without warning joellapointe1717 Linux - Newbie 28 10-15-2016 12:40 AM
Booting Problem. Windows and ubuntu on internal hdd. Centos on External USB hdd faisal59 Linux - Distributions 1 07-17-2013 08:19 AM
Slow USB transfer rates (60kb p/s) External HDD --> Internal HDD drfrostbyte Linux - Hardware 4 03-28-2011 01:20 AM
External ubuntu install on external USB HDD th3_tr00p3r Linux - Newbie 1 05-11-2008 02:56 PM
External installation - USB HDD petercockroach Linux - Newbie 1 11-04-2004 04:06 PM

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

All times are GMT -5. The time now is 11:26 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