[1744] in linux-scsi channel archive
Re: Adaptec 3940 problems with Linux 2.0.29
daemon@ATHENA.MIT.EDU (Mr. Ryan Behnke)
Wed Apr 23 03:57:30 1997
Date: Tue, 22 Apr 1997 18:53:02 -0500 (CDT)
From: "Mr. Ryan Behnke" <behnkera@mrs.umn.edu>
To: Zane Dodson <dodson@mza.com>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <199704222212.QAA13084@redwood>
I am having similar problems with our linux server ie. the NFS problems,
and Reboot problems, and fsck problems with extra i-nodes after hard
rebooting. We have an older DPT scsi card, I would put a list of messages
that we get on ours but that part of the disk is unreadable due to the
problems. The server is on a p-100 and worked fine till a week or two
ago. The only recent change to it was upgrading it to redhat 4.1, but
that was over a month ago. Had no problems with it before that. The scsi
disk is a two gig seagate.
Ryan
On Tue, 22 Apr 1997, Zane Dodson wrote:
> Hello,
>
> I am experiencing some bizarre problems that I believe are software
> related with a SuperMicro P6DNE motherboard (with 1 Pentium Pro 200),
> 64MB RAM, and an Adaptec 3940UW SCSI controller. This is a twin channel
> SCSI host adapter and I have two large ultra wide Micropolis disks,
> a Jaz drive, a CDROM drive, and an 8mm tape drive. The exact configuration
> is listed below. The kernel is 2.0.29..
>
> My problems lead me to believe my particular configuration and the
> Adaptec 3940UW scsi driver are not functioning together properly.
>
> Any pointers would be appreciated.
>
> Best regards,
>
> Zane Dodson
> dodson@mza.com
> http://www.mza.com/~dodson
>
> Here is a summary of my problems:
>
> Jaz access problems
> An ls of the jaz directory hangs indefinitely. It does not appear to
> be related to the spin down of the drive.
>
> NFS problems
> As an NFS server, its disks often become inaccessible to other
> clients, hanging indefinitely when access is attempted. However, the
> disks are accessible locally. Client-side NFS and NIS work fine.
> This period of broken NFS is just before the machine begins to
> exhibit some of the other behaviors I have listed below.
>
> shutdown problems
> Occassionally, the machine cannot be shutdown with the shutdown or
> reboot commands. They run and warn of a shutdown, but nothing happens.
> The only way to recover is with a hard reset.
>
> After a hard reset, there are many filesystem problems and I
> normally have to run fsck manually to fix the filesystem.
>
> non-existent partition filesystem complaints
> The syslog logs messages about filesystem errors and directory problems
> on partition /dev/sdb5 (major 08, minor 21), which does not exist in
> the partition table. Here is an excerpt:
>
> Apr 11 20:27:07 knuth kernel: VFS: Mounted device 08:21 - tssk, tssk
> Apr 11 20:27:07 knuth kernel: VFS: inode busy on removed device 08:21
> Apr 11 20:27:07 knuth kernel: Device busy for revalidation (usage=1)
> Apr 12 01:39:07 knuth kernel: scsidisk I/O error: dev 08:21, sector 528
> Apr 12 01:39:07 knuth kernel: EXT2-fs error (device 08:21): ext2_readdir: directory #2 contains a hole at offset 0
> Apr 12 01:39:08 knuth kernel: scsidisk I/O error: dev 08:21, sector 16
> Apr 12 01:39:08 knuth kernel: Kernel panic: EXT2-fs panic (device 08:21): ext2_write_inode: unable to read i-node block - inode=2, block=8
> Apr 12 01:39:08 knuth kernel:
> Apr 12 01:39:10 knuth kernel: scsidisk I/O error: dev 08:21, sector 2
>
> Another excerpt is:
>
> Apr 19 01:48:00 knuth kernel: scsidisk I/O error: dev 08:21, sector 528
> Apr 19 01:48:01 knuth kernel: EXT2-fs error (device 08:21): ext2_readdir: directory #2 contains a hole at offset 0
> Apr 19 01:48:04 knuth kernel: scsidisk I/O error: dev 08:21, sector 16
> Apr 19 01:48:04 knuth kernel: Kernel panic: EXT2-fs panic (device 08:21): ext2_write_inode: unable to read i-node block - inode=2, block=8
> Apr 19 01:48:04 knuth kernel:
> Apr 19 01:48:04 knuth kernel: scsidisk I/O error: dev 08:21, sector 2
>
> And another one:
>
> Apr 21 09:00:14 knuth kernel: Device not ready. Make sure there is a disc in the drive.
> Apr 21 09:00:14 knuth kernel: Device busy for revalidation (usage=1)
> Apr 21 09:02:14 knuth kernel: Device not ready. Make sure there is a disc in the drive.
> Apr 21 09:02:14 knuth kernel: Device busy for revalidation (usage=1)
> Apr 21 09:02:19 knuth kernel: Device not ready. Make sure there is a disc in the drive.
> Apr 21 09:02:19 knuth kernel: Device busy for revalidation (usage=1)
> Apr 21 09:02:40 knuth kernel: scsidisk I/O error: dev 08:21, sector 20
> Apr 21 09:02:40 knuth kernel: Kernel panic: EXT2-fs panic (device 08:21): ext2_read_inode: unable to read i-node block - inode=17, block=10
> Apr 21 09:02:40 knuth kernel:
> Apr 21 09:02:40 knuth kernel: scsidisk I/O error: dev 08:21, sector 2
> Apr 21 09:09:43 knuth su: dodson on /dev/ttyp5
> Apr 21 09:11:11 knuth init: Switching to runlevel: 0
> Apr 21 09:11:13 knuth kernel: scsidisk I/O error: dev 08:21, sector 16
>
>
>
>
> Kernel information (uname -a)
> =============================
> Linux knuth 2.0.29 #3 Fri Apr 11 08:36:31 MDT 1997 i686
>
> Partition information
> =====================
> [root@knuth /root]# fdisk -l
> The number of cylinders for this disk is set to 1106.
> This is larger than 1024, and may cause problems with:
> 1) software that runs at boot time (e.g., LILO)
> 2) booting and partitioning software form other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
>
> Disk /dev/sda: 255 heads, 63 sectors, 1106 cylinders
> Units = cylinders of 16065 * 512 bytes
>
> Device Boot Begin Start End Blocks Id System
> /dev/sda1 1 1 2 16033+ 83 Linux native
> /dev/sda2 3 3 33 249007+ 82 Linux swap
> /dev/sda3 34 34 700 5357677+ 83 Linux native
> /dev/sda4 701 701 1106 3261195 83 Linux native
> The number of cylinders for this disk is set to 1106.
> This is larger than 1024, and may cause problems with:
> 1) software that runs at boot time (e.g., LILO)
> 2) booting and partitioning software form other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
>
> Disk /dev/sdb: 255 heads, 63 sectors, 1106 cylinders
> Units = cylinders of 16065 * 512 bytes
>
> Device Boot Begin Start End Blocks Id System
> /dev/sdb1 1 1 1106 8883913+ 83 Linux native
>
> Disk /dev/sdc: 64 heads, 32 sectors, 1021 cylinders
> Units = cylinders of 2048 * 512 bytes
>
> Device Boot Begin Start End Blocks Id System
> /dev/sdc1 1 1 1021 1045488 83 Linux native
>
>
>
> SCSI Bus information
> ====================
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: MICROP Model: 3391WS Rev: P429
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 03 Lun: 00
> Vendor: NEC Model: CD-ROM DRIVE:462 Rev: 1.16
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: MICROP Model: 3391WS Rev: P429
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 04 Lun: 00
> Vendor: iomega Model: jaz 1GB Rev: G.60
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 06 Lun: 00
> Vendor: EXABYTE Model: EXB-85058SQANXR1 Rev: 07R0
> Type: Sequential-Access ANSI SCSI revision: 02
>
> Adapter information scsi0
> =========================
> Adaptec AIC7xxx driver version: 4.0/3.2/4.0
>
> Compile Options:
> AIC7XXX_RESET_DELAY : 15
> AIC7XXX_TWIN_SUPPORT : Enabled
> AIC7XXX_TAGGED_QUEUEING: Disabled
> AIC7XXX_PAGE_ENABLE : Disabled
> AIC7XXX_PROC_STATS : Disabled
>
> Adapter Configuration:
> SCSI Adapter: AHA-3940 Ultra
> (AIC-788x chipset)
> Host Bus: Wide
> Base IO: 0xdc00
> IRQ: 10
> SCBs: Used 2, HW 16, Page 16
> Interrupts: 29085
> Serial EEPROM: True
> Extended Translation: Enabled
> SCSI Bus Reset: Enabled
> Ultra SCSI: Enabled
> Target Disconnect: Enabled
>
> Adapter Information scsi1
> =========================
> Adaptec AIC7xxx driver version: 4.0/3.2/4.0
>
> Compile Options:
> AIC7XXX_RESET_DELAY : 15
> AIC7XXX_TWIN_SUPPORT : Enabled
> AIC7XXX_TAGGED_QUEUEING: Disabled
> AIC7XXX_PAGE_ENABLE : Disabled
> AIC7XXX_PROC_STATS : Disabled
>
> Adapter Configuration:
> SCSI Adapter: AHA-3940 Ultra
> (AIC-788x chipset)
> Host Bus: Wide
> Base IO: 0xd800
> IRQ: 9
> SCBs: Used 4, HW 16, Page 16
> Interrupts: 16604
> Serial EEPROM: True
> Extended Translation: Enabled
> SCSI Bus Reset: Enabled
> Ultra SCSI: Disabled
> Target Disconnect: Enabled
>
>
>
