|
Hello Carl, (sorry for my english, it's not my mother's tongue) I had to revive those "clicking drives" a several times, here are some tips, but before you start: this is normally the last time you can power on such a drive, so you better think before acting ! OK, here we go: Without a look to SST/DST you are on your own to find out the failed drive: If you are not exactly sure which of drives makes the noise, take of everything which is not needed to run the drives ... with your model 600 this means to take off the front cover, loosen the screws of the plate that covers the drive cage and put your ear at the drives while starting up the machine. If you still cannot locate it, take a srewdriver and put it on one drive after the other, like a doctor does to check your lungs. The drives are started in sequence of the SCSI IDs, one after the other, so you should have enough time to check each. Now that you know the drive position (you sure do now !?), you power down the system again. You take the back of a screwdriver (should not be very heavy that part) and, while powering up again, you wait for "your" drive to be the one and you knock against it. You should notice a different noise from the motor trying to spin up the drive spindle, best moment is when it just would try to "click". With some feeling you should get it going ... good luck ! If this did still not help, then we got to go the hard way ... Power down again, see the blue handle on the drive frame of that particular drive, pull it until it comes out. Now the frame is released and you can pull the drive out. OK, take a breath and KNOCK IT flat on the floor with your hand above and around the drive frame (I admit this takes some feeling) :-) Put it back in, until there is a slight resistance, then push the blue plastic handle in again and power it up. Now you should not power off the machine again, because this is normally the last time this drive will spin up again. Sometimes it makes heavy noises, but most times I did this, I got my data (my customers data) off the drives and then we could safely replace it. BTW: pulling the cable of the load source cannot help you, because the drive set ist broken, then and you will not be able to get on your data (I assume that you did not mirror or RAID-protect the drives). If there are still questions open, don't hesitate to ask. HTH, regards from germany, Philipp Rusch Carl Galgano schrieb: > I know there is a problem with one of the drives, it makes a clicking > noise. One of the guys I work with says that sometimes you can put a > drive in the freezer to have it contract a bit, enough to get it to boot > up and get the data off. Looks like a reload is in my future. Thanks > to Fritz and Steve for their comments. And BTW, why is there not an SRC > manual anywhere on line? Seems like this is a no brainier. Or perhaps > I am the no brainer, cause I could not find it. The last SRC code > manual I have came with an E04 system. > cjg > > Carl J. Galgano > EDI Consulting Services, Inc. > 550 Kennesaw Avenue, Suite 800 > Marietta, GA 30060 > (770) 422-2995 - voice > (419) 730-8212 - fax > mailto:cgalgano@ediconsulting.com > http://www.ediconsulting.com > AS400 EDI, Networking, E-Commerce and Communications Consulting and > Implementation > http://www.icecreamovernight.com > Premium Ice Cream Brands shipped Overnight > FREE AS/400 Timesharing Service - > http://www.ediconsulting.com/timeshare.html > "You ain't gonna learn what you don't want to know" - rw > > -----Original Message----- > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com] On Behalf Of Steve Richter > Sent: Sunday, April 14, 2002 11:09 AM > To: midrange-l@midrange.com > Subject: Re: SRC code A1934505 > > Carl, > > Looks like there is a problem with the load source drive. I dont know > for > sure, but you might be able to disconnect the scsi cable to the load > source drive. ( Of course you need to know which is the load source > drive, and I dont know <g> ) . The load source may just be the first > drive in the scsi chain of drives. The ipl D may just be hard coded to > write to the load source ( first ) drive. If your first drive is > failing, then the ipl D will fail. > > Steve Richter > AutoCoder, LLC > > ----- Original Message ----- > From: "Carl Galgano" <cgalgano2@ediconsulting.com> > To: <midrange-l@midrange.com> > Sent: Sunday, April 14, 2002 7:18 AM > Subject: RE: SRC code A1934505 > > > OK thanks. I am not authorized to look at the link you reference, but > > > thanks for the info. cjg > > > > Carl J. Galgano > > EDI Consulting Services, Inc. > > 550 Kennesaw Avenue, Suite 800 > > Marietta, GA 30060 > > (770) 422-2995 - voice > > (419) 730-8212 - fax > > mailto:cgalgano@ediconsulting.com http://www.ediconsulting.com > > AS400 EDI, Networking, E-Commerce and Communications Consulting and > > Implementation > > http://www.icecreamovernight.com > > Premium Ice Cream Brands shipped Overnight > > FREE AS/400 Timesharing Service - > > http://www.ediconsulting.com/timeshare.html > > "You ain't gonna learn what you don't want to know" - rw > > > > > > -----Original Message----- > > From: midrange-l-admin@midrange.com > > [mailto:midrange-l-admin@midrange.com] On Behalf Of Fritz Hayes > > Sent: Saturday, April 13, 2002 11:13 PM > > To: midrange-l@midrange.com > > Subject: RE: SRC code A1934505 > > > > > > >From the Problem Analysis PDF referenced at the following link: > > > > > http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/v4r5hwpdf/pdf/ > > model7xx.htm > > > > A1XX - 4505 Problem with load source device media > > > > Note: If the system has undergone a recent hardware upgrade, please > > check the installation procedures for required corresponding software > > upgrades. > > > > If the failing system is going through an IMPI to PowerPC AS upgrade > and > > the original IMPI load source disk unit is still associated with the > > MFIOP, do the following: > > > > Change the address of the original IMPI load source disk unit so that > > > > 1) the DSA is different than used on IMPI and > > > > 2) the PowerPC AS load source has a lower DSA than the original IMPI > > load source. > > > > Failing Item: FI00072 > > > > > > Best Regards > > > > Fritz Hayes > > Atwater Associates > > 503-636-5914 > > > > <snip> > > | Subject: SRC code A1934505 > > | > > | Here is the situation. > > | AS/400, model 600-9406, running V4R2. > > | Kept receiving critical messages that a DASD (6607) was about to > fail. > > > > | So I tried to do a save to get the best back up possible. The > machine > > > > | was running fine, except for the impending DASD failure message. > So, > > I > > | started an option 21 save. That is when the trouble started. While > > | doing the option 21 the machine hung with a B1000255 SRC. (Disk > > failure > > | I think). So I powered it down to see if I could do a manual IPL, > and > > I > > | can not. Now no matter what IPL I try (A, B or D Manual or an A or > B > > | normal), the machine dies with an A1934505. Anyone have any ideas? > > The > > | manual I have does not list this SRC code. > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list To post a message email: MIDRANGE-L@midrange.com To subscribe, > > unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
