- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- mt status reports 'nrmt0h: No such device or addre...
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-05-2010 08:09 PM
тАО09-05-2010 08:09 PM
mt status reports 'nrmt0h: No such device or address'
CAM Equipment Device Table (EDT) Information:
Device: RRD47 Bus: 0, Target: 4, Lun: 0, Type: Read-Only Direct Access
Device: DLT2000 15/30 GB Bus: 1, Target: 5, Lun: 0, Type: Sequential Access
From reading /dev/MAKEDEV, I inferred that the command I needed to make a tape device node was either:
./MAKEDEV tms0
or maybe
./MAKEDEV tz0
I tried the first, and set TAPE first to /dev/nrmt0h and later /dev/nrmt0l, but 'mt status' consistently returned 'nrmt0h: No such device or address' (or same for nrmt0l). I rm'ed the device nodes and tried the latter MAKDEV command (tz0) and got the same results when I tried to use mt status on nrmt0h, nrmt0l, nrmt0m, and nrmt0a.
Whats the proper incantation to create a functional tape device node that will allow me to operate the Quantum DLT drive using the mt and dd utilities?
Thank you!
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2010 10:31 PM
тАО09-05-2010 10:31 PM
Re: mt status reports 'nrmt0h: No such device or address'
I have /dev/rmt1a, h l and m -- what differences if any are there between these device nodes?
Thank you!
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2010 06:55 AM
тАО09-06-2010 06:55 AM
Re: mt status reports 'nrmt0h: No such device or address'
Have you tried anything like?:
man mt
Density/compression, rewind, ...?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2010 11:03 AM
тАО09-06-2010 11:03 AM
Re: mt status reports 'nrmt0h: No such device or address'
tz## at scsi1 target 5 lun 0
use the tz## in the MAKEDEV command. I'm coming from modern BSD, where MAKEDEV is no longer used, and devices generally get numbered sequentially from 0, based on their probe order, so the first device being tz13 didn't occur to me.
I'm also unclear whether the scsimgr command actually helped, or whether it was just coincident with something else I did. But knowing the precise device to MAKEDEV has solved my device node issues for now.
Thank you for replying!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2010 01:50 PM
тАО09-06-2010 01:50 PM
Re: mt status reports 'nrmt0h: No such device or address'
And I haven't touched Tru64 pre-V5.0 (where,
I believe, the device naming scheme changed
some), so I know nothing.
> [...] devices generally get numbered
> sequentially from 0, based on their probe
> order, [...]
There's much to be said in favor of a scheme
where the name of a device does not change
when you add another device, I claim. I was
recently annoyed by some GNU/Linux system
where adding a disk left the boot disk
unbootable because all the stuff in its
/etc/fstab was rendered invalid because of
the device name changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2010 06:40 AM
тАО09-15-2010 06:40 AM
Re: mt status reports 'nrmt0h: No such device or address'
In Tru64 V4.0F the device must be adressed according to it's scsi id.
so most likely ./MAKEDEV tz5 (or tz15 as it is on bus-1) creates the device special files so the system can communicate with it.