I can't provide any insight, but nice to know I'm not the site n00b anymore.
Welcome to Neko Bunn....these folks are pretty cool and helpful.
Aaron
Welcome to Neko Bunn....these folks are pretty cool and helpful.
Aaron
jan-jaap wrote:zagnut wrote: Nope. More than likely, it will be a redundant RAID array for serving photographs.
IRIX does not do 'software' RAID, other than JBOD, RAID0 (striping) and RAID1 (plexing). The latter requires a license.
As far as hardware RAID goes: there are no hardware RAID controllers for SGI/MIPS systems. You'll need a disk array with built-in RAID capabilities, or a SAN server. Beware that there's a 2TB logical LUN limit in IRIX (this is a 32bit limit), arrays returning 64bit LUN numbers here will result in kernel panics and massive corruption. XFS does not have a 2TB limit, and XVM can be used to create large volumes out of 2TB or smaller LUNs.
I've got an old IBM DS4300 SAN server I occasionally use with my IRIX systems, it has ~ 8TB raw capacity (28*300GB). I can configure the disks in 2TB RAID5 LUNs and serve them up to an IRIX system which can then stripe them into a single, large volume using XVM (effectively a RAID50), and put a single XFS filesystem on it spanning the entire volume. SGI used to sell the same unit as the InfiniteStorage TP9300 and this is the way you were supposed to add large, redundant storage capacity to an SGI server.
The DS4300 is fully licensed and has many interesting enterprise features, but the noise level and power consumption of ~ 500W make this a silly thing to operate 24/7 at home. My current storage server (Supermicro, Haswell Xeon, 16TB raw capacity) idles at ~ 20W and is all but silent. And faster. Much faster.
foetz wrote: that can be in a couple of locations. first have a look into /extra. that might be hidden so use the terminal or make hidden files and folders visible otherwise.
alternatively you could mount the small efi partition directly and look for the boot.plist there
foetz wrote:zagnut wrote: I know there's a file somewhere, similar to Win boot.ini or BCD. I just dont know where it is located or how to edit it.
yeah that's the default com.apple.Boot.plist. if you don't have either chameleon will just use the defaults
foetz wrote:zagnut wrote:foetz wrote:zagnut wrote: I know there's a file somewhere, similar to Win boot.ini or BCD. I just dont know where it is located or how to edit it.
yeah that's the default com.apple.Boot.plist. if you don't have either chameleon will just use the defaults
Is there any way to add a specific boot list?
sure, just create that file in /Extra. shouldn't be hard to find an example out there
uunix wrote: But are we not being a bit two faced on the fact, we like to use this retro equipment for what it was at the time and lets face it, yes in this day and age there are possibly better, faster ways on other hardware, but we like SGI (some of it) and that's why we make the best of what it is.
So comparing SGI server abilities to modern solutions is rather unfair on SGI.
And at the time, I bet we could produce a million people who companied about IRIX, AIX, HPUX etc, but I bet we could find the same number to complain about modern day servers also.
dexter1 wrote: With verify bits you mean identifying the hardware and testing its individual components?
First do a hinv -vm so you can write down the individual part numbers and revisions of the components.
Then you can do a general hardware test, by booting into the PROM and selecting Diagnostics. You need a recent IRIX installation CD overlay containing the diagnostic tools.
There probably is more info on Ian's site regarding specific tests, especially graphics hardware.
jan-jaap wrote:dexter1 wrote: You need a recent IRIX installation CD overlay containing the diagnostic tools.
If the system has IRIX installed, PROM will boot the diagnostics from the hard disk. It will try to load diagnostics from a CD first, but failing that it will start them from the system disc.
NB: since we're talking about an Octane2 here: the standard diagnostics do not test VPRO graphics boards.
toasty wrote: I've always used Ian Mapleson's parts and spares page as a reference: http://www.sgidepot.co.uk/sgidepot/partsspares.html
SGI part numbers should look something like "030-1467-001 Rev H" and are almost always found on every board, module, etc.