hard drive – Disk Support HP 400 SAS controller

I receive a months ago an HP Proliant DL360 G5 with an HP Smart Array P400i Controller with 256 Mb, i have 2 sas 10k 72 Tb disk and i want to upgrade.
I buyed 4 HDD SAS 10K Hitachi 450 Gb, but the controller don’t recognize them, the led will remain red in this units when i power on the server.
I think the firmware in the Controller is the last (7.24b version)
I read that this controller support disk until 1 Tb or more in SAS

Any Idea about this? Thanks!

windows – Lsi MegaRaid sas 9271-8i raid-0 crash

I have 8 hhd , all of it have RAID-0. Yesterday one disk change status to configurate good, it’s disk with OS. And now I can’t start my server , import foreign configuration not work, and I can not discard cache it’s not work too. How to reestablish server work.

Hi, I have a data set without replication, how can I analyze that in R or SAS

3 Genotypes, 2 temperature treatment (1= Control, 2= Stress) and CMT is the Variable I want to check the interaction of temperature and genotypes and apply Tukey and Scott Knott test.

Treatment Genotype CMT
1 BEL 84.67
1 BGB86 98.88
1 BGB444 92.45
2 BEL 80.28
2 BGB86 67.29
2 BGB444 86.11

debian – Very low IOP in an array of SAS 16x 15K drives

I am having trouble with one of our servers running SAS 16x 900GB 15K drives in a RAID 1 + 0 array on a PERC H710P, under normal load. ~ 450 PIO (almost all writes) and has a delay of ~ 80 ms, when speed is tested with dd if=/dev/zero of=/root/testfile bs=4 count=10000 oflag=dsync peaks at about 800 PIO with a delay of 200 ms.

I tried to disable the ReadAhead function on the RAID card and changed the disk cache of default disk to enabled, without IOP write enhancement.

Doing the same test on our other database servers gets much better results:

  • 12x 4TB 7.2k SAS RAID1 + 0 PERC H710P: ~ 15,000 PIO

  • 24x 300GB 10K SAS RAID1 + 0 PERC H710P: ~ 21,000 IOP

As far as I can see, all the drives are fine and the RAID card settings are correct, what other reason could be the reason for this problem?

Server details

Relevant part of lspci -vv

02:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2208 (Thunderbolt) (rev 01)
        Subsystem: Dell PERC H710P Adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

RAID card information megacli -AdpAllInfo -aAll

Adapter #0

==============================================================================
                    Versions
                ================
Product Name    : PERC H710P Adapter
Serial No       : 29P00AB
FW Package Build: 21.3.2-0005

                    Mfg. Data
                ================
Mfg. Date       : 09/27/12
Rework Date     : 09/27/12
Revision No     : A00
Battery FRU     : N/A

                Image Versions in Flash:
                ================
BIOS Version       : 5.42.00.1_4.12.05.00_0x05290003
Ctrl-R Version     : 4.04-0003
Preboot CLI Version: 05.00-03:#%00008
FW Version         : 3.131.05-4520
NVDATA Version     : 2.1108.03-0096
Boot Block Version : 2.03.00.00-0004
BOOT Version       : 06.253.57.219

                Pending Images in Flash
                ================
None

                PCI Info
                ================
Controller Id   : 0000
Vendor Id       : 1000
Device Id       : 005b
SubVendorId     : 1028
SubDeviceId     : 1f31

Host Interface  : PCIE

ChipRevision    : B0

Link Speed           : 2
Number of Frontend Port: 0
Device Interface  : PCIE

Number of Backend Port: 8
Port  :  Address
0        500056b37789abff
1        0000000000000000
2        0000000000000000
3        0000000000000000
4        0000000000000000
5        0000000000000000
6        0000000000000000
7        0000000000000000

                HW Configuration
                ================
SAS Address      : 590b11c015d8b800
BBU              : Present
Alarm            : Absent
NVRAM            : Present
Serial Debugger  : Present
Memory           : Present
Flash            : Present
Memory Size      : 1024MB
TPM              : Absent
On board Expander: Absent
Upgrade Key      : Absent
Temperature sensor for ROC    : Present
Temperature sensor for controller    : Present

ROC temperature : 79  degree Celsius
Controller temperature : 79  degree Celcius

                Settings
                ================
Current Time                     : 4:1:13 4/14, 2020
Predictive Fail Poll Interval    : 300sec
Interrupt Throttle Active Count  : 16
Interrupt Throttle Completion    : 50us
Rebuild Rate                     : 30%
PR Rate                          : 30%
BGI Rate                         : 30%
Check Consistency Rate           : 30%
Reconstruction Rate              : 30%
Cache Flush Interval             : 4s
Max Drives to Spinup at One Time : 4
Delay Among Spinup Groups        : 12s
Physical Drive Coercion Mode     : 128MB
Cluster Mode                     : Disabled
Alarm                            : Disabled
Auto Rebuild                     : Enabled
Battery Warning                  : Enabled
Ecc Bucket Size                  : 255
Ecc Bucket Leak Rate             : 240 Minutes
Restore HotSpare on Insertion    : Disabled
Expose Enclosure Devices         : Disabled
Maintain PD Fail History         : Disabled
Host Request Reordering          : Enabled
Auto Detect BackPlane Enabled    : SGPIO/i2c SEP
Load Balance Mode                : Auto
Use FDE Only                     : Yes
Security Key Assigned            : No
Security Key Failed              : No
Security Key Not Backedup        : No
Default LD PowerSave Policy      : Controller Defined
Maximum number of direct attached drives to spin up in 1 min : 20
Auto Enhanced Import             : No
Any Offline VD Cache Preserved   : No
Allow Boot with Preserved Cache  : No
Disable Online Controller Reset  : No
PFK in NVRAM                     : No
Use disk activity for locate     : No
POST delay                       : 90 seconds
BIOS Error Handling              : Stop On Errors
Current Boot Mode                 :Normal
                Capabilities
                ================
RAID Level Supported             : RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, PRL11-RLQ0 DDF layout with no span, PRL11-RLQ0 DDF layout with span
Supported Drives                 : SAS, SATA

Allowed Mixing:

Mix in Enclosure Allowed

                Status
                ================
ECC Bucket Count                 : 0

                Limitations
                ================
Max Arms Per VD          : 32
Max Spans Per VD         : 8
Max Arrays               : 128
Max Number of VDs        : 64
Max Parallel Commands    : 1008
Max SGE Count            : 60
Max Data Transfer Size   : 8192 sectors
Max Strips PerIO         : 42
Max LD per array         : 16
Min Strip Size           : 64 KB
Max Strip Size           : 1.0 MB
Max Configurable CacheCade Size: 512 GB
Current Size of CacheCade      : 0 GB
Current Size of FW Cache       : 883 MB

                Device Present
                ================
Virtual Drives    : 1
  Degraded        : 0
  Offline         : 0
Physical Devices  : 18
  Disks           : 16
  Critical Disks  : 0
  Failed Disks    : 0

                Supported Adapter Operations
                ================
Rebuild Rate                    : Yes
CC Rate                         : Yes
BGI Rate                        : Yes
Reconstruct Rate                : Yes
Patrol Read Rate                : Yes
Alarm Control                   : Yes
Cluster Support                 : No
BBU                             : No
Spanning                        : Yes
Dedicated Hot Spare             : Yes
Revertible Hot Spares           : Yes
Foreign Config Import           : Yes
Self Diagnostic                 : Yes
Allow Mixed Redundancy on Array : No
Global Hot Spares               : Yes
Deny SCSI Passthrough           : No
Deny SMP Passthrough            : No
Deny STP Passthrough            : No
Support Security                : Yes
Snapshot Enabled                : No
Support the OCE without adding drives : Yes
Support PFK                     : No
Support PI                      : No
Support Boot Time PFK Change    : No
Disable Online PFK Change       : No
Support Shield State            : No
Block SSD Write Disk Cache Change: No

                Supported VD Operations
                ================
Read Policy          : Yes
Write Policy         : Yes
IO Policy            : Yes
Access Policy        : Yes
Disk Cache Policy    : Yes
Reconstruction       : Yes
Deny Locate          : No
Deny CC              : No
Allow Ctrl Encryption: No
Enable LDBBM         : Yes
Support Breakmirror  : Yes
Power Savings        : Yes

                Supported PD Operations
                ================
Force Online                            : Yes
Force Offline                           : Yes
Force Rebuild                           : Yes
Deny Force Failed                       : No
Deny Force Good/Bad                     : No
Deny Missing Replace                    : No
Deny Clear                              : No
Deny Locate                             : No
Support Temperature                     : Yes
NCQ                                     : No
Disable Copyback                        : Yes
Enable JBOD                             : No
Enable Copyback on SMART                : No
Enable Copyback to SSD on SMART Error   : No
Enable SSD Patrol Read                  : No
PR Correct Unconfigured Areas           : Yes
Enable Spin Down of UnConfigured Drives : No
Disable Spin Down of hot spares         : Yes
Spin Down time                          : 30
T10 Power State                         : Yes
                Error Counters
                ================
Memory Correctable Errors   : 0
Memory Uncorrectable Errors : 0

                Cluster Information
                ================
Cluster Permitted     : No
Cluster Active        : No

                Default Settings
                ================
Phy Polarity                     : 0
Phy PolaritySplit                : 0
Background Rate                  : 30
Strip Size                       : 64kB
Flush Time                       : 4 seconds
Write Policy                     : WB
Read Policy                      : Adaptive
Cache When BBU Bad               : Disabled
Cached IO                        : No
SMART Mode                       : Mode 6
Alarm Disable                    : No
Coercion Mode                    : 128MB
ZCR Config                       : Unknown
Dirty LED Shows Drive Activity   : No
BIOS Continue on Error           : 0
Spin Down Mode                   : None
Allowed Device Type              : SAS/SATA Mix
Allow Mix in Enclosure           : Yes
Allow HDD SAS/SATA Mix in VD     : No
Allow SSD SAS/SATA Mix in VD     : No
Allow HDD/SSD Mix in VD          : No
Allow SATA in Cluster            : No
Max Chained Enclosures           : 4
Disable Ctrl-R                   : No
Enable Web BIOS                  : No
Direct PD Mapping                : Yes
BIOS Enumerate VDs               : Yes
Restore Hot Spare on Insertion   : No
Expose Enclosure Devices         : No
Maintain PD Fail History         : No
Disable Puncturing               : No
Zero Based Enclosure Enumeration : Yes
PreBoot CLI Enabled              : No
LED Show Drive Activity          : Yes
Cluster Disable                  : Yes
SAS Disable                      : No
Auto Detect BackPlane Enable     : SGPIO/i2c SEP
Use FDE Only                     : Yes
Enable Led Header                : No
Delay during POST                : 0
EnableCrashDump                  : No
Disable Online Controller Reset  : No
EnableLDBBM                      : Yes
Un-Certified Hard Disk Drives    : Allow
Treat Single span R1E as R10     : Yes
Max LD per array                 : 16
Power Saving option              : Don't spin down unconfigured drives
Don't spin down Hot spares
Don't Auto spin down Configured Drives
Power settings apply to all drives - individual PD/LD power settings cannot be set
Max power savings option is  not allowed for LDs. Only T10 power conditions are to be used.
Cached writes are not used for spun down VDs
Can schedule disable power savings at controller level
Default spin down time in minutes: 30
Enable JBOD                      : No
TTY Log In Flash                 : Yes
Auto Enhanced Import             : No
BreakMirror RAID Support         : Yes
Disable Join Mirror              : Yes
Enable Shield State              : No
Time taken to detect CME         : 60s

Exit Code: 0x00

Battery status megacli -AdpBbuCmd -GetBbuSTatus -aAll

BBU status for Adapter: 0

BatteryType: BBU
Voltage: 3900 mV
Current: 0 mA
Temperature: 45 C
Battery State: Optimal
BBU Firmware Status:

  Charging Status              : None
  Voltage                                 : OK
  Temperature                             : OK
  Learn Cycle Requested                   : No
  Learn Cycle Active                      : No
  Learn Cycle Status                      : OK
  Learn Cycle Timeout                     : No
  I2c Errors Detected                     : No
  Battery Pack Missing                    : No
  Battery Replacement required            : No
  Remaining Capacity Low                  : No
  Periodic Learn Required                 : No
  Transparent Learn                       : No
  No space to cache offload               : No
  Pack is about to fail & should be replaced : No
  Cache Offload premium feature required  : No
  Module microcode update required        : No

BBU GasGauge Status: 0x0228
Relative State of Charge: 99 %
Charger Status: Complete
Remaining Capacity: 387 mAh
Full Charge Capacity: 391 mAh
isSOHGood: Yes

Exit Code: 0x00

Virtual Drive Information megacli -LDInfo -Lall -aAll

Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :PrimaryStorage
RAID Level          : Primary-1, Secondary-0, RAID Level Qualifier-0
Size                : 6.544 TB
Sector Size         : 512
Mirror Data         : 6.544 TB
State               : Optimal
Strip Size          : 64 KB
Number Of Drives per span:8
Span Depth          : 2
Default Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy   : Enabled
Encryption Type     : None
Default Power Savings Policy: Controller Defined
Current Power Savings Policy: None
Can spin up in 1 minute: Yes
LD has drives that support T10 power conditions: Yes
LD's IO profile supports MAX power savings with cached writes: No
Bad Blocks Exist: No
Is VD Cached: Yes
Cache Cade Type : Read Only

Exit Code: 0x00

INTELLIGENT data from unit 0 smartctl /dev/sda -a -d megaraid,0

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              DL900MP0136
Revision:             KT55
Compliance:           SPC-4
User Capacity:        900,185,481,216 bytes (900 GB)
Logical block size:   512 bytes
Physical block size:  4096 bytes
Formatted with type 2 protection
LU is fully provisioned
Rotation Rate:        15000 rpm
Form Factor:          2.5 inches
Logical Unit id:      0x5000c500b8c86e4f
Serial number:        WAG0BWG2
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Tue Apr 14 14:08:12 2020 NZST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     31 C
Drive Trip Temperature:        60 C

Manufactured in week 25 of year 2018
Specified cycle count over device lifetime:  10000
Accumulated start-stop cycles:  13
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  547
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 1794649432
  Blocks received from initiator = 3529373256
  Blocks read from cache and sent to initiator = 120960058
  Number of read and write commands whose size <= segment size = 13007345
  Number of read and write commands whose size > segment size = 10656

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 12864.37
  number of minutes until next internal SMART test = 9

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   (10^9 bytes)  errors
read:   224258814        0         0  224258814          0        933.218           0
write:         0        0         0         0          0       4097.456           0
verify:      471        0         0       471          0          0.000           0

Non-medium error count:      371

What kind of websites would benefit from SSD (shared) hosting instead of SAS NL?

I am fully aware of the technical data (and have undergone the switch from HDD to SSD) about SSD and HDD, however I am wondering what kind of websites could specifically benefit from using SSD based shared hosting instead of shared based hosting at SAS. Assuming the SERVER data is on SSD either way, only the website files are on SSD or SAS HDD (although feel free to comment on other scenarios, I like to gather information and understand how things work).

I suppose only large sites with lots of visitors could benefit, but that is based only on the assumption of higher performance.

Another thing to consider, I think, is that it is a shared hosting, although SAS NL is probably in RAID, which would reduce the strain caused by someone who might have heavy sites on the same shared hosting machine …

So would you see any benefit in using SSD for site files vs SAS NL for site files, for a small or medium size site with low or average visitor count, assuming system files are stored on an SSD independently , in a shared web hosting environment? ?

I know, it's a complex question, but it's interesting, right? I'm sure someone has tried it just for fun. I know I would if I had the hardware.

Storage: SAS disk vs input level SSD

We are acquiring the new Lenovo SR650 server (which will host multiple Oracle DB, SAP servers) and the providers propose the following storage options

  • ThinkSystem 2.5 "1.2TB 10K SAS 12Gb Hot Swap 512n HDD (QUANTITY: 16 discs)
  • ThinkSystem 2.5 "5210 960GB SATA 6Gb Hot Swap QLC SSD Input (QUANTITY: 16 discs)
  • ThinkSystem 2.5 "5210 1.92TB SATA 6Gb Hot Swap QLC SSD Input (QUANTITY: 16 discs)

We read somewhere that, given a sudden power failure, there is a better chance of total data corruption compared to SAS disks.

What is the most appropriate storage option from above from the perspective of performance and reliability?
And is it better to divide them into 2 Raid-10 matrices? so if the full backup is in progress, the performance of another DBA server should not be reduced.

sas: What is the difference between the SFF-8482 and SFF-8082 connectors?

A popular way to connect SAS hard drives to a SAS card that has SFF-8087 sockets is to use an SFF-8087 to SFF-8482 cable.

It can also be found in the market SFF-8087 to SFF-8082 cables, but I could hardly find documentation on the SFF-80 082 connector and seems much less known.

At first, I believed that 0 of 8082 was a typo, because there I couldn't find documentation about this type of connector.
However, there is a specification: https://www.optcore.net/wp-content/uploads/2017/04/SFF-8082.pdf

I just wonder what the SFF-8082 connector is and its difference with SFF-8482.
Is the first an ancestor of the second?

Windows Server 2016: SAS drives not recognized in Netapp DS4486

To begin, here are the relevant hardware specifications:

  • Dell R710 with Windows Server 2016
  • Dell PERC H200e
  • Dell PERC H810
  • Dell PowerVault MD1200 with 03DJRJ drivers
  • NetApp DS4486 with IOM6 drivers

I have a total of 26 SAS drives. All are Seagate ST4000NM0023 4TB units, Seagate ST33000650SS 3TB units or Seagate ST3600002SS 600GB units. I tested them in multiple configurations on the DS4486: one unit per sled (both positions), two units per sled, mixing of each type in a sled and all those configurations in multiple different bays of the cabinet. Each attempt ends with unrecognized units. If I take exactly the same drive and put it in a Dell MD1200, the operating system recognizes them and can be accessed without problems. I have connected both the DS4486 and the MD1200 to a PERC H200e and a PERC H810 and the results are the same. I have even tried to chain the cabinets as follows: host -> MD1200 -> DS4486. The results are always the same, all units are not recognized in the DS4486.

The drives are shown in Disk Management as uninitialized drives. The properties of the unit report the correct model number of the disk. Unit property sizes are displayed as 0 bytes in size. If I try to initialize the unit as GPT, an error appears indicating that the size is not large enough. If I choose MBR, I get an I / O error. When I run diskpart -> list disk, the output seems to freeze a little and then the units are shown in the list approximately 30% of the time, otherwise, the list is empty. If i try to use select disk <##> (using the disk management disk number) and then execute any other command like clean or online disk I receive an error message at the exit.

Any ideas on what to try next? If you need more information, let me know, I will provide everything I can.

Chemistry – What argument of MoleculeValue does SAS return?

I have been trying to calculate the synthetic accessibility score of a molecule. But I don't know what property of the extensive list returned by MoleculeValue("Properties") corresponds to the SAS value.

I know there is a function in rdkit called sascorer which calculates the SAS of a molecule. And if, as this Jason ad suggests, chemistry-related calculations are backed by rdkit, I imagine one of the MoleculeValueThat's what I'm looking for. So, my questions are:

  1. What argument (or parameter) of MoleculeValue Does the synthetic accessibility score of a molecule return?
  2. They are all (or most) of the chemical properties available through rdkit available in Mathematica for now?

Thanks in advance.

Motherboard – How to connect a SATA III port to a SAS hard drive?

On my motherboard, the ASUS Z9D8 says it has a row of 8 SAS ports to connect to SAS hard drives.

enter the description of the image here

It is the line of blue things in the lower left of the image. They are clearly seen as SATA III ports. And I can connect a SATA III 6.0 GB / S data transfer cable. But, when I'm going to connect them to a SAS hard drive, it doesn't work.

What type of cable should I buy to connect from this port to a regular SAS hard drive? I know that these ports are compatible with SAS.

The documentation calls them "PSAS," but I don't know what that means, and it's not on the web. I just want to know how to make these SAS hard drives work with this board.