- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Is this an ignite bug?
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
Discussions
Discussions
Forums
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
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
тАО09-17-2002 12:54 PM
тАО09-17-2002 12:54 PM
Is this an ignite bug?
NOTE: /opt/ignite/bin/make_recovery(103): The make_recovery command will be replaced by
make_tape_recovery. Both commands are supported in this
release (Ignite-UX Revision 3.2). Please read the man page
make_tape_recovery(1M) for usage of the new command. In a
future release, make_recovery will be replaced by a script
that calls make_tape_recovery.
*** Previewing only ***
make_recovery(284): Writing to the tape failed. Please check the existence of the tape, or the tape is write protected, or the tape is bad.
make_recovery(210): Encountered a fatal error.
make_recovery(212): Please fix errors and re-try.
Cleanup
# ioscan -funC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 8/12/5.1.0 stape CLAIMED DEVICE HP C1533A
/dev/rmt/0m /dev/rmt/c1t1d0BEST
/dev/rmt/0mb /dev/rmt/c1t1d0BESTb
/dev/rmt/0mn /dev/rmt/c1t1d0BESTn
/dev/rmt/0mnb /dev/rmt/c1t1d0BESTnb
#
Tape drive can be accessed on SAM to do backup.
HPUX 10.20
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2002 12:56 PM
тАО09-17-2002 12:56 PM
Re: Is this an ignite bug?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2002 12:58 PM
тАО09-17-2002 12:58 PM
Re: Is this an ignite bug?
Ted
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2002 12:59 PM
тАО09-17-2002 12:59 PM
Re: Is this an ignite bug?
Use the "make_tape_recovery" command with the non-rewinding device.
Thanks.
Prashant.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2002 01:05 PM
тАО09-17-2002 01:05 PM
Re: Is this an ignite bug?
You should use the newer version, make_tape_recovery. The device file should have been /dev/rmt/0mn (you missed an n at the end.). You do not need to mention the device file unless you want to specify one like /dev/rmt/1mn.
Hai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2002 01:11 PM
тАО09-17-2002 01:11 PM
Re: Is this an ignite bug?
Anyway, the default tape drive is /dev/rmt/0m.
make_tape_recovery was called by make_recovery.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2002 03:41 PM
тАО09-17-2002 03:41 PM
Re: Is this an ignite bug?
George,
Install the newest version for 10.20: A.3.7.95
http://software.hp.com/products/IUX/download.html
Plus, use the custom patch manager to make sure you have the latest ignite related patches.
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2002 12:31 PM
тАО09-18-2002 12:31 PM
Re: Is this an ignite bug?
Jerry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2002 12:38 PM
тАО09-18-2002 12:38 PM
Re: Is this an ignite bug?
IgniteUX require(d/s) a dds1 driver as well the no rewind driver to make a bootable tape.
To configure the tape, use SAM.
I know I made a booboo 1 time, and had a system blow out only to find out it's image was put on a DDS2 tape. I now keep data on a cluster and if clients blow up I use the network install feature of Ignite as it's just as fast and easy to update.
Regards,
Shannon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2002 01:19 PM
тАО09-18-2002 01:19 PM
Re: Is this an ignite bug?
I suggest you be sure you have the latest version of Ignite and use make_tape_recovery instead of make_recovery.
Earlier versions of make_recovery allowed you to specify a rewind device name for the tape drive even though documentation said to use the no-rewind device. I'm not sure of the reliablity of a make_recovery tape made using the rewind device. I have, in the past, successfully used them to rebuild a system however, I almost always rewind tapes before unloading and after loading them.
The current version of make_tape_recovery will error out if you specify a rewind device. I don't remember if earlier versions of make_tape_recovery did so or not.
Considering your error: It appears that make_recovery requires a tape be available even for preview mode (note that make_tape_recovery does not require the tape for preview). Was a tape loaded? Was it write-protected? Is it possible the tape was bad?
Just another reason to use make_tape_recovery.
Darrell