[SOLVED] Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0)

fjur94 · 01-26-2014, 07:26 PM

let me install it one more time, but this time using 'exit' option.

fjur94 · 01-26-2014, 07:46 PM

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.

Richard Cranium · 01-26-2014, 08:17 PM

OK, I'll have to try it under VM player.

Richard Cranium · 01-26-2014, 09:30 PM

My VM player version worked as expected.

What options did you select when you created the VM?

markush · 01-26-2014, 10:03 PM

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

Richard Cranium · 01-26-2014, 10:33 PM

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

Richard Cranium · 01-26-2014, 11:20 PM

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

fjur94 · 01-28-2014, 09:15 AM

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

Richard Cranium · 01-29-2014, 01:42 AM

Try setting the guest operating system to Linux and the version to 3.x kernel.

markush · 01-29-2014, 04:11 AM

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

Richard Cranium · 01-29-2014, 08:00 PM

*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.

markush · 01-29-2014, 10:06 PM

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

fjur94 · 01-31-2014, 12:10 AM

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"

fjur94 · 01-31-2014, 12:12 AM

Thanks Richard and Markush for all your help.!!

fjur94 · 01-31-2014, 12:14 AM

Thanks guys,