LinuxQuestions.org
Visit Jeremy's Blog.
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-23-2017, 08:03 PM   #46
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

I totally forgot about it being in Virtualbox and that it had a virtualbox name for the disk id. That would definitely cause issues when you try and boot it normally since that id would only be present in a virtualbox environment. I'm glad you figured it out, because I don't think I would've been able to help further.

And yes, the live usb installer *should* be able to install to any target on the system. If it doesn't I would take up the issue on Eric's blog, as he tends to prefer that medium to provide support for his software.
 
Old 05-26-2017, 01:58 AM   #47
apmount
Member
 
Registered: Mar 2009
Location: Athens
Distribution: Slackware
Posts: 81

Original Poster
Rep: Reputation: 5
So, after some days after accomplishing the task to have en external usb Slackware hdd, and an "accident" in the mean time, summarizing the process I believe there are 3 key points one should pay attention to.
First, one has to have inline all boot definitions and use UUIDs instead of /dev/sdxY so to have absolute names of reference (fstab, initrd, grub/lilo, etc.)
Then, at least for my case, the scenario works with the huge (plus initrd) and not with the general kernel.
And lastly but of equal importance, one has to specify the correct modules in initrd so that the system will be able to recognize usb and load from it.
At this point I had a frightening experience when a slackpkg install-new followed by a careless slackpkg upgrade-all upgraded the kernel from 4.4.14 to 4.4.38! So I needed to make a new initrd but I forgot the modules I used previously in the successful attempts. And all the nightmares of the previous failed efforts came back to life...
Anyway, finally I found that the following modules
Code:
usb-storage:xhci-hcd:uas:ehci-hcd:uhci-hcd:ohci-hcd:hcd:ehci-pci:xhci-pci:usbhid:sdhci:xhci-pci:squashfs:hid:hid-lenovo
do the job. I don't know which one -or more- of them is the savior, but now it works OK as with the previous kernel. And not only that, but I was able also to boot from this disk using another laptop -usb2- (whereas in the previous case I was able to boot only from the laptop I had used though out the whole process -usb3-).
Again, thanx to all who helped me to accomplish this task.

@bassmadrigal
At some point, when you showed me how to make an initrd from another linux distro (with the mountings etc.), you have mentioned some bind mounts. Previously I was attempting to make the initrd from another distro without these bind mounts (I did only the mount /dev/sdb1 /mnt) and it failed. Why do we need these? Aren't these directories exist also in the /dev/sdxY that we mount to /mnt? Why do we need to bind mount the other's linux distro directories to the /mnt also?


Regards, Apostolos.

Last edited by apmount; 05-26-2017 at 03:19 AM.
 
Old 05-26-2017, 08:32 AM   #48
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
At this point I had a frightening experience when a slackpkg install-new followed by a careless slackpkg upgrade-all upgraded the kernel from 4.4.14 to 4.4.38!
This is one reason I usually recommend blacklisting the kernels from slackpkg. Even Pat recommends blacklisting them (even though they're enabled by default).

Quote:
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below
My normal recommendation is to installpkg (not upgradepkg) the new kernels, then you can go through the process of building your new initrds and updating your bootloader. Then you can try and boot the new kernel. If it doesn't work, you still have your old kernel to rely on until you can get the new one fixed. Once you've verified the new one works fine, you can removepkg the old kernels.

Keep in mind, the default output for the mkinitrd command is /boot/initrd.gz, so I'd recommend changing that to match your kernel, something like /boot/initrd-4.4.38.gz. This would prevent you from accidentally overwriting the old, working one when you build the new initrd.

Quote:
Originally Posted by apmount View Post
@bassmadrigal
At some point, when you showed me how to make an initrd from another linux distro (with the mountings etc.), you have mentioned some bind mounts. Previously I was attempting to make the initrd from another distro without these bind mounts (I did only the mount /dev/sdb1 /mnt) and it failed. Why do we need these? Aren't these directories exist also in the /dev/sdxY that we mount to /mnt? Why do we need to bind mount the other's linux distro directories to the /mnt also?
These directories contain information about the running system, this includes many files that cover kernel parameters as well as all your device nodes. If these aren't available, many applications won't function properly, especially if they're trying to get a running snapshot of the system (like mkinitrd would need information from the running kernel to be able to build an initrd).
 
1 members found this post helpful.
  


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 12:34 AM.

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