I'm pretty intermediate with Unix and pretty much a neophyte when it comes to SCO, so any help would be appreciated. We have an old SCO Openserver 5.0.5 system running our decommissioned accounting package. We've been keeping it running for ease of copying old PO descriptions into our new package. Unfortunately this morning the system failed to boot.
When reset the machine will display the boot: prompt, then after a second or two will commence booting. It gets through all the "loading kernel" "dots" then refreshes the screen. "SCO OpenServer(TM) Release 5" and copyright information is displayed at the top of the screen. Below that it appears as if drivers are being loaded. The last five lines I see are:
%Sdsk - - - cyls=2212 hds=225 secs=63 fts=sdb
mem: total = 138616k, kernel = 13468k, user = 117148k
swapdev = 1/41, swplo = 0, nswap=1024000, swapmem = 512000k
Autoboot from rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: Hz = 100, i/o bufs = 6652k
After that I get a cursor. I can ALT-F2 to another console, but again all I see is a cursor. I am able to ping the IP, but I am not able to telnet in. I've tried booting using "boot: unix.safe" only to experience the same problem.
Anyone have any ideas or anything I can try?
-Craig
When reset the machine will display the boot: prompt, then after a second or two will commence booting. It gets through all the "loading kernel" "dots" then refreshes the screen. "SCO OpenServer(TM) Release 5" and copyright information is displayed at the top of the screen. Below that it appears as if drivers are being loaded. The last five lines I see are:
%Sdsk - - - cyls=2212 hds=225 secs=63 fts=sdb
mem: total = 138616k, kernel = 13468k, user = 117148k
swapdev = 1/41, swplo = 0, nswap=1024000, swapmem = 512000k
Autoboot from rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: Hz = 100, i/o bufs = 6652k
After that I get a cursor. I can ALT-F2 to another console, but again all I see is a cursor. I am able to ping the IP, but I am not able to telnet in. I've tried booting using "boot: unix.safe" only to experience the same problem.
Anyone have any ideas or anything I can try?
-Craig