Maybe someone forgot to label this volume. checkout libv CHECKLABEL=barcode should work. And use label libv to label this volume again.
Regard, Karel -----Oorspronkelijk bericht----- Van: Zosimo Noriega [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 4 november 2003 10:44 Aan: [EMAIL PROTECTED] Onderwerp: Volume could not be mounted in drives Hi All TSMers, I got these error messages from one of the volume. This is a scratch volume. If you encountered this problem before please share to me the solutions. ... 3584LIB A00097 Private TSMSRV1 Data 1,099 3584LIB A00098 Scratch 1,098 3584LIB A00099 Private TSMSRV1 Data 1,096 ** 11/04/03 11:43:00 ANR8381E LTO volume A00098 could not be mounted in drive DRIVE4 (/dev/rmt4). 11/04/03 12:16:27 ANR2017I Administrator ZBN3669 issued command: CHECKOUT LIBVOLUME 3584LIB A00098 CHECKLABEL=YES FORCE=NO REMOVE=YES 11/04/03 12:16:27 ANR0984I Process 1087 for CHECKOUT LIBVOLUME started in the BACKGROUND at 12:16:27. 11/04/03 12:16:27 ANR8434I CHECKOUT LIBVOLUME: Operation for volume A00098 in library 3584LIB started as process 1087. 11/04/03 12:16:27 ANR0609I CHECKOUT LIBVOLUME started as process 1087. 11/04/03 12:16:28 ANR8437E CHECKOUT LIBVOLUME for volume A00098 in library 3584LIB failed. 11/04/03 12:16:28 ANR0985I Process 1087 for CHECKOUT LIBVOLUME running in the BACKGROUND completed with completion state FAILURE at 12:16:28. Thanks in advance, Zosi Noriega Analyst, Data Storage SSD/IS&T - ITD ADNOC Abu Dhabi - UAE Tel. # 009712 6024987
