Slack 13 - no target disk - Acer Aspire one 11.6 - sata issue?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Slack 13 - no target disk - Acer Aspire one 11.6 - sata issue?
Loaded slack 13 fine on a Sony Viao la top and an HP mini netbook. Slack 12.2 and now 13 still fail to find an install destination (tried /dev/hda, hdb, ... and /dev/sda, b, c etc. Install will find the 4 GB SD mem card, but obviously, I do not wan to choose that. Centos, fedora and ubuntu all see the disk as /dev/hda. I am stumped. Try booting into the bare.i or other kernels?
Centos, fedora and ubuntu all see the disk as /dev/hda.
This is quite strange, as Ubuntu hacks their kernel to make almost all devices use /dev/sd$ - unless it's a generic PATA device that no model is available for. They literally hack lib.ata to force it to be used, even for devices that lib.ata does not support. Been this way since pre Gusty. Which is why I suggested to check the BIOS for AHCI settings.
pci=nomsi did not product any partitions that the system saw. Not sure what to try next. I guess I could try loading fedora and then try to load slack over that, But I think even then, slack does not see a disk.
This is weird. Still researching. Maybe worth using RH or fedora to build a system and then find all the drivers etc the system uses? Would that help?
I got around the install problem with help from this armedslack mailing list response:
I installed Slackware 13 on a fit-pc 2 (Intel Atom Z530) and I had the
same problem, it couldn't see the ide hard drive.
Like you I tried without success to pass "ide generic" options to the kernel...
I sorted out the problem by recompiling the kernels (both the kernel
used by the Slack installer 188.8.131.52 and afterwards my "daily" kernel
using 184.108.40.206) and adding pata_sch support (CONFIG_PATA_SCH=y in the
Basically the pata_sch support has to be either built into your
kernel (or into the initrd...I don't use initrd would that work ??
would that be a simpler way of adding pata_sch support on boot ??)
otherwise the kernel won't be able to access your root partition when
As he hinted at, I get a scsi error at boot time. Any way to tell the kernel to use the pata_sch module when it tries to boot? [I know, chicken and the egg... ;-]
Going to give it another shot tonight.. Try the noudev option also.
Thanks onebuck. That was what I was thinking. As an experiment this morning, I hit tab at lilo prompt and entered
boot> Linux append="noudev"
error is still:
VFS: Cannot open root device "801" or unknown-block(8.1)
Please append a correct "root=" boot option; here are the available partitions:
kernel panic - not syncing: VFS: Unable to mount root fs unknown-block(8,1)
Requires a power cycle. Now, just to find the right combination to get it to boot and then I can edit lilo with the correct parameters. Essentially, it sounds like I need to enable the
Never messed with making an initrd, so I will search that in the forums. If I can modprobe or include that module in a new kernel it should work. initrd might be better... Thanks!
onebuck - eggcellent info, and I grok it now. Almost worked even. Let me list out what I did to try this out, and ya'll tear it to shreds. Right idea, wrong implementation on my part. Will post and then try new things while I wait for the flames ;-]
o boot off slack 13 dvd iso.
o when ready to run setup, but needing to "see" the disk, I installpkg the kernel modules etc and modprobe pata_sch
mount /dev/sr0 /mnt/cdrom
o [system now sees /dev/sda1 which has the freshly installed slack 13 system]
I figure to mkinitrd and to edit/run lilo, I need to be chroot'd into /dev/sda1
mkdir /dev/dora [dora is the name of the machine]
mount /dev/sda1 /mnt/dora
modprobe pata_sch [tried with inatlling all the kernel stuff in the readme]
mkinitrd -c -k 220.127.116.11 -m pata_sch
vi lilo.conf [make edits adding the initrd line after the kernel image name]
lilo [to recreate lilo]
o this is where I figure I am screwing things up, because I end up with a "you should never end up here, trouble ahead" shell, with the following errors:
Freeing unused kernel momory: 364k freed
No kernel modules found for Linux 18.104.22.168-smp
mount: no /etc/mtab
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try and fix it. Type 'exit' when things are done.
o I am thinking this cannot be accomplished in a chroot'd environment, because mkinitrd complained that /proc/something [cannot remember the /proc device] was not there to read for disk partitions.
What I am confused about is how to run mkinitrd when the system cannot see the disk drive at boot time. I think I am confused about initrd ;-]
Ok, getting closer. I took the advice in other replies to other threads and _searched_ a bit ;-] I was only chroot'ing into the mounted disk, I was not mounting critical partitions. I found this [thx rworkman]:
I can mount /proc ok, but /sys is not in fstab. Could be because of my lazy installs /, /home and swap ;-]
I get further, now it sees the disk and lists the partitions. The panic into rescue shell is new, and makes more sense:
mounting /dev/sda1 on /mnt failed: No such device [I think this is the key - should not be mounting on /mnt]
ERROR: No /sbin/init found on rootdev (or not mounted)
As soon as I find the missing mount point and get it working, I will update all. Thanks for all the help so far... I am sure I am going to need more later...