Date: Thu, 2 Mar 1995 00:37:54 +0100 (MET) From: yves@cpcoup5.tn.tudelft.nl (Yves Fonk) To: current@FreeBSD.org Subject: SCSI problems (?) Message-ID: <9503012337.AA16595@cpcoup5.tn.tudelft.nl>
next in thread | raw e-mail | index | archive | help
Hi, I know the SCSI driver is going to be renewed soon. I just want to report the problems I have had with a SCSI drive in case its cause lies somewhere else. I've had problems the last few days, but hadn't time to look into it. Today I wanted to upgrade from sup to CTM and needed the disk. Fsck refused to alleviate the problem: it complained about bad summary information goes ahead anyway, and at the end discovers MEDIUM errors: Mar 1 00:01:39 tnfonk kernel: RE info:00000142 asc:03, retries:1 Mar 1 00:01:39 tnfonk kernel: sd1(aha0:0:0): HARDWARE FAILURE info:00000142 asc :03, FAILURE ... and more of the same.... It fails to resolve these and the disk stays bad, unusable, and unmountable. The kernel I currently use is a few weeks old; a little bit older kernel (but one without modifications by me) has the same problems: Mar 1 19:49:40 tnfonk kernel: FreeBSD 2.1.0-Development #0: Mon Feb 13 11:45:35 MET 1995 Mar 1 19:49:40 tnfonk kernel: yves@tnfonk:/usr/src/sys.Orig/compile/TNFONK Having tried various aproaches to get the disk going again and having failed, I started up from the old BSD partition (kept for occasions like this :-): Mar 1 20:26:18 tnfonk /386bsd: FreeBSD 1.1.0(Current) (SYSCONS) #6: Tue Dec 6 03:14:50 WET 1994 Mar 1 20:26:18 tnfonk /386bsd: yves@tnfonk:/usr2/Current/usr/src/sys/compile/ SYSCONS This one also complained, but one go with fsck solved the problems. It also removed the bad block messages I was getting. This is exactly what I expected to happen the first time. Secondly, the ``old'' fsck managed to notice that the original superblock was bad and proposed to use the backup at blk 32, the new one didn't and even -b 32 wouldn't help. All this reminds me that I was getting a message like Shadow superblock mismatches original, or something like it whenever I started up the ``old'' BSD partition in the past. I never paid much attention to it then, now I'm wondering whether there is/was something wrong. Since the problem has been solved I cannot check out the differences any more. One question remains: isn't fsck supposed to add badblocks to the badblock list of a SCSI device? Furthermore, suddenly I cannot write a tape anymore (not write protected :-(). Mar 1 19:44:37 tnfonk kernel: st0(aha0:4:0): ILLEGAL REQUEST csi:00,00,80,08 Mar 1 19:44:37 tnfonk kernel: st0(aha0:4:0): DATA PROTECT csi:00,00,80,08 Mar 1 19:45:44 tnfonk kernel: st0(aha0:4:0): ILLEGAL REQUEST csi:00,00,80,08 Mar 1 19:45:45 tnfonk kernel: st0(aha0:4:0): DATA PROTECT csi:00,00,80,08 Mar 1 19:46:53 tnfonk kernel: st0(aha0:4:0): ILLEGAL REQUEST csi:00,00,80,08 Tape drive is an Archive 2525S. Don't know whether its a related problem but before digging any further may be any of you can tell me what the problem is. Hope this message is of some use. If anyone has some suggestions, thanks in advance, Yves --- Yves Fonk yves@cpcoup5.tn.tudelft.nl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9503012337.AA16595>