LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Asus netbook + USB IDE HDD + Slack 14 = Kernel panic during boot-up (http://www.linuxquestions.org/questions/slackware-14/asus-netbook-usb-ide-hdd-slack-14-%3D-kernel-panic-during-boot-up-4175452326/)

lee88abc 03-01-2013 07:50 PM

Asus netbook + USB IDE HDD + Slack 14 = Kernel panic during boot-up
 
Asus eeepc 1015PX netbook with a USB IDE HDD plugged in. Slackware 14 installed.
Boots up then kernel panics.

Anyone able to USB HDD boot an Asus netbook?

lee88abc 03-01-2013 08:02 PM

vfs: cannot open root device 802 or unknown-block(8c2)
please append a correct root= boot option
pid 1, comm: swapper/0 not tainted 3.2.29 #2

call trace:
panic+0x91/0x189
mount_block_root +0x1ce/0x27f
mount_root+0xa1/0xa5
prepare_namespace+0x16d/0x1a6
? release_tgcred. isra.5+0x30/0x30
kernel_init+0x14b/0x150
kernel_thread_helper+0x4/0x10
start_kernel+0x390/0x390
gs_change+0xb/0xb

the_penguinator 03-01-2013 08:03 PM

Quote:

Originally Posted by lee88abc (Post 4902842)
Asus eeepc 1015PX netbook with a USB IDE HDD plugged in. Slackware 14 installed.
Boots up then kernel panics.

Anyone able to USB HDD boot an Asus netbook?

so if I read you correctly, you have slack 14 installed on the hd of an eeepc, but you're trying to boot from a usb stick? why, pray tell?

lee88abc 03-01-2013 08:04 PM

its a spinning hdd

lee88abc 05-17-2013 10:17 AM

Quote:

Originally Posted by the_penguinator (Post 4902846)
so if I read you correctly, you have slack 14 installed on the hd of an eeepc, but you're trying to boot from a usb stick? why, pray tell?

what? when did I say that?
just one usb hard drive.

mrclisdue 05-17-2013 01:02 PM

External/usb hds (actually, *all* drives in my experience) can be identified differently on each reboot: so whilst it's possible that when you first set up lilo, your usb hd may have been identified as /dev/sdb1, whereas on a reboot, it may be newly identified as /dev/sda1 (or /dev/sdc1.)

I'm not expert enough to tell you *why* this is the case, but I know that at some point between 13.37 and 14.0, this occurred.

The only surefire way around this that I'm aware of is to use either labels or uuids with lilo, which also requires an initrd. It's actually easier than it sounds, so if you go this route, I can help you out.

cheers,


All times are GMT -5. The time now is 01:00 AM.