Koozali.org: home of the SME Server

ATA100

Miguel

ATA100
« on: February 23, 2001, 01:49:55 AM »
Hi.
I am trying to install E-Smith 4.1 on two (RAID 1) IBM ATA100, with Asus A7V mainboard (Via Apollo KT133) "UltraDMA/100 ready".
According to the Linux hardware databases, Asus A7V is supported. But when I start the E-Smith CD-Rom, the installation fails when it gets to the hardrives, and kernel panic comes around.
My question is this: does E-Smith (Red-Hat) supports ATA100 harddrives? If not, is there a patch or update?.
Otherwise, is there a way to tell the kernel to see the disks? I have been reading an article by Aaron Cline where he manages to tell Red-Hat installation to get the ATA100 disks, but for that I need to write at the command prompt the I/O for the Promise controller. And E-Smith installation only gives me the chance to write "accept".
Any way out?
Thanks a lot in advance.
Miguel

Gerald Jansen

Re: ATA100
« Reply #1 on: February 24, 2001, 09:18:46 AM »
e-smith is set up to accept a SINGLE drive. This is clear in all documentation. If you wish to have a second drive recognized you must do it yourself.

Stephan

Re: ATA100
« Reply #2 on: February 25, 2001, 04:48:27 PM »
Just install it as usual. After the installation you can execute the command:

hdparm -Xnn /dev/hda  

where nn is:

64 for ATA33
66 for ATA66
68 for ATA100

Tim Larson

Re: ATA100 and SW RAID
« Reply #3 on: February 28, 2001, 04:11:54 AM »
It is possible and not very difficult to set up software RAID using two IDE drives and an ATA/100 controller.  I recently installed E-smith 4.1 onto two 40GB Maxtor drives, each on it's own ATA/100 controller, using SW RAID, and here are some instructions on how to do the same.

NB: I took a bunch of this from http://www.linuxnewbie.org/nhf/intel/hardware/udma66.html
but modified it to suit the e-smith distro.

Boot up on the esmith CD, typing "accept", etc., and when you finally get to the part where you can start choosing what hard drive option you want, hit "Alt-F2" or "Ctrl-Alt-F2".  I forget which one.  One of these should bring you to a shell.  If you see a "#" in the top of the screen you did it right.  Now type in "cat /proc/pci | more"   This will show you more than you wanted to know about all the PCI devices in your system.

Look for something like this:

----begin snip from web page listed above---------

Unknown mass storage controller: Promise Technology Unknown device (rev 1). Vendor id=105a. Device id=4d38.
Medium devsel. IRQ 5. Master Capable. Latency=64.
I/O at 0x1400 [0x1401].
I/O at 0x10f4 [0x10f5].
I/O at 0x10f8 [0x10f9].
I/O at 0x10f0 [0x10f1].
I/O at 0x1080 [0x1081].

Now Note down the values on those lines beginning with I/O, call them a, b, c, d (which in my case are 0x1400, 0x10f4, 0x10f8, 0x10f0). Ignore "e" (0x1080).

Then give the following command line argument to your kernel on the "lilo" prompt.

lilo: linux ide2=a,b+2 ide3=c,d+2

Which in my case is:
lilo: linux ide2=0x1400,0x10f6 ide3=0x10f8,0x10f2
-----end snip--------


What I did was a little different.  This guy had only one ATA/100 controller, I had two.  So, if I had a,b,c, and d from my first controller, and e,f,g,h from my second controller, I used the following:
lilo: accept ide2=a,b+2 ide3=e,f+2
(a and b are for the primary cable on my first controller card, c and d are for the secondary cable on my first controller card, e and f are for the primary cable on my second controller card, and g and h are for the secondary controller on my second card - hope that makes sense)

Well, after you note down all these bizarre numbers, reboot (Ctrl-Alt-Del).

This time, type in what you learned from above (except, instead of typing "linux ide2=.....", type in "accept ide2=.....", without the quotation marks, and with the hex numbers you figured out above.

This will let the installation find your hard drive.  Setting up the raid-1 is easy - you just choose if from the menu when it comes up.  But the problem after installation is that every time you boot you have to type this funny sequence of numbers in.

You have to do this the first time - except now, instead of typing "accept ide2=....", hit the key to find out what you put in place of "accept".  That will get your system up and running.

  You don't want to have to do that every time you boot up the machine, though.  So after you get everything up and running, log in as root with your root password (if all you see is the colorful administration menu, hit "Alt-F2" to get a login prompt, and "Alt-F1" later to get back to the administration menu - and when you are going back to F1, don't forget to first log out by typing "exit").

After you have logged in, type "pico /etc/lilo.conf" to edit the bootup configuration file.  Under the entry where it says "image=/boot/vmlinuz-2.2.16-22" (or similar), you should see four or five settings.  Go down below these and add an append line.  Here is what my /etc/lilo.conf looks like:

----------begin /etc/lilo.conf-------------
boot=/dev/md0
disk=/dev/md0
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/e-smith.pcx
default=esmith

image=/boot/vmlinuz-2.2.16-22
        initrd=/boot/initrd-2.2.16-22.img
        label=esmith
        read-only
        root=/dev/md1
        append="ide2=0xda00,0xd803 ide3=0xd000,0xce03"

--------------end /etc/lilo.conf--------------

Note:  the quotation marks are needed in the append line.  And make sure you put in for the 0xda00 and such whatever you put in to boot off the CD in the first place - the ones here are just the values for my computer.

After you change the file, hit "Ctrl-O" to save it, then "Ctrl-X" to quit the editor.  Now type "lilo" to save the settings to the boot sector of your hard drive.  If you've used lilo before, this will look a little funny because you are using RAID - it will write the boot sector to both hard drives (I think that's what it's doing, at least).

Now reboot and pray that it worked.  

I got a great deal on my drives - after various mail-in-rebates, I get both 40GB Maxtor drives and both ATA/100 controllers for $200 total.  I couldn't pass up the deal, so I got them, and then dug around to figure this stuff out.

If I need to clarify this, I'll be glad to, just let me know.

      Tim Larson

Miguel

Re: ATA100 and SW RAID
« Reply #4 on: February 28, 2001, 03:33:18 PM »
Thanks a lot for your help, Tim.
I will try your ideas when I come back from my holydays and let you know.
What controller are you using? I am using Promise, incorporated in my A7V Asus mainboard. Do you know if there is any problem with it? Or with Athlon micro (800)?
Miguel

Miguel

Re: ATA100 and SW RAID
« Reply #5 on: March 10, 2001, 02:14:14 AM »
Tim, I tried your ideas. Everything went as you wrote.
A couple of things. First, the kernel keeps every time to detect /dev/hda and /dev/hdc, although discs have moved to hde and hdg.
Second, I have check speed qith hdparm -t and the values is about the same I get in my ata/33, about 10 MB/s, and before, with discs attached to IDE controller, I used to get 30 MB/s. But then I moved a 45 MB. file from one side to the other, from partion to a different partition, and it took a couple of seconds to pass 45 MB. Obsolete hdparm? Any clue about tese things?
Miguel

Chris Glanzer

Re: ATA100 and SW RAID
« Reply #6 on: April 29, 2001, 09:33:05 AM »
I am currently trying to set up something simular.  I have an old 166 with bios so old it will not recognize my new maxtor 40gb drives.  I have a promise fasttrack 66 and it sees the drives.  I tried what you said and progress to a point right after typing "progress".  I get an error creating swap on drive md2.  Did this ever occur for you?  Please let me know if you have any ideas.

Thanks,
Chris Glanzer