AIX is good because you cannot remove anything that the OS believes is in use so it protects itself. You can detach them at the SAN end, but that will cause hardware alerts.
Are you relinquishing all IP addresses? Is this part of a cluster perhaps?
I presume you mean that you want to reclaim the disks/LUNs for use on other servers/partitions so:
You cannot remove these safely from AIX without them being removed from the relevant volume group.
You cannot remove them from the volume group unless they are empty (no logical volumes)
You cannot remove the logical volumes if they are in use as either raw devices (such as for a database) or as formatted and mounted filesystems.
You cannot unmount filesystems if they are in use, i.e. open files or any process with their current directory within the tree.
Before going through the process to unwind them, will anything be left of the server at the end of this or is it being turned off? If so, shut it down and use the SAN to detach/dis-associate the LUNs from the client AIX node (or whatever terminology your SAN uses) To reuse the server at a later date, you would be best to re-install over the root volume group so that it doesn't try to use devices that have been removed or use IP addresses that may have been reallocated elsewhere.
If you need to do a partial removal, it would be helpful to know what we're dealing with. Can you share the output (pasted in CODE tags) from the following:-
Code:
oslevel -s
df
lsvg
lsvg -p each volume group in turn
lsvg -l each volume group in turn
lspv
Thanks, in advance,
Robin
Last edited by rbatte1; 01-12-2017 at 10:36 AM..
Reason: Added welcome
I'm trying to mount a USB Lacie external hardrive in my Linux system but am having trouble doing so, I'm also having trouble mounting my USB ZIP 250 drive.
It is totally me being stupid, but I'm new to unix and am having a few teathing problems.
the command I'm using is the following mount... (4 Replies)
I have the following system:
- DELL Dimension 8300
- Pentium IV @ 2.66GHz
- BIOS Revision A07
- 1.5GB RAM
- 2 Hard Disks (Master 120GB, Slave 80GB), I guess it's IDE
I had WinXP on the master disk (hd0) and recently installed Solaris 10 1/06 on the slave disk (hd1). The NTLDR is in MBR... (0 Replies)
I need to insert a new hard disk into a Sun Fire v210 machine. The (only) internal disk which is already in the machine is part number XRA-SC1CB-73G10K (DISK DRIVE ASSY. 73GB, 10K RPM, with SPUD BRACKET).
I also have nearly endless access to IBM hard disks at extremely low prices and would there... (2 Replies)
How can I get only the local hard disks in Solaris?
I've tried iostat -x, iostat -E, etc, but it shows the cdroms, dvds, external storage... I want only the local physical hard disks.
Thanks. (2 Replies)
Hi
I am oracle DBA and sometimes need to see on which disks oracle data files are residing . How can we check that . The file system is jfs on aix 5.2.0.0
The method is use is to use mount |grep oracle_dir_name
or lsfs mount_point_name command to see what /dev/logical_volume_name is mounted... (1 Reply)
Could you please explain us what are these transport/hard errors...
when i ran the following command,
iostat -E | grep Errors
i got the following:
sd240 Soft Errors: 37 Hard Errors: 1144 Transport Errors: 0
sd578 Soft Errors: 0 Hard Errors: 890 Transport Errors: 0
Please... (5 Replies)
Hello to all,
what is the command in Solaris/Unix which I can use to determine how many hard disks exist in the system?
I have tried with different command such as df -lk and similar but cannot know for sure how many actual disks are installed.
Commands like # fdisk -l | grep Disk and #... (14 Replies)
Discussion started by: Mick
14 Replies
LEARN ABOUT HPUX
diskscan
diskscan(1M) System Administration Commands diskscan(1M)NAME
diskscan - perform surface analysis
SYNOPSIS
diskscan [-W] [-n] [-y] raw_device
DESCRIPTION
diskscan is used by the system administrator to perform surface analysis on a portion of a hard disk. The disk portion may be a raw parti-
tion or slice; it is identified using its raw device name. By default, the specified portion of the disk is read (non-destructive) and
errors reported on standard error. In addition, a progress report is printed on standard out. The list of bad blocks should be saved in a
file and later fed into addbadsec(1M), which will remap them.
OPTIONS
The following options are supported:
-n Causes diskscan to suppress linefeeds when printing progress information on standard out.
-W Causes diskscan to perform write and read surface analysis. This type of surface analysis is destructive and should be invoked
with caution.
-y Causes diskscan to suppress the warning regarding destruction of existing data that is issued when -W is used.
OPERANDS
The following operands are supported:
raw_device The address of the disk drive (see FILES).
FILES
The raw device should be /dev/rdsk/c?[t?]d?[ps]?. See disks(1M) for an explanation of SCSI and IDE device naming conventions.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO addbadsec(1M), disks(1M), fdisk(1M), fmthard(1M), format(1M), attributes(5)NOTES
The format(1M) utility is available to format, label, analyze, and repair SCSI disks. This utility is included with the diskscan, addbad-
sec(1M), fdisk(1M), and fmthard(1M) commands available for x86. To format an IDE disk, use the DOS format utility; however, to label, ana-
lyze, or repair IDE disks on x86 systems, use the Solaris format(1M) utility.
SunOS 5.10 24 Feb 1998 diskscan(1M)
01-12-2017
