• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Quantum i6000 cannot open path


ADSM.ORG Senior Member
Our i2k was just upgraded to an i6k, and after doing so, I cannot bring up paths to the library.

ANR8840E Unable to open device /dev/tsmscsi/lb0 with error number 255 and PVRRC 2813.
ANR2032E DEFINE PATH: Command failed - internal server error detected.
ANR9999D Thread<150> issued message 2032 from:
ANR9999D Thread<150> 0x00000000de7a0a outTextf
ANR9999D Thread<150> 0x000000009ed95d PvrTranslateResult
ANR9999D Thread<150> 0x000000009d1bb4 pvrUpdateLibrary
ANR9999D Thread<150> 0x00000000987526 naDefinePath
ANR9999D Thread<150> 0x000000005905db AdmDefinePath
ANR9999D Thread<150> 0x000000004eb91e AdmCommandLocal
ANR9999D Thread<150> 0x000000004ecb6e admCommand
ANR9999D Thread<150> 0x00000000cb0aea SmAdminCommandThread
ANR9999D Thread<150> 0x00000000e85b2a StartThread
ANR9999D Thread<150> 0x00003a5a4064a7 *UNKNOWN*
ANR9999D Thread<150> 0x00003a5a0d3c2d *UNKNOWN*
ANS8001I Return code 15

OS RHEL 5.6 64bit
TSM was 6.3.3 which I updated, including the tsmscsi drivers, to 6.3.6. Still out of support, but - to go to 7.1 will require an OS update, and 8.1 OS and memory, so I started by bringing it up as far as I could.
The error 15 translates to "block device required", which makes no sense when connecting to a character device. IBM's got nothing for a failure involving that particular return code, nor that PVRRC. Quoting the whole error brings three irrelevant google results. The raw devices belong to the instance , and the tsmscsi directory is world-readble/scannable.

This may be as simple as the i6k was never supported by tsm 6, but I'm hoping someone else has seen this before and has a workaround.


ADSM.ORG Moderator
do you even need the tsmscsi driver? No experience with Quantum libraries (concurrently with TSM/ISP) - but our Overland libraries work with native "sg" driver.
To have path persistency I have created an udev rule so my libraries and drives always create /dev/driveX or /dev/libraryY device (which is always a link to /dev/sgZ) - where X and Y stay the same and Z is changing - but the udev takes care of the links.
Another idea is to use "product emulation" - as far as I know you can change it on the partition level with Quantum libraries - i6000 should be able to emulate i500 at least.
Hope it helps

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 9 16.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 32 58.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 16.4%
  • Other (please comement)

    Votes: 5 9.1%

Forum statistics

Latest member