INFO-VAX Wed, 20 Feb 2008 Volume 2008 : Issue 102 Contents: Re: Another Alpha turned off... Emacs Re: Emacs Re: Emacs Re: Emacs Re: Emacs Re: Emacs Enterprise Directory & Decnet Re: Enterprise Directory & Decnet Re: Enterprise Directory & Decnet Re: Errors during shadow set merge Re: Errors during shadow set merge Re: Errors during shadow set merge Re: Errors during shadow set merge Re: Errors during shadow set merge Re: F$UNIQUE library function Free: VMS orange wall, VAXstation RAM, TCPware manuals; FA: DS10L, VAXstation 40 Re: Rdb version restriction question Re: Rdb version restriction question Re: VAX BASIC, file specs, and command line arguments Re: VAX BASIC, file specs, and command line arguments ---------------------------------------------------------------------- Date: Wed, 20 Feb 2008 04:45:14 -0800 (PST) From: Neil Rieck Subject: Re: Another Alpha turned off... Message-ID: <89fd46a4-a7d2-45a4-aae3-a4a3f4fb4d1a@q70g2000hsb.googlegroups.com> On Feb 16, 5:17=A0pm, Michael Austin wrote: > It was a sad day for me today as I completed the final backup and making > sure everything I needed was removed from my trusty Alpha 2100 that has > been running firstdbasource.com and spacelots.com for the past 8-9 > years. I purchased (or traded services for systems) 2 Alpha 2100's > during 1999. =A0Both had just been retired at 2 separate Charlotte-based > companies and had been running at those sites for 4-5 years at that > time. =A0I lost one of them about 3 years ago - bad I/O board and it has > been sitting silent acting as storage unit for a monitor/keyboard of the > other server. =A0During Christmas week, I found 2 inexpensive DS10L's that= > have taken the place of the 2100's. =A0The "good" 2100/275 may live yet > again as a small Samba file server for a local law firm, but that is > still being negotiated. (hey, I may even make back the $1K I paid for it > :) ). The other will be taken to a local computer recycling center for > disposal after cannibalizing any remaining boards. (The SCSI card is now > in my DS10L :)) > > DEC made the very best hardware in the business. =A0I do not see ANY > vendor that even comes close to competing. =A0Along with the 2 2100's, I > also have been running a |d|i|g|i|t|a|l| Starion 266MhzPentI+32Mb mem. > I purchased it in '97 from a Frye's Electronics in Phoenix and it had > been a floor demo that ran from the time they received it in 1995 until > I bought it. =A0In 1999, I wiped Windows95 off of it and installed Caldera= > Linux. =A0It's sole purpose in life since 1999 is to keep my DSL IP > address in sync with my Dynamic DNS provider ZONEEDIT.COM =A0In 2000 the > primary port on the IDE controller died in such a way that there was no > more "C:" drive. =A0I created a boot-floppy that stays in the floppy drive= > and boots, then turns control over to the D: drive... It has been doing > this now for 8+ years - headless. =A0I have a feeling the Starion is dying= > as the fan gets loud at times and the box reboots itself every couple > months. I have a feeling my 6 year old Dell box will replace its > functionality - but do not think it will last as long as the Starion > has... almost 13 years - almost as long as the 2100's. > > They have served me well -please pause for a moment of silence... > > Long Live Alpha. My employer still has lots of VAXs (8550, 3500, 4300, etc.) and older Aphas (2100, 4100, etc) that just refuse to die and, because marketing people now control the purse strings at most companies, will probably never be replaced anytime soon. More than 80% of them have full software support contracts with HP so they probably appear as 25-50 line-items on some accountant's balance sheet at HP, but in the long run I fear that HP won't consider this stuff real until I can convince someone here to at leat replace the VAX machines with a newer Itanium boxs. Hardware dies while new hardware evolves, but let's hope that OpenVMS lives on. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/links/cool_openvms.html http://www3.sympatico.ca/n.rieck/links/openvms_demos.html ------------------------------ Date: Wed, 20 Feb 2008 14:18:18 -0000 From: "issinoho" Subject: Emacs Message-ID: <13rodlbt4gmeh20@corp.supernews.com> Does anyone know of a recent port of Emacs for VMS that, (a) Works on Alpha V8.3 (b) Preferably has binaries (c) Is not horribly complex to install & configure (d) Has decent instructions The closest thing I can find is from the Freeware V6.0 distribution but it fails on most of the above criteria. Thanks in advance. ------------------------------ Date: 20 Feb 2008 14:57:42 GMT From: billg999@cs.uofs.edu (Bill Gunshannon) Subject: Re: Emacs Message-ID: <622tf6F21phmoU1@mid.individual.net> In article <13rodlbt4gmeh20@corp.supernews.com>, "issinoho" writes: > Does anyone know of a recent port of Emacs for VMS that, > > (a) Works on Alpha V8.3 > (b) Preferably has binaries > (c) Is not horribly complex to install & configure > (d) Has decent instructions > > The closest thing I can find is from the Freeware V6.0 distribution but it > fails on most of the above criteria. All versions of Emacs fail on (c). If they didn't, it wouldn't be Emacs. All the non-commercial versions of Emacs I have seen fail on (d). bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves billg999@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Wed, 20 Feb 2008 15:23:25 GMT From: "jo jimbo" Subject: Re: Emacs Message-ID: Are you sure you want to use emacs? A friend of mine who is now on disability for RSI (carpal tunnel injury) was a big emacs user. When it got to the point of pain in his forearms that he couldn't type he started therapy. One of the things the therapist told him was that the emacs is very hard on the body. It's the multiple keys pressed at once that makes it so bad. Personally, I'm trying to be real careful about posture and typing position and taking breaks, and I think we all should be. There are stories around that Richard Stallman, creator of emacs, has had severe wrist problems, take that as you may. Regards, Jim ------------------------------ Date: Wed, 20 Feb 2008 11:45:43 -0500 From: JF Mezei Subject: Re: Emacs Message-ID: <47bc5b0e$0$22060$c3e8da3@news.astraweb.com> issinoho wrote: > Does anyone know of a recent port of Emacs for VMS that Since emacs started off as a bunch of TECO scripts... TECO still runs on alpha, right ? ------------------------------ Date: 20 Feb 2008 17:09:05 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Emacs Message-ID: <47bc5eb1$0$15201$607ed4bc@cv.net> In article <47bc5b0e$0$22060$c3e8da3@news.astraweb.com>, JF Mezei writes: >issinoho wrote: >> Does anyone know of a recent port of Emacs for VMS that > >Since emacs started off as a bunch of TECO scripts... > >TECO still runs on alpha, right ? Yup! Here's an Emacs question. I've been doing a large amount of web page updating on a linux server. For the most part, I get by with my rudimentary 'vi' skills. However, on occasion I use emacs setup as tpu/edt. Being the old dog that I am, I've been conditioned to do things when using edt on VMS. One of them is the PF2 key (which is normally the keypad help) which I have defined to be 'beginning of line'. I've never delved into setup of emacs more than getting it to default to tpu/edt mode. Can somebody familar with emacs give me a pointer on how to make the alternate keybad PF2 key perform 'beginning of line'? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Wed, 20 Feb 2008 12:28:14 -0500 From: JF Mezei Subject: Re: Emacs Message-ID: <47bc635b$0$10271$c3e8da3@news.astraweb.com> VAXman- @SendSpamHere.ORG wrote: > "Well my son, life is like a beanstalk, isn't it?" > >http://tmesis.com/drat.html I checked out you Sanyo manufactured VAXbar at: http://www.tmesis.com/zymological_zealotry/ Out of curiosity, how long does the keg last ? Or is your consumption so high that you never worry about it going stale ? Is there an explanation for the need to mix N2 and CO2 to produce the VAXman ingestible dark gold elixir ? And does the stuff actually come from Ireland, or is there a brewery in the USA ? More importantly, in the winter, do you move it indoors ? Or is the hardware capable of heating the contents to maintain the proper temperature ? ------------------------------ Date: Wed, 20 Feb 2008 11:04:03 +0000 (UTC) From: gartmann@nonsense.immunbio.mpg.de (Christoph Gartmann) Subject: Enterprise Directory & Decnet Message-ID: Hello, according to the SPD it should be possible to install HP's Enterprise Directory (V5.5) without DECnet. On the node where we tried to install it, DECnet Phase IV is not running but it is available because it is running on some other cluster node. Looking into the KITINSTAL.COM reveals that it does a F$GETSYI("decnet_version") which returns "4", although DECnet is neither running nor configured. If it returned "0" the installation would proceed and look for TCP/IP stacks. But in our case it aborts telling us to upgrade to DECnet V :-( Thus, what should we do? Regards, Christoph Gartmann -- Max-Planck-Institut fuer Phone : +49-761-5108-464 Fax: -452 Immunbiologie Postfach 1169 Internet: gartmann@immunbio dot mpg dot de D-79011 Freiburg, Germany http://www.immunbio.mpg.de/home/menue.html ------------------------------ Date: Wed, 20 Feb 2008 08:16:47 -0500 From: "Richard B. Gilbert" Subject: Re: Enterprise Directory & Decnet Message-ID: <47BC283F.9080301@comcast.net> Christoph Gartmann wrote: > Hello, > > according to the SPD it should be possible to install HP's Enterprise Directory > (V5.5) without DECnet. On the node where we tried to install it, DECnet Phase > IV is not running but it is available because it is running on some other > cluster node. Looking into the KITINSTAL.COM reveals that it does a > F$GETSYI("decnet_version") which returns "4", although DECnet is neither > running nor configured. If it returned "0" the installation would proceed and > look for TCP/IP stacks. But in our case it aborts telling us to upgrade to > DECnet V :-( Thus, what should we do? > > Regards, > Christoph Gartmann > Patch KITINSTAL.COM??? ------------------------------ Date: Wed, 20 Feb 2008 06:49:29 -0800 (PST) From: Volker Halle Subject: Re: Enterprise Directory & Decnet Message-ID: <197d9947-9b0d-4700-bf8a-364bba05c75c@h11g2000prf.googlegroups.com> Christoph, > Patch KITINSTAL.COM??? ... and hope for the best ;-) And please log a call to HP and/or send feedback via the 'edir' WEB page. The wording in the SPD clearly states: HP OpenVMS Enterprise Directory V5.4 implements a distributed network directory service over TCP/IP without the need to install DECnet-Plus or OSI transport in the environment Volker. ------------------------------ Date: Wed, 20 Feb 2008 05:08:44 -0800 (PST) From: Jim Subject: Re: Errors during shadow set merge Message-ID: On Feb 19, 7:59=A0am, tadamsmar wrote: > On Feb 18, 11:17=A0pm, Michael Austin > wrote: > > > > > > > tadamsmarwrote: > > > On Feb 18, 5:00 pm, "Richard B. Gilbert" > > > wrote: > > >> tadamsmarwrote: > > >>> I noticed I was getting errors when adding a member to a shadow > > >>> set. > > >>> I have been getting errors during shadow set merges since I bought > > >>> this refurb DS10. > > >>> Got 109 error today when I remerged after doing an image. =A016 erro= rs > > >>> on DKA0 and 93 on DKA100. > > >>> What do you think is causing this? > > >>> Are these soft errors? > > >>> Here is the log for one: > > >>> **** V3.4 =A0********************* ENTRY 1667 > > >>> ******************************** > > >>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. OpenVMS= > > >>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > > >>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V7.3-= 2 > > >>> Event sequence number =A0 =A0 =A0 =A0 11474. > > >>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 09:52= :48 > > >>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(s) 1= :23:46 > > >>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0EES= D > > >>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 AlphaSe= rver DS10 617 MHz > > >>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Device = Error > > >>> ---- Device Profile ---- > > >>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= $1$DKA0 > > >>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATLAS10= K2-TY184L > > >>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Q= UANTUM > > >>> -- Driver Supplied Info - > > >>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > > >>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense Data= from Device > > >>>SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>>SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > >>>SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0- =A0= normal successful > > >>> completion > > >>>SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte comma= nd) > > >>> Command Data > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x06 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x44 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x8A > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x01 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>>SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check Condi= tion > > >>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > > >>> --- Device Sense Data --- > > >>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Current= Error > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Information Bytes are Valid > > >>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > >>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0LBA= : =A0x0206448A > > >>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Medium = Error > > >>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > > >>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0x23 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0x3E > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0xD4 > > >>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC =A0= =3D =A0 x0011 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0ASCQ =3D =A0 x0000 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Unrecovered Read Error > > >>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > >>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Data > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 x00 > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 xA0 > > >>> ----- Software Info ----- > > >>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries Rem= aining > > >>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries All= owable > > >>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > > >>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Software Valid > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Unload At Dismount > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Volume is Valid on the local > > >>> node > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Unit supports the Extended > > >>> Function bit > > >>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor "PI= D" > > >>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Page O= ffset > > >>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Transfer = Size In Byte(s) > > >>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors This= Unit > > >>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This Unit= > > >>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > > >>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Structu= red > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0File Oriented > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Sharable > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Available > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Mounted > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Error Logging > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Capable of Input > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Capable of Output > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0Random Access > > >> Is that system under service contract? =A0If so, ask to have the driv= e > > >> replaced! > > > >> I hope you have a recent backup that's readable. =A0 If you don't, tr= y to > > >> make one! =A0Right now!!!! > > > >> It could be just a single bad block. =A0It could also be all the warn= ing > > >> you are going to get that the disk is failing! =A0Once you hear that = "loud > > >> scraping sound" it's all over!! > > > >> If you don't have a service contract, order a replacement disk and ge= t a > > >> rush on the delivery! > > > >> Meanwhile, keep an eye on the disk. =A0If you get more error messages= with > > >> different LBAs it means the situation is deteriorating and you may ha= ve > > >> an emergency within a few minutes or hours.- Hide quoted text - > > > >> - Show quoted text - > > > > Are these hard or soft errors? > > > These are generally HARD errors - do what he said and order a disk ASAP.= - Hide quoted text - > > > - Show quoted text - > > I am skeptical that its the disks (In my original message, I indicated > that I get errors for both disks) > > I have had this problem for a while. =A0I have run: > > ANAL/MEDIA/EXER > > on the disks and found no errors. > > These error bursts only happen when I do a shadow set merge. > > I suspect something about the SCSI, or connections, that is stressed > by a merge.- Hide quoted text - > > Information Byte 3 x02 > Byte 2 x06 > Byte 1 x44 > Byte 0 x8A LBA: x0206448A > Sense Key x03 Medium Error This is indicative of the problem - a media failure - and not one of electronics. It might be interesting to determine where that logical block address lives. I suspect that you'll find that it belongs to some file that is rarely or never accessed - until such time as a shadow copy/merge occurs - and then when it is touched the media error is noted. You might find that the integrity of said file is compromised (I presume the block is located in a file and not in free space) and requires restoration (note that this event was recorded as an unrecovered read). ------------------------------ Date: Wed, 20 Feb 2008 07:06:09 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: On Feb 20, 8:08=A0am, Jim wrote: > On Feb 19, 7:59=A0am, tadamsmar wrote: > > > > > > > On Feb 18, 11:17=A0pm, Michael Austin > > wrote: > > > > tadamsmarwrote: > > > > On Feb 18, 5:00 pm, "Richard B. Gilbert" > > > > wrote: > > > >> tadamsmarwrote: > > > >>> I noticed I was getting errors when adding a member to a shadow > > > >>> set. > > > >>> I have been getting errors during shadow set merges since I bought= > > > >>> this refurb DS10. > > > >>> Got 109 error today when I remerged after doing an image. =A016 er= rors > > > >>> on DKA0 and 93 on DKA100. > > > >>> What do you think is causing this? > > > >>> Are these soft errors? > > > >>> Here is the log for one: > > > >>> **** V3.4 =A0********************* ENTRY 1667 > > > >>> ******************************** > > > >>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. OpenV= MS > > > >>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > > > >>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V7.= 3-2 > > > >>> Event sequence number =A0 =A0 =A0 =A0 11474. > > > >>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 09:= 52:48 > > > >>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(s)= 1:23:46 > > > >>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0E= ESD > > > >>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Alpha= Server DS10 617 MHz > > > >>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Devic= e Error > > > >>> ---- Device Profile ---- > > > >>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 $1$DKA0 > > > >>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATLAS= 10K2-TY184L > > > >>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= QUANTUM > > > >>> -- Driver Supplied Info - > > > >>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > > > >>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense Da= ta from Device > > > >>>SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > >>>SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > > >>>SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > >>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0- = =A0normal successful > > > >>> completion > > > >>>SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte com= mand) > > > >>> Command Data > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 2 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 6 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x4= 4 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x8= A > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 1 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>>SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check Con= dition > > > >>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > > > >>> --- Device Sense Data --- > > > >>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Curre= nt Error > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Information Bytes are Valid > > > >>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > >>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0L= BA: =A0x0206448A > > > >>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Mediu= m Error > > > >>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > > > >>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0x23 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0x3E > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0xD4 > > > >>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC =A0= =3D =A0 x0011 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0ASCQ =3D =A0 x0000 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unrecovered Read Error > > > >>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > > >>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Data > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 x00 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 xA0 > > > >>> ----- Software Info ----- > > > >>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries R= emaining > > > >>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries A= llowable > > > >>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > > > >>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Software Valid > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unload At Dismount > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Volume is Valid on the local > > > >>> node > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unit supports the Extended > > > >>> Function bit > > > >>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor "= PID" > > > >>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Page= Offset > > > >>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Transfe= r Size In Byte(s) > > > >>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors Th= is Unit > > > >>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This Un= it > > > >>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > > > >>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Struc= tured > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0File Oriented > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Sharable > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Available > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Mounted > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Error Logging > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Capable of Input > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Capable of Output > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Random Access > > > >> Is that system under service contract? =A0If so, ask to have the dr= ive > > > >> replaced! > > > > >> I hope you have a recent backup that's readable. =A0 If you don't, = try to > > > >> make one! =A0Right now!!!! > > > > >> It could be just a single bad block. =A0It could also be all the wa= rning > > > >> you are going to get that the disk is failing! =A0Once you hear tha= t "loud > > > >> scraping sound" it's all over!! > > > > >> If you don't have a service contract, order a replacement disk and = get a > > > >> rush on the delivery! > > > > >> Meanwhile, keep an eye on the disk. =A0If you get more error messag= es with > > > >> different LBAs it means the situation is deteriorating and you may = have > > > >> an emergency within a few minutes or hours.- Hide quoted text - > > > > >> - Show quoted text - > > > > > Are these hard or soft errors? > > > > These are generally HARD errors - do what he said and order a disk ASA= P.- Hide quoted text - > > > > - Show quoted text - > > > I am skeptical that its the disks (In my original message, I indicated > > that I get errors for both disks) > > > I have had this problem for a while. =A0I have run: > > > ANAL/MEDIA/EXER > > > on the disks and found no errors. > > > These error bursts only happen when I do a shadow set merge. > > > I suspect something about the SCSI, or connections, that is stressed > > by a merge.- Hide quoted text - > > > Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0LBA: =A0= x0206448A > > Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Medium Erro= r > > This is indicative of the problem - a media failure - and not one of > electronics. It might be interesting to determine where that logical > block address lives. I suspect that you'll find that it belongs to > some file that is rarely or never accessed - until such time as a > shadow copy/merge occurs - and then when it is touched the media error > is noted. You might find that the integrity of said file is > compromised (I presume the block is located in a file and not in free > space) and requires restoration (note that this event was recorded as > an unrecovered read).- Hide quoted text - > > - Show quoted text - Thanks for thinking about it. I am stumped. I am thinking about swapping controllers with another computer to see if the problem moves. The box is still under warranty, I could try to get the vendor to swap it. It is a refurb I bought in August 2007. Then why does ANALYZE/MEDIA/EXERCISE show no problems? I got 109 errors on two disks involving about a dozen LBAs (most on dka100, only 16 errors on dka0). In many cases, I got 10 errors for one LBA, but never more than 10. Seems like 10 is a magic number of some sort. If you are correct, then I guess I should see the same LBAs in the error message if I break up the shadow set and remerge it. Right? ------------------------------ Date: Wed, 20 Feb 2008 07:26:13 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: <8781c442-7fe4-4ba1-9618-4dee049281f8@j28g2000hsj.googlegroups.com> On Feb 20, 8:08=A0am, Jim wrote: > On Feb 19, 7:59=A0am, tadamsmar wrote: > > > > > > > On Feb 18, 11:17=A0pm, Michael Austin > > wrote: > > > > tadamsmarwrote: > > > > On Feb 18, 5:00 pm, "Richard B. Gilbert" > > > > wrote: > > > >> tadamsmarwrote: > > > >>> I noticed I was getting errors when adding a member to a shadow > > > >>> set. > > > >>> I have been getting errors during shadow set merges since I bought= > > > >>> this refurb DS10. > > > >>> Got 109 error today when I remerged after doing an image. =A016 er= rors > > > >>> on DKA0 and 93 on DKA100. > > > >>> What do you think is causing this? > > > >>> Are these soft errors? > > > >>> Here is the log for one: > > > >>> **** V3.4 =A0********************* ENTRY 1667 > > > >>> ******************************** > > > >>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. OpenV= MS > > > >>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > > > >>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V7.= 3-2 > > > >>> Event sequence number =A0 =A0 =A0 =A0 11474. > > > >>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 09:= 52:48 > > > >>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(s)= 1:23:46 > > > >>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0E= ESD > > > >>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Alpha= Server DS10 617 MHz > > > >>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Devic= e Error > > > >>> ---- Device Profile ---- > > > >>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 $1$DKA0 > > > >>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATLAS= 10K2-TY184L > > > >>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= QUANTUM > > > >>> -- Driver Supplied Info - > > > >>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > > > >>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense Da= ta from Device > > > >>>SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > >>>SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > > >>>SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > >>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0- = =A0normal successful > > > >>> completion > > > >>>SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte com= mand) > > > >>> Command Data > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 2 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 6 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x4= 4 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x8= A > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 1 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x0= 0 > > > >>>SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check Con= dition > > > >>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > > > >>> --- Device Sense Data --- > > > >>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Curre= nt Error > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Information Bytes are Valid > > > >>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > >>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0L= BA: =A0x0206448A > > > >>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Mediu= m Error > > > >>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > > > >>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0x23 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0x3E > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0xD4 > > > >>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC =A0= =3D =A0 x0011 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0ASCQ =3D =A0 x0000 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unrecovered Read Error > > > >>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > > >>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Data > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 x00 > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 xA0 > > > >>> ----- Software Info ----- > > > >>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries R= emaining > > > >>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries A= llowable > > > >>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > > > >>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Software Valid > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unload At Dismount > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Volume is Valid on the local > > > >>> node > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unit supports the Extended > > > >>> Function bit > > > >>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor "= PID" > > > >>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Page= Offset > > > >>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Transfe= r Size In Byte(s) > > > >>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors Th= is Unit > > > >>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This Un= it > > > >>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > > > >>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Struc= tured > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0File Oriented > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Sharable > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Available > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Mounted > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Error Logging > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Capable of Input > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Capable of Output > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Random Access > > > >> Is that system under service contract? =A0If so, ask to have the dr= ive > > > >> replaced! > > > > >> I hope you have a recent backup that's readable. =A0 If you don't, = try to > > > >> make one! =A0Right now!!!! > > > > >> It could be just a single bad block. =A0It could also be all the wa= rning > > > >> you are going to get that the disk is failing! =A0Once you hear tha= t "loud > > > >> scraping sound" it's all over!! > > > > >> If you don't have a service contract, order a replacement disk and = get a > > > >> rush on the delivery! > > > > >> Meanwhile, keep an eye on the disk. =A0If you get more error messag= es with > > > >> different LBAs it means the situation is deteriorating and you may = have > > > >> an emergency within a few minutes or hours.- Hide quoted text - > > > > >> - Show quoted text - > > > > > Are these hard or soft errors? > > > > These are generally HARD errors - do what he said and order a disk ASA= P.- Hide quoted text - > > > > - Show quoted text - > > > I am skeptical that its the disks (In my original message, I indicated > > that I get errors for both disks) > > > I have had this problem for a while. =A0I have run: > > > ANAL/MEDIA/EXER > > > on the disks and found no errors. > > > These error bursts only happen when I do a shadow set merge. > > > I suspect something about the SCSI, or connections, that is stressed > > by a merge.- Hide quoted text - > > > Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0LBA: =A0= x0206448A > > Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Medium Erro= r > > This is indicative of the problem - a media failure - and not one of > electronics. It might be interesting to determine where that logical > block address lives. I suspect that you'll find that it belongs to > some file that is rarely or never accessed - until such time as a > shadow copy/merge occurs - and then when it is touched the media error > is noted. You might find that the integrity of said file is > compromised (I presume the block is located in a file and not in free > space) and requires restoration (note that this event was recorded as > an unrecovered read).- Hide quoted text - > > - Show quoted text - Perhaps you are on to something. I checked the error log more extensively and did find LBAs that appear in more than one error burst. ------------------------------ Date: Wed, 20 Feb 2008 07:47:40 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: <949155f7-e92c-4368-a425-9bcf0096729a@e60g2000hsh.googlegroups.com> On Feb 20, 10:26=A0am, tadamsmar wrote: > On Feb 20, 8:08=A0am, Jim wrote: > > > > > > > On Feb 19, 7:59=A0am, tadamsmar wrote: > > > > On Feb 18, 11:17=A0pm, Michael Austin > > > wrote: > > > > > tadamsmarwrote: > > > > > On Feb 18, 5:00 pm, "Richard B. Gilbert" > > > > > wrote: > > > > >> tadamsmarwrote: > > > > >>> I noticed I was getting errors when adding a member to a shadow > > > > >>> set. > > > > >>> I have been getting errors during shadow set merges since I boug= ht > > > > >>> this refurb DS10. > > > > >>> Got 109 error today when I remerged after doing an image. =A016 = errors > > > > >>> on DKA0 and 93 on DKA100. > > > > >>> What do you think is causing this? > > > > >>> Are these soft errors? > > > > >>> Here is the log for one: > > > > >>> **** V3.4 =A0********************* ENTRY 1667 > > > > >>> ******************************** > > > > >>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Ope= nVMS > > > > >>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > > > > >>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V= 7.3-2 > > > > >>> Event sequence number =A0 =A0 =A0 =A0 11474. > > > > >>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 0= 9:52:48 > > > > >>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(= s) 1:23:46 > > > > >>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0EESD > > > > >>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Alp= haServer DS10 617 MHz > > > > >>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Dev= ice Error > > > > >>> ---- Device Profile ---- > > > > >>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 $1$DKA0 > > > > >>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATL= AS10K2-TY184L > > > > >>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 QUANTUM > > > > >>> -- Driver Supplied Info - > > > > >>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > > > > >>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense = Data from Device > > > > >>>SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > > >>>SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > > > >>>SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > > >>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0-= =A0normal successful > > > > >>> completion > > > > >>>SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte c= ommand) > > > > >>> Command Data > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x00 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x02 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x06 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x44 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x8A > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x00 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x00 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x01 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = x00 > > > > >>>SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check C= ondition > > > > >>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > > > > >>> --- Device Sense Data --- > > > > >>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Cur= rent Error > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Information Bytes are Valid > > > > >>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > > > > >>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A = =A0LBA: =A0x0206448A > > > > >>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Med= ium Error > > > > >>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > > > > >>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 =A0x23 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 =A0x3E > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 0 =A0 =A0 =A0 =A0xD4 > > > > >>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC = =A0=3D =A0 x0011 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0ASCQ =3D =A0 x0000 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unrecovered Read Error > > > > >>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > > > > >>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Dat= a > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 x00 > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 xA0 > > > > >>> ----- Software Info ----- > > > > >>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Remaining > > > > >>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Allowable > > > > >>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > > > > >>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Software Valid > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unload At Dismount > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Volume is Valid on the local > > > > >>> node > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Unit supports the Extended > > > > >>> Function bit > > > > >>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor= "PID" > > > > >>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Pa= ge Offset > > > > >>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Trans= fer Size In Byte(s) > > > > >>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors = This Unit > > > > >>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This = Unit > > > > >>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > > > > >>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Str= uctured > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0File Oriented > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Sharable > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Available > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Mounted > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Error Logging > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Capable of Input > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Capable of Output > > > > >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0Random Access > > > > >> Is that system under service contract? =A0If so, ask to have the = drive > > > > >> replaced! > > > > > >> I hope you have a recent backup that's readable. =A0 If you don't= , try to > > > > >> make one! =A0Right now!!!! > > > > > >> It could be just a single bad block. =A0It could also be all the = warning > > > > >> you are going to get that the disk is failing! =A0Once you hear t= hat "loud > > > > >> scraping sound" it's all over!! > > > > > >> If you don't have a service contract, order a replacement disk an= d get a > > > > >> rush on the delivery! > > > > > >> Meanwhile, keep an eye on the disk. =A0If you get more error mess= ages with > > > > >> different LBAs it means the situation is deteriorating and you ma= y have > > > > >> an emergency within a few minutes or hours.- Hide quoted text - > > > > > >> - Show quoted text - > > > > > > Are these hard or soft errors? > > > > > These are generally HARD errors - do what he said and order a disk A= SAP.- Hide quoted text - > > > > > - Show quoted text - > > > > I am skeptical that its the disks (In my original message, I indicated= > > > that I get errors for both disks) > > > > I have had this problem for a while. =A0I have run: > > > > ANAL/MEDIA/EXER > > > > on the disks and found no errors. > > > > These error bursts only happen when I do a shadow set merge. > > > > I suspect something about the SCSI, or connections, that is stressed > > > by a merge.- Hide quoted text - > > > > Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > > > =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > > > =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > > > =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0LBA: = =A0x0206448A > > > Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Medium Er= ror > > > This is indicative of the problem - a media failure - and not one of > > electronics. It might be interesting to determine where that logical > > block address lives. I suspect that you'll find that it belongs to > > some file that is rarely or never accessed - until such time as a > > shadow copy/merge occurs - and then when it is touched the media error > > is noted. You might find that the integrity of said file is > > compromised (I presume the block is located in a file and not in free > > space) and requires restoration (note that this event was recorded as > > an unrecovered read).- Hide quoted text - > > > - Show quoted text - > > Perhaps you are on to something. =A0I checked the error log more > extensively and did find LBAs that appear in more than one error > burst.- Hide quoted text - > > - Show quoted text - I just started a ANAL/MEDIA/EXER=3DFULL I have not tried FULL before, maybe that will make a difference. Also, it's been months since I tried ANAL/MEDIA/EXER ------------------------------ Date: Wed, 20 Feb 2008 18:10:14 GMT From: Tad Winters Subject: Re: Errors during shadow set merge Message-ID: tadamsmar wrote in news:949155f7-e92c-4368-a425-9bcf0096729a@e60g2000hsh.googlegroups.com: > On Feb 20, 10:26 am, tadamsmar wrote: >> On Feb 20, 8:08 am, Jim wrote: >> >> >> >> >> >> > On Feb 19, 7:59 am, tadamsmar wrote: >> >> > > On Feb 18, 11:17 pm, Michael Austin >> > > wrote: >> >> > > > tadamsmarwrote: >> > > > > On Feb 18, 5:00 pm, "Richard B. Gilbert" >> > > > > wrote: >> > > > >> tadamsmarwrote: >> > > > >>> I noticed I was getting errors when adding a member to a >> > > > >>> shadow set. >> > > > >>> I have been getting errors during shadow set merges since >> > > > >>> I bought this refurb DS10. >> > > > >>> Got 109 error today when I remerged after doing an image. >> > > > >>>  16 errors on DKA0 and 93 on DKA100. >> > > > >>> What do you think is causing this? >> > > > >>> Are these soft errors? >> > > > >>> Here is the log for one: >> > > > >>> **** V3.4  ********************* ENTRY 1667 >> > > > >>> ******************************** >> > > > >>> Logging OS                        1. OpenVMS >> > > > >>> System Architecture               2. Alpha >> > > > >>> OS version                           V7.3-2 >> > > > >>> Event sequence number         11474. >> > > > >>> Timestamp of occurrence              18-FEB-2008 09:52:48 >> > > > >>> Time since reboot                    77 Day(s) 1:23:46 >> > > > >>> Host name                            EESD >> > > > >>> System Model                         AlphaServer DS10 617 >> > > > >>> MHz Entry Type                        1. Device Error >> > > > >>> ---- Device Profile ---- >> > > > >>> Unit                                 $1$DKA0 >> > > > >>> Product Name                         ATLAS10K2-TY184L >> > > > >>> Vendor                               QUANTUM >> > > > >>> -- Driver Supplied Info - >> > > > >>> Device Firmware Revision             DA40 >> > > > >>> VMSSCSIError Type               5. Extended Sense Data >> > > > >>> from Device >> > > > >>>SCSIID                         x00 >> > > > >>>SCSILUN                        x00 >> > > > >>>SCSISUBLUN                     x00 >> > > > >>> Port Status               x00000001  NORMAL  -  normal >> > > > >>> successful completion >> > > > >>>SCSICommand Opcode             x28  Read (10 byte command) >> > > > >>> Command Data >> > > > >>>                                 x00 >> > > > >>>                                 x02 >> > > > >>>                                 x06 >> > > > >>>                                 x44 >> > > > >>>                                 x8A >> > > > >>>                                 x00 >> > > > >>>                                 x00 >> > > > >>>                                 x01 >> > > > >>>                                 x00 >> > > > >>>SCSIStatus                     x02  Check Condition >> > > > >>> Remaining Byte Length            18. >> > > > >>> --- Device Sense Data --- >> > > > >>> Error Code                      xF0  Current Error >> > > > >>>                                      Information Bytes >> > > > >>> are Valid Segment #                       x00 >> > > > >>> Information Byte 3              x02 >> > > > >>>             Byte 2              x06 >> > > > >>>             Byte 1              x44 >> > > > >>>             Byte 0              x8A  LBA:  x0206448A >> > > > >>> Sense Key                       x03  Medium Error >> > > > >>> Additional Sense Length         x0A >> > > > >>> CMD Specific Info Byte 3        x21 >> > > > >>>                   Byte 2        x23 >> > > > >>>                   Byte 1        x3E >> > > > >>>                   Byte 0        xD4 >> > > > >>> ASC & ASCQ                    x1100  ASC  =   x0011 >> > > > >>>                                      ASCQ =   x0000 >> > > > >>>                                      Unrecovered Read >> > > > >>> Error FRU Code                        x00 >> > > > >>> Sense Key Specific Byte 0       x80  Valid Sense Key Data >> > > > >>>                    Byte 1       x00 >> > > > >>>                    Byte 2       xA0 >> > > > >>> ----- Software Info ----- >> > > > >>> UCB$x_ERTCNT                     16. Retries Remaining >> > > > >>> UCB$x_ERTMAX                     16. Retries Allowable >> > > > >>> IRP$Q_IOSB                x0000000000000000 >> > > > >>> UCB$x_STS                 x08021810  Online >> > > > >>>                                      Software Valid >> > > > >>>                                      Unload At Dismount >> > > > >>>                                      Volume is Valid on >> > > > >>> the local node >> > > > >>>                                      Unit supports the >> > > > >>> Extended Function bit >> > > > >>> IRP$L_PID                 x82640450  Requestor "PID" >> > > > >>> IRP$x_BOFF                     4416. Byte Page Offset >> > > > >>> IRP$x_BCNT                      512. Transfer Size In >> > > > >>> Byte(s) UCB$x_ERRCNT                     32. Errors This >> > > > >>> Unit UCB$L_OPCNT                22716780. QIO's This Unit >> > > > >>> ORB$L_OWNER               x00010004  Owners UIC >> > > > >>> UCB$L_DEVCHAR1            x1C4D4008  Directory Structured >> > > > >>>                                      File Oriented >> > > > >>>                                      Sharable >> > > > >>>                                      Available >> > > > >>>                                      Mounted >> > > > >>>                                      Error Logging >> > > > >>>                                      Capable of Input >> > > > >>>                                      Capable of Output >> > > > >>>                                      Random Access >> > > > >> Is that system under service contract?  If so, ask to have >> > > > >> the drive replaced! >> >> > > > >> I hope you have a recent backup that's readable.   If you >> > > > >> don't, try to make one!  Right now!!!! >> >> > > > >> It could be just a single bad block.  It could also be all >> > > > >> the warning you are going to get that the disk is failing! >> > > > >>  Once you hear that "loud scraping sound" it's all over!! >> >> > > > >> If you don't have a service contract, order a replacement >> > > > >> disk and get a rush on the delivery! >> >> > > > >> Meanwhile, keep an eye on the disk.  If you get more error >> > > > >> messages with different LBAs it means the situation is >> > > > >> deteriorating and you may have an emergency within a few >> > > > >> minutes or hours.- Hide quoted text - >> >> > > > >> - Show quoted text - >> >> > > > > Are these hard or soft errors? >> >> > > > These are generally HARD errors - do what he said and order a >> > > > disk ASAP.- Hide quoted text - >> >> > > > - Show quoted text - >> >> > > I am skeptical that its the disks (In my original message, I >> > > indicated that I get errors for both disks) >> >> > > I have had this problem for a while.  I have run: >> >> > > ANAL/MEDIA/EXER >> >> > > on the disks and found no errors. >> >> > > These error bursts only happen when I do a shadow set merge. >> >> > > I suspect something about the SCSI, or connections, that is >> > > stressed by a merge.- Hide quoted text - >> >> > > Information Byte 3              x02 >> > >            Byte 2              x06 >> > >            Byte 1              x44 >> > >            Byte 0              x8A  LBA:  x0206448A >> > > Sense Key                       x03  Medium Error >> >> > This is indicative of the problem - a media failure - and not one >> > of electronics. It might be interesting to determine where that >> > logical block address lives. I suspect that you'll find that it >> > belongs to some file that is rarely or never accessed - until >> > such time as a shadow copy/merge occurs - and then when it is >> > touched the media error is noted. You might find that the >> > integrity of said file is compromised (I presume the block is >> > located in a file and not in free space) and requires restoration >> > (note that this event was recorded as an unrecovered read).- Hide >> > quoted text - >> >> > - Show quoted text - >> >> Perhaps you are on to something.  I checked the error log more >> extensively and did find LBAs that appear in more than one error >> burst.- Hide quoted text - >> >> - Show quoted text - > > I just started a ANAL/MEDIA/EXER=FULL > > I have not tried FULL before, maybe that will make a difference. > Also, it's been months since I tried ANAL/MEDIA/EXER > This is a bit confusing. If the system is under a maintenance contract, but you have the time to exercise the media, it would seem to me the first thing to do is get the drives swapped. That bit aside, IIRC, analyzing the media may not reveal errors since the drives generally handle their own bad block replacement. There used to be a kit called RZDISK which allowed you to send a number of SCSI commands that weren't otherwise available. I think I recently mentioned finding RZTOOLS in SYS$ETC which also provided some additional command options. It might be useful to see if you can use these to query the disk's bad block table before and after a media exercise to see how it changes. If the table keeps growing, don't waste any more time, just replace the disks. ------------------------------ Date: Wed, 20 Feb 2008 05:56:22 -0800 (PST) From: AEF Subject: Re: F$UNIQUE library function Message-ID: <1c7fb226-4817-4278-a519-35ff89b26d30@i29g2000prf.googlegroups.com> On Jan 25, 10:07 am, yyyc186 wrote: > On Jan 24, 8:51 pm, Arne Vajh=F8j wrote: > > > > >SharePointrun in IIS, so they have to be on the same box. > > SharePoint, now THERE is a God-awful product no professional would > have designed, developed, or worked on. That thing must be where the > team from Microsoft Bob went. We're using it at my company to document our upcoming data-center move. Yeah, I'm not very impressed with it. It integration with Excel is clumsy. You have to click your document to get a stupid drop down menu instead of just selecting it and having a menu already at the top. Excel lies to you about who has it checked out. I somehow managed to modify, save, and check-in what Excel told me was a "Read-Only" version. What the proper procedure for checking a document in and out is not clear. What it's going to do when you Save or Close is not clear. Surprise dialog boxes pop up with choices that you think you already did but are then not sure actually happened, so you have to open the document again to see if your changes really took. And don't get me started on navigating the folder tree!!! Yuck. AEF ------------------------------ Date: Wed, 20 Feb 2008 06:58:43 -0800 (PST) From: Tom Garcia Subject: Free: VMS orange wall, VAXstation RAM, TCPware manuals; FA: DS10L, VAXstation 40 Message-ID: <7d5fd6ba-5075-41c7-a483-cfbe58d90127@28g2000hsw.googlegroups.com> Hi all, Available for pick-up now from Worthing, West Sussex, England are twelve overfilled 34x24x25cm boxes of orange wall - VAX/VMS v3 and v4 era manuals. Or I can ship anywhere at your expense after 10 March. Detail below (era-vol-title). Condition is reasonable - some cover pages are less than pristine, while other manuals are still in their shrink wrap. Also for auction, shipping worldwide: one Alphaserver DS10L 256MB +30GB, one VAXstation 4000/60 32MB+RZ25, and one MS310-EA = 2x512MB for a DEC DS10/DS10L/XP900. The equipment has been used for the VMS hobbyist programme, and now awaits your hobbyist licenses :-). http://search.ebay.co.uk/_W0QQsassZtagq2 More stuff probably available next month (a VT240+VR201 and a DECmate III?), but for now you are welcome to walk off with / pay shipping for: - TCPware 5.4 printed docset: netcu command ref, management guide, user's guide, programmer's guide, install/config guide; - some MS44L-AA 4MB VAXstation memory modules; - a VT520 with apparently stuck-full brightness; - an HP A2094A CRT that has nothing to do with DEC but has been sitting taunting me. (1) 4-8-system messages and recovery procedures VAX-11 Fortran u/g, ref manual, installation guide 4-2A-command language, system messages 4-7-MACRO and instruction set (2) 3-8-Compatibility mode RSX-11M 3-3B-Text processing: TPU/EVE 4-8-as in (1) 3-3B-Text processing: VAX TPU ref. (3) MicroVMS 4.4 programming support manual 4-replacement binder-intro to sys routines, utility routines 4-" "-RMS manual, ana/rms, FDL 4-Guide to writing device driver for VAX/VMS (4) 3-4A-utils ref, magnetic tape u/g, SORT/MERGE u/g 4-8-as in (1) (again!) 4-4C-utilities PHONE-VERIFY (5) MicroVMS user manual part 2 MicroVMS programming support manual (again) + progarmmer pocket reference sealed-User's primer, FORTRAN primer, release notes promotional (SPD?) booklets: BASIC, BLISS, CLE, FORTRAN, MMS, RPG II, ADA, COBOL, performance + coverage analyser, APL, DEC/test manager 4-4A-ACL editor through LATCP (6) 4-Guide to networking on VAX/VMS DEQNA ethernet user's guide 4-2-Command language: DCL dictionary MicroVMS 4.4 programmer's manual 4-Guide to programming on VAX/VMS (FORTRAN edition) (7) TK50 user's reference card Booklets: Installing VAX/VMS on 8600 from HSC-based tape, " from magnetic tape Installing VAX/VMS on 11-780 from HSC-based tape, " from magnetic tape Installing VAX/VMS on UDA-based 11/730 from magnetic tape Running the UETP after installation 4-Guide to VAX/VMS file applications 4-Introduction to VAX/VMS DECNET-RSX guide to network management utilities (1985) Programming in VAX C 2.0 (8) 3-5B-System services/IO: IO user's guide volumes 1,2 3-1-General info, SPD etc. VAX-11 FORTRAN 3.0 reference manual, user's guide, installation guide (9) 4-1-Introduction, glossary etc. 4-2-Command language: DCL dictionary 4-1B-Release notes: vv4.2, 4.1, 4.0 (10) 3-7-VAX-11 Record Management Services DEC CBI course administrator's guide (1982) 4-8-as in 1 (yet again!) (11) 4-Guide to VAX/VMS disk and magnetic tape operations 4-Guide to using DCL + command procedures on VAX/VMS MicroVMS 4 programming support manual (again) (12) 4-Guide to VAXclusters MicroVMS 4.4 user's manual part 1 3-4B-prog. development tools 4-1A-general info etc. Please feel free to respond/mail me if you have any questions. -- Tom Garcia | tgarcia@hivemind.org ------------------------------ Date: Wed, 20 Feb 2008 07:48:37 -0800 (PST) From: Rich Jordan Subject: Re: Rdb version restriction question Message-ID: <32821fff-4709-4323-aa38-cc2d72704712@q78g2000hsh.googlegroups.com> On Feb 20, 12:08 am, Cluster-Karl wrote: > On 20 Feb., 01:17, Rich Jordan wrote: > > > > > I've got a question about Rdb on OpenVMS Alpha version restrictions. > > > The release notes for the latest V7.0 release state that a "maximum > > VMS version check" was put in place as of V7.0.1.5; this in addition > > to a minimum version that had been in place earlier. > > > I've heard from a few places that V7.0.8 (and concurrent CDD) release > > works fine on a system upgraded to VMS V8.3, but per the release notes > > the maximum version should be getting tripped. I know that Oracle > > will not support the outdated Rdb/CDD versions on V8.3 but they > > reportedly run fine. > > > Is the Rdb maximum VMS version check only on installation? Or is > > there an actual runtime check for maximum VMS versions which would > > stop some Rdb versions from running if they were already installed > > when the system was upgraded to V8.3? > > > I don't have a test system I can do tests on right now; its involved > > in another project> Thanks for any info. > > > Rich > > CCS > > Rich, > > sorry for the formatting, but the current V7.0.9 runs from V6.1 to > V8.3 on Alpha. > > Excerpt from oracle version matrix: > > 7.0.9 March 2007 V7.0-9 6.1 8.3 EV7 5.5-2 8.3 V7.0I > 7.0.8.3 February 2006 V7.0-83 6.1 8.2-n EV7 5.5-2 8.2-n > V7.0H ECO3 > 7.0.8.2 September 2005 V7.0-82 6.1 8.2-n EV7 5.5-2 8.2-n V7.0H > ECO2 > 7.0.8.1 June 2005 V7.0-81 6.1 8.2-n EV7 5.5-2 8.2-n > V7.0H ECO1 > > regards Kalle Kalle thanks. I do have the support matrix available but my immediate concern is with the implementation of the "maximum VMS version" mentioned in the release notes. I've had a couple responses to a much earlier question indicate that older Rdb versions ran fine on VMS V8.2 and 8.3 Alpha, but those were old enough that they didn't have the "maximum" version check so the senders didn't know if that check is install-only or runtime. I downloaded 7.0.9 and I'm going through its docs now. The distribution media Oracle sent out (supposedly the latest) included Rdb V7.0.8.3, hence the questions on V8.3 usability. Thanks again Rich ------------------------------ Date: Wed, 20 Feb 2008 09:38:31 -0800 (PST) From: Rich Jordan Subject: Re: Rdb version restriction question Message-ID: <710c573b-7dfa-4367-a414-67a7178e1281@u72g2000hsf.googlegroups.com> On Feb 19, 6:17 pm, Rich Jordan wrote: > I've got a question about Rdb on OpenVMS Alpha version restrictions. > > The release notes for the latest V7.0 release state that a "maximum > VMS version check" was put in place as of V7.0.1.5; this in addition > to a minimum version that had been in place earlier. > > I've heard from a few places that V7.0.8 (and concurrent CDD) release > works fine on a system upgraded to VMS V8.3, but per the release notes > the maximum version should be getting tripped. I know that Oracle > will not support the outdated Rdb/CDD versions on V8.3 but they > reportedly run fine. > > Is the Rdb maximum VMS version check only on installation? Or is > there an actual runtime check for maximum VMS versions which would > stop some Rdb versions from running if they were already installed > when the system was upgraded to V8.3? > > I don't have a test system I can do tests on right now; its involved > in another project> Thanks for any info. > > Rich > CCS Never mind, found it. Rdb V7.0.9 release notes state that both install and runtime checks are in place. Rdb will NOT start if it detects the VMS version its running on, OR the hardware it is running on, is not certified. That is a change Oracle put in. I know that older Rdb versions have kept running for many VMS versions past what they came out on, but that won't be the case for anything from Rdb V7.0.1.5 and newer. ------------------------------ Date: Wed, 20 Feb 2008 04:17:20 -0800 (PST) From: Neil Rieck Subject: Re: VAX BASIC, file specs, and command line arguments Message-ID: On Feb 19, 12:31=A0pm, bdhobb...@acm.org wrote: > VAX BASIC v3.8-000 > VMS 7.1 > emulating a VAX 4000-105A > > Two things I would like to do in BASIC: > =A0 1) Get the full file spec for a file; > =A0 2) Get arguments from the command line. > > I'm playing with the useropen clause of the open statement, but that > involves fab and nam blocks and sys$open/sys$create and sys$connect to > get the info I want. =A0It's not bad, but I find it clumsy to go thru > all this to get a file spec. =A0I was able to easily get both items in > VMS COBOL, but I was using features that were part of the language. > Any routines that'll give me what I want? =A0Thank you for any and all > assistance. I did a little "OpenVMS BASIC" hacking in this aread some years ago and posted my efforts here: http://www3.sympatico.ca/n.rieck/links/openvms_demos.html http://www3.sympatico.ca/n.rieck/demo_vms/basic-open-useropen-bas.zip http://www3.sympatico.ca/n.rieck/demo_vms/basic-open-fsp-bas.zip http://www3.sympatico.ca/n.rieck/demo_vms/basic-fix-ftp-savesets.zip http://www3.sympatico.ca/n.rieck/demo_vms/basic-foreign-cmd.zip These demos won't answer all your questions but may provided some of the missing pieces. Enjoy. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: 20 Feb 2008 07:39:04 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: VAX BASIC, file specs, and command line arguments Message-ID: In article <97d69540-5388-4f3c-b27b-6aac4bb86e99@s8g2000prg.googlegroups.com>, bdhobbs18@acm.org writes: > VAX BASIC v3.8-000 > VMS 7.1 > emulating a VAX 4000-105A > > Two things I would like to do in BASIC: > 1) Get the full file spec for a file; > 2) Get arguments from the command line. 1) Does basic have the equivalent of Fortrans' INQUIRE statement? 2) You can get the command line in any language by calling lib$get_foreign(). ------------------------------ End of INFO-VAX 2008.102 ************************