Re: Origin 200 Boot Problem
- From: "Randal T. Rioux" <randy@xxxxxxxxxxxxxxx>
- Date: Fri, 10 Mar 2006 00:43:43 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Yes, and both models support the same drives/sleds. I have a bunch, and
even tried 4 different hard drives (from clean image). I can't help but
think it is something to do with NVRAM settings, but none were changed
(and I even reset them all).
Robert Ramsey wrote:
Hello,
Does the drive still work in the Octane? As an FYI, you can buy O200/Octane
compatible drives on sleds for the cost of lunch at Subway on ebay.
-Rob
"Randal T. Rioux" <randy@xxxxxxxxxxxxxxx> wrote in message
news:440b53ee$0$944$6d36acad@xxxxxxxxxxxxxxxxxxxxxxxx
First, yes I searched every single newsgroup, mailing list and tortured
Google(tm) for a week now. I don't like to give up, but this one is a
bugger.
I have done this many times in the past, which is why at last resort I
think it may be a hardware problem in the Origin 200. Hopefully not. I
take a HD with a fresh install of IRIX 6.5.27m from an Octane2 and put
it in the Origin 200. All the times past, it boots right up without a
problem. Now I get this message:
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
Option? 1
Starting up the system...
Cannot load dksc(0,1,0)unix.
Range check failure: Section start 0xa800000020010000, size 0x544680.
Section would overwrite an already loaded program.
Unable to execute dksc(0,1,0)unix: not enough space
Autoboot failed.
dksc(0,1,0)unix: not enough space.
Hit Enter to continue.
*******************
If I boot manually from SASH, I get this:
ls
dksc(0,1,8)/:
sash ide
dksc(0,1,0)/:
. .. .desktophost dumpster Desktop .desktop-IRIS mnt etc usr hw
var
dev lib ns opt sbin stand 0esp lib32 lib64 root proc hosts bin
.cshrc .login .profile .varupdate unix debug .wshttymode
.Sgiresources
tmp core
boot -f dksc(0,1,8)sash
896+111704+16853+3848 entry: 0xa8000000012a6ea8
Standalone Shell SGI Version 6.5 ARCS Jan 6, 2005 (64 Bit)
sash: boot -f dksc(0,1,0)unix
Cannot load dksc(0,1,0)unix.
Range check failure: Section start 0xa800000020010000, size 0x544680.
Section would overwrite an already loaded program.
Unable to execute dksc(0,1,0)unix: not enough space
Unable to load dksc(0,1,0)unix: not enough space
*******************
The NVRAM is configured correctly, and is not any different from the
past succesful efforts. I have read that using a disk from different IP
levels (IP30 -> IP27 in this case) but this has never been a problem
with this configuration. I've even swapped some of the RAM with no
change in results. Anybody have some advice? Thanks for any help folks.
--
Randal T. Rioux | Procyon Labs
IT Security R&D and Consulting
Virtual: www.procyonlabs.com
Physical: DC / Baltimore
PGP: gpg --keyserver pgp.mit.edu --recv-keys 0xD08D1941
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEERIORrGMQdCNGUERA9uIAJ9ZIbCG8vAmLHezDPSDOC9a8Hp7fACgnOfu
xokN8gk9JppfkkRyc5286H8=
=H9Op
-----END PGP SIGNATURE-----
*** Free account sponsored by SecureIX.com ***
*** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
.
- References:
- Origin 200 Boot Problem
- From: Randal T. Rioux
- Re: Origin 200 Boot Problem
- From: Robert Ramsey
- Origin 200 Boot Problem
- Prev by Date: Re: Origin 200 Boot Problem
- Next by Date: Re: EIZO Flexscan TFT on SGI MaxImpact Gfx ?
- Previous by thread: Re: Origin 200 Boot Problem
- Next by thread: use of FPM SIMM modules on Indy
- Index(es):
Relevant Pages
|
