I. HARDWARE DIAGNOSTICS
A. default_intr. An interrupt has occurred for which there is no
device driver.
B.
I/O err in swap. While swapping a user process, a hard error
occurred on the swap disk.
C. parity error. A parity error occurred somewhere in the onboard
memory. A message will precede this diagnostic to indicate where
in physical memory the error occurred. Unfortunately, UNIX can't
diagnose the memory failure. If the error persists, the memory
diagnostic should be used.
D. iinit. The system was not able to read the root file system. This
could either be a hardware or a software problem, but it most likely
means that either the disk drive is damaged or the root file system
on the disk drive is damaged.
E.
The following diagnostics indicate that something is wrong with the
disk controller:
II. SYSTEM SOFTWARE DIAGNOSTICS
A. getmajor. While attempting to boot, the system configured a disk
drive which had no entry in the bdevsw[] array (the array of block
devices). The system was incorrectly configured.
out of memory during boot. The system is too large to run in the
B.
given memory.
C. The following diagnostics indicate that something is wrong with the
buffer cache / inode tables:
Version 1.0
Appendix C: Diagnostics
dsd: couldn't start!
a.
qicstart: couldn't start!
b.
dsd: no status posted
c.
dsdstatus
d.
e.
dsdstart unknown type
Need help?
Do you have a question about the IRIS Workstation and is the answer not in the manual?
Questions and answers