- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_recovery
Operating System - HP-UX
1747997
Members
4621
Online
108756
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО09-12-2000 06:44 AM
тАО09-12-2000 06:44 AM
make_recovery
Heres my setup:
A VME Chasis, a 743 processor card, a Osicom FDDI card, & HP-UX 10.20
I am performing the following commands to create a recovery tape:
ioscan -f -C tape
mksf -v -H [hardware path from above command] -b DDS1 -a
make_recovery -v -A
The recovery tape completes without errors.
I replace the hard drive, perform the installation from tape, and it completes without errors.
The problem is: after recovery, my FDDI card is no longer talking between the system. I check all files after the recovery and they appear to have been recovered correctly, including all the neccessary configuration files for the FDDI card.
If I replace the HD with the original HD I used to make the recovery, my FDDI is fine.
Thanks in advance.
Greg Huber
ghuber@comptek.com
A VME Chasis, a 743 processor card, a Osicom FDDI card, & HP-UX 10.20
I am performing the following commands to create a recovery tape:
ioscan -f -C tape
mksf -v -H [hardware path from above command] -b DDS1 -a
make_recovery -v -A
The recovery tape completes without errors.
I replace the hard drive, perform the installation from tape, and it completes without errors.
The problem is: after recovery, my FDDI card is no longer talking between the system. I check all files after the recovery and they appear to have been recovered correctly, including all the neccessary configuration files for the FDDI card.
If I replace the HD with the original HD I used to make the recovery, my FDDI is fine.
Thanks in advance.
Greg Huber
ghuber@comptek.com
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2000 07:05 AM
тАО09-12-2000 07:05 AM
Re: make_recovery
Try reinstalling the FDDI driver and any associated FDDI patches. Ive seen problems when restoring systems with FDDI or 100Mb lan cards, reinstalling the dirver and patches fixes it.
Im from Palmerston North, New Zealand, but somehow ended up in London...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2000 07:12 AM
тАО09-12-2000 07:12 AM
Re: make_recovery
Did you do a comparison of the ouput from 'lanscan' and 'ioscan -fnC lan' on both systems.
It is possible that the device files may have changed if you have more than one LAN card.
It is possible that the device files may have changed if you have more than one LAN card.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2000 08:02 AM
тАО09-12-2000 08:02 AM
Re: make_recovery
using the latest version of make_recovery?
supposedly the make_recovery boot kernel has a lot of drivers built-in so that it can boot on most hardware (there's 3 or 4 versions of this kernel - depending on the hardware platform V, N, L, other - documented somewhere)
then if the boot kernel sees its a different box, it can regenerate a new kernel, and if it detect other hardware (like FDDI), if the driver software is installed (which should be in the archive) then supposedly it will automatically put into the new kernel and device files created. so it should work.
maybe the boot kernel can't recognize the FDDI hardware, so it doesn't know to build in the driver - is the FDDI stuff HP brand?
if its the same box, then the boot kernel just restores the kernel from archive - and it should work...?
supposedly the make_recovery boot kernel has a lot of drivers built-in so that it can boot on most hardware (there's 3 or 4 versions of this kernel - depending on the hardware platform V, N, L, other - documented somewhere)
then if the boot kernel sees its a different box, it can regenerate a new kernel, and if it detect other hardware (like FDDI), if the driver software is installed (which should be in the archive) then supposedly it will automatically put into the new kernel and device files created. so it should work.
maybe the boot kernel can't recognize the FDDI hardware, so it doesn't know to build in the driver - is the FDDI stuff HP brand?
if its the same box, then the boot kernel just restores the kernel from archive - and it should work...?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP