PROXMOX v3.3 (2.6.32-34)+ LSI MegaRAID 9271-4i + RAID5 [3x 480 GB SSD]

Ferminator

Renowned Member
Hi everyone.!

First of all, Happy new year !
;-)

Into 'open-matrix.es' have servers in OVH (Spain), which we use to service hosting, VPS's and applications dedicated to
customer companies in powerful configurations with Xeon + LSI 9271-4i RAID 5 + SSD ... etc.

The problem ONLY happens with this server, others work OK, with identical configurations seem.
This problem with server has also been running without any fault during more than 100 days,
until they started 'hanged' and to vomit the KERNEL ... now let me explain.

::HOST::
-------------
Enterprise Server SP-64 Xeon E5-1620v2 + RAM 64 GB + LSI MegaRAID 9271-4i + RAID5 (3x 480GB SDD) + 1 TB NFS Backup


::SOFTWARE::
---------------------
Proxmox VE 3.3 (Kernel 2.6.32-34-pve SMP 19 Dec 2014 7:42:04 CET)
Currently running a total of about 36 VPS (OpenVZ - Ubuntu / CentOS / Debian - Virtualmin / Plesk)


::pROBLEM::
-------------------
Suddenly becomes the RAID5 of LSI MegaRAID 9271-4i in READ ONLY mode, rejecting any writing
on discs and blocked everything that happens within 48 hours, to be in READ ONLY mode does not write to the
logs and I had to catch the flight, SSH and KVM-IP errors so it is quite difficult to trace the problem.

Note:
All tests on HARDWARE into OVH maintenance mode 'RESCUE-Pro' have successfully passed and the smartctl discs
and FSCK for the SSD discs file system, Xeon cpu, RAM all are OK.

some idea ?

Best Regards.
admin @ open-matrix.es
( SPAIN - Valencia )


-----------------------------------------------------------------------------------------------------------------------------------
----- SYSLOG - CRASH -----------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------

Dec 29 23:28:59 leopard kernel: EXT4-fs warning (device dm-0): ext4_end_bio: I/O error writing to inode 5926096
Dec 29 23:28:59 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:28:59 leopard kernel: end_request: I/O error, dev sda, sector 0
Dec 29 23:28:59 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: [sda] CDB: Write(10): 2a 00 47 d6 14 70 00 00 10 00
Dec 29 23:29:00 leopard kernel: end_request: I/O error, dev sda, sector 1205212272
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: [sda] Unhandled error code
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: [sda] CDB: Write(10): 2a 00 46 e8 78 d8 00 00 08 00
Dec 29 23:29:00 leopard kernel: JBD2: Detected IO errors while flushing file data on dm-0-8
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: Aborting journal on device dm-0-8.
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal
Dec 29 23:29:00 leopard kernel: JBD2: I/O error detected when updating journal superblock for dm-0-8.
Dec 29 23:29:00 leopard kernel: EXT4-fs (dm-0): Remounting filesystem read-only
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0) in ext4_new_inode: Journal has aborted
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write: Journal has aborted
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0) in ext4_orphan_add: Journal has aborted
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0) in ext4_new_inode: Journal has aborted

Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write: Journal has aborted
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device

Dec 29 23:29:00 leopard kernel: end_request: I/O error, dev sda, sector 29771464
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: end_request: I/O error, dev sda, sector 143513600

Dec 29 23:29:00 leopard kernel: EXT4-fs warning (device dm-0): ext4_end_bio: I/O error writing to inode 5920323
Dec 29 23:29:00 leopard kernel: end_request: I/O error, dev sda, sector 698531976

Dec 29 23:29:00 leopard kernel: EXT4-fs warning (device dm-0): ext4_end_bio: I/O error writing to inode 18756785
Dec 29 23:29:00 leopard kernel: sd 0:2:0:0: rejecting I/O to offline device
Dec 29 23:29:00 leopard kernel: end_request: I/O error, dev sda, sector 628082184
Dec 29 23:29:00 leopard kernel: EXT4-fs error (device dm-0) in ext4_orphan_add: Journal has aborted

Message from syslogd@leopard at Dec 29 23:29:02 ...
kernel:journal commit I/O error
Message from syslogd@leopard at Dec 29 23:29:02 ...
kernel:journal commit I/O error
Message from syslogd@leopard at Dec 29 23:29:02 ...
kernel:journal commit I/O error

Dec 30 17:46:52 leopard kernel: INFO: task jbd2/sda1-8:462 blocked for more than 120 seconds.

Dec 30 17:46:52 leopard kernel: Tainted: G --------------- T 2.6.32-31-pve #1
Dec 30 17:46:52 leopard kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 30 17:46:52 leopard kernel: jbd2/sda1-8 D ffff881073c2e980 0 462 2 0 0x00000000
Dec 30 17:46:52 leopard kernel: ffff881073f0fc10 0000000000000046 ffff881073f0fba0 ffffffff81086871
Dec 30 17:46:52 leopard kernel: ffff881073f0fb80 ffffffff81014d79 ffff881073f0fbc0 ffffffff810aaa44
Dec 30 17:46:52 leopard kernel: ffff88107373aeb8 ffff88107952c760 ffff881073f0ffd8 ffff881073f0ffd8

Dec 30 17:46:52 leopard kernel: Call Trace:
Dec 30 17:46:52 leopard kernel: [<ffffffff81086871>] ? del_timer+0x81/0xe0
Dec 30 17:46:52 leopard kernel: [<ffffffff81014d79>] ? read_tsc+0x9/0x20
Dec 30 17:46:52 leopard kernel: [<ffffffff810aaa44>] ? ktime_get_ts+0xb4/0xf0
Dec 30 17:46:52 leopard kernel: [<ffffffff811df180>] ? sync_buffer+0x0/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff8155a5c3>] io_schedule+0x73/0xc0
Dec 30 17:46:52 leopard kernel: [<ffffffff811df1c0>] sync_buffer+0x40/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff8155b5d0>] __wait_on_bit+0x60/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff811df180>] ? sync_buffer+0x0/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff8155b67c>] out_of_line_wait_on_bit+0x7c/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff8109fd10>] ? wake_bit_function+0x0/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff811dfbe6>] __wait_on_buffer+0x26/0x30
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d1fe7>] jbd2_journal_commit_transaction+0xa27/0x1460 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Dec 30 17:46:52 leopard kernel: [<ffffffff81084e38>] ? lock_timer_base.isra.52+0x38/0x70
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d8208>] kjournald2+0xb8/0x200 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff8109fc90>] ? autoremove_wake_function+0x0/0x40
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d8150>] ? kjournald2+0x0/0x200 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff8109f6f8>] kthread+0x88/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Dec 30 17:46:52 leopard kernel: [<ffffffff8100c3ca>] child_rip+0xa/0x20
Dec 30 17:46:52 leopard kernel: [<ffffffff8109f670>] ? kthread+0x0/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20

Dec 30 17:46:52 leopard kernel: INFO: task flush-8:0:1187 blocked for more than 120 seconds.

Dec 30 17:46:52 leopard kernel: Tainted: G --------------- T 2.6.32-31-pve #1
Dec 30 17:46:52 leopard kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 30 17:46:52 leopard kernel: flush-8:0 D ffff881077674500 0 1187 2 0 0x00000000
Dec 30 17:46:52 leopard kernel: ffff881075993570 0000000000000046 0000000000000000 00000000000800f1
Dec 30 17:46:52 leopard kernel: ffff881075993510 ffffffff811e08c6 ffff8810759934f0 0000000000000000
Dec 30 17:46:52 leopard kernel: 000000000001bc40 0000000000001000 ffff881075993fd8 ffff881075993fd8

Dec 30 17:46:52 leopard kernel: Call Trace:
Dec 30 17:46:52 leopard kernel: [<ffffffff811e08c6>] ? __find_get_block_slow+0xb6/0x140
Dec 30 17:46:52 leopard kernel: [<ffffffff8109fc5e>] ? prepare_to_wait+0x4e/0x80
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d0b1d>] do_get_write_access+0x26d/0x480 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff8109fd10>] ? wake_bit_function+0x0/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d0e80>] jbd2_journal_get_write_access+0x30/0x50 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffffa0223426>] __ext4_journal_get_write_access+0x36/0x80 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa01faa73>] ext4_reserve_inode_write+0x73/0xa0 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa01faae9>] ext4_mark_inode_dirty+0x49/0x1a0 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa021d15d>] ext4_ext_dirty.isra.18+0x2d/0x40 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa021eb18>] ext4_ext_insert_extent+0x5f8/0x10e0 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa021da95>] ? ext4_ext_find_extent+0x295/0x310 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa0220e45>] ext4_ext_get_blocks+0x325/0x13a0 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffff812688e3>] ? submit_bio+0x83/0x190
Dec 30 17:46:52 leopard kernel: [<ffffffff811e4026>] ? __bio_clone+0x26/0x70
Dec 30 17:46:52 leopard kernel: [<ffffffffa01fc365>] ext4_get_blocks+0x1c5/0x220 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa01fd937>] mpage_da_map_and_submit+0xa7/0x3a0 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffffa01cf6e0>] ? jbd2_journal_start+0xc0/0x100 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffffa01fe42b>] ext4_da_writepages+0x2fb/0x630 [ext4]
Dec 30 17:46:52 leopard kernel: [<ffffffff81146750>] ? __writepage+0x0/0x40
Dec 30 17:46:52 leopard kernel: [<ffffffff81147c3f>] do_writepages+0x1f/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff811d5586>] __writeback_single_inode+0xa6/0x2a0
Dec 30 17:46:52 leopard kernel: [<ffffffff811d57ba>] writeback_single_inode+0x3a/0xc0
Dec 30 17:46:52 leopard kernel: [<ffffffff811c48d0>] ? iput+0x30/0x70
Dec 30 17:46:52 leopard kernel: [<ffffffff811d6216>] writeback_sb_inodes+0xf6/0x1e0
Dec 30 17:46:52 leopard kernel: [<ffffffff811d644f>] writeback_inodes_wb+0xff/0x170
Dec 30 17:46:52 leopard kernel: [<ffffffff811d6763>] wb_writeback+0x2a3/0x3f0
Dec 30 17:46:52 leopard kernel: [<ffffffff81559d9c>] ? thread_return+0xbc/0x870
Dec 30 17:46:52 leopard kernel: [<ffffffff811d6a41>] wb_do_writeback+0x191/0x250
Dec 30 17:46:52 leopard kernel: [<ffffffff811d6b8e>] bdi_writeback_task+0x8e/0x1e0
Dec 30 17:46:52 leopard kernel: [<ffffffff8115cbd2>] bdi_start_fn+0x92/0x100
Dec 30 17:46:52 leopard kernel: [<ffffffff8115cb40>] ? bdi_start_fn+0x0/0x100
Dec 30 17:46:52 leopard kernel: [<ffffffff8109f6f8>] kthread+0x88/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Dec 30 17:46:52 leopard kernel: [<ffffffff8100c3ca>] child_rip+0xa/0x20
Dec 30 17:46:52 leopard kernel: [<ffffffff8109f670>] ? kthread+0x0/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20

Dec 30 17:46:52 leopard kernel: INFO: task jbd2/dm-0-8:1757 blocked for more than 120 seconds.

Dec 30 17:46:52 leopard kernel: Tainted: G --------------- T 2.6.32-31-pve #1
Dec 30 17:46:52 leopard kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 30 17:46:52 leopard kernel: jbd2/dm-0-8 D ffff881071e3e380 0 1757 2 0 0x00000000
Dec 30 17:46:52 leopard kernel: ffff8810759fbb40 0000000000000046 ffff8810759fbaf0 ffffffff8143b8ec
Dec 30 17:46:52 leopard kernel: ffff8810759fbab0 ffffffff81014d79 ffff8810759fbaf0 0000000000000282
Dec 30 17:46:52 leopard kernel: ffff8810759fbaf0 00000000fba8805e ffff8810759fbfd8 ffff8810759fbfd8
Dec 30 17:46:52 leopard kernel: Call Trace:
Dec 30 17:46:52 leopard kernel: [<ffffffff8143b8ec>] ? dm_table_unplug_all+0x5c/0x100
Dec 30 17:46:52 leopard kernel: [<ffffffff81014d79>] ? read_tsc+0x9/0x20
Dec 30 17:46:52 leopard kernel: [<ffffffff811302a0>] ? sync_page+0x0/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff8155a5c3>] io_schedule+0x73/0xc0
Dec 30 17:46:52 leopard kernel: [<ffffffff811302db>] sync_page+0x3b/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff8155b5d0>] __wait_on_bit+0x60/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff81130470>] wait_on_page_bit+0x80/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff8109fd10>] ? wake_bit_function+0x0/0x50
Dec 30 17:46:52 leopard kernel: [<ffffffff811307aa>] wait_on_page_writeback_range.part.36+0xea/0x180
Dec 30 17:46:52 leopard kernel: [<ffffffff812688e3>] ? submit_bio+0x83/0x190
Dec 30 17:46:52 leopard kernel: [<ffffffff81131165>] wait_on_page_writeback_range+0x15/0x20
Dec 30 17:46:52 leopard kernel: [<ffffffff81131d8f>] filemap_fdatawait+0x2f/0x40
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d1d48>] jbd2_journal_commit_transaction+0x788/0x1460 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Dec 30 17:46:52 leopard kernel: [<ffffffff81084e38>] ? lock_timer_base.isra.52+0x38/0x70
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d8208>] kjournald2+0xb8/0x200 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff8109fc90>] ? autoremove_wake_function+0x0/0x40
Dec 30 17:46:52 leopard kernel: [<ffffffffa01d8150>] ? kjournald2+0x0/0x200 [jbd2]
Dec 30 17:46:52 leopard kernel: [<ffffffff8109f6f8>] kthread+0x88/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Dec 30 17:46:52 leopard kernel: [<ffffffff8100c3ca>] child_rip+0xa/0x20
Dec 30 17:46:52 leopard kernel: [<ffffffff8109f670>] ? kthread+0x0/0x90
Dec 30 17:46:52 leopard kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20


------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------


# cat /etc/fstab

# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sda1 / ext4 errors=remount-ro 0 1
/dev/sda2 swap swap defaults 0 0
/dev/pve/data /var/lib/vz ext4 noatime,relatime,nodelalloc 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0



-->> DETAIL PROXMOX:


# pveversion -v

proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-31-pve: 2.6.32-132
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1



-->> DETAIL MODULE CONTROLLER :


# modinfo megaraid_sas

filename: /lib/modules/2.6.32-34-pve/kernel/drivers/scsi/megaraid/megaraid_sas.ko
description: LSI MegaRAID SAS Driver
author: megaraidlinux@lsi.com
version: 06.703.11.00
license: GPL
srcversion: D459B6A575926A72EB8FFAB
alias: pci:v00001000d0000005Fsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Dsv*sd*bc*sc*i*
alias: pci:v00001000d0000005Bsv*sd*bc*sc*i*
alias: pci:v00001028d00000015sv*sd*bc*sc*i*
alias: pci:v00001000d00000413sv*sd*bc*sc*i*
alias: pci:v00001000d00000071sv*sd*bc*sc*i*
alias: pci:v00001000d00000073sv*sd*bc*sc*i*
alias: pci:v00001000d00000079sv*sd*bc*sc*i*
alias: pci:v00001000d00000078sv*sd*bc*sc*i*
alias: pci:v00001000d0000007Csv*sd*bc*sc*i*
alias: pci:v00001000d00000060sv*sd*bc*sc*i*
alias: pci:v00001000d00000411sv*sd*bc*sc*i*
depends:
vermagic: 2.6.32-34-pve SMP mod_unload modversions
parm: max_sectors:Maximum number of sectors per IO command (int)
parm: msix_disable
icon10.gif
isable MSI-X interrupt handling. Default: 0 (int)
parm: msix_vectors:MSI-X max vector count. Default: Set by FW (int)
parm: throttlequeuedepth:Adapter queue depth when throttled due to I/O timeout. Default: 16 (int)
parm: resetwaittime:Wait time in seconds after I/O timeout before resetting adapter. Default: 180 (int)
parm: crashdump_enable:Firmware Crash dump feature enable/disbale Default: enable(1) (int)




-->> DETAIL INFO CONTROLLER :


# MegaCli -AdpAllInfo -aALL

Adapter #0

================================================== ============================
Versions
================
Product Name : LSI MegaRAID SAS 9271-4i
Serial No : SV32510176
FW Package Build : 23.28.0-0015

Mfg. Data
================
Mfg. Date : 06/18/13
Rework Date : 00/00/00
Revision No : 07C
Battery FRU : N/A

Image Versions in Flash:
================
BIOS Version : 5.46.02.1_4.16.08.00_0x06060A03
WebBIOS Version : 6.1-72-e_72-01-Rel
Preboot CLI Version : 05.07-00:#%00011
FW Version : 3.400.45-3507
Boot Block Version : 2.05.00.00-0010

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

PCI Info
================
Vendor Id : 1000
Device Id : 005b
SubVendorId : 1000
SubDeviceId : 9276

Host Interface : PCIE

Number of Frontend Port: 0
Device Interface : PCIE

Number of Backend Port: 8
Port : Address
0 4433221101000000
1 4433221102000000
2 4433221103000000
3 0000000000000000
4 0000000000000000
5 0000000000000000
6 0000000000000000
7 0000000000000000

HW Configuration
================
SAS Address : 500605b006b879f0
BBU : Present
Alarm : Present
NVRAM : Present
Serial Debugger : Present
Memory : Present
Flash : Present
Memory Size : 1024MB
TPM : Absent

Settings
================
Current Time : 18:18:27 12/30, 2014
Predictive Fail Poll Interval : 300sec
Interrupt Throttle Active Count : 16
Interrupt Throttle Completion : 50us
Rebuild Rate : 30%
PR Rate : 30%
Resynch Rate : 30%
Check Consistency Rate : 30%
Reconstruction Rate : 30%
Cache Flush Interval : 4s
Max Drives to Spinup at One Time : 2
Delay Among Spinup Groups : 12s
Physical Drive Coercion Mode : Disabled
Cluster Mode : Disabled
Alarm : Enabled
Auto Rebuild : Enabled
Battery Warning : Enabled
Ecc Bucket Size : 15
Ecc Bucket Leak Rate : 1440 Minutes
Restore HotSpare on Insertion : Disabled
Expose Enclosure Devices : Enabled
Maintain PD Fail History : Enabled
Host Request Reordering : Enabled
Auto Detect BackPlane Enabled : SGPIO/i2c SEP
Load Balance Mode : Auto
Use FDE Only : No
Security Key Assigned : No
Security Key Failed : No
Security Key Not Backedup : No

Any Offline VD Cache Preserved : No

Capabilities
================
RAID Level Supported : RAID0, RAID1, RAID5, RAID6, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, SRL 3 supported
Supported Drives : SAS, SATA

Allowed Mixing:

Mix in Enclosure Allowed
Mix of SAS/SATA of HDD type in VD 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
Min Stripe Size : 8 KB
Max Stripe Size : 1.0 MB

Device Present
================
Virtual Drives : 1
Degraded : 0
Offline : 0
Physical Devices : 4
Disks : 3
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 : Yes
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 : 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

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
Disable Copyback : No
Enable Copyback on SMART : No
Enable Copyback to SSD on SMART Error : Yes
Enable SSD Patrol Read : No
Enable Spin Down of UnConfigured Drives : 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
Stripe Size : 256kB
Flush Time : 4 seconds
Write Policy : WB
Read Policy : Adaptive
Cache When BBU Bad : Disabled
Cached IO : No
SMART Mode : Mode 6
Alarm Disable : Yes
Coercion Mode : None
ZCR Config : Unknown
Dirty LED Shows Drive Activity : No
BIOS Continue on Error : No
Spin Down Mode : None
Allowed Device Type : SAS/SATA Mix
Allow Mix in Enclosure : Yes
Allow HDD SAS/SATA Mix in VD : Yes
Allow SSD SAS/SATA Mix in VD : No
Allow HDD/SSD Mix in VD : No
Allow SATA in Cluster : No
Max Chained Enclosures : 16
Disable Ctrl-R : Yes
Enable Web BIOS : Yes
Direct PD Mapping : No
BIOS Enumerate VDs : Yes
Restore Hot Spare on Insertion : No
Expose Enclosure Devices : Yes
Maintain PD Fail History : Yes
Disable Puncturing : No
Zero Based Enclosure Enumeration : No
PreBoot CLI Enabled : Yes
LED Show Drive Activity : Yes
Cluster Disable : Yes
SAS Disable : No
Auto Detect BackPlane Enable : SGPIO/i2c SEP
Use FDE Only : No
Enable Led Header : No
Delay during POST : 0

Exit Code: 0x00
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!