That was the answer!!!!! THANK YOU!!!!!
Changed sch0 to sg1 (after verifying the autochanger is at sg1) and did
the: update slots scan, and it worked!
Greg
On Monday, April 13, 2026 at 6:36:25 AM UTC-5 Bruno Friedmann
(bruno-at-bareos) wrote:
> And by the way change the value of
> Maximum File Size to something suitable for real LTO7/8/9 hardware ~100GB
> or more would works.
>
> On Monday, 13 April 2026 at 10:02:25 UTC+2 Bruno Friedmann
> (bruno-at-bareos) wrote:
>
>> Did you try to use the real device /dev/sgXXX for the changer. I've seen
>> several failure using /dev/sch0 (and redo a change in our documentation
>> recently)
>> It's seems kernel/udev rules are filtering essential scsi io command to
>> manipulate correctly the autochanger.
>>
>> Recently I've rechange working sch0 to generic sgX device for my
>> autochanger and everything work correctly since then,
>> On Monday, 13 April 2026 at 09:13:13 UTC+2 Gregory West wrote:
>>
>>> I did the mtx command, and it worked perfectly:
>>> root@backup:~# mtx -f /dev/sch0 status
>>> Storage Changer /dev/sch0:1 Drives, 8 Slots ( 0 Import/Export ) Data
>>> Transfer Element 0:Empty
>>> Storage Element 1:Full :VolumeTag=DBW501L5
>>> Storage Element 2:Full :VolumeTag=DBW502L5
>>> Storage Element 3:Empty
>>> Storage Element 4:Empty
>>> Storage Element 5:Empty
>>> Storage Element 6:Empty
>>> Storage Element 7:Empty
>>> Storage Element 8:Empty
>>> root@backup:~#
>>>
>>> Greg
>>> On Sunday, April 12, 2026 at 12:35:41 PM UTC-5 Oleg Cherkasov wrote:
>>>
>>>> On 11.04.2026 20:41, Gregory West wrote:
>>>> > OK now I am really confused. sch0 WAS showing up as cd/dvd now it
>>>> is
>>>> > showing up as mediummx. This is after I added bareos to the sudo
>>>> group.
>>>> > dumb question. I am running bconsole as root. Is this an issue?
>>>> > When I try and run bconsole as a generic user get the
>>>> following: Config
>>>> > error: Cannot open config file "/etc/bareos/bconsole.conf":
>>>> Permission
>>>> > denied
>>>> >
>>>> > Going to add user to bearos group.
>>>> > Greg
>>>> >
>>>> > On Saturday, April 11, 2026 at 11:26:36 AM UTC-5 Gregory West wrote:
>>>> >
>>>> > The TAPE group is OK, but not the complete story. For some reason
>>>> > my setup has sch0 (the name given to my autochanger) as a cd/dvd. I
>>>> > have added CRROM to by bareos user and i still does not work.
>>>> > Looking into have to change sch0 from CDROM to TAPE.
>>>> > root@backup:~# lsscsi
>>>> > [0:0:0:0] tape HP Ultrium 5-SCSI Z6DW /dev/st0
>>>> > [0:0:0:1] mediumx HP 1x8 G2 AUTOLDR 4.30 /dev/sch0
>>>> > [3:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sda
>>>> > [4:0:0:0] disk ATA WDC WD5000AAKX-0 1H19 /dev/sdb
>>>> > [5:0:0:0] cd/dvd HL-DT-ST DVD-RAM GH10N EX02 /dev/sr0
>>>> > [6:0:0:0] disk ATA WDC WD7501AALS-0 0K05 /dev/sdc
>>>> >
>>>> It seems you are on the correct path but need to locate the HP
>>>> Autoloader device. Have you tried to run as root:
>>>>
>>>> mtx -f /dev/sch0 status
>>>>
>>>> It shall print the status of the Drive and all slots. If you are not
>>>> sure about the device name, then try all available devices that look
>>>> like Autoloader.
>>>>
>>>> As far as I can recall, on Linux, I had to update the udev
>>>> configuration
>>>> to specify the exact /dev/sg? name using the UUID of the device. If the
>>>> device is not customized in udev, then after a reboot, the device
>>>> jumped
>>>> between /dev/sg{1,2,3}. If you are using `lsscsi -g` then the last
>>>> column would be the device name you need to try with mtx command.
>>>>
>>>> Regarding the bconsole, I always run it as root, and the actual DIR
>>>> daemon is running as the bareos user. I do not think it is an issue.
>>>>
>>>>
>>>> Cheers,
>>>> Oleg
>>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/698c1ced-37c5-464f-b430-fc58040061bdn%40googlegroups.com.
