DebianThis forum is for the discussion of Debian 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.
I have two 160 GB Maxtor SATA-disks attached to a Silicon Image 3112A controller. I'm running the 2.6.5 kernel and have aded support for Silicon Image chip and RAID functionality. When runnig fdisk I can see a /dev/hde device, eaven though fdisk seems to read the partition table wrong.
However, when I try to mount the partitions (FAT32 fs) I get an error msg saying "wrong fs type, bad option, bad superblock on /dev/hde1, or too many mounted filesystems". I used the following command:
You may want to read up on the subject. The Sil3112(a)/3114 is like most onboard UATA/SATA controllers not a "real" RAID device. You may want to look into Thomas Horsten's Medley driver and read this excellent document.
The struggle goes on. I did something to the 2.6.6 kernel config (messed up graphics), so now I run 2.4.26. A happy surprise was that the drivers I need was included in this kernel for the first time. However, when I add support for the Silicon Image 3112 controller, the SATA drives shows up as hda and hdc (even though they are RAID-0, I thought is would be /dev/md0 or something). The normal hda drive (attached to the old primary IDE controller) is gone, and so the kernel is unable to mount root.
I can't find any info about this problem, but it's late and I've studied for 13 hours today so my mind is not the sharpest one in sweden right now...
compiled the Silicon Image drive as module instead of static, and so I got a correct mount of the root fs. But "insmod siimage.o" make the SATA disks cause problems with the hda IDE disk still. I get som output telling me that the two SATA disks are identified as /dev/hda and /dev/hdc, and then the fun begins.
The msg "hda irq interrupt" keeps coming up on the screen, and any type of access to any harddrive is impossible. I can use the keyboard, but all I really can to is pull the plug to reboot.