Sponsored Content
Full Discussion: Bad disk, how to replace ?
Operating Systems Solaris Bad disk, how to replace ? Post 303018819 by Peasant on Friday 15th of June 2018 10:58:27 PM
Old 06-15-2018
Take the following example, where i'm using files but it's the same with real devices.
This will tolerate 1 to 2 device failures.

If two devices fail from one top level vdev (mirror-N) you will lose data.

I would strongly suggest using odd number of disks and keeping one hot spare in pool.
In your configuration, get one more disk if you really love your data.

Code:
[root@gimmick ~]# ls -dl /zones/test/disk*
-rw------T   1 root     root     104857600 Jun 16 02:48 /zones/test/disk0
-rw------T   1 root     root     104857600 Jun 16 02:48 /zones/test/disk1
-rw------T   1 root     root     104857600 Jun 16 02:48 /zones/test/disk2
-rw------T   1 root     root     104857600 Jun 16 02:48 /zones/test/disk3
[root@gimmick ~]# 

[root@gimmick ~]# zpool status testpool

  pool: testpool
 state: ONLINE
  scan: none requested
config:

	NAME                 STATE     READ WRITE CKSUM
	testpool             ONLINE       0     0     0
	  /zones/test/disk1  ONLINE       0     0     0
	  /zones/test/disk0  ONLINE       0     0     0

errors: No known data errors
[root@gimmick ~]# zpool attach testpool /zones/test/disk0 /zones/test/disk2
[root@gimmick ~]# zpool attach testpool /zones/test/disk1 /zones/test/disk3
[root@gimmick ~]# zpool status testpool
  pool: testpool
 state: ONLINE
  scan: resilvered 49K in 0h0m with 0 errors on Sat Jun 16 02:48:41 2018
config:

	NAME                   STATE     READ WRITE CKSUM
	testpool               ONLINE       0     0     0
	  mirror-0             ONLINE       0     0     0
	    /zones/test/disk1  ONLINE       0     0     0
	    /zones/test/disk3  ONLINE       0     0     0
	  mirror-1             ONLINE       0     0     0
	    /zones/test/disk0  ONLINE       0     0     0
	    /zones/test/disk2  ONLINE       0     0     0

errors: No known data errors

[root@gimmick  ~]#

Hope that helps
Regards
Peasant.
 

10 More Discussions You Might Find Interesting

1. Solaris

Big UH-OH "Bad magic number in disk label"

I tried rebooting my Sun server just a few minutes ago and I got the following at boot: -- Sun Fire 280R (UltraSPARC-III+) , No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies

2. UNIX for Dummies Questions & Answers

trying to replace a disk, that's all...

Actually have a few different issues, wondering if I could get input on (tried reading/searching for an answer, with no luck) 1. Have a v240 running sol9 that needs a bad disk replaced. So, here are the steps I took: a. detached from mirroring b. cleared mirroring (metaclear) c.... (4 Replies)
Discussion started by: mr.moralito
4 Replies

3. UNIX for Advanced & Expert Users

Replace, fromat, label bad harddrive

All, Here is the situation. Four 72GB hard drive installed on Sun V-240 server. HDD3 has gone bad. The server will not boot up completely. It keeps booting into single user mode. FSCK has been run and it did not fix the problem. I believe the harddrive is bad and needs to be replaced. The... (1 Reply)
Discussion started by: Kevin1166
1 Replies

4. OS X (Apple)

Can't Mount Disk / Image after bad unmount

I have had a little issue with one of my disks, the usb cacble was pulled out and one of the external drives on it would no longer mount. I used First Aid and it verified and repaired both OK / nothing to do). After lots of messing around and not being able to mount I used Drive Genius 2 and that... (1 Reply)
Discussion started by: Cranie
1 Replies

5. Solaris

How to replace failed disk?

Dear all Please can any one explain me how to replace failed disk in Solaris 10. Please tell me the step by step procedure. (9 Replies)
Discussion started by: suneelieg
9 Replies

6. 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

7. SCO

Replace Disk

Originally Posted by panos83 Hello there Sir, according to this old post, https://www.unix.com/sco/100001-warni...ler-found.html i try to restore an old image to a new hard disk drive. The problem is that i don't have basic information such as: 1) Which btld driver do i... (3 Replies)
Discussion started by: jgt
3 Replies

8. HP-UX

LVM: is possible to replace a disk?

Scenario1: VG00 lvm,not mirrored,2 disk of 36GB vg size VG00 size is under 30G. Is possible to remove a disk of 36GB and replace "on fly" with a disk of 300GB on VG00? Thanks (6 Replies)
Discussion started by: Linusolaradm1
6 Replies

9. Solaris

Bad magic number in disk label.

This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following: Boot device: disk File args: Bad magic number in disk label Can't open disk label package Evaluating: boot Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies

10. AIX

AIX lpar bad disk I/O performance - 4k per IO limitation ?

Hi Guys, I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0 and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2 There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 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 07:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy