Linux won't detect HD's with my PCI RAID controller enabled.

Linux won't detect HD's with my PCI RAID controller enabled.

Post by Jack Whitm » Sat, 31 Jan 2004 14:03:07



Hey guys, and good day.

Here is my problem: I recently downloaded and compiled a new kernel so
I would have support for my new PCI ATA-133 RAID controller (Sil680
chip), and be able to access the HD that it controlls. I compiled the
kernel with support, made bzimage and tossed 'er place of the current
/vmlinuz, then I try booting this new kernel I get the error message:

Kernel panic: No init found. Try passing init=

The problem is, I have tried init=/bin/bash and I KNOW that /sbin/init
is in fact, valid and not corrupt.
So I proceed onto figuring out what else could be the problem.
So I realize that my root HD has changed, I was always booting with
root=/dev/hda1 since my root hd is IDE controller 1, disk 1, partition
1. The problem be that now that I have added support for this ATA PCI
controller, I look and notice that the kernel finds the controller and
it's attatched HD and assigns it as hda, successfully overriding my
default root disk/partition. Now being half intelligent, I try and
pass root as being everything from /dev/hdb to /dev/hdd with no luck
of landing on my hard drive. It seems the kernel is not recognzing my
standard IDE drives now that I have added support for this new PCI ATA
controller, this is in deed my problem. The kernel version is 2.4.24.

--K-sPecial

p.s plz help me boot :)

 
 
 

Linux won't detect HD's with my PCI RAID controller enabled.

Post by Adam » Sat, 31 Jan 2004 15:16:41



> Hey guys, and good day.

> Here is my problem: I recently downloaded and compiled a new kernel so
> I would have support for my new PCI ATA-133 RAID controller (Sil680
> chip), and be able to access the HD that it controlls. I compiled the
> kernel with support, made bzimage and tossed 'er place of the current
> /vmlinuz, then I try booting this new kernel I get the error message:

> Kernel panic: No init found. Try passing init=

> The problem is, I have tried init=/bin/bash and I KNOW that /sbin/init
> is in fact, valid and not corrupt.
> So I proceed onto figuring out what else could be the problem.
> So I realize that my root HD has changed, I was always booting with
> root=/dev/hda1 since my root hd is IDE controller 1, disk 1, partition
> 1. The problem be that now that I have added support for this ATA PCI
> controller, I look and notice that the kernel finds the controller and
> it's attatched HD and assigns it as hda, successfully overriding my
> default root disk/partition. Now being half intelligent, I try and
> pass root as being everything from /dev/hdb to /dev/hdd with no luck
> of landing on my hard drive. It seems the kernel is not recognzing my
> standard IDE drives now that I have added support for this new PCI ATA
> controller, this is in deed my problem. The kernel version is 2.4.24.

> --K-sPecial

> p.s plz help me boot :)

I presume you have tried using fdisk -l /dev/hda then hdb, hdc, etc
until you find the properly partitioned disk?

You could also look at the bios and find out how your bios is
identifying your old ide drive. I can't remember exactly how it all
looks and it depends a little on your motherboard and bios but basicaly
Primary Master IDE is hda Primary Slave is hda2 Secondary IDE is hdc,
etc. If your old drive is identified by your bios then Linux should pick
it up.

Hope this helps,

Adam

 
 
 

Linux won't detect HD's with my PCI RAID controller enabled.

Post by Jack Whitm » Sun, 01 Feb 2004 01:32:23




> > Hey guys, and good day.

> > Here is my problem: I recently downloaded and compiled a new kernel so
> > I would have support for my new PCI ATA-133 RAID controller (Sil680
> > chip), and be able to access the HD that it controlls. I compiled the
> > kernel with support, made bzimage and tossed 'er place of the current
> > /vmlinuz, then I try booting this new kernel I get the error message:

> > Kernel panic: No init found. Try passing init=

> > The problem is, I have tried init=/bin/bash and I KNOW that /sbin/init
> > is in fact, valid and not corrupt.
> > So I proceed onto figuring out what else could be the problem.
> > So I realize that my root HD has changed, I was always booting with
> > root=/dev/hda1 since my root hd is IDE controller 1, disk 1, partition
> > 1. The problem be that now that I have added support for this ATA PCI
> > controller, I look and notice that the kernel finds the controller and
> > it's attatched HD and assigns it as hda, successfully overriding my
> > default root disk/partition. Now being half intelligent, I try and
> > pass root as being everything from /dev/hdb to /dev/hdd with no luck
> > of landing on my hard drive. It seems the kernel is not recognzing my
> > standard IDE drives now that I have added support for this new PCI ATA
> > controller, this is in deed my problem. The kernel version is 2.4.24.

> > --K-sPecial

> > p.s plz help me boot :)

> I presume you have tried using fdisk -l /dev/hda then hdb, hdc, etc
> until you find the properly partitioned disk?

> You could also look at the bios and find out how your bios is
> identifying your old ide drive. I can't remember exactly how it all
> looks and it depends a little on your motherboard and bios but basicaly
> Primary Master IDE is hda Primary Slave is hda2 Secondary IDE is hdc,
> etc. If your old drive is identified by your bios then Linux should pick
> it up.

> Hope this helps,

> Adam

Ok, the drive that should be hda (and was untill I upgraded to add
support for the PCI ATA RAID controller) is ide controller 1, ide
device 1 in the bios (which it should be), although as we know, linux
doesn't occupy itself with the BIOS as much as other os's (such as
windows) do.
On boot of the kernel, it shows itself finding the PCI ATA RAID
controller, and identifying the HD that is attatched, and assigning it
as hda, while IT should be something more to the sort of hde. I don't
have access to fdisk around with this kernel, or to read /proc/ide, I
could of course do it with my old kernel which doesn't have the PCI
ATA-133 compiled on it (which would bump the correct HD back to hda),
but that of course would be defeating any reason for me to have posted
this problem. I will try to toss it higher devices such as hde-hdi(if
it exists) and will probably not have much success. Any further help
would be greatly appreciated.

--Jack

 
 
 

Linux won't detect HD's with my PCI RAID controller enabled.

Post by Gene » Sun, 01 Feb 2004 10:44:11



Quote:> Hey guys, and good day.

> Here is my problem: I recently downloaded and compiled a new kernel so
> I would have support for my new PCI ATA-133 RAID controller (Sil680
> chip), and be able to access the HD that it controlls. I compiled the
> kernel with support, made bzimage and tossed 'er place of the current
> /vmlinuz, then I try booting this new kernel I get the error message:

> Kernel panic: No init found. Try passing init=

Thats a very confusing error message.  IIRC, What the kernel is looking
for at that point is an hd spec in the form of "init=hd(0,0)" IF the /
directory is on /dev/hda1.  The first 0 is the drive number, and the
second 0 is the partition number on that drive that is thee /
partition.

Quote:> The problem is, I have tried init=/bin/bash and I KNOW that /sbin/init
> is in fact, valid and not corrupt.
> So I proceed onto figuring out what else could be the problem.
> So I realize that my root HD has changed, I was always booting with
> root=/dev/hda1 since my root hd is IDE controller 1, disk 1, partition
> 1. The problem be that now that I have added support for this ATA PCI
> controller, I look and notice that the kernel finds the controller and
> it's attatched HD and assigns it as hda, successfully overriding my
> default root disk/partition. Now being half intelligent, I try and
> pass root as being everything from /dev/hdb to /dev/hdd with no luck
> of landing on my hard drive. It seems the kernel is not recognzing my
> standard IDE drives now that I have added support for this new PCI ATA
> controller, this is in deed my problem. The kernel version is 2.4.24.

> --K-sPecial

> p.s plz help me boot :)

--
---
Cheers, Gene
There are 4 boxes to be used in the defense of liberty:
Soap, Ballot, Jury, and Ammo.  Please use in that order.
-Ed Howdershelt (Author)
 
 
 

Linux won't detect HD's with my PCI RAID controller enabled.

Post by Gene » Sun, 01 Feb 2004 10:51:44






>> > Hey guys, and good day.

>> > Here is my problem: I recently downloaded and compiled a new kernel
>> > so I would have support for my new PCI ATA-133 RAID controller
>> > (Sil680 chip), and be able to access the HD that it controlls. I
>> > compiled the kernel with support, made bzimage and tossed 'er place
>> > of the current /vmlinuz, then I try booting this new kernel I get
>> > the error message:

>> > Kernel panic: No init found. Try passing init=

>> > The problem is, I have tried init=/bin/bash and I KNOW that
>> > /sbin/init is in fact, valid and not corrupt.
>> > So I proceed onto figuring out what else could be the problem.
>> > So I realize that my root HD has changed, I was always booting with
>> > root=/dev/hda1 since my root hd is IDE controller 1, disk 1,
>> > partition 1. The problem be that now that I have added support for
>> > this ATA PCI controller, I look and notice that the kernel finds
>> > the controller and it's attatched HD and assigns it as hda,
>> > successfully overriding my default root disk/partition. Now being
>> > half intelligent, I try and pass root as being everything from
>> > /dev/hdb to /dev/hdd with no luck of landing on my hard drive. It
>> > seems the kernel is not recognzing my standard IDE drives now that
>> > I have added support for this new PCI ATA controller, this is in
>> > deed my problem. The kernel version is 2.4.24.

>> > --K-sPecial

>> > p.s plz help me boot :)

>> I presume you have tried using fdisk -l /dev/hda then hdb, hdc, etc
>> until you find the properly partitioned disk?

>> You could also look at the bios and find out how your bios is
>> identifying your old ide drive. I can't remember exactly how it all
>> looks and it depends a little on your motherboard and bios but
>> basicaly Primary Master IDE is hda Primary Slave is hda2 Secondary
>> IDE is hdc, etc. If your old drive is identified by your bios then
>> Linux should pick it up.

No, incorrect I believe. hda is ide0,0,  hdb is ide0,1,  hdc is ide1,0
and hdd is ide1,1

Linux uses a base 0 numbering system, and this is a different numbering
scheme from my previous answer.

It also gets a whole lot easier if you use grub instead of lilo.  Then
you just add another entry to the boot choice table.  I currently have
a choice of 16 different kernels I can boot from.  Currently running
2.6.2-rc2-mm2.

- Show quoted text -

Quote:>> Hope this helps,

>> Adam

> Ok, the drive that should be hda (and was untill I upgraded to add
> support for the PCI ATA RAID controller) is ide controller 1, ide
> device 1 in the bios (which it should be), although as we know, linux
> doesn't occupy itself with the BIOS as much as other os's (such as
> windows) do.
> On boot of the kernel, it shows itself finding the PCI ATA RAID
> controller, and identifying the HD that is attatched, and assigning it
> as hda, while IT should be something more to the sort of hde. I don't
> have access to fdisk around with this kernel, or to read /proc/ide, I
> could of course do it with my old kernel which doesn't have the PCI
> ATA-133 compiled on it (which would bump the correct HD back to hda),
> but that of course would be defeating any reason for me to have posted
> this problem. I will try to toss it higher devices such as hde-hdi(if
> it exists) and will probably not have much success. Any further help
> would be greatly appreciated.

> --Jack

--
---
Cheers, Gene
There are 4 boxes to be used in the defense of liberty:
Soap, Ballot, Jury, and Ammo.  Please use in that order.
-Ed Howdershelt (Author)
 
 
 

1. Newbie Question: Trying to install LinuxPPC but won't detect my HD

When I try to install linux, either from X Linux Install or the RedHad
install, the installer does not detect my HD (and it is not spinning).

Can anyone find what I am doing wrong? (I hope it isn't something
stupid =])

Before I start, yes I have read every single word of the user guide and
checked the linuxppc website...

I am using a G4-PCI/400, with 2 HD installed (master-slave
configuration).  I am using the BlueG3 Rev.2 kernel, as specified in
the note for G4 PowerMac on linux.org
(http://www.linuxppc.org/hardware/g4.shtml).  I want to install linux
on the slave HD, which has 4 partitions. 1 is the root (HFS), 1 is the
swap (HFS), 1 is a Mac/Linux shared stuff (HFS) and one is a personal
backup (HFS+).  The root and swap have been unflagged for the "auto
mount at startup" as explained in the user guide.

First, I was booting from the master HD, then I tried booting from the
Mac/Linux shared partition - nothing changed.  I use the hdX=noautotune
(as explained in the note) and I tried "hdb" since I am using a slave
HD, but then I also tried "hdd" since the bus used is 1 (not 0 since 0
is used by the CD-ROM and Zip drive).

When I boot from the ram image, first, the two hd are unmounted (this I
can hear), then I get the black console screen, lots of stuff I don't
have the time to read (btw, is there a way to freeze the screen so that
I can read?), and then it says it could not find live.filesystem (but
at that point, the two HD are still unmounted, so I don't even think it
really checks for that file.  I have downloaded and uncompressed the
file live.filesystem and it is on my HFS Mac/Linux shared partition).
Then it launches the redhat installers.  I cannot *try* to install from
the HD, it will quit instantly and reboot.  I tried from ftp.
Everything went fine until I had to use fdisk which told my I had no
device connected to the computer.

I downloaded about 100Mb of stuff from ftp.linuxppc.org (I followed
what was said in the user guide).

Anyone can see what I am doing wrong?

Gaspard Petit

2. Damn it, Beavis!!!

3. Problem: Slackware won't detect my adaptec controller

4. shutdown.allow

5. PROBLEM: Slackware won't detect my adaptec controller

6. Linux connection to LineOne?

7. Red Hat 5.0 won't detect Always IN2000 SCSI controller

8. Fedora 5 with Cisco VPN Client

9. Linux's INSTALL won't find files on HD partition

10. 3com Etherlink III PCI Combo won't detect correctly

11. Install program won't recognize integrated PCI E/N controller

12. Help: Doesn't detect my SCSI HD's

13. x-win won't start with eth0 enabled