![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| how to change the boot sequence? | wrapster | SUN Solaris | 5 | 02-17-2008 04:10 AM |
| linux 2.4 boot up sequence | Franco | Linux | 7 | 01-30-2008 01:53 PM |
| Wierd boot-up sequence | nitinp82 | UNIX for Dummies Questions & Answers | 1 | 02-01-2007 04:40 PM |
| Boot Sequence | delphine | UNIX for Dummies Questions & Answers | 3 | 01-25-2006 11:08 AM |
| Unix Boot Sequence | sajjan2 | UNIX for Advanced & Expert Users | 6 | 10-09-2002 11:27 AM |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
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 |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|