Cant boot tinycore 10.0 - Kernel Panic

[oovy]

Hi there!
I was tinkering with tinycore once more and tried to run it in a virtual machine. The thing is, I cant get it to boot due to a kernel panic.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)



I already had this issue once with a debian installation. This was a Grub error, where it couldn't handle the kernel. Is this the same thing? Has anybody experienced this or a solution for this?
I wasn't able to fix it, so I went back to an older version...

Thanks in advance.

[Rich]

Hi oovy
Insufficient RAM allocated to your VM could cause that:
http://forum.tinycorelinux.net/index.php/topic,22268.msg139361.html#msg139361
http://forum.tinycorelinux.net/index.php/topic,22481.msg140876.html#msg140876

[oovy]

Hi there Rich!

Sadly, this does seem not to be the problem. I'm still wondering if this isn't just a bootloader issue, but I'm not sure at all.

Could there be another reason?

[andyj]

Maybe you could give us some details about the VM environment, like vmware, esxi, hyperv, virtualbox, xen, qemu?

[oovy]

Hi!
Of course, here's some info about the VM:

- VMWare Workstation 15 Pro
- 1 CPU Core
- 2 GB RAM
- Running "Other 4.x Linux Kernel"

[curaga]

Try adding "debug" to the boot args, to see more messages. Did you edit core.gz?

[oovy]

Okay, i'll try that.
No, I didn't edit core.gz. Not that I know.

core.gz is the kernel modules stuff right?

[andyj]

Is this booting from the ISO, or did you already install it to a virtual hard drive to boot from?

[oovy]

It's installed on a virtual hard drive. Already tried it multiple times.

[Rich]

Hi oovy

... core.gz is the kernel modules stuff right?

Not exactly.  core.gz  contains  rootfs.gz  +  modules.gz.

[andyj]

Since the ISO booted and the kernel saw the hard drive at the time of installation it was working at some point. Which disk controller are you using? What bootloader are you using, and what does the configuration look like?

[oovy]

Since the ISO booted and the kernel saw the hard drive at the time of installation it was working at some point. Which disk controller are you using? What bootloader are you using, and what does the configuration look like?

I am using a IDE controller, already tried SATA. It's the default TC bootloader (grub i guess). What do you mean by configuration?

[Rich]

Hi oovy

...  What do you mean by configuration?

If you used the  tc-install  utility, you should have a  /boot/extlinux/  directory with a  extlinux.conf  file in it.
If you used a third party installation tool that can install any and all Linux distros, use the  tc-install  utility.

[oovy]

Here's my extlinuxconfig

Code: [Select]

DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
INITRD /tce/boot/core.gz
APPEND quiet  waitusb=5 waitusb=5:UUID="7c01923d-d05d-454f-9738-7a1f88bb32a1" tce=UUID="7c01923d-d05d-454f-9738-7a1f88bb32a1"

[Rich]

Hi oovy

Try adding "debug" to the boot args, to see more messages. ...

Change this:

Code: [Select]

APPEND quiet  waitusb=5 waitusb=5:UUID="7c01923d-d05d-454f-9738-7a1f88bb32a1" tce=UUID="7c01923d-d05d-454f-9738-7a1f88bb32a1"To this:

Code: [Select]

APPEND quiet  debug waitusb=5:UUID="7c01923d-d05d-454f-9738-7a1f88bb32a1" tce=UUID="7c01923d-d05d-454f-9738-7a1f88bb32a1"