|
|
Sponsored Content
Operating Systems
Solaris
DiskSuite: Breaking mirrors.
Post 94022 by Perderabo on Monday 26th of December 2005 05:35:32 PM
12-26-2005
I'm not sure what version of Solaris you're using, but I thought that when I boot into single user mode, only / and /usr was mounted. Even if /var was mounted, I would think that a "umount /var" would take care of that. I'm not sure if stuff is mirrored in single user mode. But I would resist breaking a mirror if I didn't need to. And I don't see how that will help here. Actually, I now think that you simply had a typo in /etc/vfstab. Someone had changed /var to "ro". Later, a reboot caused your problem to occur. 
As for "fsck -n", it simply provides information and I try to gather information when I don't understand something. "fsck -n" might result in anything from "all looks cool" to "file system? what file system?". Knowing the state of /var would be a help. If I'm right about the typo in /etc/fstab, "fsck -n" will not find a problem. That would lead me to stop looking at /var. Add that to the odd read-only status of /var and my next step would be to check vfstab.
I also like to run "fsck -n" to see how bad stuff is before I run a plain "fsck". I have deeply regretted not doing that on several occasions.
As for "fsck -n", it simply provides information and I try to gather information when I don't understand something. "fsck -n" might result in anything from "all looks cool" to "file system? what file system?". Knowing the state of /var would be a help. If I'm right about the typo in /etc/fstab, "fsck -n" will not find a problem. That would lead me to stop looking at /var. Add that to the odd read-only status of /var and my next step would be to check vfstab.
I also like to run "fsck -n" to see how bad stuff is before I run a plain "fsck". I have deeply regretted not doing that on several occasions.
|
|
6 More Discussions You Might Find Interesting
1. Solaris
Hi,
Ii am facing the belwo problem:
d50: Mirror
Submirror 0: d30
State: Needs maintenance
Submirror 1: d40
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 212176648 blocks (101 GB)
d30:... (3 Replies)
Discussion started by: sag71155
3 Replies
2. Linux
How can I add additional mirrors to my CENTOS distro, according to this page AdditionalResources/Repositories - CentOS Wiki there are few fedora project repositories I'd like to add any of them but I don't know how?
Thank you in advance (0 Replies)
Discussion started by: c0mrade
0 Replies
3. Linux
Dear all,
CentOS 6
After executing "yum update -y" command I am facing this error. Please help me out.
thanks in advance. Full error & error code is given as follow:
... (7 Replies)
Discussion started by: saqlain.bashir
7 Replies
4. Solaris
Hi Guys,
I need a help with attaching the sub mirrors as it keep throwing errors.
I have done solaris live upgrade and it was succesful but it keeps throwing error only for root (s0) and swap (s1)when i try to attach them.
For rest of the partitions for slices 3,4,5 on target 1 are able to... (4 Replies)
Discussion started by: phanidhar6039
4 Replies
5. Solaris
All,
One-way mirror. Elements of the concat in Last-errd state. What would be the best way to correct it?
metastat -s db2test -pc
db2test/d220 p 5.0GB db2test/d200
db2test/d219 p 5.0GB db2test/d200
db2test/d218 p 5.0GB db2test/d200
db2test/d217 p 30GB db2test/d200... (0 Replies)
Discussion started by: ossupport55
0 Replies
6. Solaris
I have a single zpool with 3 2-way mirrors ( 3 x 2 way vdevs) it has a degraded disk in mirror-2, I know I can suffer a single drive failure, but looking at this how many drive failures can this suffer before it is no good? On the face of it, I thought that I could lose a further 2 drives in each... (4 Replies)
Discussion started by: fishface
4 Replies
LEARN ABOUT X11R4
installboot
installboot(1M) installboot(1M) NAME
installboot - install bootblocks in a disk partition SYNOPSIS
installboot bootblk raw-disk-device The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition. The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be found using the -i option of uname(1). The installboot utility is a SPARC only program. It is not supported on the architecture. users should use installgrub(1M) instead. bootblk The name of the bootblock code. raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is read- able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive. Example 1: Installing UFS Boot Block To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use: example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s0 /usr/platform/platform-name/lib/fs/ufs directory where ufs boot objects reside. /platform/platform-name/ufsboot second level program to boot from a disk or CD See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5) WARNINGS
The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device. 11 Apr 2005 installboot(1M)