I would like to publicly acknowledge those who can't seem to properly configure their auto-responders: ken@mail.condocerts.com SreenivasaRao Vadalasetty Wallimann Stefan Obst, Thomas Abia, Iquo Original question follows. First of all, those warnings about failed forcemod can be ignored, that's just Solaris Volume Manager trying to load the kitchen sink. You can comment out entries in /etc/system to avoid the warnings. Sorry about the RTFM question. You can find the explanation in metaroot's manpage WARNING: forceload of misc/md_hotspares failed might appear during boot if root is on a metadevice and no hot spares are specified. This can be eliminated by defining an empty hot spare pool. WARNING: forceload of misc/md_trans failed might appear if no trans devices have been configured. WARNING: forceload of misc/md_raid failed might appear if no RAID5 devices have been configured. My problems with my volume not having a device, and hence not being mountable, on boot is because it is set up as a "disk set" using -s with metainit. Eugene Schmidt nailed this: The problem is that you have created the volumes in set (-s) option. Metaset require RPC calls. In the bootup sequence, this is after the mount in /etc/rc2.d. I suggest destroying all volumes and metadb's, then restart - without creating metasets. 1) create "metadb -f -a cXtYdNsZ", etc till all metadbs are created ( -f only with first) 2) metainit d1 ...... (no -s) etc I had already made sure that the rpc.meta* entries in /etc/inetd.conf were not disabled, as suggested by several people. Some more helpful info from Eric van de Meerakker: You always need the system to explicitly take ownership of a diskset at boot-up. Non-diskset devices will be automatically mounted and can be specified as usual in /etv/vfstab, diskset devices cannot be mounted directly from /etc/vfstab. Other general suggestions were to check if the state database replicas are set up properly (metadb -i) as well as the stripe (metaset). Thanks to the following: Jacob J. Rieper Harrington, David B Gary Chambers Ronny Martin Eric van de Meerakker Dave Foster > > We have a V880z with Solaris 9 (8/03) installed, latest > recommended patches. > > I created a 4 x 73GB striped RAID volume using Solaris Volume > Manager, via Sun Management Center. Had no problems creating > a filesystem with 'newfs', and the volume mounted find. > > But on boot the system complains about not being able to load > several modules related to Volume Manager: > > Nov 14 16:20:55 shine genunix: [ID 370176 kern.warning] WARNING: forceload of mi > sc/md_trans failed > Nov 14 16:20:55 shine genunix: [ID 370176 kern.warning] WARNING: forceload of mi > sc/md_raid failed > Nov 14 16:20:55 shine genunix: [ID 370176 kern.warning] WARNING: forceload of mi > sc/md_hotspares failed > Nov 14 16:20:55 shine genunix: [ID 370176 kern.warning] WARNING: forceload of mi > sc/md_sp failed > > The fsck of this volume fails on boot (set to fsck in pass 3 in vfstab), > and when I try it manually it complains that the device is not found. > > Once the system boots up, if I run Sun Management Center and go to > Enhanced Storage and select my Disk Set, it complains that my server > doesn't own the disk set. I specify to take ownership of the disk set, > (runs the command '/usr/sbin/metaset -s share0 -t') > and then I can mount my volume (after having to umount it first, > /etc/mnttab gets an entry from our NIS map of NFS shares...WTF?? > don't see this on any of our other Suns). > > What really confuses me is that if I reboot I need to go through this > same procedure again, the server still doesn't "own" the disk set. > > Can someone tell me what I have missed which is (a) causing Volume > Manager modules to fail forceload on boot; and (b) causing me to have > to take ownership of my disk set each time I boot up. > > I'm used to Veritas Volume Manager, I am a Sun Volume Manager beginner > so please be kind. > > Dave Foster > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > David Foster National Center for Microscopy and Imaging Research > Programmer/Analyst University of California, San Diego > dfoster[at]ucsd[dot]edu Department of Neuroscience, Mail 0608 > (858) 534-7968 http://ncmir.ucsd.edu/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > "The reasonable man adapts himself to the world; the unreasonable one > persists in trying to adapt the world to himself. Therefore, all progress > depends on the unreasonable." -- George Bernard Shaw > _______________________________________________ > sunmanagers mailing list > sunmanagers@sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagers << All opinions expressed are mine, not the University's >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= David Foster National Center for Microscopy and Imaging Research Programmer/Analyst University of California, San Diego dfoster[at]ucsd[dot]edu Department of Neuroscience, Mail 0608 (858) 534-7968 http://ncmir.ucsd.edu/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable." -- George Bernard Shaw _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Fri Nov 21 16:49:23 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:24 EST