[Unraid 6.9.2 and Disk Disabled, contents emulated]

Ok so I figured it out eventually and I am posting a follow-up with my solution to help anyone else that might be having the same issue.

 

Edit from Itimpi below:

Quote

It is not clear from your description but steps 1 to 5 were running against the 'emulated' drive and would be fixing an 'unmountable' status.  Steps 6 to 12 are rebuilding the emulated drive contents back onto a physical drive to clear the 'disabled' status.

 

1. Stopped the array
2. Started the array in maintenance mode, went to disk and ran a check.
3. Once check was done, I ran the same check but this time with no -n.
4. Stop the array in maintenance mode
5. Started the array normally
6. Stop the array
7. Remove the disk from the array
8. Start the array normally so the disk will be registered as missing
9. Stop the array
10. Reassign the disk
11. Start the array to begin rebuilding
12. Wait for the rebuild to complete

[Unraid 6.9.2 and Disk Disabled, contents emulated]

7 hours ago, JorgeB said:

Run it again without -n, and if it asks for -L use it.

 

Ok I ran it without the -n and got a whole mess of output. (attached - HDD Check (without -n).txt)

 

I went back and stopped the array and started again normally. This time disk 2 mounted, but is still disabled. I stopped the array and restarted in maintenance mode again and ran the check again. This time the output looked normal. (Attached - HDD Check 2.txt)

 

The both outputs didn't say to use the -L option so I didn't, since the help menu said "Do this as a last resort".

 

I don't know what my next step is to get this Disk 2 back into enabled status and not have the contents emulated. 

HDD Check (without -n).txt HDD Check 2.txt

[Unraid 6.9.2 and Disk Disabled, contents emulated]

5 hours ago, itimpi said:

Handling of unmountable disks is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.   The Unraid OS->Manual section covers most aspects of the current Unraid release.

I started the arrary in maintenance mode like the documentation said and ran a check. Under "Running the Test using the webGui" and step 8 it says to come back to forums. So here is the output attached. 

 

I am unsure about the output however. Is the HDD dead, dieing, or should I continue the "Repairing a File System" section?

HDD Check.txt

[Unraid 6.9.2 and Disk Disabled, contents emulated]

I have never had this error before and I am not sure what to do about it.

I have 11 disks in total and disk 2 is now "device is disabled, contents emulated"

 

All of these drives are running on a HP P200 G3 SAS. The HDD shows up there just fine.

 

I have tried to manually mount the /dev/sdj to /mnt/tmp just to see if I can see what is going on, but the command hangs.

 

I have found in the syslog that corruption is detected. It says I should unmount and run xfs_repair. This is where I am confused, because the disk says it is unmountable. Should I:

1) Just run a Check on the Main page

2) Goto command line and use "xfs_repair /dev/sdj". Are there any other options I should use?

3) Stop the array and start in maintenance mode, the run a Check on the Main page

4) Stop the array and use "xfs_repair /dev/sdj". Are there any other options I should use?

 

I have also attach a diagnostic.zip as well to help. I am not sure what I need to do to repair this disk.

 

 

tower-diagnostics-20240415-2247.zip

[Setting up Unraid with a HP P2000 G3]

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."

[Setting up Unraid with a HP P2000 G3]

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.

[Setting up Unraid with a HP P2000 G3]

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.

 

[Setting up Unraid with a HP P2000 G3]

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

[Setting up Unraid with a HP P2000 G3]

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

[Unraid Forum 100K Giveaway]

One thing i like:

The ability to add new features using docker and plugins.

 

One thing i would like to see added:

On the webUI, be able to browse community docker/plugins directly from a database. The ability to filter these would also be useful in finding functionality I hadn't known about.

 

EDIT:

I am new to UnRaid(still in 30day trial), so I just found the community apps and associated plugins with search. So I would change the item I wanted added would be to create VM snapshots. (until I find that later on during my playing with this.)