I had a Slack 13.1 machine with 2.6.36 kernel. Then, I updated the kernel to 3.12.1.
This machine has connected: a bootable disk with three partions (/dev/sda1 --> Linux OS files..., /dev/sda2 --> data, /dev/sda3 --> more data), a "dummy" SSD just to store things (/dev/sdb1) and USB ports.
The fact is that whenever I try to start Linux with a USB containing data (not a LiveUSB) connected to the machine, during the startup process there is something going on that assigns the sda device to the USB so it is not possible to mount the Linux partitions in the "bootable disk" due to a Kernel Panic:
VFS: Mounted root (vfat filesystem) readonly on device 8:1. devtmpfs: error mounting -2 [...] Kernel panic - not syncing: no init found. Try passing init=..
The bootloader I am using is LILO. I don't know if there is anyway to force the boot process not to change device names or pre-assign any of them to a certain device. This is its configuration:
# Linux bootable partition config begins image = /boot/vmlinuz root=/dev/sda1 append="panic=120" label=3.12.20-smp read-only
/dev/sda1 / ext4 rw 1 1
As the USB device partition is considered as sda1, it obviosuly doesn't contain any kind of init process or application so I get the kernel panic.
I had tried with root="LABEL=myLabel" or root="LABEL=current" with no luck...I think because it searches for the label in the root node, not in all partitions :S
Any suggestion of what is going on? Is it possible to fix it? Thanks in advance!