Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Stale PPs in AIX, failed disks.. how to replace?
Operating Systems AIX Stale PPs in AIX, failed disks.. how to replace? Post 302926079 by bakunin on Friday 21st of November 2014 02:27:31 AM
Old 11-21-2014
Quote:
Originally Posted by c3rb3rus
In turn, if I now run "bootlist -m normal -o" I get..

Code:
hdisk10 blv=hd5 pathid=0
hdisk14 pathid=0

Why is it showing there? I am concerned if a reboot happens I may not be able to boot.. how can I remove it and assign hdisk20 which is the replacement for hdisk14 in rootvg... or do I need to do anything further at this point?
There are two commands you need to know: "bosboot" and "bootlist".

With "bootlist" you can set (or display) the order (in NVRAM) in which devices are used to boot from. There are basically 2 lists of such boot devices, "normal" and "service". There is a "key position" that determines which boot list is getting used. Back then, in the times of physical machines, this was really a lock with a key and the key could be in one of 3 possible positions, "normal", "service" (sometimes named "maint") and "lock". Today this is only a virtual construct, but the terminology stuck.

With "bosboot" you bring a boot image to boot from onto a device. This copies the code that is executed during the boot onto the device you designated as boot device with "bootlist".

I suggest you read carefully the man pages of both commands, then read them again. You can render the system unusable with these commands, so spend some time and effort to really, firmly understand what they are doing. Only then use them to alter the boot list. (You will need both of them - proceed only if you understand why.)

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disks on AIX

Hello I've been working on AIX 5.3 ML3 on IBM pSeries520. That server has 6 HDD drives in 3 volume groups (1+mirror in each group). I must check which phisical disk is which disk in the system. For ex. I want to know that disk in 4th slot in the machine is marked as hdisk5 on AIX. Does anybody... (2 Replies)
Discussion started by: piooooter
2 Replies

2. AIX

Replace a Failed Root Disk in AIX

My root disk is failed and how to replace the root disk in AIX. Can u give a detailed explanation in step wise. Pls give the answer taking different scenarios. Regards Praveen (1 Reply)
Discussion started by: chinnu_mulakala
1 Replies

3. AIX

system disks on aix 5.3

hello i'm running on P570 box aix 5.3 8 cpus 24G ram there are 1850 users loged in to this box the problem is that the two sysytem disks busy all the time hdisk0 100% busy hdisk1 100% busy some one have an idea what writing to this disks? thanks ariec (9 Replies)
Discussion started by: ariec
9 Replies

4. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

5. AIX

Configuring new disks on AIX cluster

We run two p5 nodes running AIX 5L in a cluster mode (HACMP), both the nodes share external disk arrays. Only the primary node can access the shared disks at a given point of time. We are in the process of adding two new disks to the disk arrays so as to make them available to the existing... (3 Replies)
Discussion started by: dnicky
3 Replies

6. Solaris

Command to find the failed disks in SVM and VxVM

How to find & replace bad disks in solaris & VXVM?plz explain step by step? (2 Replies)
Discussion started by: xtreams
2 Replies

7. AIX

Issue with increasing size of SAN disks on AIX

HI, I have had an issue last night while trying to extend a filesystsem . chvg -g <vg> command cameback with an error 0516-1790 chvg: Failed bootinfo -s hdisk9. Ensure the physical volume is available and try again. 0516-732 chvg: Unable to change volume group u01vg. the VG has 1... (1 Reply)
Discussion started by: xmen01
1 Replies

8. AIX

How to reclaim hard disks and IP's in AIX?

Hello I recently received a request to reclaim hard disks and IP addresses within an AIX system(s). THe file systems are no longer in use and the client has indicated that it is OK to remove them and reclaim the disks and release the IP's. Now, since the file systems belong to a Volume group I... (8 Replies)
Discussion started by: Joseph Sabo
8 Replies

9. AIX

AIX - stale partition

Hi everybody, I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirror. After problem with SAN pathing of our one Datacenter, I have LV at stale state. # lsvg cpsdata2vg VOLUME GROUP: cpsdata2vg VG IDENTIFIER: 00fb518c00004c0000000169445f4c2c VG STATE: ... (6 Replies)
Discussion started by: Necronomic
6 Replies

10. UNIX for Beginners Questions & Answers

DISKs are gone after shutting down and replace an FC card

Hi there, I had issue with one of MY FC cards on T4-2 servers so system team replace it and start the machine but when launch FORMAT command so I don't see my shared disks coming from storage controller. i have checked at the Fabric switch so WWN numbers are visible and zones are ok and after... (1 Reply)
Discussion started by: janakors
1 Replies

LEARN ABOUT CENTOS

systemd-readahead-collect.service

SYSTEMD-READAHEAD-REPLAY.SERVICE(8)			 systemd-readahead-replay.service		       SYSTEMD-READAHEAD-REPLAY.SERVICE(8)

NAME

       systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd-
       readahead - Disk read ahead logic

SYNOPSIS

       systemd-readahead-replay.service

       systemd-readahead-collect.service

       systemd-readahead-done.service

       systemd-readahead-done.timer

       /usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE]

DESCRIPTION

       systemd-readahead-collect.service is a service that collects disk usage patterns at boot time.  systemd-readahead-replay.service is a
       service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended
       to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process.

       systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data
       collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead.

       Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from
       the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot
       be stored, it might be a good idea to disable systemd-readahead-collect.service.

       On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location
       on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it,
       systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times.

OPTIONS

       systemd-readahead understands the following options:

       -h, --help
	   Prints a short help text and exits.

       --max-files=
	   Maximum number of files to read ahead. Only valid for thes collect command.

       --file-size-max=
	   Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands.

       --timeout=
	   Maximum time in microseconds to spend collecting data. Only valid for the collect command.

COMMANDS

       The following commands are understood by systemd-readahead:

       collect [DIRECTORY]
	   Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the
	   read-ahead data.

       replay [DIRECTORY]
	   Perform read-ahead on the specified directory tree.

       analyze [FILE]
	   Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read
	   ahead by the replay command.

SEE ALSO

       systemd(1)

systemd 208												       SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
All times are GMT -4. The time now is 01:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy