Date: Thu, 6 Mar 1997 07:58:16 -0800 From: "Harry Reed" <doon@eeyore.lv-hrc.nevada.edu> To: "Harry Reed" <doon@eeyore.lv-hrc.nevada.edu>, "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: 2.1.5->2.1.7 causes SCSI errors? Message-ID: <199703061557.HAA00182@eeyore.lv-hrc.nevada.edu>
next in thread | raw e-mail | index | archive | help
---------- > From: Jordan K. Hubbard <jkh@time.cdrom.com> > To: Harry Reed <doon@eeyore.lv-hrc.nevada.edu> > Cc: Nathan Torkington <gnat@frii.com>; freebsd-questions@FreeBSD.ORG > Subject: Re: 2.1.5->2.1.7 causes SCSI errors? > Date: Wednesday, March 05, 1997 5:28 PM > > You guys just need to update your firmware (at least this is > a definite in Nathan's case). The modern driver takes more advantage > these drives, and firmware bugs in the earlier revisions of them > cause problems for this code. > Hm, Unfortunately our disk is a conner! As /sbin/dmesg reveals .... (aha0:0:0): "CONNER CFP1080S 4040" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1030MB (2110812 512 byte sectors) We had the exact same harward running Linux 1.2.13 for many months. We had a severe security breah and decided to move up to a more secure, robust OS - FreeBSD :} Went to install 2.1.6 and out 2940 gave out the strange messages all without even cycling power on the box! Had to put in an old spare 1542B. Do we have a case where an old, crusty version of Linux can do something that FBSD 2.1.6 can't???? 10 * :} - that's a joke son, I say, that's a joke!!!! While I would not say that FBSD broke our 2940 :), but it seems like it! I would like to go back to our 2940, but until I have an idea what went wrong I can't justify too much downtime just for tinkering when the 1542 works. cheers, Harry Reed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703061557.HAA00182>