Solaris 8.2 Bad magic number

I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run a fsck and there were no noticable issues. After that the errors didn't return, instead I got a different one:

"Bad magic number in disk label
Can't open disk label package
Cannot open /pci@1f,0/pci@2/scsi@4/disk@0,0:a
panic - boot: ufsboot: cannot determine filesystem type of root device
Program terminated"

I confirmed all the envs were properly set and I could still bring it up in single-user mode to confirm the files were where they were supposed to be, based upon memory. Any help would be appreciated.

Are you still able to boot the from the disk into single user mode? If not then the 1st option seems to be booting the system from CD or in case if you have boot server in single user mode and mounting the slick on /a and running the fsck. Once you are through you can execute iostat -En to see if you an find something unusual in output

I'm afraid that we do not have the OS disc (the Marine Corps doesn't trust us :S). However, we have been able to run an fsck via single-user mode straight from the server. There were no issues that we (3 technicians, not software guys ^^') could find.

As for the iostat -En, isn't that a CPU statistics command? :S

What do you mean by straight from server?

If you can run the system in single user mode from the same disk then there shouldn't be as such something major. Do you have mirroring and all in your system if so break the mirror and try to boot the system through the secondary disk.

Iostat -En is used to find / report the I/O statistics

My apologies, I've worked with it for so long while referring to it as a server. The "server" I meant was the drive that I'm having the issue on. It can run in single-user mode but fsck has no issues and booting regularly results in the error I gave.

I'll go out and take a look at the iostat -En command results, but I'm not sure what I'd be looking for. ^^'