What's the physical layout of the disks in the case? There are three slots for drives - which is being used by the system disk and which by disk2? It may be that disk2 has been moved from middle to top and the partition being seen by the system as /dev/dsk/dks0d3s0, though it should still show up in hinv as "unit 3" on controller 0. I'm assuming that your PROM boot variable is still pointing to disk 1, the lowest slot.
Same if someone has repartitioned disk2 as an option disk - /dev/dsk/dks0d2s0 will be pointing to a partition that no longer exists (but again, if disk2 were there hinv would see it whether it has a partition 0 or partition 7).
Note - you post state fstab to contain "/dev/dsk/dks0d250" - is that a copy-and-paste or a tr-yping typo? It ought to read "/dev/dsk/dks0d2s0" (s0 = partition 0 on d2 = disk with SCSI ID2 on dks0 = controller 0).
Can you hear two disks spinning up / "chattering"? (maybe not over Octane fan sound!) or, if you take the good disk out, can you here the other one? (IRIX won't boot, of course, if you take the good system disk out).
Same if someone has repartitioned disk2 as an option disk - /dev/dsk/dks0d2s0 will be pointing to a partition that no longer exists (but again, if disk2 were there hinv would see it whether it has a partition 0 or partition 7).
Note - you post state fstab to contain "/dev/dsk/dks0d250" - is that a copy-and-paste or a tr-yping typo? It ought to read "/dev/dsk/dks0d2s0" (s0 = partition 0 on d2 = disk with SCSI ID2 on dks0 = controller 0).
Can you hear two disks spinning up / "chattering"? (maybe not over Octane fan sound!) or, if you take the good disk out, can you here the other one? (IRIX won't boot, of course, if you take the good system disk out).