AHA-2940UW Nightmares - Further info...

Marco Bravi (marco@impchim2.ing.uniroma1.it)
Fri, 31 Jan 1997 08:55:43 +0100 (MET)


This is a further clarification of the problem, since it seems that
simplification from my part of the actual setup of the computer room
brought to some confusion.

The basic test of the new controller and disk (and the one from which the
reported errors came---excerpt given below) is:

i486, k. 2.0.28, SCSI AHA-29xx compiled in (NOT module)
32MB RAM

/dev/hda (IDE, 540 MB) contains:

- /dev/hda1 (/)
- /dev/hda2 (swap)
- /dev/hda3 (/tmp)
- /dev/hda4 (extended)
- /dev/hda5 (/var)
- /dev/hda6 (/dos: actually an ext2 filesystem containing DOS prgms)

/dev/hdc (IDE, 2 GB) contains:

- /dev/hdc1 (/usr, all of the disk size)

This machine exports /usr and /dos (read-only) and mounts /home,
/var/spool/mail and /var/lib/texmf/fonts (all read-write) over NFS.

The planned switch was from a 2GB IDE drive to a 2GB Seagate Hawk 20 MB/s
SCSI drive---thus there was no new controller here and no SCSI disk
previously used on a different controller was used in this case. It was a
simple move-this-fs-on-a-different-partition task.

The HD appears to be terminated from a shorted jumper on the case.
Internal termination on the controller part was tried as both automatic
and manual on the used channel.

The HD was:
-low level formatted and verified
-Partitioned (only one 2 GB partition): fdisk would find an incorrect
partition table but suggested that w would correct this situation as it
actually did.
(Reboot performed)
-Formatted as ext2
-Mounted over /mnt
-started copy both with "cp -a" and "double pipe-connected tar"

450 to 600 MB of data were copied (out of 1.1GB) with occasional errors of
the type shown below. At the end of the copy a second try on the missing
files would return the same type of errors. Unmounting the (/dev/sda1)
partition and running fsck on it would return a _lot_ of errors;
conversely, /dev/hdc1 was clean at any time.

An excerpt of the errors observed:

Jan 30 21:01:49 pcainf2 kernel: EXT2-fs error (device 08:01):
ext2_find_entry: bad entry in directory #88145: r
ec_len % != 0 - offset=0, inode=400, rec_len=46863, name_len=8256
Jan 30 21:01:49 pcainf2 kernel: EXT2-fs error (device 08:01):
ext2_add_entry: bad entry in directory #88145: re
c_len % != 0 - offset=0, inode=400, rec_len=46863, name_len=8256
Jan 30 21:01:49 pcainf2 kernel: EXT2-fs error (device 08:01):

Thanks a lot for *any* help!!!!!! (I promise a summary).

-Marco

------------------------------+
Marco Bravi |
Dip. Ing. Chimica M. M. P. M. |
via Eudossiana, 18 | Phone #: (+39) (6) 44584780
I - 00184 Roma | Fax#: (+39) (6) 4837453 - 44585519