Opened 4 days ago
Last modified 4 days ago
#1911 new enhancement
Add SAS support for Windows CSMI RAID drivers
| Reported by: | Bab | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | unscheduled |
| Component: | all | Version: | |
| Keywords: | csmi windows | Cc: |
Description
I have a physical server with 2 SAS disk and I have created a logical disk with raid0 and did not create second disk. now It cannot detect second disk
What is the issue ? what should I do now?
C:\Program Files\smartmontools\bin>smartctl -a /dev/sdd -d scsi smartctl 7.4 2023-08-01 r5530 [x86_64-w64-mingw32-2022-21H2] (sf-7.4-1) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HP Product: LOGICAL VOLUME Revision: 6.00 Compliance: SPC-3 User Capacity: 299,966,445,568 bytes [299 GB] Logical block size: 512 bytes Logical Unit id: 0x600508b1001c946bd66ba494be33fc2b Serial number: 00143803006BD80 Device type: disk Local Time is: Sat Nov 30 16:31:02 2024 PST SMART support is: Unavailable - device lacks SMART capability. === START OF READ SMART DATA SECTION === Current Drive Temperature: 0 C Drive Trip Temperature: 0 C Error Counter logging not supported Device does not support Self Test logging
Attachments (1)
Change History (13)
comment:1 by , 4 days ago
| Keywords: | windows added |
|---|---|
| Milestone: | → undecided |
| Priority: | major → minor |
| Type: | defect → enhancement |
comment:2 by , 4 days ago
I am using physical server HPE DL380 G8 and reside that Smart Array P420i Controller
Also I have inset 2 disks on the server . As need to install OS first of all create a logical disk for one disk (Raid0) but did not any change on second disk also not use it in the raid .
Now smartctl cannot detect second disk that does not include in raid and just resides on the server
comment:4 by , 4 days ago
This is my output :
C:\Program Files\smartmontools\bin>smartctl -r ioctl,2 --scan
\\.\PhysicalDrive0: successfully opened
IOCTL_STORAGE_QUERY_PROPERTY returns:
Vendor: "DGC "
Product: "LUNZ "
Revision: "0533"
Removable: No
BusType: 0x06
\\.\PhysicalDrive1: successfully opened
IOCTL_STORAGE_QUERY_PROPERTY returns:
Vendor: "DGC "
Product: "LUNZ "
Revision: "0533"
Removable: No
BusType: 0x06
\\.\PhysicalDrive2: successfully opened
IOCTL_STORAGE_QUERY_PROPERTY returns:
Vendor: "DGC "
Product: "LUNZ "
Revision: "0533"
Removable: No
BusType: 0x06
\\.\PhysicalDrive3: successfully opened
IOCTL_STORAGE_QUERY_PROPERTY returns:
Vendor: "HP "
Product: "LOGICAL VOLUME "
Revision: "6.00"
Removable: No
BusType: 0x08
SMART_GET_VERSION failed, Error=1117
\\.\Scsi0:: successfully opened
IOCTL_SCSI_MINIPORT(CC_CSMI_1) failed, Error=1
\\.\Scsi1:: successfully opened
IOCTL_SCSI_MINIPORT(CC_CSMI_1) failed, Error=1
\\.\Scsi2:: successfully opened
IOCTL_SCSI_MINIPORT(CC_CSMI_1) failed, Error=1117
\\.\Scsi3:: successfully opened
IOCTL_SCSI_MINIPORT(CC_CSMI_1) failed, Error=1117
\\.\Scsi4:: successfully opened
IOCTL_SCSI_MINIPORT(CC_CSMI_1) succeeded, bytes returned: 204
CSMI_SAS_DRIVER_INFO:
Name: "HpSAMD.sys"
Description: "Smart Array SAS/SATA Controller Media Driver"
Revision: 8.0
IOCTL_SCSI_MINIPORT(CC_CSMI_20) succeeded, bytes returned: 2080
IOCTL_SCSI_MINIPORT(CC_CSMI_10) failed, ReturnCode=2
CSMI_SAS_PHY_INFO: NumberOfPhys=8
Phy[0] Port: 0
Type: 0x10, 0x10
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x08
PortIdent: 0x00
PhyIdent: 0x00, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 80, 50 00 c5 00 72 7a 66 fd
Phy[1] Port: 1
Type: 0x10, 0x10
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x08
PortIdent: 0x01
PhyIdent: 0x01, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 80, 50 00 c5 00 72 79 fe cd
Phy[2] Port: 2
Type: 0x10, 0x00
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x00
PortIdent: 0xff
PhyIdent: 0x02, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 80, 00 00 00 00 00 00 00 00
Phy[3] Port: 3
Type: 0x10, 0x00
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x00
PortIdent: 0xff
PhyIdent: 0x03, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 80, 00 00 00 00 00 00 00 00
Phy[4] Port: 4
Type: 0x10, 0x00
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x00
PortIdent: 0xff
PhyIdent: 0x04, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 84, 00 00 00 00 00 00 00 00
Phy[5] Port: 5
Type: 0x10, 0x00
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x00
PortIdent: 0xff
PhyIdent: 0x05, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 84, 00 00 00 00 00 00 00 00
Phy[6] Port: 6
Type: 0x10, 0x00
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x00
PortIdent: 0xff
PhyIdent: 0x06, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 84, 00 00 00 00 00 00 00 00
Phy[7] Port: 7
Type: 0x10, 0x00
InitProto: 0x0f, 0x00
TargetProto: 0x00, 0x00
PortIdent: 0xff
PhyIdent: 0x07, 0x00
SignalClass: 0x00, 0x00
Restricted: 0x00, 0x00
SASAddress: 50 01 43 80 30 06 bd 84, 00 00 00 00 00 00 00 00
\\.\Scsi0:: successfully opened
nvme probe failed: NVME_PASS_THROUGH failed, Error=1
\\.\Scsi1:: successfully opened
nvme probe failed: NVME_PASS_THROUGH failed, Error=1
\\.\Scsi2:: successfully opened
nvme probe failed: NVME_PASS_THROUGH failed, Error=1117
\\.\Scsi3:: successfully opened
nvme probe failed: NVME_PASS_THROUGH failed, Error=1117
\\.\Scsi4:: successfully opened
nvme probe failed: NVME_PASS_THROUGH failed, Error=1117
\\.\Scsi5:: Open failed, Error=2
\\.\Scsi6:: Open failed, Error=2
\\.\Scsi7:: Open failed, Error=2
\\.\Scsi8:: Open failed, Error=2
\\.\Scsi9:: Open failed, Error=2
\\.\Scsi10:: Open failed, Error=2
\\.\Scsi11:: Open failed, Error=2
\\.\Scsi12:: Open failed, Error=2
\\.\Scsi13:: Open failed, Error=2
\\.\Scsi14:: Open failed, Error=2
\\.\Scsi15:: Open failed, Error=2
\\.\Scsi16:: Open failed, Error=2
\\.\Scsi17:: Open failed, Error=2
\\.\Scsi18:: Open failed, Error=2
\\.\Scsi19:: Open failed, Error=2
\\.\Scsi20:: Open failed, Error=2
\\.\Scsi21:: Open failed, Error=2
\\.\Scsi22:: Open failed, Error=2
\\.\Scsi23:: Open failed, Error=2
\\.\Scsi24:: Open failed, Error=2
\\.\Scsi25:: Open failed, Error=2
\\.\Scsi26:: Open failed, Error=2
\\.\Scsi27:: Open failed, Error=2
\\.\Scsi28:: Open failed, Error=2
\\.\Scsi29:: Open failed, Error=2
\\.\Scsi30:: Open failed, Error=2
\\.\Scsi31:: Open failed, Error=2
/dev/sdd -d scsi # /dev/sdd, SCSI device
comment:5 by , 4 days ago
All 3 items include :
Vendor: "DGC"
are using HBA card that connect to san storage and does not local disk
Now It just detect Vendor: "HP" although there are 2 disks on the server
comment:6 by , 4 days ago
Result of IOCTL_STORAGE_QUERY_PROPERTY scan:
\\.\PhysicalDrive0: DGC LUNZ, BusType 0x06 (Fibre Channel) \\.\PhysicalDrive1: DGC LUNZ, BusType 0x06 (Fibre Channel) \\.\PhysicalDrive2: DGC LUNZ, BusType 0x06 (Fibre Channel) \\.\PhysicalDrive3: HP LOGICAL VOLUME, BusType 0x08 (RAID)
No additional non-RAID SAS device is reported.
Is the missing drive actually visible from Windows? If yes, which drive number does diskmgmt.msc report?
by , 4 days ago
comment:7 by , 4 days ago
Please see attached pic . This is from ILO that is showing there are 2 disks on the server
and I have create raid one of them . On the other hand we have to create logical driver on physical server to be visible on the os . So just one disk is visible by OS and the other disk can not detect . So what should I do now ? On the other hand If add second disk to raid smartctl cannot detect it to scan . Pleas see attach file . Also cannot detect in diskmgmt
comment:8 by , 4 days ago
Two SAS disk appear in the CSMI scan of the RAID controller:
CSMI_SAS_PHY_INFO: NumberOfPhys=8 Phy[0] Port: 0 Type: 0x10, 0x10 InitProto: 0x0f, 0x00 TargetProto: 0x00, 0x08 PortIdent: 0x00 PhyIdent: 0x00, 0x00 SignalClass: 0x00, 0x00 Restricted: 0x00, 0x00 SASAddress: 50 01 43 80 30 06 bd 80, 50 00 c5 00 72 7a 66 fd Phy[1] Port: 1 Type: 0x10, 0x10 InitProto: 0x0f, 0x00 TargetProto: 0x00, 0x08 PortIdent: 0x01 PhyIdent: 0x01, 0x00 SignalClass: 0x00, 0x00 Restricted: 0x00, 0x00 SASAddress: 50 01 43 80 30 06 bd 80, 50 00 c5 00 72 79 fe cd
Do you mean these?
If yes: smartctl supports SATA behind CSMI, but not SAS.
comment:9 by , 4 days ago
Thanks. Actually I cannot find out from your output but I think that is is correct . Does it your mean smartctl support sata controller and I am using sas controller ?
comment:10 by , 4 days ago
| Keywords: | csmi added |
|---|---|
| Milestone: | undecided → unscheduled |
| Summary: | smartctl cannot detect new physical disk without logical disk → Add SAS support for Windows CSMI RAID drivers |
Yes.
CMSI was a specification of a vendor independent management API for RAID controllers, including SCSI and ATA pass-through access to physical devices. The latter is required for smartctl. The standardization effort was discontinued after early drafts (2004), but device drivers for some controllers (e.g. Intel RST and apparently the controller of your system) still implement it.
Smartctl for Windows supports SATA devices behind CSMI capable drivers, but not SAS devices. So it may work (or not) for SATA disks behind this controller.
Changing ticket summary accordingly. Leaving ticket open as unscheduled just in case a volunteer with access to such hardware and plenty of time for testing is willing to provide a patch.
comment:11 by , 4 days ago
Is that possible smartctl can detect disk and work on Linux instead of windows ?
comment:12 by , 4 days ago
Possibly, please see smartctl man page or the RAID support wiki page for different -d TYPE for RAID controllers under Linux.
The above is the expected SCSI view of the logical drive emulated by the RAID firmware. This view is typically useless because SCSI diagnostic commands are not emulated.
There is no standard way to access physical devices behind RAID controllers. Therefore this is platform and controller specific, see the wiki page about RAID support.
Please provide detailed info about the RAID hardware configuration (SAS RAID controller?, USB bridge with RAID support?, ...).