01-25-2006
Script in boot sequence
Hi ,
I have some problems with my library when the sytem boot :
When HPUX is booting, HPUX and STAPE claim the drive initially. HPUX assigns an instance
number. The instance number is tied to the hardware path. Near the end of the boot, the ATDD driver claims the drive from
STAPE based upon the Inquiry ID (either ULTRIUM-TDx or ULT3580.TDx, where x=1, 2 or 3 depending on the drive
generation.) When ATDD claims the drive, it generates the special file based on the instance number. This is the standard
way devices are handled with HPUX. If a drive is moved, host is rebooted or for other undefined reasons HPUX will assign
a different instance number, which will generate a new special file when ATDD claims the drive.
For some reason that is not understood, HPUX will sometimes claim a drive, or number of drives, with a different instance
number, even if the hardware path does not change. When this happens the new instance numbers do not match up with
the existing special files, and the customer has a problem. Although, it is not understood why this happens, but this is not
an uncommon problem for a HPUX customer to have.
====>
Answer from IBM :
The following commands can be run manually or scripted to run during bootup
So as an example, if they want to assign the instance number for the following two drives.
tape 90 1/0/0/0.97.19.255.2.6.0 atdd CLAIMED DEVICE IBM 03590E11
tape 35 1/0/0/0.97.20.255.2.7.0 atdd CLAIMED DEVICE IBM 03592J1A
You do this for each drive: STEP 1
rmsf -H 1/0/0/0.97.19.255.2.6.0
rmsf -H 1/0/0/0.97.20.255.2.7.0
ioscan -M atdd -H 1/0/0/0.97.19.255.2.6.0 -I 1 <=this change it to instance number 1
ioscan -M atdd -H 1/0/0/0.97.20.255.2.7.0 -I 2 <=this change it to instance number 2
Then you do this: STEP 2
/opt/atdd/bin/atdd_claim
These steps could be automated by creating a script and putting the new script in the boot up sequence."
Question :
====> Can you confirm me that i have to create my script with the differents drives .I have to create a sh file with the rmsf commands of my differents hardware path and ioscan with the new instance number.
It's only that?
Thanks
DElphine
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all Unix fans.
What files are involved in the Unix boot sequence,
i guess there is alot of them but some must be the main files?
For example the service SENDMAIL starts on our Unix machine
where should i edit so that it will not start at BOOT.
initd.conf? rc2.d?
I hope you... (6 Replies)
Discussion started by: sajjan2
6 Replies
2. UNIX for Dummies Questions & Answers
Hi everybody,
I have to create a script and put it in the boot up sequence .
Can you give me the path where i can put it?
Sorry it's my first script.
DElphine (3 Replies)
Discussion started by: delphine
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have two machines, one is a E3500 and the other one is a V490;
I face a strange issue with both of them. The boot up sequence gives the output of the devalias command. Has anybody faced this?? Please do let me know what needs to be done o resolve this.
Regards,
NP (1 Reply)
Discussion started by: nitinp82
1 Replies
4. Linux
I am running linux red hat and I need to know the command to view the boot up process.... (that is the driver initialization, drive mount, etc).... Does anyone know this command? (7 Replies)
Discussion started by: Franco
7 Replies
5. Solaris
Hi all,
I have solaris and xp installed...
Usually solaris occupies the first boot slot.
So i wanted to know if it is possible to change the boot sequence to xp first and then solaris? (5 Replies)
Discussion started by: wrapster
5 Replies
6. Shell Programming and Scripting
Hello,
I need Unix script for Checking sequence and get output in a file for missing sequences information.
We are moving archive log to a server for DR .if any files miss from sequence DR will fails. so we need script to monitor sequence of files which are FTP from the Production servers .... (2 Replies)
Discussion started by: Rata_raj
2 Replies
7. Shell Programming and Scripting
Hi,
My requirement is i need to touch a sequence of files like
touch a
touch b
touch c
now i need the script in a way that checks if all files are touched or not.
if any file say b is not touched then i should get this notification.
Please suggest as i am new to unix (2 Replies)
Discussion started by: sussane
2 Replies
8. Filesystems, Disks and Memory
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
" .....
EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have written this script below to run a mathematica notebook, and then I want to launch another one when the first one finishes doing what it must. The notebook includes a command which will exit the program math. If I do it like below the two math processes begin at the same time, and... (3 Replies)
Discussion started by: amen_corner
3 Replies
10. Shell Programming and Scripting
Hi all,
I have a file like this
ID 3BP5L_HUMAN Reviewed; 393 AA.
AC Q7L8J4; Q96FI5; Q9BQH8; Q9C0E3;
DT 05-FEB-2008, integrated into UniProtKB/Swiss-Prot.
DT 05-JUL-2004, sequence version 1.
DT 05-SEP-2012, entry version 71.
FT COILED 59 140 ... (1 Reply)
Discussion started by: manigrover
1 Replies
LEARN ABOUT OPENSOLARIS
path_to_inst
path_to_inst(4) File Formats path_to_inst(4)
NAME
path_to_inst - device instance number file
SYNOPSIS
/etc/path_to_inst
DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers.
The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible
devices that it may drive is referred to by a given special file.
In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by add_drv(1M) and devfsadm(1M).
Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it.
The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However,
any changes made in this file will be lost if add_drv(1M) or devfsadm(1M) is run before the system is rebooted.
Each instance entry is a single line of the form:
"physical name" instance number "driver binding name"
where
physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes.
instance number is a decimal or hexadecimal number.
driver binding name is the name used to determine the driver for the device. This name may be a driver alias or a driver name. The
driver binding name must be enclosed in double quotes.
EXAMPLES
Example 1 Sample path_to_inst Entries
Here are some sample path_to_inst entries:
"/iommu@f,e0000000" 0 "iommu"
"/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma"
"/obio/serial@0,100000" 0 "zs"
"/SUNW,sx@f,80000000" 0 "SUNW,sx"
FILES
/etc/path_to_inst Mapping of physical device names to instance numbers.
SEE ALSO
add_drv(1M), boot(1M), devfsadm(1M), mknod(1M)
WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap
device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers
than they did before, and special files created via mknod(1M) may refer to different devices than expected.
For the same reasons, changes should not be made to this file without careful consideration.
NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future release.
The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API.
SunOS 5.11 18 May 2007 path_to_inst(4)