home *** CD-ROM | disk | FTP | other *** search
Wrap
Xref: sparky comp.sys.sun.admin:4892 mail.sun-managers:16 Path: sparky!uunet!mcsun!ariadne!erato.csi.forth.gr!psikos From: psikos@erato.csi.forth.gr (Panos Psikos) Newsgroups: comp.sys.sun.admin,mail.sun-managers Subject: Re: ATTENTION: A problem with dump under 4.1.1 Message-ID: <3188@ariadne.csi.forth.GR> Date: 23 Jul 92 05:59:38 GMT References: <1992Jul20.073110.20195@aristo.tau.ac.il> <1992Jul21.195006.112389@zeus.calpoly.edu> Sender: news@csi.forth.GR Followup-To: comp.sys.sun.admin Organization: FORTH - ICS, P.O.Box 1385, Heraklio, Crete, Greece 71110 tel: +30(81)221171, 229302 fax: +30(81)229342,3 tlx: 262389 CCI Lines: 53 In article <1992Jul21.195006.112389@zeus.calpoly.edu>, etsiao@joule (Eddie Tsiao) writes: |> In article <1992Jul20.073110.20195@aristo.tau.ac.il> shani@GENIUS.TAU.AC.IL (Oren Shani) writes: |> >Hello |> |> Omitted... |> |> >about once in two weeks with a writeback error. It took us some time to |> >realize that this is due to another problem and to notice that it happens while |> >performing the backups, but once we did, we called Sun technicians. The |> >technicians tried to replace everything - from the SCSI cable to eventually, the |> >whole computer - but it didn't help. In fact, after the ROM revision was |> >upgraded, the problem got even worse - the computer now gets stuck with some |> >strange memory error on the console, and can be revived only by turning the |> >power on and off. Meanwhile our Exabyte died (something with it's r/w head, |> >probably have nothing to do with this), so we no longer use it, we don't use |> >mt either because we backup either to a free disk partition or to a remote |> >computer, and the crashes still continue. |> > |> > After every link of the chain was checked (Hardware, SCSI, Exabyte, mt) we |> >have to conclude that the problem is with dump. So I would like you all to take |> >note, and let me know if you encounter anything that supports this suspicion. |> > |> >-- |> > __ __ Oren Shani (shani@genius.tau.ac.il) |> > / / / Faculty of Engineering, Tel Aviv university |> > / / -- Israel |> > /__/ . __/ . "Hold your temper" -- The caterpillar to Alice |> |> We have had (are having?) similar problems. We occationally get an error: |> |> DUMP: Tape write error 753 feet into tape 1 |> DUMP: fopen on /dev/tty fails |> DUMP: The ENTIRE dump is aborted. |> |> - E.T. ********Stuff deleted ************************ |> |> ------------------------------------------------------------------------------- |> |Eddie Tsiao | etsiao@onramp.ARDFA.CalPoly.EDU | |> |System Administrator | Voice: (805) 756-1706 | |> |ARDFA Cal Poly, San Luis Obispo | FAX: (805) 756-1702 | |> ------------------------------------------------------------------------------ I tried posting that followup before but I think it didn't get through. Sorry If you have already seen that. We had the same problems here with an EXB8200 connected to a Sun 4/80 running SunOs 4.1.1. Machine would crash once in a while with memory writeback errors.The only way to proceed was to turn it on and off since even the console would not respond. After upgrading to 4.1.2 everything is ok both with the EXB8200 and with a new 5GB drive we got.Of cource I am waiting to see what new bugs have been introduced in 4.1.2 to keep the total number of bugs equal to that of 4.1.1, now that dump is fixed (just kiddin g). Panos -- ================================================================================These are my OWN opinions. I do not speak for anybody else. Can I have a Testa Rossa pretty please? ================================================================================