Am 2017-09-20 um 21:58 schrieb Nathan Stratton Treadway:
> On Wed, Sep 20, 2017 at 20:56:22 +0200, Stefan G. Weichinger wrote:
>>
>> put the controller + drive back into the gentoo server
>>
> [...]
>> Maybe someone on the list with similar hardware could compare "dmesg" ?
>
> Does Gentoo have the "udevadm" command installed? If so, what does
> $ udevadm info -a -n /dev/st0
>
> (or
> $ udevadm info --attribute-walk --name /dev/st0
> in long-option format)
>
> give you? Hopefully it will show you the set of kernel modules
> (DRIVERS=) involved in providing the /dev/st0 device file
I am sorry to get a bit off topic on the amanda-users-ml now ...
I filed an issue at
https://github.com/eLvErDe/hwraid/issues/71
maybe that helps.
And I did the suggested:
# udevadm info -a -n /dev/st0
looking at device
'/devices/pci:00/:00:01.1/:02:00.0/host6/target6:0:4/6:0:4:0/scsi_tape/st0':
KERNEL=="st0"
SUBSYSTEM=="scsi_tape"
DRIVER==""
ATTR{default_blksize}=="-1"
ATTR{default_compression}=="-1"
ATTR{default_density}=="-1"
ATTR{defined}=="1"
ATTR{options}=="0x0107"
looking at parent device
'/devices/pci:00/:00:01.1/:02:00.0/host6/target6:0:4/6:0:4:0':
KERNELS=="6:0:4:0"
SUBSYSTEMS=="scsi"
DRIVERS=="st"
ATTRS{device_blocked}=="0"
ATTRS{eh_timeout}=="10"
ATTRS{evt_capacity_change_reported}=="0"
ATTRS{evt_inquiry_change_reported}=="0"
ATTRS{evt_lun_change_reported}=="0"
ATTRS{evt_media_change}=="0"
ATTRS{evt_mode_parameter_change_reported}=="0"
ATTRS{evt_soft_threshold_reached}=="0"
ATTRS{iocounterbits}=="32"
ATTRS{iodone_cnt}=="0x316574"
ATTRS{ioerr_cnt}=="0x4"
ATTRS{iorequest_cnt}=="0x316574"
ATTRS{model}=="Ultrium 3-SCSI "
ATTRS{queue_depth}=="256"
ATTRS{queue_ramp_up_period}=="12"
ATTRS{queue_type}=="none"
ATTRS{rev}=="Q51D"
ATTRS{scsi_level}=="6"
ATTRS{state}=="running"
ATTRS{timeout}=="900"
ATTRS{type}=="1"
ATTRS{vendor}=="HP "
looking at parent device
'/devices/pci:00/:00:01.1/:02:00.0/host6/target6:0:4':
KERNELS=="target6:0:4"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device
'/devices/pci:00/:00:01.1/:02:00.0/host6':
KERNELS=="host6"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci:00/:00:01.1/:02:00.0':
KERNELS==":02:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="megaraid_sas"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x010400"
ATTRS{config}==""
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{d3cold_allowed}=="1"
ATTRS{device}=="0x0073"
ATTRS{dma_mask_bits}=="64"
ATTRS{enable}=="1"
ATTRS{irq}=="17"
ATTRS{local_cpulist}=="0-31"
ATTRS{local_cpus}==""
ATTRS{msi_bus}==""
ATTRS{subsystem_device}=="0x1177"
ATTRS{subsystem_vendor}=="0x1734"
ATTRS{vendor}=="0x1000"
looking at parent device '/devices/pci:00/:00:01.1':
KERNELS==":00:01.1"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{d3cold_allowed}=="0"
ATTRS{device}=="0x0155"
ATTRS{dma_mask_bits}=="32"
ATTRS{enable}=="1"
ATTRS{irq}=="41"
ATTRS{local_cpulist}=="0-31"
ATTRS{local_cpus}==""
ATTRS{msi_bus}=="1"
ATTRS{subsystem_device}=="0x11d7"
ATTRS{subsystem_vendor}=="0x1734"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci:00':
KERNELS=="pci:00"
SUBSYSTEMS==""
DRIVERS==""
--- so only megaraid_sas involved here, as it seems.
