mtx -- a native linux media changer tool

media changer tool


mtx is a native linux media changer tool, it controls SCSI media changer devices.The mtx command controls single or multi-drive SCSI media changers such as tape changers, autoloaders, tape libraries, or optical media jukeboxes. It can also be used with media changers that use the ’ATTACHED’ API, presuming that they properly report the  MChanger  bit as required by the SCSI T-10 SMC specification.
In this article, same as others, I’ll show you examples of mtx usage, in my case, it’s version 1.3.12

Package info

$rpm -ql mtx-1.3.12-501.sl6.x86_64/usr/sbin/loaderinfo/usr/sbin/mtx/usr/sbin/mtx-driveinfo/usr/sbin/mtx-inventory/usr/sbin/scsieject/usr/sbin/scsitape/usr/sbin/tapeinfo…mtx-driveinfo and mtx-inventory are hacked by me for particular purpose, will tell you more in other articles.

SYNOPSIS

mtx [-f <scsi-generic-device>] [nobarcode] [invert] [noattach] command [ command … ]The list of the commands of mtx:
Inquiry, Inventory, status, load, unload, transfer, Invert, First, Last, Next, Position, Eject
Here are examples for these commands

Inquiry

Inquiry   Report the product type (Medium Changer, Tape Drive, etc.), Vendor ID, Product  ID,  Revision,  and  whether  this  uses  the Attached Changer API (some tape drives use this rather than reporting a Medium Changer on a separate LUN or SCSI address).
# mtx -f /dev/changer3 inquiryProduct Type: Medium ChangerVendor ID: ‘IBM ‘Product ID: ‘03584L32 ‘Revision: ‘B540’Attached Changer API: No

Inventory — not applicable to all libraries

Inventory Makes the robot arm go and check what elements are in the slots. This is needed for a few libraries like the Breece Hill ones that do not automatically check the tape inventory at system startup.

Status

Reports how many drives and storage elements are contained in the device. For each drive, reports whether it has media loaded in it, and if so, from which storage slot the media originated.
For each storage slot, reports whether it is empty  or  full, and  if the media changer has a bar code, MIC reader, or some other way of uniquely identifying media without loading it into a drive, this reports the volume tag and/or alternate volume tag for each piece of media. 
For historical reasons drives  are numbered from 0 and storage slots are numbered from 1.
# mtx -f /dev/changer3 status Storage Changer /dev/changer3:1 Drives, 46 Slots ( 16 Import/Export )Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = A04592 Storage Element 1:Full :VolumeTag=A04590 Storage Element 2:Full :VolumeTag=A04591 Storage Element 3:Empty:VolumeTag= Storage Element 4:Full :VolumeTag=A04593 Storage Element 5:Full :VolumeTag=A04594 Storage Element 6:Full :VolumeTag=A04595 Storage Element 7:Full :VolumeTag=A04596 Storage Element 8:Full :VolumeTag=A04597 Storage Element 9:Full :VolumeTag=A04598 Storage Element 10:Full :VolumeTag=A04599 Storage Element 11:Empty:VolumeTag= Storage Element 12:Empty:VolumeTag= Storage Element 13:Empty:VolumeTag= Storage Element 14:Empty:VolumeTag= Storage Element 15:Empty:VolumeTag= Storage Element 16:Empty:VolumeTag=…

Load

 Load media from slot <slotnum> into drive <drivenum>. Drive 0 is assumed if the drive number is omitted.
load <slotnum> [ <drivenum> ]# mtx -f /dev/changer3 load 3 0Loading media from Storage Element 3 into drive 0…done

Unload

unload [<slotnum>] [ <drivenum> ]Unloads  media from drive <drivenum> into slot <slotnum>. If <drivenum> is omitted, defaults to drive 0 (as do all commands). If <slotnum> is omitted, defaults to the slot that the drive was loaded from.Note that  there’s  currently  no  way  to  say ’unload drive 1’s media to the slot it came from’, other than to explicitly use that slot number as the destination.
# mtx -f /dev/changer3 unload 3 0Unloading drive 0 into Storage Element 3…done

Transfer

[eepos <operation>] transfer <slotnum> <slotnum>Transfers  media  from  one  slot to another, assuming that your mechanism is capable of doing so. Usually used to move media to/from an import/export port. ’eepos’ is used to extend/retract the import/export tray on certain mid-range to high end tape libraries  (if, e.g., the tray was slot 32, you might say say ’eepos 1 transfer 32 32’ to extend the tray).  Valid values for eepos <operation> are 0 (do nothing to the import/export tray), 1, and 2 (what 1 and 2 do varies depending upon the  library,consult your library’s SCSI-level documentation).# mtx -f /dev/changer3 transfer 10 11# mtx -f /dev/changer3 status Storage Changer /dev/changer3:1 Drives, 46 Slots ( 16 Import/Export )Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = A04592 Storage Element 1:Full :VolumeTag=A04590 Storage Element 2:Full :VolumeTag=A04591 Storage Element 3:Empty:VolumeTag= Storage Element 4:Full :VolumeTag=A04593 Storage Element 5:Full :VolumeTag=A04594 Storage Element 6:Full :VolumeTag=A04595 Storage Element 7:Full :VolumeTag=A04596 Storage Element 8:Full :VolumeTag=A04597 Storage Element 9:Full :VolumeTag=A04598 Storage Element 10:Empty:VolumeTag= Storage Element 11:Full :VolumeTag=A04599…

Invert

— I don’t even see use case for this option       [eepos <operation>] [invert] [invert2] exchange <slotnum> <slotnum> [<slotnum>]Move  medium  from  the  first  slot to the second slot, placing the medium currently in the second slot either back into the first slot or into the optional third slot.

First

first [<drivenum>]Loads drive <drivenum> from the first slot in the media changer. Unloads the drive if there is already media in it (note: you may  need to eject the tape using your OS’s tape control commands first). Note that this command may not be what you want on large tape libraries — e.g. on Exabyte 220, the first slot is usually a cleaning tape.
If <drivenum> is omitted, defaults to first drive.
# mtx -f /dev/changer3 firstUnloading drive 0 into Storage Element 3…doneLoading media from Storage Element 1 into drive 0…done

Last

last [<drivenum>]Loads  drive  <drivenum>  from the last slot in the media changer. Unloads the drive if there is already a tape in it.(Note: you may need to eject the tape using your OS’s tape control commands first).
# mtx -f /dev/changer3 lastUnloading drive 0 into Storage Element 1…doneLoading media from Storage Element 30 into drive 0…Source Element Address 1056 is EmptyNote: there is no tape in the last slot in this case

Next

next [<drivenum>]Unloads the drive and loads the next tape in sequence. If the drive was empty, loads the first tape into the drive.# mtx -f /dev/changer3 nextLoading media from Storage Element 1 into drive 0…done

Position

position <slotnum>Positions the robot at a specific slot. Needed by some changers to move to and open the import/export, or mailbox, slot.# mtx -f /dev/changer3 position 10

Eject

eject, eject tape from tape drive, no robot movement.

Other tools in the same package

In addition to mtx tool, there are other tools in mtx package

loaderinfo

Usage: loaderinfo -f <generic-device>
# loaderinfo -f /dev/changer3Product Type: Medium ChangerVendor ID: ‘IBM ‘Product ID: ‘03584L32 ‘Revision: ‘B540’Attached Changer: NoBar Code Reader: NoEAAP: YesNumber of Medium Transport Elements: 2Number of Storage Elements: 30Number of Import/Export Elements: 16Number of Data Transfer Elements: 1Transport Geometry Descriptor Page: YesInvertable: NoDevice Configuration Page: YesStorage: Data Transfer, Import/Export, StorageSCSI Media Changer (rev 2): NoTransfer Medium Transport: ->Data Transfer, ->Import/Export, ->StorageTransfer Storage: ->Data Transfer, ->Import/Export, ->StorageTransfer Import/Export: ->Data Transfer, ->Import/Export, ->StorageTransfer Data Transfer: ->Data Transfer, ->Import/Export, ->StorageExchange Medium Transport: NoneExchange Storage: <>Data Transfer, <>Import/Export, <>StorageExchange Import/Export: <>Data Transfer, <>Import/Export, <>StorageExchange Data Transfer: <>Data Transfer, <>Import/Export, <>Storage

tapeinfo

# tapeinfo /dev/fcnst18Usage: tapeinfo -f <generic-device>[root@t1-ppshead ~]# tapeinfo -f /dev/fcnst18Product Type: Tape DriveVendor ID: ‘IBM ‘Product ID: ‘ULT3580-TD5 ‘Revision: ‘BBNE’Attached Changer API: NoSerialNumber: ‘00078A2295’MinBlock: 1MaxBlock: 8388608SCSI ID: 1SCSI LUN: 0Ready: yesBufferedMode: yesMedium Type: 0x58Density Code: 0x58BlockSize: 0DataCompEnabled: noDataCompCapable: yesDataDeCompEnabled: yesCompType: 0x1DeCompType: 0x1BOP: yesBlock Position: 0Partition 0 Remaining Kbytes: -1Partition 0 Size in Kbytes: -1ActivePartition: 0EarlyWarningSize: 0NumPartitions: 0MaxPartitions: 1

scsieject — unlike mtx, this is to control SCSI tape devices, as well as CD/DVD

The  scsieject  command  controls  SCSI  devices  in  a  platform-independent  manner.  As long as ‘mtx’ works on the platform, so does ‘scsieject’.

Usage:

scsieject [-f <scsi-generic-device>] commands

COMMANDS

load Load the medium into the drive. When this command is issued to a CD/DVD drive and the tray is extended the tray will be retracted if the drive is capable of it.unload Unload the medium from the drive (also known as eject). When this command is issued to a CD/DVD drive or a tape drive the media will be ejected if the device supports it.start Start the device. Some devices require a start command after a media changer has loaded new media into the device.stop Stop the device. Some devices require a stop command prior to unloading the medium from the device when using a media changer.lock Lock the device. Locks the device so that the medium cannot be removed manually.unlock Unlock the device. Unlocks the device so that the medium can be removed manually.

scsitape

I don’t use it, I use mt instead, which control magnetic tape drive operation, not generic-scsi-device.
# scsitape -hUsage: scsitape -f <generic-device> <command> where <command> is: setblk <n> | fsf <n> | bsf <n> | eod | rewind | eject | mark <n> | seek <n> | read [<blksize> [<numblocks]] | write [<blocksize>]

MeasureMeasure

Read more

How to migrate Raspberry Pi 5 OS from micro SD to NVME m.2 SSD

首先我買了Raspberry Pi CM5後來買了Raspberry Pi CM5 I/O board來當個人電腦使用,系統是安裝在256GB SD卡上運行的很好。用久了在開啟較肥的程式像Web Browser或LiberOffice會有慢半拍的反應,而有了升級NVME m.2 SSD念頭。 因為Raspberry Pi 5支援的最快PCIe gen3 x 4就不去考慮快的Gen4 or Gen5 m.2 SSD。找了ADATA出的 LEGEND 710入門級的產品,會利用HMB(Host Memory Buffer)來加速I/O速度,因為是Raspberry Pi OS kernel會認不得而無法正常使用 事先在SD卡的/boot/firmware/cmdline.txt 加入 kernel command line參數如下,然後重開機m.

By Phillips Hsieh

How to document Home Lab and Network

運維機房和跨域的網路,會遇到各式需求與問題,用對工具才能分析問題,個人覺得最重要的是使用能處理問題的工具。 推薦目前想學和正在使用的平台與軟體,協助將公司/家用機房文件化 佈告欄任務管理 Focalboard 白板可管理任務指派 網路架構文件編寫 netbox 精細管理網路設備與連接線路 IP 資源管理 phpipam 專注網路IP分配 邏輯塊文件編寫 draw.io 視覺化概念圖 機房設備管理 ITDB 管理設備生命週期與使用者

By Phillips Hsieh

如何在Raspberry Pi4上安裝Proxmox for ARM64

第一步 準備好Raspberry Pi 4 / CM4 4GB RAM,這裡要留意CM4如果是買有內建eMMC storage會限制不能使用SD卡開機而限制本地空間容量,如果沒有NAS外接空間或使用USB開機的話,建議買CM4 Lite插上大容量SD卡 第二步 去Armbian官網下載最小化Debian bookworm image https://www.armbian.com/rpi4b/ Armbian 25.2.2 Bookworm Minimal / IOT 然後寫入SD/USB開機碟,寫入方法參考官方文件 https://github.com/raspberrypi/usbboot/blob/master/Readme.md Note: 官方提供的預先設定系統方法,可以在Armbian初次啟動自動化完成系統設定。連結在此 https://docs.armbian.com/User-Guide_Autoconfig/

By Phillips Hsieh

世界越快心越慢

在晚飯後的休息時間,我特別享受在客廳瀏灠youtube上各樣各式創作者的影音作品。很大不同於傳統媒體,節目多是針對大多數族群喜好挑選的,在youtube上我會依心情看無腦的動畫、一些旅拍記錄、新聞時事談論。 尤其在看了大量的Youtube的分享後,我真的感受到會限制我的是我的無知,特別是那些我想都沒想過的實際應用,在學習後大大幫助到我的生活和工作層面。 休息在家時,我喜歡想一些沒做過的菜,動手去設計生活和工作上的解決方案,自己是真的很難閒著沒事做。 如創作文章,陪養新的習慣都能感覺到成長的喜悅,是不同於吃喝玩樂的快樂的。 創作不去限制固定的形式,文字是創作、影像聲音也是創作,記錄生活也是創作,我想留下的就是創造—》實現—》回憶,這樣子的循環過程,在留下的足跡面看到自己一路上的成長、失敗、絕望、重新再來。 雖然大部份的時候去做這些創作也不明白有什麼特別的意義,但不去做也不會留下什麼,所以呀不如反事都去試試看,也許能有不一樣的水花也許有意想不到的結果,投資自己永遠不會是失敗的決定,不是嗎?先問問自己再開始計畫下一步,未來沒人說得準。 像最近看youtube仍大一群人在為DOS開

By Phillips Hsieh