No DISK devices reported on systems with RAID controllers

Bug #942548 reported by Brendan Donegan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Critical
Brendan Donegan
0.9
Fix Released
Critical
Unassigned

Bug Description

This is directly related to https://bugs.launchpad.net/checkbox/+bug/940249 and I give my apologies for not addressing this in the same merge request.

Servers systems which use a RAID controller as their main backing storage will have a DISK device with the ID_BUS value of 'cciss', as seen here:

P: /devices/pci0000:00/0000:00:0d.0/0000:03:00.0/cciss0/c0d0/block/cciss!c0d0
N: cciss/c0d0
W: 53
S: block/104:0
S: disk/by-id/cciss-3600508b1001030374541443833300300
S: disk/by-path/pci-0000:03:00.0
S: disk/by-id/wwn-0x600508b1001030374541443833300300
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:0d.0/0000:03:00.0/cciss0/c0d0/block/cciss!c0d0
E: MAJOR=104
E: MINOR=0
E: DEVNAME=/dev/cciss/c0d0
E: DEVTYPE=disk
E: SUBSYSTEM=block
E: ID_SCSI=1
E: ID_VENDOR=HP
E: ID_VENDOR_ENC=HP\x20\x20\x20\x20\x20\x20
E: ID_MODEL=LOGICAL_VOLUME
E: ID_MODEL_ENC=LOGICAL\x20VOLUME\x20\x20
E: ID_REVISION=2.74
E: ID_TYPE=disk
E: ID_SERIAL=3600508b1001030374541443833300300
E: ID_SERIAL_SHORT=600508b1001030374541443833300300
E: ID_WWN=0x600508b100103037
E: ID_WWN_VENDOR_EXTENSION=0x4541443833300300
E: ID_WWN_WITH_EXTENSION=0x600508b1001030374541443833300300
E: ID_SCSI_SERIAL=5001438007EAD830
E: ID_BUS=cciss
E: ID_PATH=pci-0000:03:00.0
E: ID_PART_TABLE_TYPE=dos
E: DEVLINKS=/dev/block/104:0 /dev/disk/by-id/cciss-3600508b1001030374541443833300300 /dev/disk/by-path/pci-0000:03:00.0 /dev/disk/by-id/wwn-0x600508b1001030374541443833300300

This needs to be addressed in the code of the udevadm parser as it only acknowledges 'ata' and 'scsi' devices at the moment.

Related branches

Changed in checkbox:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Brendan Donegan (brendan-donegan)
Revision history for this message
Marc Tardif (cr3) wrote :

On which system(s) is this bug occuring? Please don't just say all the systems using the cciss driver, a CID would be much appreciated.

Revision history for this message
Marc Tardif (cr3) wrote :

Nevermind: 200810-1113, 201105-8033, 200911-4613, 200902-1667, 200712-197, 201005-5725, 200906-2959, 201010-6628, 200902-1665, 200906-2958, 201009-6568, 200804-267, 201011-6764, 201009-6563, 201009-6566, 200911-4610, 201009-6570, 200712-191, 200911-4612, 201107-8315, 200906-2960, 200712-189, 201108-8817, 201104-7600, 200909-3751, 201011-6765, 201103-7388, 200712-190, 201009-6565, 201010-6625, 201010-6627, 201107-8316, 201009-6564, 200902-1663, 201201-10335, 200804-257, 200810-1111, 200902-1670, 201005-5728, 201005-5724, 201011-6769, 201011-6766, 200810-1117, 201009-6567 and 200712-199.

Changed in checkbox:
status: In Progress → Fix Committed
Daniel Manrique (roadmr)
Changed in checkbox:
milestone: none → 0.13.4
Changed in checkbox:
status: Fix Committed → Fix Released
status: Fix Released → Fix Committed
Ara Pulido (ara)
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.