Sponsored Content
Full Discussion: label a slice on disk erorr
Operating Systems Solaris label a slice on disk erorr Post 302597290 by newbi8321 on Friday 10th of February 2012 12:01:36 AM
Old 02-10-2012
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 and size 0mb. When I do the same on partition 6 I could not able to label the partition 6 and its shows an error. Please help me . Thanks in advance.

Code:
partition> 6
Part      Tag    Flag     Cylinders        Size            Blocks
  6 unassigned    wm    4027 - 4047      104.34MB    (21/0/0) 213696

Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[4027]: 0
Enter partition size[213696b, 21c, 20e, 104.34mb, 0.10gb]: 0mb
partition> label
Ready to label disk, continue? y

Warning: error writing VTOC.
Warning: no backup labels
Label failed.

---------- Post updated at 11:01 PM ---------- Previous update was at 10:42 PM ----------

Solution : You should never make size of slice 2 0mb. Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cannot label disk when partitions are in use as described

:confused: Hello, In my Solaris system, I want to resize my mounted home directory slice. 1.I unmount the slice, #umount /export/home 2.Resize the directory #format>partition> 3.#format>label 4.#format>Cannot label disk when partitions are in use as described. So, How can label ? Thanks (2 Replies)
Discussion started by: XNOR
2 Replies

2. Solaris

Warning: No Disk Label

Hi Fellows, I am trying to mirror 2 identical disks on a SUN Ultra 10 machines (with new installation of Solaris 8). In the process, I found 2 issues: 1. prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0 Result: Disk partitions between the 2 disks do not match up. 2. manually... (2 Replies)
Discussion started by: o51974
2 Replies

3. Solaris

Ways to analyse root disk slice

Hi, Recently I faced with need of analyze root disk. I figured out two possible ways to do it: 1. Practical. Boot from CD and run format 2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format. I've already... (3 Replies)
Discussion started by: Sapfeer
3 Replies

4. Solaris

ZFS disk label missing

I 'm having problem in importing a zfs pool was getting error device missing and upon further digging found that labels on my disk for zpool are missing Does anyone know how to recover from it ? root@essapl020-u006 # zdb -l /dev/dsk/emcpower0c --------------------------------------------... (0 Replies)
Discussion started by: fugitive
0 Replies

5. Solaris

Help:"Bad checksum in disk label" and "Can't open disk label package"?

Hello, I'm brand new to Sun/Solaris. I have a Sun Blade 150, with SunOS 5.8. I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies

6. UNIX for Dummies Questions & Answers

How to read a disk label?

Hi there, I'm wondering how to display a disk label (why not edit it but I don't need that yet). I found several commands on forums like disklabel and diskinfo but I can't find them on my system and don't know the package they belong to. Can you help me? Cheers Santiago (2 Replies)
Discussion started by: chebarbudo
2 Replies

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... (1 Reply)
Discussion started by: robsonde
1 Replies

8. Solaris

Script to label a disk

Hi Guys, Do you have any script to label a disk automatically. It is part of my script but I am not able to find solution to label this inside script without user intervention. (2 Replies)
Discussion started by: prashant2507198
2 Replies

9. Hardware

Unrecognized disk label on my external HD

Hi everyone, I have an external hard drive and I accidentally deleted the partition table. Can I restore my files? If I try to run the f-disk command this is what it says Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units =... (1 Reply)
Discussion started by: Sampa
1 Replies

10. 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 ... (2 Replies)
Discussion started by: mzainal
2 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 10:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy