Summary: SuperBlock Issue

Thanks to all who replied (too many to name)!
 
I am still not sure why I recieved this error but I did find a way to get
through it.  I ran the 'newfs' command which cleared the problem.  LUCKILY I
had just rebuilt the system and the partition that I was having problems
with was the 'home' partition so there was currently no data on it.  Now
everything is working fine and I haven't recieved another problem with it
yet.
 
THANKS AGAIN!  This mailing list is a life-saver!
 
Chad Truhn 
 
#######ORIGINAL MESSAGE######## 

Guru's,
 
I've got 2 different issues on 2 different systems....
 
I am using a Solaris V440 server running Solaris 9.  I am attempting to
create a mirror from one hard drive to another.  I have done this before on
another system without errors, but on the current system I am having
problems with one paticular metadevice (corresponds directly with one
slice).  I have created the state database replicas and the metadevices on
both disks.  I attached the first slice (D10) to the RAID1 volume (D0) and
the second slice (D17) to the RAID1 volume (D7).  I then performed the
metaroot command to change the /etc/system file and the /etc/vfstab file to
boot off of the RAID1 volume.  I changed the second entry in the /etc/vfstab
to reflect the D7 mirror for the home partition.  When booting up (before
syncing with the other disk) I get the error:
 
/dev/md/rdsk/d7: BAD SUPERBLOCK: MAGIC NUMBER WRONG
/dev/md/rdsk/d7: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY THE NEEDED
INFORMATION
/dev/md/rdsk/d7: eg. fsck [-f ufs] -o b=# [special ...]
/dev/md/rdsk/d7: where # is the alternate super block.  SEE fsck_ufs (1M).
 
I then performed the 'newfs -Nv /dev/md/rdsk/d7' command to list the
alternate superblocks.  I attempted to run 'fsck -y -F ufs -o b=92592
/dev/md/rdsk/d7' to try to fix the superblock but to no avail.  It comes
back with the same 'bad superblock' error.  I then tried 10 +/- of the other
listed superblocks but everytime it comes back with the 'bad superblock'
error.  Is there something I missed or I am doing wrong?  I have fixed bad
superblocks before using this technique and never had a problem again.  Is
there another way to fix this?  I am not sure what to do...
 
The second issue is almost identical to the first, but on bootup I get the
error:
 
###  Can't roll the log for /dev/md/rdsk/d7  ###
/dev/md/rdsk/d7: BAD SUPERBLOCK: MAGIC NUMBER WRONG
/dev/md/rdsk/d7: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY THE NEEDED
INFORMATION
/dev/md/rdsk/d7: eg. fsck [-f ufs] -o b=# [special ...]
/dev/md/rdsk/d7: where # is the alternate super block.  SEE fsck_ufs (1M).
 
When I try to run fsck with an alternate superblock I get the error:
 
###  Can't roll the log for /dev/md/rdsk/d7  ###
 
I have never seen that before.  I don't know what would cause it.  I did
some searching on the SUN website and it had one section talking about the
error but it said that it could have a stale system mount.  It said to do a
'df -k' to show the mounted partitions and unmount the one that I am getting
the error on.  I attempted this but the results of 'df -k' do not show the
d7 partition being mounted.  I performed a reboot (hoping it would clear it
up, for whatever reason) but to no avail.  
 
PLEASE HELP!!!

Thanks, 
Chad M Truhn 
Jr. Computer Analyst
Chugach McKinley, Inc. 
N83 - Computer Systems Group 
(540) 653-2772 
Truhncm@nswc.navy.mil 
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers