- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_tape_recovery device failed
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
10-19-2004 01:11 AM
10-19-2004 01:11 AM
I have started trying to do a make_tape_recovery on a RP8400 using an LTO1. I am receiving the error "This is not a character special device" "Check tape device failed". A make_tape_recovery on a DDS tape would use /dev/rmt/0mn, would I still use /dev/rmt/0mn with LTO1 or just use /dev/rmt/0m or is this not causing my problem?
Thanks
Andrew Pollard
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 01:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 01:22 AM
10-19-2004 01:22 AM
Re: make_tape_recovery device failed
Can you tell me LTO is connected with FC or SCSI?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 01:26 AM
10-19-2004 01:26 AM
Re: make_tape_recovery device failed
The LTO is connected using scsi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 01:28 AM
10-19-2004 01:28 AM
Re: make_tape_recovery device failed
insf -e
This will recreate the device drivers, just in case you've accidentally overwritten your tape device driver.
You should also look at the permissions on the device driver ll /dev/rmt/0m or whatever device your script uses.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 01:30 AM
10-19-2004 01:30 AM
Re: make_tape_recovery device failed
Try then to recreate the device files with
insf -e
command
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 01:34 AM
10-19-2004 01:34 AM
Re: make_tape_recovery device failed
Probably your /dev/rmt/0mn is not a character device file. You should get the following output with the file command.
# file /dev/rmt/0mn
/dev/rmt/0mn : character special (xx/y)
If not then it's a normal file. Delete it and recreate the special file by using "insf -e" command as told earlier.
Hope that helps.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2004 03:03 AM
10-19-2004 03:03 AM
Re: make_tape_recovery device failed
After reading all the suggestions and doing more investigation, it seems that "Too many hands in the cookie jar" has caused human error and not device file error.
I do believe that the problem is fixed. Thanks for all the suggestions and help on this problem. 10 points all around!!
Thanks
Andrew