path_id is not implemented for SAS drives

[Mario Limonciello]

Binary package hint: casper

Version: 1.236

Normally casper will search all HDD's for a livefs allowing a recovery partition to be recognized. In the scenario that a HDD is hooked up to a SAS controller, it appears that casper is not recognizing it as a valid device.

Looking at the udevadm info output, ID_PATH is not being set for this device, which casper appears to depend upon.

# /sbin/udevadm info -p /block/sdb -q all

P: /devices/pci0000:00/0000:00:1c.0/0000:05:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sdb
N: sdb
W: 46
S: block/8:16
S: disk/by-id/ata-SAMSUNG_HD083GJ_S1VBJ90S739669
S: disk/by-id/scsi-SATA_SAMSUNG_HD083GJ_S1VBJ90S739669
S: disk/by-id/wwn-0x50024e9200c27f94
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1c.0/0000:05:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sdb
E: MAJOR=8
E: MINOR=16
E: DEVNAME=/dev/sdb
E: DEVTYPE=disk
E: SUBSYSTEM=block
E: ID_ATA=1
E: ID_TYPE=disk
E: ID_BUS=ata
E: ID_MODEL=SAMSUNG_HD083GJ
E: ID_MODEL_ENC=SAMSUNG\x20HD083GJ\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=1AC01171
E: ID_SERIAL=SAMSUNG_HD083GJ_S1VBJ90S739669
E: ID_SERIAL_SHORT=S1VBJ90S739669
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=20
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=20
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM=1
E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=128
E: ID_ATA_FEATURE_SET_PUIS=1
E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=1
E: ID_ATA_FEATURE_SET_APM_CURRENT_VALUE=254
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_WWN=0x50024e9200c27f94
E: ID_WWN_WITH_EXTENSION=0x50024e9200c27f94
E: ID_SCSI_COMPAT=SATA_SAMSUNG_HD083GJ_S1VBJ90S739669
E: ID_PART_TABLE_TYPE=dos
E: UDISKS_PRESENTATION_NOPOLICY=0
E: UDISKS_PARTITION_TABLE=1
E: UDISKS_PARTITION_TABLE_SCHEME=mbr
E: UDISKS_PARTITION_TABLE_COUNT=2
E: UDISKS_ATA_SMART_IS_AVAILABLE=1
E: DEVLINKS=/dev/block/8:16 /dev/disk/by-id/ata-SAMSUNG_HD083GJ_S1VBJ90S739669 /dev/disk/by-id/scsi-SATA_SAMSUNG_HD083GJ_S1VBJ90S739669 /dev/disk/by-id/wwn-0x50024e9200c27f94

[James Ferguson (jamesf)]

Appears to be a udev bug.

Attached is an strace of the path_id command. It appears to be trying to treat the device as firewire. Also attaching this info to the other bug.

lstat64("/sys/devices/pci0000:00/0000:00:1c.0/0000:05:00.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/ieee1394_id", 0xbfdbfd6c) = -1 ENOENT (No such file or directory)

[Mario Limonciello (superm1)]

if you look at extras/path_id/path_id.c there is no code for the SAS case right now, so I'd suspect someone will have to go and implement that handler.

static struct udev_device *handle_scsi_sas(struct udev_device *parent, char **path)
{
        return NULL;
}

[stevecs (stevecs)]

I see the exact same thing here with LSI HBA's (9200-8E's/LSI2008 chipset) on numerous external drives under 10.04.2LTS

complete strace output and udevadm attached.

[stevecs (stevecs)]

note, that path_id appears to be fixed with v1.71. so a back-port to 10.04 would seem to be in order.

[Mario Limonciello (superm1)]

Yeah, I can confirm path_id from udev 172 populates the SAS controller on my server now. I'll mark the bug accordingly.