Xgamer911 Posted March 8, 2020 Share Posted March 8, 2020 I started out with unraid on a home built server and it has been working fine, but I wanted more space. So I recently bought: HP Proliant DL360 G7 HP P2000 G3 LFF Modular Smart Array I have connected two of the SAS ports between the server and the SAN. (See picture 1) I have then connected only 1 of the hard drives in the SAN. (See picture 2, upper left on the SAN, none connected on Proliant) I have gotten Unraid started on the Proliant but I am unable to see the hard drive on the SAN. Can anyone point me in the right direction? I have attached my diagnostics. tower-diagnostics-20200308-0716.zip Quote Link to comment
Xgamer911 Posted March 8, 2020 Author Share Posted March 8, 2020 Quick update: I did a lspci and found: 06:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 09:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) I believe these are my SAS controllers connected to my HP P2000 SAN. I guess the next question would be, how can I use them to see the SAN HDD? edit: I have also attached my syslog. Syslog.txt Quote Link to comment
JorgeB Posted March 9, 2020 Share Posted March 9, 2020 Both enclosures are being detected correctly: Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(05.00.13.00), ChipRevision(0x03), BiosVersion(07.05.04.00) Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: Protocol=( Mar 8 04:54:20 Tower kernel: Initiator Mar 8 04:54:20 Tower kernel: ,Target Mar 8 04:54:20 Tower kernel: ), Mar 8 04:54:20 Tower kernel: Capabilities=( Mar 8 04:54:20 Tower kernel: TLR Mar 8 04:54:20 Tower kernel: ,EEDP Mar 8 04:54:20 Tower kernel: ,Snapshot Buffer Mar 8 04:54:20 Tower kernel: ,Diag Trace Buffer Mar 8 04:54:20 Tower kernel: ,Task Set Full Mar 8 04:54:20 Tower kernel: ,NCQ Mar 8 04:54:20 Tower kernel: ) Mar 8 04:54:20 Tower kernel: scsi host1: Fusion MPT SAS Host Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: sending port enable !! Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b0055d6fa0), phys(8) Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: port enable: SUCCESS Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: Enclosure HP P2000 G3 SAS T200 PQ: 0 ANSI: 5 Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: SSP: handle(0x0009), sas_addr(0x500c0ff1233b4000), phy(4), device_name(0x0000000000000000) Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: enclosure logical id (0x500605b0055d6fa0), slot(4) Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: Power-on or device reset occurred Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: Attached scsi generic sg2 type 13 Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: LSISAS2008: FWVersion(05.00.13.00), ChipRevision(0x03), BiosVersion(07.05.04.00) Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: Protocol=( Mar 8 04:54:20 Tower kernel: Initiator Mar 8 04:54:20 Tower kernel: ,Target Mar 8 04:54:20 Tower kernel: ), Mar 8 04:54:20 Tower kernel: Capabilities=( Mar 8 04:54:20 Tower kernel: TLR Mar 8 04:54:20 Tower kernel: ,EEDP Mar 8 04:54:20 Tower kernel: ,Snapshot Buffer Mar 8 04:54:20 Tower kernel: ,Diag Trace Buffer Mar 8 04:54:20 Tower kernel: ,Task Set Full Mar 8 04:54:20 Tower kernel: ,NCQ Mar 8 04:54:20 Tower kernel: ) Mar 8 04:54:20 Tower kernel: scsi host3: Fusion MPT SAS Host Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: sending port enable !! Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: host_add: handle(0x0001), sas_addr(0x500605b0029eafe0), phys(8) Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: port enable: SUCCESS Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: Enclosure HP P2000 G3 SAS T200 PQ: 0 ANSI: 5 Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: SSP: handle(0x0009), sas_addr(0x500c0ff1233b4400), phy(0), device_name(0x0000000000000000) Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: enclosure logical id (0x500605b0029eafe0), slot(0) Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: Power-on or device reset occurred Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: Attached scsi generic sg3 type 13 This suggest the connections are good but the enclosure is not detecting the disk, though you should update both LSIs firmware since they are ancient, current release is 20.00.07.00 Quote Link to comment
Xgamer911 Posted March 9, 2020 Author Share Posted March 9, 2020 16 minutes ago, johnnie.black said: Both enclosures are being detected correctly: Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(05.00.13.00), ChipRevision(0x03), BiosVersion(07.05.04.00) Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: Protocol=( Mar 8 04:54:20 Tower kernel: Initiator Mar 8 04:54:20 Tower kernel: ,Target Mar 8 04:54:20 Tower kernel: ), Mar 8 04:54:20 Tower kernel: Capabilities=( Mar 8 04:54:20 Tower kernel: TLR Mar 8 04:54:20 Tower kernel: ,EEDP Mar 8 04:54:20 Tower kernel: ,Snapshot Buffer Mar 8 04:54:20 Tower kernel: ,Diag Trace Buffer Mar 8 04:54:20 Tower kernel: ,Task Set Full Mar 8 04:54:20 Tower kernel: ,NCQ Mar 8 04:54:20 Tower kernel: ) Mar 8 04:54:20 Tower kernel: scsi host1: Fusion MPT SAS Host Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: sending port enable !! Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b0055d6fa0), phys(8) Mar 8 04:54:20 Tower kernel: mpt2sas_cm0: port enable: SUCCESS Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: Enclosure HP P2000 G3 SAS T200 PQ: 0 ANSI: 5 Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: SSP: handle(0x0009), sas_addr(0x500c0ff1233b4000), phy(4), device_name(0x0000000000000000) Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: enclosure logical id (0x500605b0055d6fa0), slot(4) Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: Power-on or device reset occurred Mar 8 04:54:20 Tower kernel: scsi 1:0:0:0: Attached scsi generic sg2 type 13 Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: LSISAS2008: FWVersion(05.00.13.00), ChipRevision(0x03), BiosVersion(07.05.04.00) Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: Protocol=( Mar 8 04:54:20 Tower kernel: Initiator Mar 8 04:54:20 Tower kernel: ,Target Mar 8 04:54:20 Tower kernel: ), Mar 8 04:54:20 Tower kernel: Capabilities=( Mar 8 04:54:20 Tower kernel: TLR Mar 8 04:54:20 Tower kernel: ,EEDP Mar 8 04:54:20 Tower kernel: ,Snapshot Buffer Mar 8 04:54:20 Tower kernel: ,Diag Trace Buffer Mar 8 04:54:20 Tower kernel: ,Task Set Full Mar 8 04:54:20 Tower kernel: ,NCQ Mar 8 04:54:20 Tower kernel: ) Mar 8 04:54:20 Tower kernel: scsi host3: Fusion MPT SAS Host Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: sending port enable !! Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: host_add: handle(0x0001), sas_addr(0x500605b0029eafe0), phys(8) Mar 8 04:54:20 Tower kernel: mpt2sas_cm1: port enable: SUCCESS Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: Enclosure HP P2000 G3 SAS T200 PQ: 0 ANSI: 5 Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: SSP: handle(0x0009), sas_addr(0x500c0ff1233b4400), phy(0), device_name(0x0000000000000000) Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: enclosure logical id (0x500605b0029eafe0), slot(0) Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: Power-on or device reset occurred Mar 8 04:54:20 Tower kernel: scsi 3:0:0:0: Attached scsi generic sg3 type 13 This suggest the connections are good but the enclosure is not detecting the disk, though you should update both LSIs firmware since they are ancient, current release is 20.00.07.00 I will go and figure out how to update the firmware and post back. At the same time, I will also plug in more HDD into enclosure. Maybe I am testing with a bad drive. Quote Link to comment
IKWeb Posted May 14, 2020 Share Posted May 14, 2020 Hello @Xgamer911 - How did you get on with this?? I have the same SAN but with ISCSI which I am swapping out for SAS and intend to do what you have. Feedback would be good? Quote Link to comment
Xgamer911 Posted May 14, 2020 Author Share Posted May 14, 2020 (edited) 11 minutes ago, IKWeb said: Hello @Xgamer911 - How did you get on with this?? I have the same SAN but with ISCSI which I am swapping out for SAS and intend to do what you have. Feedback would be good? I ended up updating the LSI HBA firmware. Didn't help, but didn't hurt to do it anyways. In the end I finally realized that I had to connect to the P2000's Storage Management web interface over network and setup the hard drives into separate vdisks. After I had all the HDDs into vdisks, I only had to create the volumes for each and the Unraid was able to see them. Edited May 14, 2020 by Xgamer911 1 Quote Link to comment
kayjay010101 Posted July 27, 2020 Share Posted July 27, 2020 Did you manage to get SMART and drive temps to work in Unraid with the P2000 G3? I've managed to get everything setup myself, but drives lack SMART capability and report 0C as their temp. SMART works according to the drive shelf's web interface, but as always with HPE products it's severely lacking in ease of use, and I'd like to have it reported in Unraid. Quote Link to comment
Xgamer911 Posted July 27, 2020 Author Share Posted July 27, 2020 33 minutes ago, kayjay010101 said: Did you manage to get SMART and drive temps to work in Unraid with the P2000 G3? I've managed to get everything setup myself, but drives lack SMART capability and report 0C as their temp. SMART works according to the drive shelf's web interface, but as always with HPE products it's severely lacking in ease of use, and I'd like to have it reported in Unraid. I don't believe the P2000 G3 has the SMART capability. All drives I have ever installed in it have always said "SMART support: Unavailable - device lacks SMART capability." Quote Link to comment
kayjay010101 Posted July 27, 2020 Share Posted July 27, 2020 Strange, going under my drives it does say "Enabled" under SMART. Are you running HP-branded drives? Also, did you get temperatures per drive to work in any capacity? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.