[4829] in linux-scsi channel archive
bt958 & sense errors
daemon@ATHENA.MIT.EDU (Sandy Basickes)
Wed Oct 7 00:05:44 1998
Date: Tue, 6 Oct 1998 22:13:06 -0400 (EDT)
To: linux-scsi@vger.rutgers.edu
From: Sandy Basickes <basic@Op.Net>
scsi disk errors
linux 2.035 bt958 disk controler (5.06i version) on a pentium
a baracuda 4.2 gig and a syquest sysjet are attached.
the seagate baaaracuda is terminated on the board.
the syjet has an active idc terminator placed on the cable that attaches to
to the bt958 controller.
the tmc company attached the terminator to the cable and sent it to me.
sda1 failure
run fsck
fsck /dev/sda1
parallelizing fsck version 1.10 (24apr97)
e2fsck 1.10,24apr97 for EXT2 FS 0.5b,95/08/09
/dev/sda1 was not cleanly unmounted, check forced.
pass 1: checking inodes,blocks,sizes
scsio:Medium Error on channel 0,id 0,lun 0, CDB: Read (6) 0c 80 61 02 00
current error sd08:01: sense key meduium error.
additional sense indicates Data synchronization mark error.
scsidisk i/o error: dev 08:01,sector 819234,absolute sector 819297
scsio:Medium Error on channel 0,id 0,lun 0, CDB: Read (6) 0c 80 61 02 00
current error sd08:01: sense key meduium error.
additional sense indicates Data synchronization maark error.
scsidisk i/o error: dev 08:01,sector 819234,absolute sector 819297
error reading block 409617(attempt to read block from filesystem resulted
in short read) while
doing inode scan.
ignore error <y> ? ( made several failued efforts but this time when i
hit return it went on and
worked.)
Pass 2: checking directory structure
3: checking directory connectivity
4: checking reference counts
5: checking group summarty information.
scsio:Medium Error on channel 0,id 0,lun 0, CDB: Read (6) 0c 80 61 02 00
current error sd08:01: sense key meduium error.
additional sense indicates ID crc or ecc error
scsidisk i/o error: dev 08:01,sector 819234,absolute sector 819297
/dev/sda1:19410/153000 files(0.9% non-contiguous,407227/610438 blocks)
just prior to this boot up problem i had been trying to run kermit on
two computers connected by a cable.
i had two screens open on the linux system console . booth were being
used by non-root simple
/home users.
one screen was at the shell prompt.
the other screen was running kermit.
i had made all the kermit sets and typed connect. i had typed to the linux
kermit from the foreign computer. this causes the linux screen to lock. i
cannot kill the program.
i must reboot in another screen.
this time, i hit atl-del-cntr simultaneously. the screen stayed locked. i
looked at the second screen. it had the terminate message,but it had not
rebooted either. the system was locked. i hit the reset on the computer box.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
