HPE Smart Array P420i - no drives detected

[Kegelcizer]

I've got 2 raid 1 arrays, 2 disks each.

Using the docker version, I gave it the drives /dev/sda and /dev/sdb that I've gathered with lsblk.

Then I ran docker exec scrutiny /scrutiny/bin/scrutiny-collector-metrics run, the webpage gives the same message that I need to run the collector.

Inside the container smartctl --scan returns nothing.

But if I run smartctl with "cciss,0-3", I can see all my 4 disks, in the container and in the host.

I'd appreciate any help! Thank you.

[rarobert]

I was able to read drives from my P420i in raid, and my P222 in HBA, by modifying the collector.yaml file.

The example.collector.yaml file is a good start, but you just want to add something like this (modifying devices as required).

devices:
    - device: /dev/sda
      type:
        - 'cciss,0'
        - 'cciss,1'
    - device: /dev/sdb
      type:
        - 'cciss,0'
        - 'cciss,1'

Upload the collector.yaml to your persistent 'scrutiny/config' directory and restart the container, drives should appear automatically.

[Kegelcizer]

That worked, I've got data now. Thank you!

Still one thig is weird for sda, it only shows the last cciss:

devices: - device: /dev/sda type: - 'cciss,0' - 'cciss,1'
Shows only cciss 1

devices: - device: /dev/sda type: - 'cciss,1' - 'cciss,0'
Shows only cciss 0

devices: - device: /dev/sda type: - 'cciss,0'
Shows only cciss 0

devices: - device: /dev/sda type: - 'cciss,1'
Shows only cciss 1

Update:
The drive displayed for both cciss 0 and 1 is the same one and it is actually 0.
So the problem is cciss 1 is not working.

Can't seem to format those, new lines are ignored in code block.

[rarobert]

I’ve recently noticed this too, although my drives are working fine. It looks as if the way scrutiny interprets the smart data is causing it. I’ve read that the uuid is used as an is for drives in the database and if the uuid is the same for the overall disk then it doesn’t matter which drive type is specified, only the last will be displayed and tracked.

This might be fixed alongside the name feature, or others like #144.

[Kegelcizer]

Thanks for the info!
Seems solved to me.

[Ziut3k-dev]

Smth still wronk

[Ziut3k-dev]

Collector don't parse config file properly

[Ziut3k-dev]

#724