RE: A SCSI problem

From: Mike Westkamper (mjwestkamper_at_weiinc.com)
Date: 01/30/04

  • Next message: Scott Burns: "Re: newbie PS1 config question"
    To: <fedora-list@redhat.com>
    Date: Thu, 29 Jan 2004 19:23:09 -0500
    
    

    -----Original Message-----
    From: fedora-list-admin@redhat.com
    [mailto:fedora-list-admin@redhat.com]On Behalf Of Alexander Dalloz
    Sent: Friday, January 23, 2004 10:03 AM
    To: fedora-list@redhat.com
    Subject: RE: A SCSI problem

    Am Fr, den 23.01.2004 schrieb Mike Westkamper um 15:31:
    > I seemingly am unable to make this work at boot time.
    > I believe I followed Alexanders instructions correctly, however the system
    > still does not find the adapter nor mount the drives at boot time.

    You made a ramdisk initrd.img which contains the scsi module?

    > Furthermore, I cannot mount the drives after I do a manual modprobe aix*.

    No, "modprobe aic7xxx" is the correct syntax, nothing else. Maybe you
    need to pass special options as I wrote in my first reply!

    > fdisk list all 8 drives correctly after the modproble, however a number of
    > attempts to mount them fail.

    Please post syslog entries when the modprobe was executed but not drives
    are recognized (/var/log/messages is the relevant file).

    > The drives were configured as a softraid by RedHat Linux 7.2.
    >
    > I copied the raidtab from the 7.2 version and updated the fstab to the
    > Fedora version and it still does not seem to work.

    And the Adaptec controller was used on RH 7.2 too or was it different
    hardware?

    > Thanks in advance for any direction...
    >
    > Mike

    Please do NOT top-post. Not good for following and answering in
    discussion.

    Alexander

    Greetings:

    After a few days away I am back trying to solve this problem.

    I modified the modules.conf to:
    ===============
    alias eth0 3c509
    alias scsi_host_adapter aic7xxx
    options aic7xxx 'aic7xxx=probe_eisa_vl.tag_info:{{}.{.10}}.seltime:1'
    ===============

    Next I did a mkinitrd and logged the results:
    ===============
    Looking for deps of module scsi_mod
    Looking for deps of module sd_mod scsi_mod
    Looking for deps of module scsi_mod
    Looking for deps of module unknown
    Looking for deps of module aic7xxx scsi_mod
    Looking for deps of module scsi_mod
    Looking for deps of module ide-disk
    Looking for deps of module ext2
    Using modules: ./kernel/drivers/scsi/scsi_mod.o
    ./kernel/drivers/scsi/sd_mod.o ./kernel/drivers/scsi/aic7xxx/aic7xxx.o
    Using loopback device /dev/loop0
    /sbin/nash -> /tmp/initrd.iF2107/bin/nash
    /sbin/insmod.static -> /tmp/initrd.iF2107/bin/insmod
    `/lib/modules/2.4.22-1.2149.nptlcustom/./kernel/drivers/scsi/scsi_mod.o' ->
    `/tmp/initrd.iF2107/lib/scsi_mod.o'
    `/lib/modules/2.4.22-1.2149.nptlcustom/./kernel/drivers/scsi/sd_mod.o' ->
    `/tmp/initrd.iF2107/lib/sd_mod.o'
    `/lib/modules/2.4.22-1.2149.nptlcustom/./kernel/drivers/scsi/aic7xxx/aic7xxx
    .o' -> `/tmp/initrd.iF2107/lib/aic7xxx.o'
    Loading module scsi_mod
    Loading module sd_mod
    Loading module aic7xxx with options
    'aic7xxx=probe_eisa_vl.tag_info:{{}.{.10}}.seltime:1'
    ===============

    Upon rebooting the machine, carefully choosing the correct kernel, the boot
    process proceeds normally until it produced the following error on the
    console:
    ===============
    /lib/aic7xxx.0
     insmod errors can be caused by incorrect IO or IRQ .....
    /bin/insmod exited abnormally
    ===============
    The error text may not be exactly correct as it was scrolling when I tried
    to catch it. I could not find the message in the boot sequence logged in
    /var/log/messages or dmesg or in boot.log A fdisk -l did not show the SCSI
    drives.

    Next, if I do an insmod aic7xxx the module loads and the drives appear.

    Help is really appreciated.

    --
    Alexander Dalloz | Enger, Germany
    PGP key valid: made 13.07.1999
    PGP fingerprint: 2307 88FD 2D41 038E 7416  14CD E197 6E88 ED69 5653
    --
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Scott Burns: "Re: newbie PS1 config question"

    Relevant Pages

    • RE: A SCSI problem
      ... I seemingly am unable to make this work at boot time. ... I believe I followed Alexanders instructions correctly, ... I cannot mount the drives after I do a manual modprobe aix*. ... Alexander Dalloz | Enger, Germany ...
      (Fedora)
    • Re: (aic78xx) ReBoot Problem
      ... 1 (SCSI Request Completed Ok!) Error! ... is the first command the SCSI system sets on a new-found device. ... There is no reason to assume that the buffer was pre-zeroed. ... At boot time I think the standard inquiry data are ...
      (comp.periphs.scsi)
    • RE: A SCSI problem
      ... den 23.01.2004 schrieb Mike Westkamper um 15:31: ... > still does not find the adapter nor mount the drives at boot time. ... No, "modprobe aic7xxx" is the correct syntax, nothing else. ... Alexander Dalloz | Enger, Germany ...
      (Fedora)
    • Re: Mirrored SCSI Drives and 5.0.7
      ... > I am setting up a new IBM server which has two Ultra 160 SCSI hard drives ... > connected to a dual channel Ultra320 SCSI controller. ... Your on board Ultra320 SCSI controller, I believe, but not absolutely sure, ... you may need a boot time loadable driver and defbootstr at install ...
      (comp.unix.sco.misc)
    • Kernel 2.4.21 gives kernel panic at boot time
      ... but i got follwing message at boot time. ... /lib/mptscsih.o: unresolved symbol ... Looking for deps of module scsi_mod ... Looking for deps of module mptbase ...
      (Linux-Kernel)