LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-26-2014, 07:26 PM   #31
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled

let me install it one more time, but this time using 'exit' option.
 
Old 01-26-2014, 07:46 PM   #32
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
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.
 
Old 01-26-2014, 08:17 PM   #33
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
OK, I'll have to try it under VM player.
 
Old 01-26-2014, 09:30 PM   #34
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
My VM player version worked as expected.

What options did you select when you created the VM?
 
Old 01-26-2014, 10:03 PM   #35
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
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 01:01 AM.
 
Old 01-26-2014, 10:33 PM   #36
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
Quote:
Originally Posted by markush View Post
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
 
Old 01-26-2014, 11:20 PM   #37
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
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
 
Old 01-28-2014, 09:15 AM   #38
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
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
 
Old 01-29-2014, 01:42 AM   #39
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
Try setting the guest operating system to Linux and the version to 3.x kernel.
 
Old 01-29-2014, 04:11 AM   #40
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
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
 
Old 01-29-2014, 08:00 PM   #41
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
*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.
 
Old 01-29-2014, 10:06 PM   #42
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
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
 
Old 01-31-2014, 12:10 AM   #43
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
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"
 
Old 01-31-2014, 12:12 AM   #44
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
Thanks Richard and Markush for all your help.!!
 
Old 01-31-2014, 12:14 AM   #45
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
Thanks guys,
Attached Images
File Type: png slack.PNG (47.9 KB, 7 views)
 
  


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
Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0) fjur94 Slackware 1 01-22-2014 06:05 PM
kernel panic - not syncing:vfs:unable to mount root fs on unknown-block (8.2) raleeha VectorLinux 6 04-21-2011 02:48 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) anjanesh Ubuntu 9 01-27-2011 12:00 PM
kernel panic - not syncing: VFS unable to mount root fs on unknown-block(8,3) AllShk Linux - Newbie 3 11-28-2009 12:56 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block akaUr Linux - Kernel 10 06-18-2009 06:59 AM


All times are GMT -5. The time now is 09:14 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration