Slackware This Forum is for the discussion of Slackware Linux.
|
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
|
01-26-2014, 08:26 PM
|
#31
|
LQ Newbie
Registered: Jan 2014
Posts: 29
Original Poster
Rep:
|
let me install it one more time, but this time using 'exit' option.
|
|
|
01-26-2014, 08:46 PM
|
#32
|
LQ Newbie
Registered: Jan 2014
Posts: 29
Original Poster
Rep:
|
Quote:
Originally Posted by Richard Cranium
I don't know if there is difference between selecting <Cancel> or actually using the Exit menu option to leave setup. I used the exit menu option.
|
There's no difference between using exit or cancel, same error.
|
|
|
01-26-2014, 09:17 PM
|
#33
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
OK, I'll have to try it under VM player.
|
|
|
01-26-2014, 10:30 PM
|
#34
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
My VM player version worked as expected.
What options did you select when you created the VM?
|
|
|
01-26-2014, 11:03 PM
|
#35
|
Senior Member
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979
Rep:
|
The system tries to mount the root-device to /mnt, this is wrong!. lilo or mkinitrd seem not to have been running from a chroot-environment. Or Maybe there's a problem with the fstab.
Sorry for pointing you the wrong way, the error-messages looked too familiar to me
Markus
Last edited by markush; 01-27-2014 at 02:01 AM.
|
|
|
01-26-2014, 11:33 PM
|
#36
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Quote:
Originally Posted by markush
The system tries to mount the root-device to /mnt, this is wrong!. lilo or mkinitrd seem not to have been running from a chroot-environment. Or Maybe there's a problem with the fstab.
Markus
|
Well, no, that's OK.
The initrd init code mounts stuff in /mnt and then (essentially) does a chroot.
Code:
# Switch to real root partition:
/sbin/udevadm settle --timeout=10
echo 0x0100 > /proc/sys/kernel/real-root-dev
mount -o ro -t $ROOTFS $ROOTDEV /mnt
if [ ! -r /mnt/sbin/init ]; then
echo "ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead."
echo " You can try to fix it. Type 'exit' when things are done."
echo
/bin/sh
fi
else
echo
echo "RESCUE mode"
echo
echo " You can try to fix or rescue your system now. If you want"
echo " to boot into your fixed system, mount your root filesystem"
echo " read-only under /mnt:"
echo
echo " # mount -o ro -t filesystem root_device /mnt"
echo
echo " Type 'exit' when things are done."
echo
/bin/sh
fi
# Need to make sure OPTIONS+="db_persist" exists for all dm devices
# That should be handled in /sbin/mkinitrd now
/sbin/udevadm info --cleanup-db
/sbin/udevadm control --exit
unset ERR
mount -o move /proc /mnt/proc
mount -o move /sys /mnt/sys
mount -o move /run /mnt/run
[ "$DEVTMPFS" = "1" ] && mount -o move /dev /mnt/dev
echo "${INITRD}: exiting"
exec switch_root /mnt $INIT $RUNLEVEL
|
|
|
01-27-2014, 12:20 AM
|
#37
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
When I installed my VM player version, there were more modules found by mkinitrd than the OP appears to have:
Code:
# This is a script used to load the kernel modules.
# To use it, chmod it 755, and then add the insmod
# lines needed to load your modules, like this:
modprobe -v mptbase
modprobe -v mptscsih
modprobe -v mptspi
modprobe -v mbcache
modprobe -v jbd2
modprobe -v ext4
|
|
|
01-28-2014, 10:15 AM
|
#38
|
LQ Newbie
Registered: Jan 2014
Posts: 29
Original Poster
Rep:
|
VM options
*i will install the operating system later, next
*guest operating system (other), version (other), next
*Virtual machine name (Slackware), next
*maximum disk size 30gb, split disk into multiple files, next
*customize hardware,
*memory (512)
*procesor (4 cores)
*new cd/dvd (use an iso image file)
*network adapter(bridged), close
*Finish
|
|
|
01-29-2014, 02:42 AM
|
#39
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Try setting the guest operating system to Linux and the version to 3.x kernel.
|
|
|
01-29-2014, 05:11 AM
|
#40
|
Senior Member
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979
Rep:
|
Hi,
today I had with my Slackware running on VMware also an Error "no /sbin/init found". Problem was that the initscript ran with wrong kernel (3.10.17 vs 3.10.17-smp). You should check that the kernel (uname -r) for which the initrd is created, is the same which will run on your system.
Markus
|
|
|
01-29-2014, 09:00 PM
|
#41
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
*shrugs* I ran the steps that I outlined in post #26 when I set up my VM in VMPlayer and the system booted just fine.
|
|
|
01-29-2014, 11:06 PM
|
#42
|
Senior Member
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979
Rep:
|
I'd recommend to check /lib/modules if there is really a directory 3.2.29-smp and that the modules are really being build into the initrd (look at the output when the initrd is created).
Markus
|
|
|
01-31-2014, 01:10 AM
|
#43
|
LQ Newbie
Registered: Jan 2014
Posts: 29
Original Poster
Rep:
|
It finally worked, the problem was: setting guest operating system to other, then i did what Richard said...
Quote:
Try setting the guest operating system to Linux and the version to 3.x kernel.
|
After i installed on linux version 3.x, running the steps that richards outlined on "POST #26" it worked.
Also... i installed again without running these steps below from "POST #26" and it worked.
Code:
mount -R /proc /mnt/proc
mount -R /sys /mnt/sys
mount -R /dev /mnt/dev
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-smp-3.2.29-smp >>/etc/lilo.conf
also i configured lilo on installation, not after. as outlined on "POST #26"
btw, this guide works too ftp://ftp.slackware.com/pub/slackwar...README_LVM.TXT
Note: i installed Slackware 19 times and the problem was VM option "linux version 3.x"
|
|
|
01-31-2014, 01:12 AM
|
#44
|
LQ Newbie
Registered: Jan 2014
Posts: 29
Original Poster
Rep:
|
Thanks Richard and Markush for all your help.!!
|
|
|
01-31-2014, 01:14 AM
|
#45
|
LQ Newbie
Registered: Jan 2014
Posts: 29
Original Poster
Rep:
|
|
|
|
All times are GMT -5. The time now is 03:23 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|