Re: Bacula or Drive problem?

Udo Kaune schrieb am 13.06.25 um 23:47:
> Hi Thorsten,
>
> Did you reboot the box recently and did by any chance your devices get 
> reordered?
> What does lsscsi -g show and does that correspond to your 
> bacula-sd.conf entries?
>
> Best regards, Udo
>
Hi Udo,

yes, I regularily reboot the system for maintenance:

sudo lsscsi -g
[0:0:0:0]    disk    Areca    ARC-1883-VOL#000 R001  /dev/sda   /dev/sg0
[0:0:0:1]    disk    Areca    ARC-1883-VOL#001 R001  /dev/sdb   /dev/sg1
[0:0:0:2]    disk    Areca    Data6            R001  /dev/sdc   /dev/sg2
[0:0:0:4]    disk    Areca    VOL_Data4        R001  /dev/sdd   /dev/sg3
[0:0:16:0]   process Areca    RAID controller  R001  -          /dev/sg4
[1:0:0:0]    enclosu ATTO     VirtualSES       0001  -          /dev/sg6
[1:0:1:0]    tape    IBM      ULTRIUM-HH9      R3G1  /dev/st0   /dev/sg7
[1:0:1:1]    mediumx BDT      FlexStor II      6.21  /dev/sch0  /dev/sg8



That looks very susual and it worked in the last months with sg7

Now, just for the fun of it I used mtx -f /dev/sg8 status additionally 
and got:

mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Unit Attention
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 2A
mtx: Request Sense: Additional Sense Qualifier = 01
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
Mode sense (0x1A) for Page 0x1D failed
  Storage Changer /dev/sg8:1 Drives, 24 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 13 Loaded):VolumeTag = 
000050CU
      Storage Element 1:Full :VolumeTag=000003L9
      Storage Element 2:Full :VolumeTag=000006L9
      Storage Element 3:Full :VolumeTag=000009L9
      Storage Element 4:Full :VolumeTag=000012L9
      Storage Element 5:Full :VolumeTag=000002L9
      Storage Element 6:Full :VolumeTag=000005L9
      Storage Element 7:Full :VolumeTag=000008L9
      Storage Element 8:Full :VolumeTag=000011L9
      Storage Element 9:Full :VolumeTag=000001L9
      Storage Element 10:Full :VolumeTag=000004L9
      Storage Element 11:Full :VolumeTag=000007L9
      Storage Element 12:Full :VolumeTag=000010L9
      Storage Element 13:Empty
      Storage Element 14:Full :VolumeTag=000021L9
      Storage Element 15:Full :VolumeTag=000018L9
      Storage Element 16:Full :VolumeTag=000015L9
      Storage Element 17:Full :VolumeTag=000023L9
      Storage Element 18:Full :VolumeTag=000020L9
      Storage Element 19:Full :VolumeTag=000017L9
      Storage Element 20:Full :VolumeTag=000014L9
      Storage Element 21:Full :VolumeTag=000022L9
      Storage Element 22:Full :VolumeTag=000019L9
      Storage Element 23:Full :VolumeTag=000016L9
      Storage Element 24:Full :VolumeTag=000013L9


As this surprisingly looked more like a changer, despite the error 
code=70, I changed the changer path in bacula-sd.conf to /dev//sg8

Then I ran a backup (catalogue to make it quick):

*And to my surprise - the backup worked again. *

Now, this is a big surprise. I would not check the devices if despite 
many reboots (both, host and changer) all of a sudden the device is not 
correct. To be honest, that would probably be something I would not have 
looked into....

Thanks. You made my weekend.

Cheers

T

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users