Sponsored Content
Full Discussion: Solaris 11 disk issue
Operating Systems Solaris Solaris 11 disk issue Post 302818085 by cbtshare on Friday 7th of June 2013 02:16:46 AM
Old 06-07-2013
Solaris 11 disk issue[solved]

I have 2 disks in my system.I recently added a zpool to the disk, but today I changed my mind and deleted the zpool ,
zpool destroy -f extra

The zpool is now deleted and I want to partition the disk, so I delete the only partition on the disk.

Now when I run format again,

Code:
format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c7d0 <SAMSUNG-S14JJ9DP72414-0001-149.05GB>
          /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
       1. c8d1 <drive type unknown>
          /pci@0,0/pci-ide@1f,2/ide@1/cmdk@1,0

Specify disk (enter its number): 1



AVAILABLE DRIVE TYPES:
        0. other

My issue is I can see the drive but I cannot access it (pressing 1)to partition it,I get the message above.Can anyone help?

Last edited by cbtshare; 06-07-2013 at 07:14 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris 8 disk/mirroring issue

Hello! I recently inherited system administration duties for a SUN v880 box. The system has 6 physical hard disks.. In doing some basic maintenance, I found they're configured for mirroring. I ran the metastat and metadb commands, and many of the mirrors are showing they are in need of... (5 Replies)
Discussion started by: ghuber
5 Replies

2. AIX

disk issue

Hi, I have a AIX 4.3 box here with problems cause of a disk in below VG. volume group: workvg lspv hdisk4 000166789869ab2d workvg hdisk5 000166789869b96b workvg now hdisk4 disk has failed and cause the quorum was set, workvg became varied off. I have to replace the... (2 Replies)
Discussion started by: karthikosu
2 Replies

3. Solaris

Disk Mirror in Solaris 9 via Solaris Volume Manager

Hello, I am trying to do mirror in solaris 9. I have total 0-7 disks 4 5 6 7 0 1 2 3 Drive 0 and Drive 4 = Boot Drives Need to Mirror following drives. Drive 1 and Drive 5 = Need to mirror Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5. Then i... (3 Replies)
Discussion started by: deal732
3 Replies

4. UNIX for Advanced & Expert Users

partition disk issue

hi guys, I've got a strange issue, may be one of you has experienced this. SunOS 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-V440 everything is mirrored. My issue is that I have a umpty directory but seems to have data on. Let me show you # df -h /data Filesystem size used... (10 Replies)
Discussion started by: moustik
10 Replies

5. AIX

Disk I/O Issue

We have a filesystem which contains 8 hard disks but i am facing disk I/O issue becuase data is not spreading across all the disks.Is there any way i can check how data is spreading and any parameter we need to change to spread ata across all disks. OS--AIX 5.3 (3 Replies)
Discussion started by: ukatru
3 Replies

6. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

7. Solaris

Solaris 10 installation issue Error 25: Disk cannot be read - Solved

Hi all, I guess most of you have seen this error message while installing Solaris 10 on an x86 platform. I got the error message while installing from DVD ISO on my home VMWare ESXi server. It took me a long time to figure the exact issue and a subsequent solution. the solution is very... (1 Reply)
Discussion started by: admin_xor
1 Replies

8. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% / ... (0 Replies)
Discussion started by: fretagi
0 Replies

9. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies

10. Solaris

Server disk issue need help

Hello all, Our Solaris 9? Sun Fire 480R backup server(in another city) is throwing disk errors such as these repeatedly. WARNING: vxvm:vxio: Subdisk rootdisk-02 block 24037056: Uncorrectable read error WARNING: vxvm:vxio: Subdisk rootdisk-02 block 7767072: Uncorrectable write error ... (18 Replies)
Discussion started by: RyanV
18 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 03:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy