- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Ignite-UX - make_recovery fails with Illegal c...
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
03-21-2002 04:36 AM
03-21-2002 04:36 AM
I would like to know how to bypass this situation. I can't remove the logical volume neither mount the file system because of environment restrictions.
I have already found a document that explains the reason of this failure, but I can't apply the recommended solution. Kmine: KBRC00008783
Thanks in advance.
Walter
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2002 04:53 AM
03-21-2002 04:53 AM
Re: Ignite-UX - make_recovery fails with Illegal character: "M"
the problem lies within the content of your file:
/var/opt/ignite/recovery/config.recover
please post it so we can have a look , also have a look yourself and see if you can find a control M or anything dubios.
cheers
John.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2002 04:54 AM
03-21-2002 04:54 AM
Re: Ignite-UX - make_recovery fails with Illegal character: "M"
Is it possible to remove the lvol temporarily from the /etc/fstab ?
Then run make_tape_recovery and put it back.
C.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2002 05:05 AM
03-21-2002 05:05 AM
SolutionI'm not an Ignite specialist so forgive me if this is besides the point, but wouldn't this work ?
make_recovery -p
# Edit /var/opt/ignite/recovery/arch.include
# remove the things you don't need
make_recovery -r
Hope this helps,
Tom Geudens
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2002 05:08 AM
03-21-2002 05:08 AM
Re: Ignite-UX - make_recovery fails with Illegal character: "M"
That might help as well. As you mentioned you would have to use make_recovery instead of make_tape_recovery.
C.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2002 04:17 AM
04-07-2002 04:17 AM
Re: Ignite-UX - make_recovery fails with Illegal character: "M"
I have ran into this problem a few times myself. You should be able to comment the unmounted lvol out of the /etc/fstab and then complete your make_tape_recovery. Or you can make a seperate /etc/fstab that you only use when you want to run make_recovery.
1.)cp -p /etc/fstab /etc/fstab.orig
2.)comment out the unmounted lvol's in /etc/fstab
4.)run make_recovery -Av or make_tape_recovery -Av
5.) Once recovery tape has completed, save your revcovery fstab off and move the orignal /etc/fstab back into place:
mv /etc/fstab /etc/fstab.recovery
mv /etc/fstab.orig /etc/fstab
Hope the this helps out.
Best Regards,
Everett