I have a old linux box (PII200MMX) Suse 7.1 ,
kernel 2.4.-xxx with a 4 gig ide drive works fine.
Now I added an adaptec 2940 scsi card
and a seagate st32430n ( yes I know 2 gigs only).
Reboot. The bios shows the card and the new drive on
scsi id 0 lun 0.
Suse boots as usual ... where is the new drive ?
How do I get the new drive to come alive.....

cat /proc/scsi/scsi says nothing attached
mount /dev/sda talks someting not entered in fstab


Nx

Unless you have an entry in fstab you need to include the filesystem type and mount point when using the mount command.
And if you want to mount as a user also include the user option.

The command /sbin/lsmod will show you what modules are loaded. You need to load the SCSI module for the card and I think it uses aic7xxx.

I haven't used SUSE in awhile so if yast doesn't have an option for load modules then use modprobe.

modprobe aic7xxx

My experience is w/RH, but I have not had problems with having the system automatically seeing SCSI adapters and devices.

Try viewing /proc/scsi/scsi to see what SCSI devices your system is aware of. You should also see Linux boot messages as it detects the SCSI hardware (view dmesg, or your system log file if you want to look at them leisurely).

Once they are detected, you will need to partition the drive and create file systems on your partitions. After that you can mount them manually, or put the appropriate entries in /etc/fstab to have them mount at boot.

Thanks for the ideas, unfortunately lsmode does not see
any aicxxxx devices and dmesg shows that Linux is not aware
of the adaptec 2940 card and the drive.
I only can see it if I get into the bios , where the adapter (with id 7 and the drive (with id 0 ) is recognized correctly.
Could it be that my kernel 2.4.16-4GB needs some change ?

You need to load the aic7xxx.o module (i'm asssuming your using the stock kernel from suse install) for linux to be able to see the scsi controller. After that, you can partition the drive and enjoy. If you are going to use this as a bootable drive, you need to compile the aic7xxx driver into the kernel or use a ramdisk at boot (initrd).

Ok, the aic7xxx.o is now loaded and cat /proc/scsi/scsi
shows something like host: scsci0 Channel: 00 Id : 00 Lun :00
now what is the next step ?

create a file system ? mkefs2 -c /dev/sda ?
partition ? ( no boot partition required)
what needs to be added to fstab ?

Thanks
Nx

You need to fdisk (cfdisk) the new drive first. I prefer cfdisk.

>cfdisk /dev/sda
>mkfs.ext2 -c /dev/sda1 (2, whatever) #you can use any other FS as well (mkfs.ext3, mkreiserfs, mkfs.jfs, etc. I use ext3, some like reiser)

/etc/fstab will look like any other parition only /dev/sd(x) not /dev/hd(x)

cfdisk /dev/sda

Results in : Error cannot read disk drive

similar message for fdisk /dev/sda

Whats wrong ? Any lowlevel formating needed first ?

Nx

Show the ' cat /proc/scsi/scsi ' results.

Should look like mine.
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: DDYS-T36950M Rev: SC4D
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: PLEXTOR Model: CD-ROM PX-40TW Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: YAMAHA Model: CRW-F1S Rev: 1.0d
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
Vendor: MATSHITA Model: DVD-RAM LF-D200 Rev: A120
Type: CD-ROM ANSI SCSI revision: 04


Also show what ' cdrecord -scanbus ' shows

Shouldn't have to low level format. Check the output of demesg for errors with the SCSI controller or the SCSI hard drive.

Make sure you have the termination on the drive set to on or a terminator on the end of the cable. Verify proper configuration with the controller manual.

ok , here is what dmesg says : the last lines are of interest


Linux version 2.4.16-4GB (root@I386.suse.de) (gcc version 2.95.2 19991024 (relea
se)) #1 Mon Apr 15 13:33:50 GMT 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000006000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 24576
zone(0): 4096 pages.
zone(1): 20480 pages.
zone(2): 0 pages.
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=linux ro root=303 BOOT_FILE=/boot/vmlinuz B
OOT_FILE=/boot/vmlinuz
Initializing CPU#0
Detected 200.456 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 399.76 BogoMIPS
Memory: 94008k/98304k available (1497k kernel code, 3908k reserved, 428k data, 1
12k init, 0k highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
CPU: Before vendor init, caps: 008001bf 00000000 00000000, vendor = 0
Intel Pentium with F0 0F bug - workaround enabled.
CPU: After vendor init, caps: 008001bf 00000000 00000000 00000000
CPU: After generic, caps: 008001bf 00000000 00000000 00000000
CPU: Common caps: 008001bf 00000000 00000000 00000000
CPU: Intel Pentium MMX stepping 03
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: none
PCI: PCI BIOS revision 2.10 entry at 0xfb470, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.15)
Starting kswapd
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_I
RQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c586a (rev 25) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0x6500-0x6507, BIOS settings: hdaio, hdbio
ide1: BM-DMA at 0x6508-0x650f, BIOS settings: hdcio, hddio
hda: ST34342A, ATA DISK drive
hdd: ASUS CD-S400, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 8404830 sectors (4303 MB), CHS=523/255/63, UDMA(33)
hdd: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
ide-floppy driver 0.97.sv
Partition check:
hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda1 hda2 hda3
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
Cronyx Ltd, Synchronous PPP and CISCO HDLC (c) 1994
Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak.
ide-floppy driver 0.97.sv
SCSI subsystem driver Revision: 1.00
3ware Storage Controller device driver for Linux v1.02.00.010.
3w-xxxx: No cards with valid units found.
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 221.200 MB/sec
32regs : 198.000 MB/sec
pII_mmx : 308.400 MB/sec
p5_mmx : 365.200 MB/sec
raid5: using function: p5_mmx (365.200 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.1-rc4(03/10/2001)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k freed
Adding Swap: 136544k swap-space (priority -1)
isapnp: Scanning for PnP cards...
isapnp: Calling quirk for 01:00
isapnp: SB audio device quirk - increasing port range
isapnp: Calling quirk for 01:02
isapnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB AWE32 PnP'
isapnp: 1 Plug & Play card detected total
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0x6600. Vers LK1.1.16
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Single Channel A, SCSI Id=7, 16/253 SCBs

blk: queue c37703d8, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:0): 10.000MB/s transfers (10.000MHz, offset 15)
Vendor: SEAGATE Model: ST32430N Rev: 0346
Type: Direct-Access ANSI SCSI revision: 02
blk: queue c37704d8, I/O limit 4095Mb (mask 0xffffffff)
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
__alloc_pages: 0-order allocation failed (gfp=0x21/0)
scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=1552, scaling
SCSI device sda: 4197405 512-byte hdwr sectors (2149 MB)
sda: unknown partition table


So there is something on the scsi disk , probably an old
windows partition , therefore fsck does not work and talks
about bad magic number in super-block

cat /proc/scsi/scsi says :
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32430N Rev: 0346
Type: Direct-Access ANSI SCSI revision: 02


What can be done ?

[/quote]Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
__alloc_pages: 0-order allocation failed (gfp=0x21/0)
scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=1552, scaling
SCSI device sda: 4197405 512-byte hdwr sectors (2149 MB)
sda: unknown partition table [/quote]

Not being an expert here, I can't tell wether you have a hardware problem so you could try a low level format and see what happens. You should be able to format the drive from the SCSI controller BIOS. With it only be 2gb it shouldn't take to long.

Ok, used the scsi controller bios to reformat , (took 6 hours )
Sorry to say output is the same no change to what we had before.

Do you have any way to verify that this is a functional hard disk? The error you are seeing is indicative that the firmware on the drive is working to the point of identifying itself to the system, but that you are having problems talking to the platters.

Assuming the HDD is not broken, your problem is probably either your SCSI termination or your SCSI cables.

You need to have one, and only one SCSI terminator on your SCSI bus. The terminator needs to be at the physical end of your SCSI bus (i.e., if your SCSI cable extends beyond your HDD, the terminator has to be on the end of the cable and the HDD should not be jumpered to act as a terminator).

The best way I know to test SCSI cables is to swap them out with a known good cable.

If this is an internal ribbon cable, try to route it so that it is not wrapped around any power cables.

Try checking your syslog for entries mentioning SCSI parity errors. This would be indicative of SCSI bus and/or termination problems.

Sound like it starting to look like a hardware issue. Either a bad drive or cable issue. Could even be a bad cable.

Unplug your other harddrives try using the scsi harddrive, cable and controller only and see if you can install Linux on it. Here is where I would keep it simply floppy, scsi harddrive, scsi controller, cdrom, video card. Just let you install partition & format it automatically.

Also you can try booting your system with a Knoppix disc and see if it finds the drive and lets you mount it format it or something. You can do all the same ' cat /proc/scsi/scsi ' .

Last Resort, See if you can find somebody with scsi setup and see if they can partition and format it. Even if it is a Winblows system.

Good luck.
Brian1