Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
System error
- Thread starter mystr
- Start date
Ashraf Aziz
Systems Engineer
I think you must do the backup first to MO drive, then try to reload the system
Been a long time since I used a DAT. ACT-RTAPE was the command I think, and DUMP-APS. Similarities and differences between the Rolm 9600 and the Siemens H300 I always found interesting. Same, but different! Then it merged from UV1.0 software and we all started speaking the same language instead of something nearly the same.
Just to re-iterate
Do not turn off the system - it will stay running in memory as long as you leave it on - if the power goes then your system is gone.
DIS-DDSM;
and display the results here - thanks.
What you can try is to remove the plate - again do not turn anything off or press anything to reset.
Remove the plate (the metal plate with the hard drive and MO drive on it)
Leave it out for a minute or so
Insert the plate - wait to see and listen to hear if it starts using the hard drive.
Do not turn off the system - it will stay running in memory as long as you leave it on - if the power goes then your system is gone.
DIS-DDSM;
and display the results here - thanks.
What you can try is to remove the plate - again do not turn anything off or press anything to reset.
Remove the plate (the metal plate with the hard drive and MO drive on it)
Leave it out for a minute or so
Insert the plate - wait to see and listen to hear if it starts using the hard drive.
- Thread starter
- #24
It happens that after some time, 2-8 hours, information from a defective HD disk can be read.
These are temperature defects.
So do what SBCSU asked you to do.
DIS-DDSM;
and display the results here - thanks.
! But the HD disk is faulty anyway!
What you can do can be determined experimentally.
These are temperature defects.
So do what SBCSU asked you to do.
DIS-DDSM;
and display the results here - thanks.
! But the HD disk is faulty anyway!
What you can do can be determined experimentally.
Last edited:
I am not so sure the HD is faulty. Maybe. If the software is EV3.0 not UV3.0 then it's even older, 1998 maybe? That HD has been spinning for two and a half decades. So HD fault is coming at some point even if not now.
But the error about INIT areas not matching means the DASM areas in RAM DB did not match the areas that were read from disc. That means, either the DB in RAM was wrong (RMX problem solved with ADS reload) or the HD did not supply right info (some other issue, solved with ADS reload, problem may or may not return soon).
So it could be a temporary problem, solved with ADS reload. Not unexpected on something as old as this.
Nevertheless this Hicom needs immediate backup taking. It doesn't need Unixware/Assistant to function and has no SL100 connection anyway. Hicom will run fine from a MO disc then as Assistant only runs from HD, but you don't need Assistant. So replacement HDs are nice but MO discs are fine also.
It needs as already mentioned
.Full Regen
.DDRSM backup to GLA area
.DDRSM backup to MO
With the MO backup you have full bootable backup which will restore a dead system. It needs doing right now. You should buy some spare MO discs, I just looked on ebay, I saw some. Probably you have the 1.3 Gigamo I expect. but there was also a 230/540/640 I think. 1.3 is most likely.
If this is the older EV3.0 software, I think the command SWI-DSSM was still available, that was another way to bring the AMOs back, if you had a good MO copy. SWI-DSSM would switch the active load device from device 1 to 6, so if you put a good MO in the MO drive, it would read the AMOs from MO instead of HD after you made a SWI-DSSM:A1,6; Later Hicom software, the SWI-DSSM command was removed, a real handicap to service, I suppose someone at Siemens asked someone else about that, and they did not know as much about service as they thought they did because removal of that command made small problems become big problems.
You were very lucky ADP reset resolved your problem, and from the pictures, it's a large Hicom. I would make backups priority #1, DDRSM MO copy being the most important, because it's bootable. If you search in this forum there will surely be instructions for how to take a regen and a ddrsm backup.
But the error about INIT areas not matching means the DASM areas in RAM DB did not match the areas that were read from disc. That means, either the DB in RAM was wrong (RMX problem solved with ADS reload) or the HD did not supply right info (some other issue, solved with ADS reload, problem may or may not return soon).
So it could be a temporary problem, solved with ADS reload. Not unexpected on something as old as this.
Nevertheless this Hicom needs immediate backup taking. It doesn't need Unixware/Assistant to function and has no SL100 connection anyway. Hicom will run fine from a MO disc then as Assistant only runs from HD, but you don't need Assistant. So replacement HDs are nice but MO discs are fine also.
It needs as already mentioned
.Full Regen
.DDRSM backup to GLA area
.DDRSM backup to MO
With the MO backup you have full bootable backup which will restore a dead system. It needs doing right now. You should buy some spare MO discs, I just looked on ebay, I saw some. Probably you have the 1.3 Gigamo I expect. but there was also a 230/540/640 I think. 1.3 is most likely.
If this is the older EV3.0 software, I think the command SWI-DSSM was still available, that was another way to bring the AMOs back, if you had a good MO copy. SWI-DSSM would switch the active load device from device 1 to 6, so if you put a good MO in the MO drive, it would read the AMOs from MO instead of HD after you made a SWI-DSSM:A1,6; Later Hicom software, the SWI-DSSM command was removed, a real handicap to service, I suppose someone at Siemens asked someone else about that, and they did not know as much about service as they thought they did because removal of that command made small problems become big problems.
You were very lucky ADP reset resolved your problem, and from the pictures, it's a large Hicom. I would make backups priority #1, DDRSM MO copy being the most important, because it's bootable. If you search in this forum there will surely be instructions for how to take a regen and a ddrsm backup.