- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Moving boot hard drive from one workstation to ano...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 02:33 AM
08-04-2005 02:33 AM
I installed a B180 w/ HP-UX 10.20 in a disk carrier hooked up to an external SCSI chassis. Since then we lost the external chassis and I had to put the drive inside the B180 case. It won't boot because the H/W address the drive boots from now is different from when it was installed.
Is there any way to fix it so the drive will boot again?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 02:42 AM
08-04-2005 02:42 AM
Re: Moving boot hard drive from one workstation to another
at the ISL prompt type HPUX.
The AUTO string on the boot disk may contain the old drive address. If the above process wors, then you will have to redefine the AUTO string with the mkboo -a command
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 02:47 AM
08-04-2005 02:47 AM
Re: Moving boot hard drive from one workstation to another
Do a search until you see the disk
type:
path pri
for future boots)
bo
and interact with ISL
type: hpux
You can set the boot path from
mkboot -a "hpux" /dev/dsk/
Best regards,
Oz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 03:01 AM
08-04-2005 03:01 AM
Solutionto configure the new HW address you can try this:
Stop the boot process at ISL. Then boot the system in maintenance mode (hpux -lm). Install new device files for your disk (insf -H
Import the VG:
# mkdir /dev/vg##
# mknod /dev/vg##/group c 64 0xXY0000
# vgimport -v -m /tmp/vg##.map vg##
Update boot information:
# lvlnboot -r /dev/
# lvlnboot -b /dev/
# lvlnboot -s /dev/
# lvlnboot -d /dev/
# lvlnboot â v
Check the results:
# vgchange -a y vg##
# vgdisplay -v vg##
Reboot!
HTH!
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 03:28 AM
08-04-2005 03:28 AM
Re: Moving boot hard drive from one workstation to another
its probably just down to the scsi id's of the drive.
the exteranl box probably had a switch on the back to change this and was connected to the drive internally.
now you have the drive out there will be no jumpers on the drive to set the scsi id.
remove the drive from the workstation again and put some jumpers on the drive to set the id to what it was when the install was done.
the default id for the drive should have been 6? can you remember.
also it may still boot if you just interupt the boot at pdc level and search for bootable devices. select the drive and boot this. If this works ok then you can just change the boot path at pdc to amtch the disk so when you turn the workstation on it boots up into hpux
andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 04:30 AM
08-04-2005 04:30 AM
Re: Moving boot hard drive from one workstation to another
also You might want to fix /stand/bootconf , but this shouldn't be too much of an issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 04:33 AM
08-04-2005 04:33 AM
Re: Moving boot hard drive from one workstation to another
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2005 05:48 AM
08-04-2005 05:48 AM
Re: Moving boot hard drive from one workstation to another
If I remeber correct, the B180 uses the same SCSI buses for internal and external drives. There is two buses, one NSE and one WSE. So, all you need to do is to find some jumpers so you can set the the SCSI ID to the same as it was set in the external box.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2005 09:59 AM
08-05-2005 09:59 AM
Re: Moving boot hard drive from one workstation to another
Your procedure worked like a charm. You obviously have done this before.
I only had to change one thing. I had to run 'vgchange -a y' to activate the volume group before running the lvlnboot commands. The first time the system booted up after the procedure it rebooted by itself. After that, it worked like a champ.
Thanks also to all the others who responded.