search

Drive-Trust-Alliance / sedutil

DTA sedutil Self encrypting drive software
613 stars 236 forks source link

Syslinux HBA/SSD detection issue #199

Open CRWdog193 opened 6 years ago

CRWdog193 commented 6 years ago

I have a machine with 2 Samsung 850 EVOs attached to a LSi-2008 (mpt2sas) HBA, and a Samsung 850 Pro attached to an on-board LSi-1068E (mptsas).

No drive attached to the 1068E will be detected by the syslinux in the BIOS32 image.

BIOS32 boots fine, but only detects the drives attached to the 2008; no sign of (e.g. there are no /dev/sd nodes for) any drives attached to the 1068E/mobo port.

I tried removing the drives attached to the 2008; no change.

Removed the 2008 altogether, to check for PCI-ordering issues (HBA is lower-numbered than on-board in bus enumeration), no change.

Tried this on another, identical (CPUs, RAM, mobo BIOS) machine on which I'd previously cross-flashed the 1068E to LSI -IT firmware over the stock Dell -IR firmware; no change.

Looks like a syslinux issue?

Interestingly, if I run the Arch Linux installer (also syslinux/ISOlinux 6.03 based) and select HDT, this utility detects the 1068E (and any disks attached there) but NOT anything attached to the 2008...

r0m30 commented 6 years ago

It certainly sounds like a syslinux issue, but the Arch test really muddies the water. Which PBA image are you using?

CRWdog193 commented 6 years ago

Sorry, only just seen the question.

The issue seems to be with the syslinux itself; the PBA was contained in the unmodified binary BIOS32.img from the Wiki here; version 1.15.1.

PBA seems to simply be reflecting whatever it gets given to it by the syslinux/udev/whatever; in other words it only scans devices nodes populated in /dev, and syslinux from different sources apparently can behave differently...