Troubleshooting Guide

QStar HSM Archive Solutions

Steps and Best Practices for

QStar HSM Advanced Debugging
 Copyright information
© 2012 Agfa HealthCare N.V., Septestraat 27, B-2640, Mortsel, Belgium. All rights reserved. No
parts of this document may be reproduced, copied, translated, adapted or transmitted in any form
or by any means without prior written permission of Agfa HealthCare N.V.

Trademark credits
Agfa and the Agfa rhombus are trademarks or registered trademarks of Agfa-Gevaert N.V., Belgium
or its affiliates. IMPAX, Connectivity Manager, Audit Manager, WEB1000, IDCV XERO, TalkStation,
Heartlab, and HeartStation are trademarks or registered trademarks of Agfa HealthCare N.V. or its
affiliates. All other trademarks are held by their respective owners and are used in an editorial fashion
with no intention of infringement.

Documentation warranty statement

Characteristics of the products described in this publication can be changed at any time without
notice.
The information contained in this document is subject to change without notice. Agfa HealthCare
N.V. and its affiliates make no warranties or representations, express, implied or statutory, with
regard to this material, including, but not limited to, the implied warranties of merchantability and
fitness for a particular purpose.
Agfa HealthCare N.V. and its affiliates shall under no circumstances be liable for any damage arising
from the use or inability to use any information, apparatus, method or process described in this
document. Agfa HealthCare N.V. and its affiliates shall not be liable for errors contained herein or
for incidental or consequential damage in connection with the furnishing, performance, or use of
this manual.
2012 - 2 - 6

Manufacturer’s responsibility
The manufacturer, installer, or importer will be responsible for the safety, reliability, and performance
of the equipment only if:
• Installation, modifications, adjustments, changes, or repairs are performed by suitably qualified
service personnel.

• The electrical installation of the site in which the equipment is used is according to an applicable
safety standard (UL, CSA, or IEC/CDE).

• The equipment is used according to the instructions provided in the operation manuals.

Troubleshooting Guide—QStar HSM Archive Solutions 2

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Giving feedback on the documentation
(Topic number: 122201)

Thank you for taking the time to provide feedback. Your comments will be forwarded to the group
responsible for this product’s documentation.
If you have a request for changes in the product, please contact your product sales representative or
the product’s technical support channel.

To give feedback on the documentation

1. In an email subject line or body, list which product, version, and publication you are
commenting on.
For example, “IMPAX 6.4 SU01 Client Knowledge Base: Extended”. (You can find this
information in the footer of the publications.)
2. Describe the incorrect, unclear, or insufficient information. Or, if you found any sections
especially helpful, let us know.
3. Provide topic titles and topic numbers where applicable.
Including your personal contact details is optional.
4. Send the email to doc_feedback@agfa.com.

Troubleshooting Guide—QStar HSM Archive Solutions 3

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Contents

1 Getting started 6
Requirements for troubleshooting QStar HSM.........................................................................6
Syslog and SCSI log files.........................................................................................................6
Troubleshooting strategies for QStar HSM..............................................................................7
Opening a ticket with QStar technical support.........................................................................7

2 Troubleshooting QStar HSM configuration issues 9

How to troubleshoot configuration issues.................................................................................9
Troubleshooting: Volume not mounted....................................................................................9
Troubleshooting: Current writing media offline (manually exported)......................................10
Troubleshooting: Device not configured or claimed...............................................................11
Troubleshooting: Lack of available (new, erased, or blank) media........................................13
Troubleshooting: Media not added to the set.........................................................................14
Troubleshooting: Overlap between different operations on the library (concurrence between
archive/retrieve/hot sync).......................................................................................................15
Troubleshooting: Cache size problems..................................................................................17
Troubleshooting: Services stop or unmount during rollover or write/read from volume.........18

3 Configuring QStar HSM to improve performance 20

SMB timeout (Windows).........................................................................................................20
Improving read performance for tape using full file mode......................................................21
Maximum transfer size...........................................................................................................22
CIFS sharing not available on Windows.................................................................................23
Troubleshooting: Configuring libraries with an adapter SCSI transfer rate less than 129 KB.23
Setting memory use priority to programs (Windows).............................................................24

4 Troubleshooting QStar HSM technical issues 25

How to troubleshoot technical issues.....................................................................................25
Troubleshooting: Recorded entity not found..........................................................................26
Troubleshooting: Unit CRC error............................................................................................27
Troubleshooting: MAM not accessible...................................................................................28
Troubleshooting: Media load or eject failure..........................................................................29
Troubleshooting: Hardware error—Internal target failure (non-responsive device)...............30
Troubleshooting: Aborted command (data phase error)........................................................31

Troubleshooting Guide—QStar HSM Archive Solutions 4

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Blank check (overwrite attempted).............................................................33
Troubleshooting: Bad drive configuration file.........................................................................34
Troubleshooting: Resource temporarily unavailable..............................................................36
Troubleshooting: Bus Device Reset occurs...........................................................................37
Troubleshooting: Hardware error—Internal target failure (target unavailable).......................38
Troubleshooting: Request cannot be performed because of I/O device error or SCSI drive
error........................................................................................................................................39

Appendix A: Upgrading QStar HSM 41

Upgrading QStar HSM 4.2.x to 4.3.x or 4.4.x (Windows).......................................................41
Upgrading QStar HSM 4.2.x to 4.3.x or 4.4.x (Solaris)..........................................................42
Upgrading QStar HSM 4.3.x or 4.4.x to 5.0.x (Windows).......................................................43
Upgrading QStar HSM 4.3.x or 4.4.x to 5.0.x (Solaris)..........................................................44
Upgrading QStar HSM 5.0.x to 5.0.y or 5.1.x (Windows).......................................................46
Upgrading QStar HSM 5.0.x to 5.0.y or 5.1.x (Solaris)..........................................................46

Glossary.......................................................................................................................................48

Index............................................................................................................................................50

Troubleshooting Guide—QStar HSM Archive Solutions 5

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Getting started
1
This guide is intended for service level 1, service level 2, and administrator personnel who support
QStar HSM archive solutions. It provides information and instructions on how to troubleshoot and
solve the most common issues before escalating to QStar support.

Requirements for troubleshooting QStar HSM

(Topic number: 140097)

To troubleshoot QStar HSM, ensure you meet the following requirements:

• Knowledge of computer hardware and software concepts

• Proficiency in operating and troubleshooting computer hardware

• Knowledge of IMPAX archiving concepts

• Knowledge of the architecture of the second archive tier and its integration between QStar
HSM and IMPAX

Syslog and SCSI log files

(Topic number: 140339)

QStar HSM uses log files to record system information and error messages that can assist with
troubleshooting.

Troubleshooting Guide—QStar HSM Archive Solutions 6

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Syslog file
To debug QStar HSM, you must analyze the syslog files. All events that describe the status and the
health of the system are reported in the syslog file. Syslogs are stored in the following locations:
• On Windows systems: C:\qstar\log

• On Solaris systems: /opt/QStar/log

Analyze the syslog in tandem with the SCSI log file to obtain a clear understanding of the environment.

SCSI log file

The SCSI log reports all default commands and hardware errors. The SCSI log window opens on
the SCSI bus. All commands are reported in vendor-neutral format so they can be read and forwarded
to the hardware vendor's technical support team.
Agfa recommends enabling the SCSI log to track down all the SCSI commands sent to and received
from the library. For information about how to enable the SCSI log, refer to the QStar Administrator's
Guide.

Troubleshooting strategies for QStar HSM

(Topic number: 140100)

The primary goal of troubleshooting QStar HSM is to restore the original configuration back online,
and where possible, recover data from a damaged media. Use the following strategy when
troubleshooting QStar HSM:
1. Identify the component not working.
2. Identify the error that is generated.
3. Identify the impact of the error (for example, volume not available, mirrors not in-sync, or
retrieve not working).

Tip:

Failure to consider and research all relevant error messages can obscure the current status
of the entire system, which can lead to additional errors or improper configurations. Adjust
the troubleshooting strategy depending on the defective component (for example, media,
drive, library, or software).

Opening a ticket with QStar technical support

(Topic number: 140316)

As per the support contract, Agfa technical support provides first line support to the customer. Agfa
initially investigates the technical problem and tries to solve it. If the problem cannot be resolved,

Troubleshooting Guide—QStar HSM Archive Solutions 7

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 escalate the call to QStar technical support. All calls must be opened through the Support Contacts
(email or phone) to generate a ticket ID and track all performed operations.

Required information
To open a support ticket, the Agfa Field Service Engineer (FSE) must provide the following
information:

Information to provide

Site name (SNDB name, if available)

Host ID

QStar HSM version installed

Detailed description of the problem

Actions already performed by Agfa personnel

Syslog and SCSI log files

Commands output
Windows
• vlcmd lsset -va

• vlcmd lsdev jb_name

• mmcmd param set_name

• jbcmd status jb_name

Solaris
• vllsset -va

• vllsdev jb_name

• mmparam set_name
• jbstatus jb_name

Phone number of Agfa FSE

Email address of Agfa FSE

Troubleshooting Guide—QStar HSM Archive Solutions 8

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Troubleshooting QStar
HSM configuration 2
issues

Configuration issues include all problems generated by improper configuration or use of the QStar
HSM software.

How to troubleshoot configuration issues

(Topic number: 140109)

All debugging and troubleshooting occurs by checking and analyzing the syslog and the SCSI log
files. For information about how to obtain these files for the different operating systems, see Syslog
and SCSI log files (refer to page 6) or refer to the QStar Administrator's Guide.

Troubleshooting: Volume not mounted

(Topic number: 140048)

Issue
IMPAX cannot store data or retrieve studies. QStar HSM does not report any errors.

Details
IMPAX archives the data in the volume set. When the volume is not mounted, this configuration
issue can arise from the IMPAX side directly being unable to store the data. QStar HSM itself does
not report any errors since it is not an illegal configuration state.

Troubleshooting Guide—QStar HSM Archive Solutions 9

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Solution
Mount the volume set using either the QStar HSM GUI or the CLUI. For information about volume
set mounting, refer to the QStar Administrator's Guide.

Troubleshooting: Current writing media offline

(manually exported)
(Topic number: 140061)

Issue
The QStar HSM syslog reports a message in the console of the GUI stating
Bring online media
The following is an example of the syslog:
06/08/2011 15:20:59 sdf_migrator: archive: sdf_get_vh: failed to open volume 16
(flag 0, original 2, fallback 2, vl_status 0x0)
06/08/2011 15:20:59 sdf_migrator: archive: sdf_ev_page_fault: return with error:
sdf_fill_page_buf: tn_num = 484776, page_num = 0, vol = 16, position = 5015502:
read_buf open: sdf_get_vh: Medium in set is offline

Troubleshooting Guide—QStar HSM Archive Solutions 10

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 06/08/2011 15:20:59 ERROR MM (archive, K:\HSM\archive)-0:
q_mm_get_migrator_response.1761: Error from migration: PAGE_FAULT
\20070329\0048a805.blob: Medium in set is offline

Details
The system goes into covered filesystem error. You cannot archive, but jobs can still be retrieved.
The error state is shown in QStar Administration Interface dialog.

Solution
1. To import the media previously exported, navigate to QStar Administration Interface > Media
> Online Media.
2. After importing the media, to clear the error condition status, navigate to QStar Administration
Interface > Integral Volumes > Migration View.
3. Click Clear Error Condition State.
The archive restarts.

Troubleshooting: Device not configured or claimed

(Topic number: 140064)

Issue
QStar HSM daemons do not start. Users cannot archive or retrieve jobs.

Troubleshooting Guide—QStar HSM Archive Solutions 11

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Details
Several messages in the QStar syslog appear. In the following example, no devices are available on
boot (claimed), and as a result, the services do not start:
12/14/2009 08:26:26 qserver: Server is starting...
12/14/2009 08:26:26 qserver: QStar Server Version 4.40.31, hostid <C0F82763>
Windows 2003
12/14/2009 08:26:26 qserver: Device available on boot:
12/14/2009 08:26:26 qserver: hostname raeas01, official name server.qstar.com,
no aliases, address 10.137.130.44 address 10.137.130.44, official name
raeas01.bradfordhospitals.nhs.uk, no aliases, address 10.137.130.44
12/14/2009 08:26:26 qserver: The system is configured with "LargeSystemCache"
option. It may significantly degrade Qstar performance 12/14/2009 08:26:26 qserver:
Starting Centera Daemon...
12/14/2009 08:26:26 centera_daemon: C:\QStar\qscsi\files\centera_conf: can't init
dynamic libraries: centera_get_config: No such file or directory 12/14/2009
08:26:26 centera_daemon: failed to start
12/14/2009 08:26:26 qserver: pid 420 on port 5005: << START >> 12/14/2009 08:26:27
FSI: FSI Server: start (DebugFile = FALSE) Security Level <No Protection>
12/14/2009 08:26:30 FSI: File System Interface Server: Lana [4] Added Name
<QSTARSERVER> Type <0x20> at Number [2]
12/14/2009 08:26:30 FSI: CIFS Browser Server on Lana [4]: start
12/14/2009 08:26:30 FSI: CIFS Request Server on Lana [4]: start
12/14/2009 08:26:30 scsiserver: create_service
12/14/2009 08:26:30 qserver: SCSI: Started 12/14/2009 08:26:40 jbserver:
C:\QStar\dev\JB0\jbctl: q_jb_init - device #0: qs_scsi_open: Device not ready
12/14/2009 08:26:40 jbserver: JB: Server start error: Device not ready
12/14/2009 08:26:40 qserver: JB: C:\QStar\dev\JB0\jbctl: q_jb_init - device #0:
qs_scsi_open: Device not ready
12/14/2009 08:26:40 qserver: error starting scsi,jb,vl server, exiting: Device
not ready

Solution
1. Ensure that the device is correctly visible by the operating system and correctly claimed
(Windows environments).
2. For Windows, from the Start > Programs menu, check the device manager and the QStar
device claiming utility. The device must be claimed and configured in the QStar HSM software
to allow startup of the QStar HSM solution.

Troubleshooting Guide—QStar HSM Archive Solutions 12

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Lack of available (new, erased, or
blank) media
(Topic number: 140067)

Issue
The following error message appears in the QStar HSM syslog and in the console of the GUI (for
Windows environments) or vlconsole –l (for Solaris environments):
Please vladdtoset erased (blank) medium. No medium to initialize
The error appears when you must archive data and the media is not present. Without an import of
the requested media, archiving is not possible. Retrieving might fail as well.

Details
The syslog and the console specify the set that requested the media:
08/11/2010 17:19:42 mmserver: Error condition: Covered error
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_call_vl: volume 1 not
available
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_get_vh: failed open
volume 1 (flag 0, original 6, fallback 6, vl_status 1) error 0/0
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: no more volumes available
08/11/2010 17:21:58 SDF: set tape_prime, sequence_number 1: Please vladdtoset
erased (blank) medium.
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: Event passthru ADDVOL: <>:
Operator help required
08/11/2010 17:21:58 SDF: set tape_mirror, sequence_number 1: Please vladdtoset
erased (blank) medium.
08/11/2010 17:21:58 sdf_slave: sdf_sl_open: can't add/get volume 1: Operator help
required
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_mir_dev_open: MIRR_open:
sdf_get_vh: can't open volume 1: Operator help required

Solution
1. Import the requested media and add the media to the set.

Note:

If the system is still in error, importing does not solve the issue. In this case, the system
remains in Covered Error mode, and neither archive nor retrieve are possible. Follow
the instructions in Troubleshooting: Current writing media offline (manually exported)
(refer to page 10).

Troubleshooting Guide—QStar HSM Archive Solutions 13

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 2. After the media has been imported and added to the set, to clear the error condition status,
navigate to QStar Administration Interface > Integral Volumes > Migration View.
3. Click Clear Error Condition State.
The archive restarts.

Troubleshooting: Media not added to the set

(Topic number: 140070)

Issue
The following message appears in the QStar syslog:
No space left on device
The error appears when you need to archive data and the media is not present. Without importing
the requested media, archiving is not possible. Retrieving might fail as well.

Details
The following is an example of the syslog:
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: no more volumes available
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: Event passthru ADDVOL: <>:
No space left on device
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_get_vh: secondary failed
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_get_vh: failed open
volume 1 (flag 0, original 6, fallback 0, vl_status 13) error 3000009/4000003
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: no more volumes available
08/11/2010 17:21:58 sdf_slave: got new volume, sending RESUME: No space left on
device
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: Event passthru MIRR_RESUME:
czc9161cg1:0 (volume 2): No space left on device
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_get_vh: secondary failed
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: sdf_get_vh: failed open
volume 1 (flag 0, original 6, fallback 0, vl_status 13) error 3000009/3000009
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: cfs_migrator_sdf:
sdf_start_vol: sdf_get_vh: No space left on device
08/11/2010 17:21:58 primary_sdf_migrator: tape_prime: No space left on device
08/11/2010 17:21:58 mmserver: S:\QStarCache: Covered filesystem error: No space
left on device: WRITE: Client UID=0, Client GID=0

Solution
1. Import the requested media and add the media to the set.

Troubleshooting Guide—QStar HSM Archive Solutions 14

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Note:

If the system is still in error, importing does not solve the issue. In this case, the system
remains in Covered Error mode, and neither archive nor retrieve are possible. Follow
the instructions in Troubleshooting: Current writing media offline (manually exported)
(refer to page 10).

2. After the media has been imported and added to the set, to clear the error condition status,
navigate to QStar Administration Interface > Integral Volumes > Migration View.
3. Click Clear Error Condition State.
The archive restarts.

Troubleshooting: Overlap between different

operations on the library (concurrence between
archive/retrieve/hot sync)
(Topic number: 140073)

Issue
No progress in archiving (backlog in the queue) or failure with retrievals.

Details
The library is typically equipped with two drives. This allows it to write two media at the same time
to maintain the mirror status. If a read request (retrieve) occurs during write operations, the write
is stopped, the request is satisfied, and the archive restarts. The library and the tape require time to
perform mechanical operations (like rewinding the tape’s ribbon, unloading the media, loading the
media, and seeking the position) which, can result in a timeout. Similarly, if a resync operation is
in progress, you cannot archive or retrieve data at the same time.
The following screenshot of the QStar HSM GUI shows the mirror status:

Troubleshooting Guide—QStar HSM Archive Solutions 15

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 The time needed by the device to perform all the physical operations on the library generates a loop
into the side operations (retrieve or archive).

Solution

Note:
This is a design issue. Integration knowledge of the architecture of the second archive tier
and its interaction between QStar HSM and IMPAX is essential.

To resolve, make the following configuration changes:

• Configure the system to archive outside of regular business hours so that the device can be free
to retrieve during the day.
Archives done during the day can be made through the cache without any impact to the system
or production. The configuration is made through the delayed archive.

• Size the cache according to the daily customer load. If the cache is too small, the system starts
the archive before the scheduled time and creates an overlap if the retrieve occurs at the same
time.

• Add more drives to the jukebox, if possible.

Troubleshooting Guide—QStar HSM Archive Solutions 16

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Cache size problems
(Topic number: 140085)

Issue
Cannot mount the volume set, archive data, or retrieve data.
Depending on the QStar HSM version, several messages appear in the syslog file describing storage
space issues with the cache:
08/24/2010 04:06:12 INFO MM (tape_prime, H:\Qstarcache): H:\Qstarcache: OS reported
available space is 1473 MB, this is less than 1473 MB required by QStar
08/24/2010 04:06:12 INFO MM (tape_prime, H:\Qstarcache):
q_mm_check_cache_files_limit.1866: H:\Qstarcache: cache area full
08/24/2010 04:06:12 INFO MM (tape_prime, H:\Qstarcache): please free space in
cache area or add new cache area
08/24/2010 04:06:12 ERROR MM (tape_prime, H:\Qstarcache): q_mm_sync_strategy.2747:
cache files limit check failed, error condition is set
08/24/2010 08:19:03 INFO MM (tape_prime, H:\Qstarcache): Primary cache: 1475 MB
free
08/24/2010 08:19:03 INFO MM (tape_prime, H:\Qstarcache): error condition cleared

Details

Important!
Data loss can result if the database becomes corrupted.

The cache files change dynamically according to the activity of the volume set. The cache directory
contains the database files, which typically grow with the file system structure.

Solution
1. Enlarge the partition where the cache files are located.
Do not configure the cache size in QStar HSM as the maximum amount of space of the partition
(D:\cache) where it is placed.
If upgrading QStar 4.2.x to 4.3.x or 4.4.x (Solaris) (refer to page 42), the cache’s partition
contains files that grow dynamically, like transaction logs and database files. For this reason,
Agfa suggests leaving at least 10% of the disk space free.
2. If no primary data is present in the cache, unmount and resize the cache, then remount it.

Troubleshooting Guide—QStar HSM Archive Solutions 17

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Note:
In QStar HSM 5.x and later, a volume cannot be mounted if less than 2 GB of space is
available. This helps prevent the cache partition from running out of space, which can lead
to possible database corruption and data loss.

Troubleshooting: Services stop or unmount during

rollover or write/read from volume
(Topic number: 140091)

Issue
No access to the volume set. Disconnection of the network drive of the QStar volume.
The services are stopped while an access to the media for retrieve or during rollover is made. If the
device is performing, certain operations are not allowed to unmount or stop the services. For instance,
during rollover, QStar HSM copies the database at the beginning of the media and the stop/unmount
might lead to a wrong or partial media initialization.

Important!
Unmounting or stopping of services during rollover or write/read from the volume is not allowed.

Details
This scenario does not generate a specific error in the syslog.
08/25/2011 10:11:43 qserver: VL: Set is mounted
08/25/2011 10:11:43 vlserver: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:43 qserver: VL: retrying ...
08/25/2011 10:11:46 VL: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:46 Last message repeated 2 times
08/25/2011 10:11:46 qserver: VL: Set is mounted
08/25/2011 10:11:46 qserver: VL: retrying ...
08/25/2011 10:11:49 VL: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:49 qserver: VL: Set is mounted
08/25/2011 10:11:49 vlserver: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:49 qserver: VL: retrying ...
08/25/2011 10:11:52 VL: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:52 Last message repeated 2 times
08/25/2011 10:11:52 qserver: VL: Set is mounted

Troubleshooting Guide—QStar HSM Archive Solutions 18

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 08/25/2011 10:11:52 qserver: VL: retrying ...
08/25/2011 10:11:55 VL: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:55 Last message repeated 2 times
08/25/2011 10:11:55 qserver: VL: Set is mounted
08/25/2011 10:11:55 qserver: VL: retrying ...
08/25/2011 10:11:58 VL: vl shut server: tape_mirror: Set is mounted
08/25/2011 10:11:58 Last message repeated 2 times
08/25/2011 10:11:58 qserver: VL: Set is mounted
08/25/2011 10:11:58 qserver: VL: retrying ...

Solution
If necessary, contact QStar technical support. For information, see Opening a ticket with QStar
technical support (refer to page 7)

Troubleshooting Guide—QStar HSM Archive Solutions 19

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Configuring QStar HSM
to improve performance 3
QStar HSM can be configured and tuned to optimize performance.

SMB timeout (Windows)

(Topic number: 140106)

The SMB timeout is the amount of time that Windows waits to access a network resource. The QStar
HSM volume share is available through a network share, which can be affected by the SMB timeout.
For example, QStar requests a file present on a media that is not already in the drive. In this case,
the jukebox might take longer than the SMB timeout to move the media from the shelf to the drive
to satisfy the read request. As a result, Windows disconnects the share and the retrieve fails.
The SMB timeout can be changed through Windows registry keys. QStar HSM has implemented a
utility, setsmbtimeout.exe, is available in c:\qstar\bin.

Note:

Agfa recommends setting the SMB timeout to at least 300 seconds. You must restart the
system after modifying the SMB timeout value.

Troubleshooting Guide—QStar HSM Archive Solutions 20

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Improving read performance for tape using full file
mode
(Topic number: 140391)

The MCFS (Magnetic Cache File System) Migration Manager handles the migration of the data and
the files from the media to the cache in two modes:
• Segmented mode—A file is viewed as a collection of data segments of discrete size. Each segment
can be migrated individually or collectively with other segments.

• Full file mode—The Migration Manager always migrates the complete file as a single entity.

For more information about the Migration Manager, refer to Chapter 6 – Migration Manager in
the QStar Administrator's Guide.
To significantly improve tape read performance, change the file migration mode of the files from
segmented mode (default) to full file mode. This forces QStar HSM to bring the full file back to the
cache with one request.

Note:
The time required to complete this procedure depends on whether you are applying it to a
new file system with little or no data, or whether it is an existing file system containing many
files.

To improve read performance for tape using full file mode (Windows)
1. Ensure that no archiving or read operations are in progress.
2. To change all file systems to full file mode, do the following:
a. Open a command prompt.
b. Type
C:\QStar\bin>mmcmd chmod +f integral_volume_name
3. To change one directory at a time to full file mode, do the following:
a. Open a command prompt.
b. To configure the first subdirectory, type
C:\QStar\bin>mmcmd chmod +f integral_volume_name\archive\sub_dir_name
c. After configuring all subdirectories, to configure the archive directory, type
C:\QStar\bin>mmcmd chmod +f primary_tape\archive
d. To configure the root directory, type
C:\QStar\bin>mmcmd chmod +f primary_tape

Troubleshooting Guide—QStar HSM Archive Solutions 21

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 To improve read performance for tape using full file mode (Solaris)
1. Ensure that no archiving or read operations are in progress.
2. To change all file systems to full file mode, do the following:
a. Open a command prompt.
b. Type the following command:
mmchmod +f mount_point/archive/sub_dir_name
3. To change one directory at a time to full file mode, do the following:
a. Open a command prompt.
b. To configure the first subdirectory, type
mmchmod +f integral_volume_name\archive\sub_dir_name
c. After configuring all subdirectories, to configure the archive directory, type
mmchmod +f mount_point/archive
d. To configure the root directory, type
mmchmod +f mount_point

Maximum transfer size

(Topic number: 141740)

The Maximum Transfer Size value is displayed in the Jukebox Configuration tab of the QStar
Administration interface. After modifying the Maximum Transfer Size value in the registry, this tab
displays the current value enabling you to verify that the value increased after modifying the registry
entry.
The SCSI Adapter Maximum Transfer Size is the largest single SCSI data transfer that can be issued.
This does not mean the largest file size but rather the largest block that can be read or written to an
optical device with a single SCSI command. When small files must be transferred by issuing multiple
SCSI commands, the impact on read performance can be significant. However, write performance
suffers when this value is too small compared to the file size. Windows SCSI Adapters default allows
a maximum SCSI bus transfer size of 64K (65536 decimal bytes). Increasing the default SCSI adapter
transfer size significantly improves large file transfer performance. Agfa recommends setting the
maximum transfer size to 512 KB or 768 KB.

SCSI registry utility

QStar HSM includes a utility, scsiregistry.exe, available in C:\qstar\bin. The utility shows all the cards
present on the system and enables you to filter by the ones used by QStar HSM. Once selected, it
shows the current value, which you can change. QStar HSM suggests using the maximum (255)
value to achieve optimal performance. You must restart the system after modifying this value.

Troubleshooting Guide—QStar HSM Archive Solutions 22

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Tape devices
Unlike an optical device that works with a small transfer size, a tape device returns an error during
write operations if the transfer size is too small. Do either of the following to clear this error:

Solution Impact on write performance

Recreate the cache for the integral volume set with 32 Write performance is less than optimal.
KB pages size (the default size is 64 KB)

Increase the Maximum Transfer Size of the SCSI Write performance improves.
adapter

CIFS sharing not available on Windows

(Topic number: 141779)

To export the volume from Windows only using NFS, create an empty file called nosmb (without
a file extension) in the C:\qstar\install folder.

Troubleshooting: Configuring libraries with an

adapter SCSI transfer rate less than 129 KB
(Topic number: 141776)

Issue
With some tape libraries associated with a SAS card or a SCSI card, you cannot attach the library in
QStar HSM. After configuring the library, the system returns the following error message:
SCSI transfer rate less than 129K not enough core

Details
This error means that this configuration must have a SCSI transfer rate greater than 129 KB.

Solution
To avoid this problem, starting from release 5.0.16.908 and later, force the system to work with a
lower transfer rate by placing an empty file (without an extension) called no129k in the C:\qstar\install
folder.

Note:
If the transfer rate displayed in the Jukebox Configuration page is less than 65 KB, even with
this workaround, the library cannot be configured.

Troubleshooting Guide—QStar HSM Archive Solutions 23

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Setting memory use priority to programs (Windows)
(Topic number: 140400)

When a small amount of memory is dedicated to applications, it forces the applications to use a
large amount virtual memory. This generates a high number of page faults that dramatically reduce
write performance. Changing the memory use priority to programs solves this performance problem
by allowing the applications priority to use real memory instead of virtual memory.

To set memory use priority to programs (Windows)

1. Right-click My Computer, and select Properties.
2. Switch to the Advanced tab.
3. Under Performance Settings, click Settings.
4. Switch to the Advanced tab.
5. Under Memory Usage, select Programs.
6. Click OK.

Troubleshooting Guide—QStar HSM Archive Solutions 24

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Troubleshooting QStar
HSM technical issues 4
Technical issues include all errors resulting from hardware failures or software issues. For hardware
failures, a third-party intervention from the hardware service is required before QStar can check the
status of the site. A typical example is the following: media unload or eject failure from a
drive with consequent damage of the cartridge. After replacing the malfunctioning hard
drive, QStar technical support can follow up by recreating (where possible) the damaged media. For
software issues, Agfa recommends upgrading the software. For information, see Upgrading QStar
HSM (refer to page 41).

How to troubleshoot technical issues

(Topic number: 140112)

Important!
Technical issues that involve damaged media must be addressed by QStar or managed under
QStar supervision.

Check the syslog and SCSI log for errors involving termination, cabling, or adapter failure. These
logs report the media or drive involved and can provide corrective actions to take. These issues must
first be managed by Agfa support. Escalate to QStar support if additional information is required.

Troubleshooting Guide—QStar HSM Archive Solutions 25

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Recorded entity not found
(Topic number: 140132)

Issue
The following error appears in the syslog, typically during a retrieve from IMPAX or during archive:
07/27/2009 21:26:50 sdf_slave: sdf_sl_read: tape_locate: C:\QStar\dev\JB\rjb29a:
Position setup error: Error doing locate to 3780534: scsi locate: I/O error, sense
key (3 14 00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND
07/27/2009 21:30:21 sdf_slave: sdf_sl_read: tape_locate: C:\QStar\dev\JB\rjb29a:
Position setup error: Error doing locate to 3780536: scsi locate: I/O error, sense
key (3 14 00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND
07/27/2009 21:33:53 sdf_slave: sdf_sl_read: tape_locate: C:\QStar\dev\JB\rjb29a:
Position setup error: Error doing locate to 3780536: scsi locate: I/O error, sense
key (3 14 00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND
07/27/2009 21:37:36 sdf_slave: sdf_sl_read: tape_locate: C:\QStar\dev\JB\rjb29a:
Position setup error: Error doing locate to 3780536: scsi locate: I/O error, sense
key (3 14 00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND
07/27/2009 21:41:07 sdf_slave: sdf_sl_read: tape_locate: C:\QStar\dev\JB\rjb29a:
Position setup error: Error doing locate to 3780536: scsi locate: I/O error, sense
key (3 14 00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND

Details
Tape media read failure. The media is not readable and its content cannot be retrieved.

Note:
Data loss is possible if the media was not synchronized with the mirror.

Solution
1. If the mirror is available (and was correctly written), resynchronize the media.
or
Run the copy tape to recover its contents to the damaged block.
2. If necessary, escalate to QStar technical support.
For information, see Opening a ticket with QStar technical support (refer to page 7).

Troubleshooting Guide—QStar HSM Archive Solutions 26

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Unit CRC error
(Topic number: 140135)

Issue
The following error appears in the syslog, typically during archive or synchronization operations:
06/14/2011 12:36:28 sdf_do_hotsync: Current Hot Sync status: main(Primary) at:
12/247966, Primary at: 12/247966, Secondary at: 11/9992692, Primary not in sync
06/14/2011 12:36:28 primary_sdf_migrator: tape_prime: Finding end of primary
volume 06/14/2011 12:36:28 primary_sdf_migrator: tape_prime: searching hw mark
on primary (main position - 12:247966, primary position - 11:9992678)
06/14/2011 12:38:14 primary_sdf_migrator: tape_prime: reported hw mark is above
expected (volume 11, position 9992694)
06/14/2011 12:38:14 primary_sdf_migrator: tape_prime: found hw mark at volume 11,
position 9992694
06/14/2011 12:38:14 sdf_do_hotsync: Current Hot Sync status: main(Primary) at:
12/247966, Primary at: 12/247966, Secondary at: 11/9992694, Primary not in sync
06/14/2011 12:43:10 primary_sdf_migrator: tape_prime: sdf_mir_verify_hw: Hot sync
failed at volume 11 position 9992694: verification failed at volume 11 position
9992692: Media are different
06/14/2011 12:43:10 sdf_do_hotsync: Current Hot Sync status: main(Primary) at:
12/247966, Primary at: 12/247966, Secondary at: 11/9992694, Primary not in sync
06/14/2011 12:43:10 mirroring: F:\Qstarcache: Hot sync incomplete: volume 11,
position 9992694: Media are different
06/14/2011 12:48:09 sdf_slave: WRITE[C:\QStar\dev\JB0\rjb26a]: pos=247966,
bk_flags=0x0: TAPE_write: C:\QStar\dev\JB0\rjb26a: Error writing data: scsi write:
I/O error, sense key (b 47 03): ABORTED COMMAND: INFORMATION UNIT CRC ERROR
06/14/2011 12:48:09 primary_sdf_migrator: tape_prime: sdf_send_buf: volume 12,
position 0: MIRR_write (secondary): I/O error
06/14/2011 12:50:47 primary_sdf_migrator: tape_prime: check_written_bufs: buffer
read from position 247966 differs from source ... 0 bufs are OK
This following message is reported in the QStar SCSI log output:
09:51:20.9750 0.0000 JB0:drive1 write_6 0a 00 01 04 00 00 ABORTED COMMAND:
INFORMATION UNIT CRC ERROR=(0b 47 03 Additional: 00 00 00 00 00 00)

Details
This issue is caused by a library problem, bad cabling, or a bad termination.
No data can be archived from the logical volume to the tape. The tape is out-of-sync with the media
if errors appear during a hot sync operation. Check for out-of-sync status:

Troubleshooting Guide—QStar HSM Archive Solutions 27

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 • In Windows environments—QStar Administration Interface > Migration View > Mirror
Media Status

• In Solaris environments—mmparam command output

Solution
1. Check with the hardware vendor to determine if the volumes are out-of-sync.
2. If necessary, escalate to QStar technical support.
For information, see Opening a ticket with QStar technical support (refer to page 7).

Troubleshooting: MAM not accessible

(Topic number: 140141)

Issue
The following error appears in the syslog, typically during a refresh or read operation:
06/07/2011 09:48:14 sdf_slave: sdf_sl_hw_search: C:\QStar\dev\JB0\rjb20a:
qs_scsi_open: find_class: inquiry: No such device
06/07/2011 09:48:14 primary_sdf_migrator: hw mark on mirror search failed at
volume 43: No such device
06/07/2011 09:48:14 primary_sdf_migrator: tape_prime: hw mark on mirror search
failed at volume 43: Hot sync failed at volume 43 position 7934564: No such device
06/07/2011 09:48:14 sdf_do_hotsync: Current Hot Sync status: main(Primary) at:
43/7934612, Primary at: 43/7934612, Secondary at: 43/7934564, Secondary not in
sync
06/07/2011 09:48:14 mirroring: G:\hsm\archive: Hot sync incomplete: volume 43,
position 7934564: No such device
06/07/2011 10:03:13 JB: standard_load wait ready: JB0 Drive 1 marked bad:
C:\QStar\dev\JB0\rdrive1: wait unit ready: scsi test unit ready: Device not ready,
sense key (2 3a 04): NOT READY: MEDIUM NOT PRESENT, MAM ACCESSIBLE

Details
The chip on the media (available from LTO3 generation) is damaged. This is the chip in the cartridge
where format information is stored. If chip content is destroyed, it may restore itself. If it is not
present (and most likely is damaged), the media is unreadable.

Note:
Data loss can result if the media was not synchronized with the mirror.

Solution
1. Read the tape using the vlcopy command.

Troubleshooting Guide—QStar HSM Archive Solutions 28

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 For more information about vlcopy, refer to the QStar Administrator's Guide.
2. Create a copy of the tape on another erased media.
Agfa can then resynchronize the media if the mirror is available (and was correctly written).
3. If the vlcopy command fails, escalate to QStar technical support.
For information, see Opening a ticket with QStar technical support (refer to page 7).

Troubleshooting: Media load or eject failure

(Topic number: 140144)

Issue
The media is locked in the drive. Unloading the media fails and the media appears jammed in the
drive.

Note:

Data loss can result if the jammed media is also damaged.

Details
The following error appears in the syslog:
07/30/2010 06:42:03 JB: standard_unload: JB0 Shelf 291 marked bad:
d:\qstar\dev\JB0\jbctl: scsi move:
I/O error, sense key (4 53 00): HARDWARE ERROR: MEDIA LOAD OR EJECT FAILED
07/30/2010 06:42:03 JB: standard_unload: JB0 Drive 4 marked bad: JB0 Shelf 291
marked bad: d:\qstar\dev\JB0\jbctl: scsi move: I/O error, sense key (4 53 00):
HARDWARE ERROR: MEDIA LOAD OR EJECT FAILED
07/30/2010 06:42:03 JB: q_jb_init_jukebox: JB0 Drive 4 marked bad: JB0 Shelf 291
marked bad: d:\qstar\dev\JB0\jbctl: scsi move: I/O error, sense key (4 53 00):
HARDWARE ERROR: MEDIA LOAD OR EJECT FAILED
The following messages appear in the SCSI log:
11:36:14 694 694 1:2:0 test unit ready 00 00 00 00 00 00 NOT READY: UNIT IS IN
PROCESS OF BECOMING READY=(02 04 01)
11:36:15 694 694 1:2:0 test unit ready 00 00 00 00 00 00 NOT READY: UNIT IS IN
PROCESS OF BECOMING READY=(02 04 01)
11:36:16 694 694 1:2:0 test unit ready 00 00 00 00 00 00 UNIT ATTENTION: NOT
READY, MEDIUM MAY HAVE CHANGED=(06 28 00)
11:36:16 694 694 1:2:0 test unit ready 00 00 00 00 00 00
11:36:16 694 694 1:2:0 test unit ready 00 00 00 00 00 00
11:36:16 694 1 803 1:2:0 start 1b 00 00 00 01 00 MEDIUM ERROR: MEDIA LOAD OR EJECT
FAILED=(03 53 00)

Troubleshooting Guide—QStar HSM Archive Solutions 29

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Solution
1. Before escalating to QStar technical support, contact hardware support to gather specific
recovery procedures to unload the media from the drive.
2. Restart the device.
3. Restart the server.
4. If the error does not clear, contact hardware support for further assistance.

Troubleshooting: Hardware error—Internal target

failure (non-responsive device)
(Topic number: 140147)

Issue
QStar HSM tries to access one of the resources (drive, media, or picker) but no answer is received
from the jukebox. The device is not responding.
The following error appears in the syslog:
09/20/2010 16:15:32 JB: standard_load wait ready: JB0 Drive 1 marked bad:
C:\QStar\dev\JB0\rdrive1: wait unit ready: scsi test unit ready: Device not ready,
sense key (4 44 00): HARDWARE ERROR: INTERNAL TARGET FAILURE
09/20/2010 16:15:32 JB: JB0, Drive 1: C:\QStar\dev\JB0\rdrive1: Sync failed: scsi
sync cache: I/O error, sense key (4 44 00): HARDWARE ERROR: INTERNAL TARGET FAILURE
09/20/2010 16:15:32 JB: Sync failure: JB0 Shelf 1 marked bad: JB0, Drive 1:
C:\QStar\dev\JB0\rdrive1: Sync failed: scsi sync cache: I/O error, sense key (4
44 00): HARDWARE ERROR: INTERNAL TARGET FAILURE

Details
No data loss or corruption is expected, but you must carefully manage the system until the issue is
resolved.

Solution
1. Reboot the library.
2. Check with hardware support to obtain more information on the system's status.

Note:
Although QStar HSM will go into error mode, this issue is caused by a prior hardware problem.

Troubleshooting Guide—QStar HSM Archive Solutions 30

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Aborted command (data phase
error)
(Topic number: 140276)

Issue
The following error appears in the syslog:
07/16/2010 08:17:32 sdf_slave: sdf_sl_write: TAPE_write: /opt/QStar/dev/jb/rjb130a:
USCSICMD ioctl:
Error writing data: scsi write:
SCSI cmd 0xa (write_6): I/O error, sense key (b 4b 00): ABORTED COMMAND: DATA
PHASE ERROR
07/16/2010 08:17:32 primary_sdf_migrator: tape_prime: hotsync: volume 163, position
5119654: MIRR_write (secondary): write: I/O error
07/16/2010 08:17:34 sdf_slave: sdf_sl_sync: TAPE_sync: tape_check_pos: Error
flushing drive buffer: First soft position mismatch: Invalid argument
07/16/2010 08:18:46 primary_sdf_migrator: tape_prime: secondary (set tape_mirror)
- jb 130a) position 5119654 (estimated space used 159989MB, capacity - 190734MB).
07/16/2010 08:18:46 primary_sdf_migrator: tape_prime: Please fix the problem and
restart hotsync orvlreplace medium (vlreplace jb 130).
07/16/2010 08:18:46 primary_sdf_migrator: tape_prime: sdf_hotsync: I/O error

Note:
The system might go out-of-sync. If the problem occurs in an already out-of-sync scenario,
the archive might also fail.

Details
If the system goes out-of-sync, the status is indicated in QStar Administration Interface > Integral
Volumes > Migration View > Mirror Media Status.

Troubleshooting Guide—QStar HSM Archive Solutions 31

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 This can be caused by a problem in the SCSI communication channel that occurs randomly. The
problem on the SCSI chain can be temporary. It can be caused by the drive where the tape has been
loaded (error flushing drive buffer).

Note:

This situation presents no risk of data loss or corruption.

Solution
1. Check the drive with a hardware technician.
The system automatically puts the mirror out-of-sync and continues writing on the primary
drive.
2. Unmount or restart QStar HSM services.
This might restart the correct operation.
3. If necessary, escalate to QStar technical support.
For information, see Opening a ticket with QStar technical support (refer to page 7).

Troubleshooting Guide—QStar HSM Archive Solutions 32

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Blank check (overwrite attempted)
(Topic number: 140279)

Issue
An overwrite in the database is attempted, but fails. The system goes into covered file system error.
You cannot archive and retrieve.

Details
The position reported by the database (where to write) is incorrect. QStar HSM recognizes that the
block already contains data and stops to avoid data corruption. The system goes out-of-sync; the
status is shown in QStar Administration Interface > Integral Volumes > Migration View > Archive
Status.

The following error appears in the syslog:

01/15/2010 11:12:07 JB: standard_unload: jb0 Shelf 8 marked bad: /dev/jb0/jbctl:
scsi move: Q_SCSI_PT_CMD ioctl: I/O error, Timeout
01/15/2010 11:12:07 JB: standard_unload: jb0 Drive 2 marked bad: jb0 Shelf 8
marked bad: /dev/jb0/jbctl: scsi move: Q_SCSI_PT_CMD ioctl: I/O error, Timeout
01/15/2010 11:25:15 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056: replaying
unfinished write
01/15/2010 11:25:25 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
/dev/jb0/rjb8a: block_number 582, block_count 16392: write failed: scsi write:

Troubleshooting Guide—QStar HSM Archive Solutions 33

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Q_SCSI_PT_CMD ioctl: I/O error, sense key (8 92 00): BLANK CHECK: OVERWRITE
ATTEMPTED
01/15/2010 11:25:41 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
/dev/jb0/rjb8a: relocation from 582 to 17031
01/15/2010 11:25:42 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
/dev/jb0/rjb8a: block_number 17031, block_count 16392: write failed: scsi write:
Q_SCSI_PT_CMD ioctl: I/O error, sense key (8 92 00): BLANK CHECK: OVERWRITE
ATTEMPTED
01/15/2010 11:25:50 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
/dev/jb0/rjb8a: relocation from 17031 to 17063
01/15/2010 11:25:51 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
/dev/jb0/rjb8a: block_number 17063, block_count 16392: write failed: scsi write:
Q_SCSI_PT_CMD ioctl: I/O error, sense key (8 92 00): BLANK CHECK: OVERWRITE
ATTEMPTED
01/15/2010 11:25:51 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
/dev/jb0/rjb8a: block_number 582 -> 17063, block_count 16392: rewrite failed
01/15/2010 11:25:56 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056:
transaction size resaved 8606115
01/15/2010 11:25:56 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056: write
left unfinished
01/15/2010 11:25:56 UDF: /work/ffse/CACHE_QSTAR/P00001_1_20100115105056: unfinished
write: I/O error

Solution
1. Obtain the full syslog file.
2. Escalate to QStar technical support.
For information, see Opening a ticket with QStar technical support (refer to page 7).

Troubleshooting: Bad drive configuration file

(Topic number: 140282)

Issue
The system has a bad drive configuration file. Services do not start and, therefore, the volume cannot
be mounted. As a result, you cannot retrieve or archive.

Details
The hardware configuration has been changed. The configuration settings in QStar HSM are not
physically returned by the device. This can be caused by the following:
• A hardware issue such as a drive not working

• A hardware intervention such as replacement of a faulty drive

Troubleshooting Guide—QStar HSM Archive Solutions 34

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 During services startup, the following error appears in the syslog file:
06/30/2011 16:10:40 qserver: Server is starting...
06/30/2011 16:10:40 qserver: QStar Server Version 5.0.18.1036 32-bit, host ID
c39dc90e Windows 2003
06/30/2011 16:10:40 qserver: Device available on boot: 06/30/2011 16:10:40 qserver:
HP Ultrium 3-SCSI 0 0 0
06/30/2011 16:10:40 qserver: HP Ultrium 3-SCSI 0 0 1 06/30/2011 16:10:40 qserver:
HP MSL6000 Series 1 0 0
06/30/2011 16:10:40 qserver: HP Ultrium 3-SCSI 1 0 1 06/30/2011 16:10:41 qserver:
HP Ultrium 3-SCSI 1 0 2
06/30/2011 16:10:41 qserver: hostname RXCAS054, official name
RXCAS054.SUSSEX.NHS.UK, no aliases, address 10.179.0.234 address 10.179.0.234,
official name rxcas054, no aliases, address 10.179.0.234
06/30/2011 16:10:41 qserver: The system is configured with "LargeSystemCache"
option. It may significantly degrade Qstar performance 06/30/2011 16:10:41 License:
Product : QStar HSM 06/30/2011 16:10:41 License: Company : QStar System
06/30/2011 16:10:41 License: Department : Technical Department 06/30/2011 16:10:41
License: Person : QStar Technical Support
06/30/2011 16:10:41 License: Phone : +39 (02) 45.171.1
06/30/2011 16:10:41 License: Email : support@qstar.com 06/30/2011 16:10:41 License:
Version : 5.0
06/30/2011 16:10:41 License: Type : Permanent
06/30/2011 16:10:41 License: Host ID : c39dc90e 06/30/2011 16:10:41 License:
Serial No. : 468768
06/30/2011 16:10:41 License: Platform : Windows/32 06/30/2011 16:10:41 License:
Jukebox type: TAPE
06/30/2011 16:10:41 License: Num. shelves: 120
06/30/2011 16:10:41 License: DDR : DDR1 06/30/2011 16:10:41 FSI: FSI Server: start
(DebugFile = FALSE) Security Level <No Protection>
06/30/2011 16:10:41 pid 5988 on port 5005: << START >> 06/30/2011 16:10:44 FSI:
File System Interface Server: Lana [9] Added Name <QSTARSERVER> Type <0x20> at
Number [2]
06/30/2011 16:10:44 FSI: CIFS Browser Server on Lana [9]: start
06/30/2011 16:10:44 FSI: CIFS Request Server on Lana [9]: start 06/30/2011 16:10:44
scsiserver: create_service
06/30/2011 16:10:44 qserver: SCSI: Started 06/30/2011 16:10:44 jbserver: JB0:
q_jb_init - device #0: Bad drive inventory file
06/30/2011 16:10:44 Last message repeated 2 times 06/30/2011 16:10:44 jbserver:
JB: Server start error: Bad drive inventory file
06/30/2011 16:10:44 qserver: JB: Failed 06/30/2011 16:10:44 qserver: error starting
scsi,jb,vl server, exiting: Bad drive inventory file

Troubleshooting Guide—QStar HSM Archive Solutions 35

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Solution
1. Check the status of the hardware.
2. Contact QStar technical support.
For information, see Opening a ticket with QStar technical support (refer to page 7).

Troubleshooting: Resource temporarily unavailable

(Topic number: 140288)

Issue
A resource is temporarily unavailable. This can result from any of the following conditions:
• Bad status of the hardware marked in the QStar HSM database

• The media was exported mistakenly by the user

• A hardware error marked the media bad (in QStar Administration Interface > Devices >
Jukebox Status)

Details
Archive or retrieve might not be possible, depending on the required media. If the media needed is
the current writing surface and the volume is not mounted, the QStar HSM volume cannot be
mounted.
The following error message appears in the syslog:
02/04/2011 22:50:15 primary_sdf_migrator: CORA_PRIME: Initiating backup based on
written data size
02/04/2011 22:50:17 primary_sdf_migrator: CORA_PRIME: cfs_migrator_sdf: Event 7:
raising error_status: Resource temporarily unavailable
02/04/2011 22:50:17 primary_sdf_migrator: CORA_PRIME: Resource temporarily
unavailable
02/04/2011 22:50:17 primary_sdf_migrator: CORA_PRIME: cfs_migrator_sdf: event 25,
error_status pending: Resource temporarily unavailable 02/04/2011 22:50:17
primary_sdf_migrator: CORA_PRIME: Resource temporarily unavailable
02/04/2011 22:50:17 ERROR MM (CORA_PRIME, E:\Qstarcache)-0:
q_mm_get_migrator_response.1761: Error from migrator: --> WRITE
\archive\20110202\035ea84c.blob, mode(0100455), ctime: Resource temporarily
unavailable
02/04/2011 22:50:17 ERROR MM (CORA_PRIME, E:\Qstarcache):
q_mm_get_migrator_response.1774: Migrator event WRITE failed, error condition is
set

Solution
1. Retrieve the syslog.

Troubleshooting Guide—QStar HSM Archive Solutions 36

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 2. Verify which media (resource) is unavailable.
To debug, you must identify the resource needed.

Troubleshooting: Bus Device Reset occurs

(Topic number: 140297)

Issue
No archive, retrieve, or hot sync is possible.
The following error appears in the syslog:
04/01/2009 14:49:19 JB: JB0 Shelf 2 marked bad: The request could not be performed
because of an I/O device error., SCSI driver error
04/01/2009 14:49:19 JB: JB0 Drive 1 marked bad: JB0 Shelf 2 marked bad: The request
could not be performed because of an I/O device error., SCSI driver error
04/01/2009 14:50:47 JB: JB0 Shelf 32 marked bad: The request could not be performed
because of an I/O device error., SCSI driver error
04/01/2009 14:50:47 JB: JB0 Drive 2 marked bad: JB0 Shelf 32 marked bad: The
request could not be performed because of an I/O device error., SCSI driver error
04/01/2009 14:51:46 JB: JB0 Shelf 24 marked bad: I/O error, sense key 6 UNIT
ATTENTION 29 00 POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
04/01/2009 14:51:46 JB: JB0 Drive 3 marked bad: JB0 Shelf 24 marked bad: I/O
error, sense key 6 UNIT ATTENTION 29 00 POWER ON, RESET, OR BUS DEVICE RESET
OCCURRED
04/01/2009 14:51:46 JB: JB0 Shelf 29 marked bad: I/O error, sense key 2 NOT READY
04 82 NOT READY, MOTOR TURNED OFF
04/01/2009 14:51:46 JB: JB0 Drive 4 marked bad: JB0 Shelf 29 marked bad: I/O
error, sense key 2 NOT READY 04 82 NOT READY, MOTOR TURNED OFF

Details
Following a hardware error (or any other abnormal situation), the device tries to reset itself by issuing
a Bus Reset command. This command interrupts and stops all the current operations in place by
the system (for example, read or archive).
The Bus Reset command is issued by the device, not by QStar HSM.

Solution
1. Escalate to QStar technical support so that they can check the status of the system.
For information, see Opening a ticket with QStar technical support (refer to page 7).
2. Contact hardware support so that they can identify why the jukebox is issuing the Bus Reset
command.

Troubleshooting Guide—QStar HSM Archive Solutions 37

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Troubleshooting: Hardware error—Internal target
failure (target unavailable)
(Topic number: 140300)

Issue
The system experiences a hardware error stating internal target failure. Archive or retrieve may not
be possible.

Details
The error indicates that the target of the operation is not available or is in an error state. The target
might be the media or the drive needed for the required operation.

Tip:

If the error occurs while reading media, the media might be corrupt. For more information,
see Troubleshooting: Recorded entity not found (refer to page 26).

The following message appears in the syslog:

01/25/2010 04:19:24 sdf_slave: sdf_sl_sync: TAPE_sync: C:\QStar\dev\JB0\rjb3a:
Error flushing drive buffer: scsi write filemarks: I/O error, sense key (4 44
00): HARDWARE ERROR: INTERNAL TARGET FAILURE
01/25/2010 04:19:24 primary_sdf_migrator: primary: sdf_write_flush: volume 1,
position 4874356: MIRR_sync (secondary): sync: trying to recover: I/O error
01/25/2010 04:31:09 sdf_slave: sdf_sl_read: volume 0 position 4873888: error
0x3000002: tape_locate: C:\QStar\dev\JB0\rjb3a: Position setup error: Error doing
locate to 4873888: scsi locate: I/O error, sense key (3 14 00): MEDIUM ERROR:
RECORDED ENTITY NOT FOUND
01/25/2010 04:31:09 primary_sdf_migrator: primary: check_written_bufs: unreadable
buffer at position 4873888 ... 0 bufs are OK 01/25/2010 04:31:09 write_queue_sync:
Sync buffers 01/25/2010 04:40:31 sdf_slave: WRITE[C:\QStar\dev\JB0\rjb3a]:
pos=4873888, bk_flags=0x0: TAPE_write: tape_locate: C:\QStar\dev\JB0\rjb3a:
Position setup error: Error doing locate to 4873888: scsi locate: I/O error, sense
key (3 14 00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND
01/25/2010 04:40:31 primary_sdf_migrator: primary: write_queue_sync: volume 1,
position 4873890: MIRR_write (secondary): trying to recover: I/O error
01/25/2010 04:52:54 sdf_slave: WRITE[C:\QStar\dev\JB0\rjb3a]: pos=4873888,
bk_flags=0x0: TAPE_write: tape_locate: C:\QStar\dev\JB0\rjb3a: Position setup
error: Error doing locate to 4873888: scsi locate: I/O error, sense key (3 14
00): MEDIUM ERROR: RECORDED ENTITY NOT FOUND
01/25/2010 04:52:54 primary_sdf_migrator: primary: write_queue_sync: volume 1,
position 4873890: MIRR_write (secondary): trying to recover: I/O error

Troubleshooting Guide—QStar HSM Archive Solutions 38

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Note:
The error might be followed (as shown in the previous log entry) by different messages, which
lead to other errors.

Solution
1. Escalate to QStar technical support so that they can check the status of the system.
For information, see Opening a ticket with QStar technical support (refer to page 7).
2. If necessary, contact hardware support

Troubleshooting: Request cannot be performed

because of I/O device error or SCSI drive error
(Topic number: 140303)

Issue
A request cannot be performed because of I/O device error or SCSI drive error. Archiving or retrieving
might not be possible.

Details
The following error appears in the syslog:
12/20/2010 11:10:33 mirroring: F:\QStarcache: Hot sync incomplete: volume 45,
position 3861944: I/O error
12/20/2010 11:10:56 sdf_slave: sdf_sl_hw_search: sdf_dev_open: The device is not
ready.
12/20/2010 11:10:56 primary_sdf_migrator: hw mark on mirror search failed at
volume 45: The device is not ready.
12/20/2010 11:10:56 primary_sdf_migrator: tape_prime: hw mark on mirror search
failed at volume 45: Hot sync failed at volume 45 position 3861944: The device
is not ready.
12/20/2010 11:10:56 sdf_do_hotsync: Current Hot Sync status: main(Primary) at:
45/6565102, Primary at: 45/6565102, Secondary at: 45/3861944, Secondary not in
sync
12/20/2010 11:10:56 mirroring: F:\QStarcache: Hot sync incomplete: volume 45,
position 3861944: The device is not ready.
12/20/2010 11:34:01 JB: preunload: JB0 Drive 2 marked bad:
C:\QStar\dev\JB0\rdrive2: scsi start/stop: The request could not be performed
because of an I/O device error., SCSI driver error
12/20/2010 11:50:54 JB: preunload: JB0 Drive 2 marked bad:
C:\QStar\dev\JB0\rdrive2: scsi start/stop: The device is not ready., SCSI driver
error

Troubleshooting Guide—QStar HSM Archive Solutions 39

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 This generic error message can point to different failing components (drives, jukebox, or media).
The error means that a specific operation (for example, the read from a media for hot synchronization)
cannot be completed. The reason can be at the operating system's drivers level or on the hardware
level.

Solution
1. Escalate to QStar technical support so that they can connect and then verify and identify the
cause of the issue.
For information, see Opening a ticket with QStar technical support (refer to page 7).
Agfa provides instructions on how to fix this problem if third-party support is required either
from the operating system or hardware level.

Troubleshooting Guide—QStar HSM Archive Solutions 40

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Upgrading QStar HSM
A
For some software problems, upgrading QStar HSM can resolve the issue. Upgrades can be performed
by the Agfa Field Service Engineer or by the customer. Many support calls that require a software
upgrade are still managed by the QStar personnel; this impacts the length of time required to close
the call.

Upgrading QStar HSM 4.2.x to 4.3.x or 4.4.x

(Windows)
(Topic number: 140407)

Before starting an upgrade, stop all IMPAX tools. Ensure that no write or retrieve activities will be
performed on the mount point during the upgrade.
You can upgrade QStar HSM to resolve some software issues.

To upgrade QStar HSM 4.2.x to 4.3.x or 4.4.x (Windows)

1. Archive all primary data present in the cache for each integral volume.
a. Navigate to Integral Volumes > Migration View.
b. Select the integral volume (for example, tape_prime).
c. Click Start Archiving.
d. Wait until the red column value decreases to 0% (primary pages).
2. Unmount the volume, stop the QStar HSM daemon, and uninstall QStar HSM software.
3. Restart the system.
4. Install the new QStar HSM package using the same path as the previous version.
5. Claim the attached device, and restart the system.

Troubleshooting Guide—QStar HSM Archive Solutions 41

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 6. Switch to the License tab and point to the demo/permanent key.
Call QStar HSM technical support or send an email to license@qstar.com.
7. Click Devices > Jukebox Configuration.
8. Name the jukebox with the same name used in version 4.2.x.
9. Start the QStar HSM services.
10. Click Media > Online Media, and ensure that all information related to the media is correct.
11. Verify that all previous integral volumes are present.
12. Mount the integral volumes.
13. Restart IMPAX.
14. Verify that the mount point is available for archive and retrieve jobs.

Upgrading QStar HSM 4.2.x to 4.3.x or 4.4.x (Solaris)

(Topic number: 140424)

Before starting an upgrade, stop all IMPAX tools. Ensure that no write or retrieve activities will be
performed on the mount point during the upgrade.

Note:

If the mount point is also exported to a third-party server via NFS, unmount and unpublish
the share.

You can upgrade QStar HSM as a way to resolve some software issues.

To upgrade QStar HSM 4.2.x to 4.3.x or 4.4.x (Solaris)

1. Archive all data for each of the integral volume sets.
mmarc -e /mount_point
2. Unmount all integral volume sets.
unmountiv /mount_point
3. Stop all jukebox schedulers.

Important!
For safety, QStar suggests saving device and integral volume set database information
by running vllsdev device_name and vllsset -va. Redirect the output to a file, jbshut.jb.

4. Change to the QStar directory.

cd /opt/QStar

Troubleshooting Guide—QStar HSM Archive Solutions 42

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 5. To start the install, run this command:
./INSTALL
6. When prompted, from the menu, select Upgrade QStar Software.
7. Select the package for the upgrade.
For example, Sunos_10.5_64_5.0.19.tar.
8. When prompted, from the menu, select Exit.
9. When the upgrade has finished, change to the opt/QStar/license directory, and type
./installkey
10. To start QStar HSM services, change to the /opt/QStar/install directory, and type
./rc start.
11. To mount the integral volumes, change to the opt/QStar/bin directory, and type
./mountiv setname Mountpoint
12. Restart IMPAX
13. Verify that the mount point is available for archive and retrieve jobs.

Upgrading QStar HSM 4.3.x or 4.4.x to 5.0.x

(Windows)
(Topic number: 140418)

Before starting an upgrade, stop all IMPAX tools. Ensure that no write or retrieve activities will be
performed on the mount point during the upgrade.
The QStar 5.0 license is provided in file format. Before starting the upgrade, ensure that you have
internet access so that you can receive the response from the QStar license department.

Note:
The QStar 5.0 license file format is incompatible with the cache files for all 4.x version, so the
system administrator will be forced to mount all integral volume sets with a clean cache after
the upgrade.

To upgrade QStar HSM 4.3.x or 4.4.x to 5.0.x (Windows)

1. Archive all primary data present in the cache for each integral volume.
a. Switch to the Integral Volumes - Migration View tab.
b. Select the integral volume (for example, tape_prime).
c. Click Start Archiving.
d. Wait until the red column value decreases to 0% (primary pages).

Troubleshooting Guide—QStar HSM Archive Solutions 43

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 2. Click Integral Volumes > Volume Management > Properties, and clear the Mount on server
restart checkbox. Repeat this procedure for every integral volume.
3. Uninstall QStar 4.3.x. or 4.4.x and restart the system.
4. Install QStar 5.0.x, claim the boot device, and restart the system.
5. Store the license file in c:\qstar\license.
6. Click Devices > Jukebox Configuration.
7. Start the QStar HSM services.
8. Configure the jukebox.
9. Start QStar services.
10. Click Integral Volumes > Volume Management > Properties, and select the Clean cache and
Mount on server restart checkboxes.
11. Mount all integral volumes.
12. Restart IMPAX
13. Verify that the mount point is available for archive and retrieve jobs.

Upgrading QStar HSM 4.3.x or 4.4.x to 5.0.x (Solaris)

(Topic number: 140503)

Before starting an upgrade, stop all IMPAX tools. Ensure that no write or retrieve activities will be
performed on the mount point during the upgrade.
The QStar 5.0 license is provided in file format. Before starting the upgrade, ensure that you have
internet access so that you can receive the response from the QStar license department. The QStar
5.0 license file format is incompatible with the cache files for all 4.x versions, so the system
administrator will be forced to mount all integral volume sets with a clean cache after the upgrade.

Note:

If the mount point is also exported to a third-party server via NFS, unmount and unpublish
the share.

To upgrade QStar HSM 4.3.x or 4.4.x to 5.0.x (Solaris)

1. Archive all data for each of the integral volume sets.
mmarc -e /mount_point
2. Unmount all integral volume sets.
unmountiv /mount_point
3. Stop all jukebox schedulers.

Troubleshooting Guide—QStar HSM Archive Solutions 44

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Important!
To protect data, QStar recommends saving device and integral volume sets database
information by running vllsdev device_name and vllsset -va. Redirect the output to a
file, jbshut.jb.

4. Change to the QStar directory.

cd /opt/QStar
5. To start the install, run this command:
./INSTALL
6. When prompted, from the menu, select Uninstall QStar Software.
7. When prompted to save the QStar database, select Yes.
8. When prompted, from the menu, click Exit.
9. Rename the /opt/Qstar directory to /opt/QStar_old.
10. Create another directory named /opt/Qstar.
11. Unzip the installation package:
gunzip filename.tar.gz
12. Extract the installation package to the /opt/QStar directory.
tar -xvf filename.tar
13. Run the ./INSTALL script.
14. When prompted, from the menu, select Install QStar HSM.
Alternatively, select Install QStar Data Director.
15. After the software installs and the devices are claimed, from the menu, select Restore QStar
Databases.
16. Store the license file in the /opt/QStar/license directory.
17. Change to the /opt/QStar/Install directory, and run the following command:
./rc start
18. Mount the integral volumes using this command:
./mountiv -n “setname”“mount_point
19. Restart IMPAX
20. Verify that the mount point is available for archive and retrieve jobs.

Troubleshooting Guide—QStar HSM Archive Solutions 45

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Upgrading QStar HSM 5.0.x to 5.0.y or 5.1.x
(Windows)
(Topic number: 140421)

Before starting an upgrade, stop all IMPAX tools. Ensure that no write or retrieve activities will be
performed on the mount point during the upgrade.
The QStar HSM 5.1 license is provided in file format. Before starting the upgrade, ensure that you
have internet access so that you can receive the response from the QStar license department.

To upgrade QStar HSM 5.0.x to 5.0.y or 5.1.x (Windows)

1. Archive all primary data present in the cache for each integral volume.
a. Switch to the Integral Volumes - Migration View tab.
b. Select the integral volume (for example, tape_prime).
c. Click Start Archiving.
d. Wait until the red column value decreases to 0% (primary pages).
2. Uninstall QStar HSM. Select Yes when prompted to save the current database information.
3. Restart the system.
4. Install QStar HSM, claim the boot device, and restart the system.

Note:
When upgrading to QStar HSM 5.1.x, install the CBFS file system component when
prompted.

5. Store the license file in the c:\qstar\license folder.

6. Start the QStar HSM services.
7. Mount all integral volumes.
8. Restart IMPAX
9. Verify that the mount point is available for archive and retrieve jobs.

Upgrading QStar HSM 5.0.x to 5.0.y or 5.1.x (Solaris)

(Topic number: 140512)

Before starting an upgrade, stop all IMPAX tools. Ensure that no write or retrieve activities will be
performed on the mount point during the upgrade.

Troubleshooting Guide—QStar HSM Archive Solutions 46

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 Note:

If the mount point is also exported to a third-party server via NFS, unmount and unpublish
the share.

The QStar HSM 5.1 license is provided in file format. Before starting the upgrade, ensure that you
have internet access so that you can receive the response from the QStar license department.

Important!
To ensure a successful upgrade, do not copy the files used for an upgrade into /opt/QStar.
Doing so will cause the upgrade to fail.

To upgrade QStar HSM 5.0.x to 5.0.y or 5.1.x (Solaris)

1. Archive all data for each of the integral volume sets.
mmarc -e /mount_point
2. Unmount all integral volume sets.
unmountiv /mount_point
3. Stop all jukebox schedulers.

Important!
To protect data, QStar recommends saving device and integral volume sets database
information by running vllsdev device_name and vllsset -va. Redirect the output to a
file, jbshut.jb.

4. Change to the QStar directory.

cd /opt/QStar
5. To start the install, run this command:
./INSTALL
6. When prompted, from the menu, select Upgrade QStar Software.
7. When prompted, from the menu, select Exit.
8. After the upgrade has completed, change to the /opt/QStar/license directory, and type:
./installkey
9. To start QStar services, change to the /opt/QStar/install directory, and type:
./rc start
10. To mount the integral volumes, change to the /opt/QStar/bin directory, and type:
./mountiv setname Mountpoint
11. Restart IMPAX
12. Verify that the mount point is available for archive and retrieve jobs.

Troubleshooting Guide—QStar HSM Archive Solutions 47

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Glossary

C G
cache GUI

Temporary storage area for data on a Graphical user interface. Visual computer
computer’s local or external hard drives. environment that represents programs, files,
and options with graphical images, such as
icons, menus, and windows.
CIFS
Common Internet File System. This protocol H
defines a standard for accessing remote files. HSM
Regardless of operating system, users can share
files without having to install software. Hierarchical Storage Management. An HSM
archive system provides long-term storage of
data and access to data. Studies archived with
CLUI HSM are stored to a file system. A mount
Command Line User Interface. A point and subdirectory to store studies to is
command-line tool to help in the service of specified. The HSM system handles data
IMPAX MVF. CLUI allows you to execute SQL storage.
statements.
J
D jukebox archive
daemon An archive with one or more drives where
A background process that performs a media is loaded, with multiple slots that hold
specified operation at a predefined time or in the media for easy storage retrieval, and with
response to a specified event. a robotic changer to move media around
within the jukebox.
device
Collection of settings and information used
L
to represent an external system (real world logical volume
device) or internal process (system device). Pooled logical extents can be concatenated
Devices are managed in Service Tools using together into virtual disk partitions called
the Device Manager. logical volumes or LVs. Systems can use LVs
as raw block devices just like disk partitions:
creating mountable file systems on them, or
using them as swap storage. In computer
storage, logical volume management provides

Troubleshooting Guide—QStar HSM Archive Solutions 48

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 a method of allocating space on mass-storage
devices that is more flexible than conventional SCSI bus
partitioning schemes. The channel over which information is
communicated between the computer and the
M devices in the library.
mirror
A copy of a primary volume. The mirror can SNDB
be used to recover studies if the primary Site Name Database. This syntax defines how
volume is damaged or lost. site names are shortened and standardized in
SMMS. The format used is
mount point country_hospital-name_region.
A directory or file at which a new file system
is made accessible. syslog
An Internet Engineering Task Force (IETF)
N standard for logging system events.
NFS
NFS stands for Network File System, a file T
system developed by Sun Microsystems, Inc. transaction log
It is a client/server system that allows users to A database file where all changes to the
access files across a network and treat them as database are recorded. It is used by the SQL
though they resided in a local file directory. Server during automatic database recovery.
This is accomplished through the processes of See redo log.
exporting (the process by which an NFS server
provides remote clients with access to its files) V
and mounting (the process by which file
systems are made available to the operating volume
system and the user). The NFS protocol is A volume refers to the division of data on the
designed to be independent of the computer, media. For example, if a tape has two sides,
operating system, network architecture, and each side is referred to as a separate volume.
transport protocol.

P
partition
An isolated section of memory on a mass
storage device.

S
SCSI
Small Computer System Interface. A
communication interface used between the
archive and the Archive Server.

Troubleshooting Guide—QStar HSM Archive Solutions 49

Agfa Company Confidential—Subject to Non-Disclosure Obligation
Index

A unavailable...............................................9
devices
aborted command........................................31 bus reset.................................................37
archiving no space available..................................14
backlog in queue...................................15 not configured or claimed....................11
not possible......................................33, 38 not ready................................................39
unavailable.....................10, 11, 14, 17, 27 unresponsive..........................................30
audience requirements...................................6 disconnection of network drive..................18
available media.............................................13 documentation
giving feedback........................................3
B warranty statement.................................2
drive configuration file................................34
blank check...................................................33 drives
blank media unresponsive..........................................39
unavailable.............................................13
bring online media.......................................10
bus device reset............................................37 E
email
C documentation feedback........................3
erased media
cabling problem...........................................27 unavailable.............................................13
cache size......................................................17
CIFS sharing.................................................23
claimed devices............................................11 F
configuration issues.......................................9 full file mode
copyright information...................................2 configuring file systems........................21
covered file system error........................10, 33
G
D
getting started.................................................6
daemons.......................................................11
damaged chip on media...............................28 H
database corruption.....................................17
database overwrite failure............................33 hardware error
data phase error............................................31 internal target failure.......................30, 38
data retrieval media ejection failure............................29
services stop...........................................18 media load failure..................................29
unavailable...........................11, 14, 15, 17 hot sync.........................................................37
data storage how to troubleshoot QStar HSM..................7

Troubleshooting Guide—QStar HSM Archive Solutions 50

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 I P
I/O device error............................................39 performance tuning.....................................20
intended audience..........................................6
internal target failure.............................30, 38 Q
QStar
J technical support.....................................7
jammed media..............................................29 QStar HSM
jukebox performance tuning..............................20
bus device reset......................................37 troubleshooting configuration issues.....9
unresponsive....................................30, 39 troubleshooting requirements................6
troubleshooting strategies.......................7
L troubleshooting technical issues...........25
upgrading..............................................41
library configuration....................................23 QStar HSM 4.2.x (Solaris)
library operations upgrading to 4.3.x or 4.4.x....................42
concurrence between library QStar HSM 4.2.x (Windows)
operations..............................................15 upgrading to 4.3.x or 4.4.x....................41
library problem............................................27 QStar HSM 4.3.x (Solaris)
log files............................................................6 upgrading to 4.4.x or 5.0.x....................44
QStar HSM 4.3.x or 4.4.x (Windows)
M upgrading to 5.0.x.................................43
QStar HSM 5.0.x (Solaris)
MAM not accessible.....................................28
upgrading to 5.0.y or 5.1.x....................46
manufacturer’s responsibility........................2
QStar HSM 5.0.x (Windows)
maximum transfer size................................22
upgrading to 5.0.y or 5.1.x....................46
media
queue backlog...............................................15
damaged chip........................................28
ejection failure.......................................29
not added to set.....................................14 R
not present.............................................13 read performance
unavailable.............................................13 improving..............................................21
unreadable.............................................28 real memory
unresponsive..........................................39 forcing applications to use....................24
medium error...............................................26 recorded entity.............................................26
memory use..................................................24 registered trademarks....................................2
requirements for logging support issues.......7
N resources
temporarily unavailable........................36
network drive
retrieval
disconnected..........................................18
not possible......................................33, 38
new media
unavailable.............................................13
S
O SCSI drive error............................................39
SCSI log..........................................................6
offline media................................................10
SCSI registry utility......................................22

Troubleshooting Guide—QStar HSM Archive Solutions 51

Agfa Company Confidential—Subject to Non-Disclosure Obligation
 SCSI transfer rate.........................................23 unit CRC error.............................................27
services unmounting services
do not start......................................11, 34 during rollover......................................18
stop/unmount during rollover.............18 upgrade procedures.....................................41
stop/unmount during write/read from upgrading QStar HSM 4.2.x .................41, 42
volume...................................................18 upgrading QStar HSM 4.3.x or 4.4.x.....43, 44
SMB timeout................................................20 upgrading QStar HSM 5.0.x........................46
Solaris
configuring full file mode.....................21 V
syslog file..................................................6
upgrading QStar HSM 4.2.x to 4.3.x or volume management.....................................9
4.4.x........................................................42 volume set
upgrading QStar HSM 4.3.x or 4.4.x to cannot mount..................................17, 36
5.0.x........................................................44 inaccessible............................................18
upgrading QStar HSM 5.0.x to 5.0.y or
5.1.x........................................................46 W
stopping services
warranty statements.......................................2
during rollover......................................18
Windows
study retrieval
configuring full file mode.....................21
failures....................................................15
setting memory use priority.................24
unavailable.........................................9, 11
SMB timeout.........................................20
suggestions for documentation.....................3
syslog file..................................................6
syslog file
upgrading QStar HSM 4.2.x to 4.3.x or
location....................................................6
4.4.x........................................................41
upgrading QStar HSM 4.3.x or 4.4.x to
T 5.0.x........................................................43
tape devices upgrading QStar HSM 5.0.x to 5.0.y or
improving read performance................21 5.1.x........................................................46
transfer size settings..............................22 writing media offline...................................10
tape media read failure................................26
target unavailable.........................................38
technical issues.............................................25
technical support
QStar........................................................7
termination problem...................................27
topics in guides and Knowledge Bases
giving feedback on..................................3
trademarks......................................................2
transfer size...................................................22
troubleshooting configuration issues............9
troubleshooting requirements.......................6
troubleshooting strategies.............................7
troubleshooting technical issues.................25

U
unavailable resources...................................36

Troubleshooting Guide—QStar HSM Archive Solutions 52

Agfa Company Confidential—Subject to Non-Disclosure Obligation