StoreEver Tape Storage
1855652 Members
8142 Online
104113 Solutions
New Discussion

Betreff: Query: Mount tape from cli on windows

 
SOLVED
Go to solution
sozarch
Occasional Advisor

Mount tape from cli on windows

How can I mount a tape with ltfs.exe on the cli on windows.

I tried ltfs.exe -o dev=\\.\Tape0 X: but this not working.

The gui app "HPE LTFS Configuration" is working

7 REPLIES 7
Azr_geek
Esteemed Contributor

Re: Mount tape from cli on windows

Hello @sozarch,

To mount a tape using LTFS from the Windows command line, you need to use the correct command and make sure you’re running it as an administrator. The command should look like this:

ltfs.exe X: -o devname=\.\Tape0

Here, "X:" is the drive letter you want to use for the tape, and "\.\Tape0" is usually the name for your tape drive. You might need to change the number if you have more than one tape drive. Make sure you’re not using a drive letter that’s already in use. Also, double-check that no other program is using the tape before you try to mount it. If you still have trouble, try mounting the tape with the GUI tool and check which device name it uses, or look in the LTFS logs for more information.

Regards,
Azr_geek

support_s
System Recommended

Query: Mount tape from cli on windows

Hello,

 

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

 

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".


Accept or Kudo

sozarch
Occasional Advisor

Betreff: Query: Mount tape from cli on windows

I tried your command in an admin cmd. I get the following output:

6e7c80 LTFS14000I LTFS starting, HPE StoreOpen Software version 3.5.0, log level 2
6e7c80 LTFS14058I LTFS Format Specification version 2.4.0
6e7c80 LTFS14104I Launched by "ltfs.exe X: -d -o devname=\.\Type0"
6e7c80 LTFS14105I This binary is built for Windows
6e7c80 LTFS14106I GCC version is 4.6.3
6e7c80 LTFS17087I Kernel version: Windows
6e7c80 LTFS14063I Sync type is "time", Sync time is 300 sec
6e7c80 LTFS17085I Plugin: Loading "ltotape_win" driver
6e7c80 LTFS17085I Plugin: Loading "unified" iosched
6e7c80 LTFS14111I Initial setup completed successfully
6e7c80 LTFS14112I Invoke 'mount' command to check the result of final setup
6e7c80 LTFS14113I Specified mount point is listed if succeeded

But there is no mounted drive.

> You might need to change the number if you have more than one tape drive.

I only have on drive

> Make sure you’re not using a drive letter that’s already in use.

X is not used. I also tried other letters.

> Also, double-check that no other program is using the tape before you try to mount it.

Done

> If you still have trouble, try mounting the tape with the GUI tool and check which device name it uses

Where can I see it? I see only a device that starts with C015...

> , or look in the LTFS logs for more information.

Where can I find it?

 

 

Azr_geek
Esteemed Contributor
Solution

Betreff: Query: Mount tape from cli on windows

@sozarch,

Use the exact device name that the HPE GUI uses instead of guessing \\.\Tape0. Mount a tape from the GUI, then open the LTFS log (check C:\Program Files\HPE\HPE LTFS\var\log\ltfs.log or the GUI’s log panel) and copy the device string it shows (it may look like \\.\C015_... or \\.\Tape0). Close the GUI so it doesn’t hold the drive, open an Administrator command prompt, and run ltfs like this: ltfs.exe X: -o devname=\\.\C015_... (replace X: with a free drive letter and the device string from the log). If you prefer, you can also find the device name in Device Manager → Tape Drives → Properties → Details → Physical Device Object Name, then use that name in the same ltfs command.

sozarch
Occasional Advisor

Betreff: Query: Mount tape from cli on windows


Use the exact device name that the HPE GUI uses instead of guessing \\.\Tape0.

The LTFS configurator is saying C01509D3AF

So I tried: ltfs.exe X: -o devname=\\.\C01509D3AF -d

2437c90 LTFS14000I LTFS starting, HPE StoreOpen Software version 3.5.0, log level 2
2437c90 LTFS14058I LTFS Format Specification version 2.4.0
2437c90 LTFS14104I Launched by "ltfs.exe X: -o devname=\\.\C01509D3AF -d"
2437c90 LTFS14105I This binary is built for Windows
2437c90 LTFS14106I GCC version is 4.6.3
2437c90 LTFS17087I Kernel version: Windows
2437c90 LTFS14063I Sync type is "time", Sync time is 300 sec
2437c90 LTFS17085I Plugin: Loading "ltotape_win" driver
2437c90 LTFS17085I Plugin: Loading "unified" iosched
2437c90 LTFS14111I Initial setup completed successfully
2437c90 LTFS14112I Invoke 'mount' command to check the result of final setup
2437c90 LTFS14113I Specified mount point is listed if succeeded

 

Unfortunately no drive appeared.

If you prefer, you can also find the device name in Device Manager → Tape Drives → Properties → Details → Physical Device Object Name, then use that name in the same ltfs command.

This shows \Device\0000003c

So I tried:

ltfs.exe X: -o devname=\\.\Device\0000003c -d and ltfs.exe X: -o devname=\\.\0000003c -d

Same output like above. Again no drive.

In all tries I used an admin console and the gui was not open.The drive X is availble.

Mount a tape from the GUI, then open the LTFS log (check C:\Program Files\HPE\HPE LTFS\var\log\ltfs.log

I did that. There is no folder: C:\Program Files\HPE\HPE LTFS. There is only a folder C:\Program Files\HPE\LTFS. But in this folder there is no var folder.

 

sozarch
Occasional Advisor

Betreff: Query: Mount tape from cli on windows

How should I proceed?

sozarch
Occasional Advisor

Betreff: Query: Mount tape from cli on windows

logging out a successful mount via UI was the right lead. Thx! For some reason, the log is being written to C:\Windows\System32, despite the path given in the UI …

As the log states, in our case it's simply "TAPE0" without any additionaly path info:

"C:\Program Files\HPE\LTFS\ltfs.exe" F: -o devname=TAPE0 -d -o trace

 

The other thing that might have us tripped up is that one needs to wait for at least as long as with the UI until the init sequence is being shown, and eventually the "Ready to receive file system requests".

Last thing to solve is that the mapping doesn't appear in the Window UI, but that is likely due to the elevated CLI session, as i can DIR the drive via console.