Bootup is hanging on this code. To fix the problem it says to upgrade the microcode, but what it dosen't tell you is to how to get it booted up to upgrade. Any suggestions on getting past this and getting the machine booted up will be helpful.
got rc.powerfail message. did a crontab -l and shows the lsat 2 lines as walled rc.powerfail. What file or dir do I go to to remon=ve this entry so it want keep popping up? Step by step would be nice.
Thanks
Yes it is a wyse dumb teminal, configured as such 19200, etc. I can ping the server but getting in is not an option. It looks to be hung at c33 and want continue the boot process.Have tried several thing but always stops at c33 and want continue.
I have 520 that during boot up shows boot up procedure on console monitor and LCD changing numbers. Will get to 0c33 on LCD and hang at that point. Can any one tell me how to get the CPU to finish the boot up process or what is causing the lock up at that point. I can ping the CPU but can't get in.
I have an issue with the IBM 520 connecting to a modem port 1 time and never connecting again until a reboot has taken place. VTY1 is the port we are using. 5.3 O/S. Any ideals?
Thanks for the tip. We are using IBM 3151 and have no option for a font change. We have the character set at multinational. Any other suggestions I'll be glad to try.
Thanks for the heads up. I committed out the dt line in inittab on 2 different machines and it seemed to work on one and not the other. Any other suggestions? I have 133 of these machines in the field and are having a problem with the console on a handfull. I did notice in my error log that I am...
I have a IBM 520 with 5.3 loaded on it. I am having a problem with the console monitor not coming up to a login. The console monitor is either a ibm3151 or a wyse 150 serial terminal. The CPU boots up but nothing will come up on the console. Does not happen on install, but rather a week or month...
I have a Risc6000 P615 on aix 5.1. At some point the system lost power and now every 24 hours a message pops up on every monitor that is logged in stating the rc power failure problem. There is a file somewhere that this message is in and it repeats every 24 hours It has somthing to do with rc...
I'm not sure I understand. I go into the tmp dir I copy a file with tar cv7 xfer(file name). I see it going onto the diskette and back to #. I then attempt to read the same file with tar tv7 and I get the checksum error above.
tar cv7 and tar tv7.
tar tv7 gets tar: directory checksum error (5351 |= 4711)
tar cv7 comes back to a # sign.
lsdev -Csscsi
cd0 hdisk0 and rmt0
errpt|head -30 has no errors listed
I can copy to diskette drive with no problem. When I tried to read diskette I keep getting tar directory checksum errors. Can anyone tell me the fix. Have tried different drives and different diskettes. Please help. thanks
we are in thr process of upgrading to 5.1L which has the latest IBM and DIGI drivers. Digi had me check that to begin with, so I'm good on that side.Any other suggestions?
Have been upgrading from 4.3.1 to 5.1L. On some of the hard drive swaps, I have been getting an additional digi on bootup. We are using a digi card (pci & mc) and a 16 port concentrator for our communication devices. On certain swaps when we bring up the cpu after the swap, it comes up with SA2...
Well,
It's taken from the 19th of Aug. till the 9th of Sept. to change back to the default setting of 32 license, but it did change back. Got any more suggestions? Thanks.
The last time we changed it was on the 19th and so far so good. The time before that it lasted about 2 weeks before it went back to default. Will keep a eye on it and hopefully this will slove problem.
Thanks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.