Ways to analyse root disk slice Post: 302299050

9 More Discussions You Might Find Interesting

1. Solaris

mirroring the boot slice (slice 8) on x86

Hi there I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice...

2. Solaris

Move root filesystem to other slice

Hi, df -h display: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% / /proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab fd 0K 0K 0K 0% /dev/fd swap 1.0G 152K 1.0G 1% /var/run swap 1.1G 24M 1.0G 3% /tmp /dev/dsk/c1t0d0s3 57G 13G 43G 24%...

3. UNIX for Dummies Questions & Answers

Does formatting slice 2 (backup) destroy disk geometry?

I am a new Unix Sys Admin who is learning mostly from books with minimal classroom training (ie: no certificates, training is largely hands-on, conducted at work). I work with Solaris 8 through 10, and with some fairly outdated hardware. In my work restoring old workstations I have been instructed...

4. Shell Programming and Scripting

Looking for help with script to assign all disk space to slice#0 on multiple disks of varying sizes

Hi Folks, I am trying to make a script to assign all diskspace to slice 0, on multiple sized disks. Since the disks are new they may need to be labelled also to avoid the error: Cannot get disk geometry Below is my code struggling with logic which doesn't seem to be producing the desired...

5. Solaris

label a slice on disk erorr

Hi there, I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0...

6. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under...

7. Solaris

ZFS - whole disk Vs slice

we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label. now we want to mount this file system into an LDOM. my understanding of how ldom's and disk works this is that we can only do this as a...

8. Solaris

Trouble creating a disk partition slice (EFI)

Hi all, I am using SPARC Solaris 11.1 with EFI labelled disks. I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs. EFI labels use sectors and blocks and I am not sure how exactly it works. From here I can try and create a...

9. Solaris

ZFS Slice disk

Hi, How to to make a slice and define as ufs from zpool? Please advice me. Thanks. ---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ---------- Before slice: Part Tag Flag Cylinders Size Blocks 0 root wm 0 ...

LEARN ABOUT SUNOS

lutab

lutab(4)																  lutab(4)

NAME

       lutab - list of boot environments

SYNOPSIS

       /etc/lutab

DESCRIPTION

       The  file /etc/lutab is a list of the boot environments (BEs) configured on a system. There are two entries for each BE. These entries have
       the following form:

       BE_id:BE_name:completion_flag:0
       BE_id:root_slice:root_device:1

       The fields in the lutab entries are described as follows:

       BE_id	       A unique, internally generated id for a BE.

       BE_name	       The user-assigned name of a BE.

       completion_flag Indicates whether the BE is complete (C) or incomplete (NC). A complete BE is one that is  not  involved  in  any  copy	or
		       upgrade operation. A BE can be activated or compared only when it is complete.

       0	       Indicates first of two lines.

       BE_id	       As described above.

       root_slice      Designation of the root slice.

       root_device     Device on which the root slice is mounted.

       1	       Indicates second of two lines.

       The lutab file must not be edited by hand. Any user modification to this file will result in the incorrect operation of live upgrade.

SEE ALSO

       lu(1M), luactivate(1M), lucreate(1M), lucurr(1M), lufslist(1M), lustatus(1M), luupgrade(1M), attributes(5), live_upgrade(5)

WARNINGS

       The  lutab  file  is  not  a public interface. The format and contents of lutab are subject to change. Use lufslist(1M) and lustatus(1M) to
       obtain information about BEs.

SunOS 5.10							    8 Jun 2001								  lutab(4)