bash-2.05# fsck -m
** /dev/md/dsk/d2
ufs fsck: sanity check:/dev/md/rdsk/d2 already mounted read/write
** /dev/md/dsk/d8
ufs fsck: sanity check:/dev/md/rdsk/d8 already mounted read/write
** /dev/md/dsk/d11
ufs fsck: sanity check: /dev/md/rdsk/d11 already mounted
** /dev/md/dsk/d28
ufs fsck: sanity check: /dev/md/rdsk/d28 already mounted
** /dev/md/dsk/d26
ufs fsck: sanity check: /dev/md/rdsk/d26 already mounted
** /dev/md/dsk/d30
ufs fsck: sanity check: /dev/md/rdsk/d30 already mounted
** /dev/md/dsk/d31
ufs fsck: sanity check: /dev/md/rdsk/d31 already mounted





On Mar 12, 4:59 pm, Darren Dunham <ddun...@redwood.taos.com> wrote:


> Hmm...
>
> I'm actually more interested in where that 'fsck' failure is coming
> from.
>
> If you do a 'fsck -m' (should be harmless), I'd expect a quick message
> about all those devices being mounted. Is that /dev/rdsk device listed
> in that output?
>
> --
> Darren Dunham ddun...@taos.com
> Senior Technical Consultant TAOS http://www.taos.com/
> Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >