SUMMARY: Disksuite 4.2.1 metadevice won't mount after newfs ( on D1000 )

From: John Adams <>
Date: Fri Feb 28 2003 - 12:43:34 EST
Thanks to:
Alex Stade <>
Galen Johnson <>
Gene Beaird <>
Hichael Morton <>
Kevin Buterbaugh <>
Kynaston Roger <>

For their help with this issue. 

Suggested Resolutions included:

* Don't use Slice 2 (s2) for Disksuite slices. Instead use 0 or 6.
* Don't combine metadb and dataslices
* fsck the volume
* Ensure that all drives have the same partition table with:
  prtvtoc /dev/rdsk/c3t0d0s2 | fmthard -s - /dev/rdsk/c3t1d0s2
* Check the A1000 Configuration and Patch Matrix, make sure patches
  are up to date.
* Check /etc/system, make sure all appropriate MD entries are in there.

Patch Matrix information Located here:

The interesting thing here is that none of these suggestions fixed our
issue. Our newfs was working, but the volume was unmountable. Mount 
attempts continually gave a 'not of this fstype' error, and while I did 
have the metadb and data on the same slices, that's supported by 
Disksuite. We were using slice2, though, but I don't think it's as much of 
an issue as people made it out to be; metadb checks passed, as well as all 
other checks, even with everthing on slice 2. 


What eventually fixed this was to reconstruct the entire RAID5, moving our
data slices onto slice 6, metadb onto slice zero, and doing a new 
newfs on the filesystem as:

	newfs -v -c 16 -C 7 -m 0 -o space /dev/md/rdsk/d10

I found this command on sunmanagers: a reference to building filesystems on sun4u.

Our machine's 'uname -a' output is: 
SunOS db3 5.8 Generic sun4u sparc SUNW,Ultra-80

And the volume size is:
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/md/dsk/d10      173752554       9 173752545     1%    /raid3

Thanks again, 

J. Adams

The secret of knowing where you are, is knowing what time it is. -- Anonymous
sunmanagers mailing list
Received on Fri Feb 28 12:58:39 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:04 EST