- #Veritas volume manager command line drivers
- #Veritas volume manager command line update
- #Veritas volume manager command line Offline
This should remove all the device paths for this particular disk. The -C option cleans up the /dev directory, and removes any lingering logical links to the device link names. Rebuilding these tape devices could cause undesirable results on non-Sun hardware. This saves time and is important on systems that have tape devices attached.
#Veritas volume manager command line update
With the “-c disk” option, devfsadm will only update disk device files. The devfsadm command then creates device special files in the /devices directory, and logical links in /dev.
#Veritas volume manager command line drivers
The default devfsadm operation, is to attempt to load every driver in the system, and attach these drivers to all possible device instances. Initiate devfsadm cleanup subroutines by entering the following command:
If the disk is multipathed, run the ‘luxadm -e offline’ on the second path as well. Physically pull the bad disk from the host run the commands: Otherwise, if you receive any errors during this step: If no errors are printed, continue to step 6. NOTE: The picld daemon notifies the system that the disk has been removed. Physically remove the disk and press the Return key. The drives are now off-line and spun down.
Please verify the above list of devices and then enter c or to Continue or q to Quit. The list of devices which will be removed is:ġ: Device name: /dev/rdsk/c1t1d0s2 Node WWN: 20000020371b1f31 WARNING!!! Please ensure that no file systems are mounted on these device(s).Īll data on these devices should have been backed up. This will produce output similar to the following: # /usr/sbin/luxadm remove_device /dev/rdsk/c1t1d0s2
#Veritas volume manager command line Offline
Once Veritas has recognized the disk as offline and ready for replacement, you need to tell the operating system. Verify the disk has been marked “offline” with “vxdisk list”: Put the disk into the “offline” state with the following command: If vxdiskadm option 4 is used to remove the disk for replacement, instruct VxVM to re-read the device tree by running the command
If it is, move it to the good side of the mirror, for example: If this is a root-disk or root-mirror, use the dumpadm command to ensure that the dump-device is not on the failed disk. Lrwxrwxrwx 1 root root 74 c1t0d0s0 -> and boot-device in nvramrc This information is needed to change nvramrc. NOTE: If this is a root-disk or root-mirror, check the following removed disk information, before this operation. After running ‘vxdiskadm’, the output should look like this: If the disk does not show up as “failed was”, as shown above, then you should run ‘vxdiskadm’ and choose option #4 to remove the disk for replacement. Before replacing any disk under VxVM control, it should be in either a ‘failed’ or ‘removed’ state: NOTE: All data on these devices should have been backed up. Procedure To Replace FC Disk which is under VxVM Control Please not If the disk is not under VxVM control, you can skip steps 3,5,10,11,12 Following below procedure will prevent the duplicate device from being created in the first place. To remove the duplicate entries from the above command, the easy way is to reboot the server. Failure to follow this procedure could result in a duplicate entry for the replaced disk in VxVM, in ‘vxdisk list’ command
The procedure below ensures to alert VxVM to the fact that the drive is being replaced, although the disks are hot-swappable. Hot swapping of a failed disk is fairly straight procedure if the disks are regular SCSI disks, but for the Fibre Channel (FC) disks we should follow different procedure for hot swaping.īelow specific procedure should be used when replacing one of the internal disks in a system with internal fibre drives (Sun Fire 280R, Sun Fire V480, Sun Fire V490, Sun Fire V880, Sun Fire V890), especially if the disk is under Veritas Volume Manager (VxVM) control.