Sponsored Content
Operating Systems Solaris Boot Solaris 10 from detached root mirrors Post 302453300 by gnom on Tuesday 14th of September 2010 07:45:07 PM
Old 09-14-2010
Here the steps I follow

- breaking the mirrors
Code:
metadetach d10 d12
metadetach d30 d32
metadetach d40 d42

- fsck the detached mirrors
Code:
fsck /dev/md/rdsk/d12
fsck /dev/md/rdsk/d32
fsck /dev/md/rdsk/d42

- Mount detached to modify /etc/system and /etc/vfstab
Code:
mount /dev/md/dsk/d12 /mnt

- Remove following line from /mnt/etc/system
Code:
rootdev:/pseudo/md@0:0,10...

- change following lines in /mnt/etc/vfstab
Code:
 /dev/md/dsk/d10  /dev/md/rdsk/d10  /     ufs  1  no
  /dev/md/dsk/d30  /dev/md/rdsk/d30  /var  ufs  1  no
  /dev/md/dsk/d40  /dev/md/rdsk/d40  /opt  ufs  1  no

To
Code:
 /dev/dsk/c2t500000E01998D020d0s0 /dev/rdsk/c2t500000E01998D020d0s0 /    ufs 1 no
  /dev/dsk/c2t500000E01998D020d0s3 /dev/rdsk/c2t500000E01998D020d0s3 /var ufs 1 no
  /dev/dsk/c2t500000E01998D020d0s4 /dev/rdsk/c2t500000E01998D020d0s4 /opt ufs 1 no

- Umount the Filesystem
Code:
umount /mnt

- Shut down the server for patching
- Patch the server
- Reboot the server
- a few days later attach the mirrors again

When the something happen during patching just boot from the mirror.

Last edited by gnom; 09-14-2010 at 08:50 PM.. Reason: Added boot
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Replacing root / boot files

Hi everybody, I am running SCO-V openserver platform running on P-100. How can I replace root / boot files ? I want to do this because, if my system is not getting booted or my root is corrupted, I want to just replace this with the back up taken or boot/root floppy. Usually I am restoring... (1 Reply)
Discussion started by: skant
1 Replies

2. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

3. SCO

sco openserver 5.0.0 boot / root disk

Hi, I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone. I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies

4. Solaris

Solaris DiskSuite, boot from detached disk

Hi, I am running Solaris 8 on Sun server with 2 hard drives. I have configured mirroring on the system using DiskSuite tool in order to have the same data on both disks. Now I want to perform some software upgrade and I would like to use the second disk as a backup disk. This means taking this... (3 Replies)
Discussion started by: carlossg
3 Replies

5. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

6. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

7. Solaris

Solaris stuck during boot after reconfigure boot

Hello, I have a problem with my machine that won't boot properly. The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies

8. UNIX for Beginners Questions & Answers

Can a root role change the root password in Solaris 10?

i do not have root on a solairs 10 server , however i do have the root role, i was wondering if I can change the root password as a a role with the passwd command? I have not tried yet. and do i have to use the # chgkey -p afterwards? i need to patch is why i am asking. thanks (1 Reply)
Discussion started by: goya
1 Replies
volfs(7FS)                                                         File Systems                                                         volfs(7FS)

NAME
volfs - Volume Management file system DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be /vol for this description. Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a particular piece of hardware). Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk provides character access to random access devices. The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a volume will be the same for both the block and character device. The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777, owner=root, group=sys. Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per- missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys. mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc- tory permissions. The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2). If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the following /vol locations: +-----------------------------------+------------------------------------+ | Location | State of Media | +-----------------------------------+------------------------------------+ |/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block | | | device access | +-----------------------------------+------------------------------------+ |/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw | | | device access | +-----------------------------------+------------------------------------+ |/vol/dev/diskette0/unlabeled | unlabeled floppy-block device | | | access | +-----------------------------------+------------------------------------+ |/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access | +-----------------------------------+------------------------------------+ |/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access | +-----------------------------------+------------------------------------+ |/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access | +-----------------------------------+------------------------------------+ For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M). Partitions Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory. For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then: /vol/dsk/foo/s0 /vol/dsk/foo/s2 /vol/dsk/foo/s5 for block access and /vol/rdsk/foo/s0 /vol/rdsk/foo/s2 /vol/rdsk/foo/s5 for character access. If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout. A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management, however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated and the user may cancel the operation with volcancel(1), if desired. SEE ALSO
volcancel(1), volcheck(1), volmissing(1) rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4) System Administration Guide: Basic Administration SunOS 5.10 8 Feb 1995 volfs(7FS)
All times are GMT -4. The time now is 10:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy