Another Day, Another Reason Why I hate Sun

I have a server that crapped on me forcing me to reboot it. Upon reboot, I get the following "friendly" error:

mount: the state of /dev/md/dsk/d5 is not okay
        and it was attempted to be mounted read/write
mount: Please run fsck and try again
mount: the state of /dev/md/dsk/d3 is not okay
        and it was attempted to be mounted read/write
mount: Please run fsck and try again
mount: the state of /dev/md/dsk/d6 is not okay
        and it was attempted to be mounted read/write
mount: Please run fsck and try again

So I do what every good little Solaris admin does--follow the directions. I reboot into SINGLE USER MODE (emphasis Solaris) to run fsck. Here's what I get:

red:~# fsck -m /dev/md/rdsk/d3
** /dev/md/rdsk/d3
ufs fsck: sanity check: /dev/md/rdsk/d3 okay

The sanity check looks okay, so let's see if there really is anything else... full fsck...

red:~# fsck /dev/md/rdsk/d3
** /dev/md/rdsk/d3
** Last Mounted on /mx01
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
48997 files, 2018615 used, 4565662 free (42742 frags, 565365 blocks,  0.6% fragmentation)

Hmm... looks ok. Let's try to mount it, shall we?

red:/# mount /mx01
mount: the state of /dev/md/dsk/d3 is not okay
        and it was attempted to be mounted read/write
mount: Please run fsck and try again

POS Sun. Is it ok, or isn't it? Make up your mind, and tell me why mount thinks it's broken, but fsck thinks its fine.
</rant>