[solved/found] fsyncs/second dropped to the ground: what to check?

M

m.ardito

Famous Member
Feb 17, 2010
1,473
17
103
Torino, Italy
Hi,

i was following another thread, and decided to compare my fsyncs/second with pveperf...

and i discovered on my 2 cluster nodes that fsyncs/seconds dropped to 60 or so... :(

i don't do those test regularly, and vm and backups are doing fine, afaik...

but searched the forums and some time ago I had 1700 on the exact same nodes, same everything, same nas...
http://forum.proxmox.com/threads/7717-pve-backup-speeds-on-my-server-should-be-better
for sure not same pve... but can't remember which version was then...

Code: 
pveperf
CPU BOGOMIPS:      72537.76
REGEX/SECOND:      788290
HD SIZE:           16.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    151.74 MB/sec
AVERAGE SEEK TIME: 4.21 ms
FSYNCS/SECOND:     1721.37
DNS EXT:           32.65 ms
DNS INT:           0.75 ms

obviously all vms are running during pveperf, with some disks on lvm/iscsi, some on nfs share (raw, mostly)

what can cause this disk performance drop? and what to check? :confused:

now I have
Code: 
pveperf
CPU BOGOMIPS:      72523.72
REGEX/SECOND:      707274
HD SIZE:           16.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    144.77 MB/sec
AVERAGE SEEK TIME: 3.80 ms
FSYNCS/SECOND:     58.13
DNS EXT:           68.05 ms
DNS INT:           0.86 ms

Code: 
 pveversion -v
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

the servers are ibm x3650m2 with 2 hw mirrored local sata disks
disk storage is lvm/scsi over a 1gb eth connection to a qnap ts809u
or nfs over a 1gb eth connection to a qnap ts809u
the 1gb eth connection is on the same nic
qnap ts809u has 8 1,5TB sata2 disk in sw raid5 (hardware serveraid m5015)

Thanks all
Marco
 
Last edited:
Re: fsyncs/second dropped to the ground: what to check?

if you do not provide a path pveperf test the root file system, you can also test others.

e.g. pveperf /var/liv/vz

- provide info about your harddisks, raid controller and settings.
- output of 'cat /proc/mounts' (only the relevant parts of the specific mount point with the performance issue)
 
Re: fsyncs/second dropped to the ground: what to check?

You are testing your root file system that is under RAID controller if I understand right.
Usualy such drops are due to the raid controller working in "write through" instead of "write back". Write back is risky if you don't have the cache safeguarded by a BBU. Many controllers with BBU can be set to act in WriteBack while BBU is operational, and "fall back" to WriteThrough once it's exausted. So have a look at your controller settings, features and BBU (if any available) state.
 
Re: fsyncs/second dropped to the ground: what to check?

hope to not forget anything...

pveperf /var/lib/vz on node 1
Code: 
CPU BOGOMIPS:      72523.72
REGEX/SECOND:      793472
HD SIZE:           32.54 GB (/dev/mapper/pve-data)
BUFFERED READS:    138.83 MB/sec
AVERAGE SEEK TIME: 4.16 ms
FSYNCS/SECOND:     59.19
DNS EXT:           70.17 ms
DNS INT:           0.79 ms

pveperf /var/lib/vz on node 2
Code: 
pveperf /var/lib/vz
CPU BOGOMIPS:      72522.89
REGEX/SECOND:      886932
HD SIZE:           32.54 GB (/dev/mapper/pve-data)
BUFFERED READS:    143.06 MB/sec
AVERAGE SEEK TIME: 4.72 ms
FSYNCS/SECOND:     58.60
DNS EXT:           177.16 ms
DNS INT:           0.76 ms

About the servers:
IBM Xseries 3650 m2
2 x Intel Xeon Quad Core E5520 2,26 Ghz
hw raid w/bbu
------------
lspci -v | grep -i raid
01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 03)
Subsystem: IBM ServeRAID M5015 SAS/SATA Controller
Kernel driver in use: megaraid_sas
------------
Hard Disk: n° 2 x 73 Gb 15.000rpm SAS -
RAM 20 Gb PC3-10600 CL9 ECC DD3-13

About the iscsi NAS:
Qnap TS-809U
capacity 12 Tb (8 Hard Disk SATA II da 1,5 Tb / each) SAMSUNG HD154UI 1AG0, raid5 (i guess sw raid on qnap)

cat /proc/mounts on both nodes (full ouput, not sure what is not relevant ...)

Code: 
cat /proc/mounts
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=10263784k,nr_inodes=2565946,mode=755 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0

/dev/mapper/pve-root / ext3 rw,relatime,errors=remount-ro,barrier=0,data=ordered 0 0

tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0

/dev/mapper/pve-data /var/lib/vz ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/sda1 /boot ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0

fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0

/dev/fuse /etc/pve fuse rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0

none /sys/kernel/config configfs rw,relatime 0 0
beancounter /proc/vz/beancounter cgroup rw,relatime,blkio,name=beancounter 0 0
container /proc/vz/container cgroup rw,relatime,freezer,devices,name=container 0 0
fairsched /proc/vz/fairsched cgroup rw,relatime,cpuacct,cpu,cpuset,name=fairsched 0 0

<qnap_lan_ip>:/iso_images /mnt/pve/iso_qnap nfs rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=<qnap_lan_ip>,mountvers=3,mountport=771,mountproto=udp,local_lock=none,addr=<qnap_lan_ip> 0 0


======================

cat /proc/mounts
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=10263784k,nr_inodes=2565946,mode=755 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0

/dev/mapper/pve-root / ext3 rw,relatime,errors=remount-ro,barrier=0,data=ordered 0 0

tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0

/dev/mapper/pve-data /var/lib/vz ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/sda1 /boot ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0

fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0

/dev/fuse /etc/pve fuse rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0

none /sys/kernel/config configfs rw,relatime 0 0

beancounter /proc/vz/beancounter cgroup rw,relatime,blkio,name=beancounter 0 0
container /proc/vz/container cgroup rw,relatime,freezer,devices,name=container 0 0
fairsched /proc/vz/fairsched cgroup rw,relatime,cpuacct,cpu,cpuset,name=fairsched 0 0

/var/lib/vz/private/108 /var/lib/vz/root/108 simfs rw,relatime 0 0
proc /var/lib/vz/root/108/proc proc rw,relatime 0 0
sysfs /var/lib/vz/root/108/sys sysfs rw,relatime 0 0
tmpfs /var/lib/vz/root/108/var/run tmpfs rw,nosuid,nodev,noexec,relatime,size=524288k,nr_inodes=131072,mode=755 0 0
tmpfs /var/lib/vz/root/108/var/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=524288k,nr_inodes=131072 0 0
tmpfs /var/lib/vz/root/108/dev/shm tmpfs rw,relatime,size=524288k,nr_inodes=131072 0 0
devpts /var/lib/vz/root/108/dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /var/lib/vz/root/108/var/run tmpfs rw,nosuid,nodev,noexec,relatime,size=524288k,nr_inodes=131072,mode=755 0 0
tmpfs /var/lib/vz/root/108/var/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=524288k,nr_inodes=131072 0 0

<qnap_lan_ip>:/iso_images /mnt/pve/iso_qnap nfs rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=<qnap_lan_ip>,mountvers=3,mountport=771,mountproto=udp,local_lock=none,addr=<qnap_lan_ip> 0 0
 
Re: fsyncs/second dropped to the ground: what to check?

adding raid controller info... sorry it's huge...

Code: 
megacli -AdpAllInfo -aALL

Adapter #0

==============================================================================
                    Versions
                ================
Product Name    : ServeRAID M5015 SAS/SATA Controller
Serial No       : SV94803337
FW Package Build: 12.0.1-0064

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

                Image Versions in Flash:
                ================
BIOS Version       : 3.07.00
FW Version         : 2.0.03-0689
Preboot CLI Version: 02.00-010:#%00008
WebBIOS Version    : 3.0-19-e_10-Rel
NVDATA Version     : 2.02.0031
Boot Block Version : 2.00.00.00-0018
BOOT Version       : 01.250.04.219

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

                PCI Info
                ================
Vendor Id       : 1000
Device Id       : 0079
SubVendorId     : 1014
SubDeviceId     : 03b2

Host Interface  : PCIE

Number of Frontend Port: 0
Device Interface  : PCIE

Number of Backend Port: 8
Port  :  Address
0        5000c5001d39ebf1
1        5000c50016f80dd9
2        0000000000000000
3        0000000000000000
4        0000000000000000
5        0000000000000000
6        0000000000000000
7        0000000000000000

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


                Settings
                ================
Current Time                     : 10:0:14 7/11, 2013
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 : 2
Delay Among Spinup Groups        : 12s
Physical Drive Coercion Mode     : 1GB
Cluster Mode                     : Disabled
Alarm                            : Disabled
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                     : 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 : 0
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

                Capabilities
                ================
RAID Level Supported             : RAID0, RAID1, RAID5, RAID00, RAID10, RAID50, PRL 11, PRL 11 with spanning, SRL 3 supported, 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            : 80
Max Data Transfer Size   : 8192 sectors
Max Strips PerIO         : 42
Max LD per array         : 16
Min Strip Size           : 8 KB
Max Strip Size           : 1.0 MB
Max Configurable CacheCade Size: 0 GB
Current Size of CacheCade      : 0 GB
Current Size of FW Cache       : 0 MB

                Device Present
                ================
Virtual Drives    : 1
  Degraded        : 0
  Offline         : 0
Physical Devices  : 3
  Disks           : 2
  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
Snapshot Enabled                : No
Support the OCE without adding drives : No
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         : No
Support Breakmirror  : No
Power Savings        : 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
Support Temperature                     : No
Disable Copyback                        : No
Enable JBOD                             : No
Enable Copyback on SMART                : No
Enable Copyback to SSD on SMART Error   : Yes
Enable SSD Patrol Read                  : No
PR Correct Unconfigured Areas           : Yes
Enable Spin Down of UnConfigured Drives : No
Disable Spin Down of hot spares         : No
Spin Down time                          : 0
T10 Power State                         : No
                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                       : 128kB
Flush Time                       : 4 seconds
Write Policy                     : WB
Read Policy                      : None
Cache When BBU Bad               : Disabled
Cached IO                        : No
SMART Mode                       : Mode 6
Alarm Disable                    : No
Coercion Mode                    : 1GB
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     : No
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               : Yes
Zero Based Enclosure Enumeration : No
PreBoot CLI Enabled              : Yes
LED Show Drive Activity          : No
Cluster Disable                  : Yes
SAS Disable                      : No
Auto Detect BackPlane Enable     : SGPIO/i2c SEP
Use FDE Only                     : Yes
Enable Led Header                : No
Delay during POST                : 4
EnableCrashDump                  : No
Disable Online Controller Reset  : No
EnableLDBBM                      : No
Un-Certified Hard Disk Drives    : Allow
Treat Single span R1E as R10     : No
Max LD per array                 : 16
Power Saving option              : All power saving options are enabled
Default spin down time in minutes: 0
Enable JBOD                      : No
Time taken to detect CME         : 60s
 
Re: fsyncs/second dropped to the ground: what to check?

maybe your BBU is defect and therefore your controller disabled write-back.
 
Re: fsyncs/second dropped to the ground: what to check?

I'm pretty sure your BBU is not working, since in your above settings I see "Cache When BBU Bad : Disabled").
Check with:
Code: 
megacli -AdpBbuCmd -GetBbuStatus -aALL | grep -i 'battery state'
(or without grepping, read and check all items)
and current cache policy with:
Code: 
megacli -LDInfo -Lall -Aall | grep -i 'Current Cache Policy'
 
Re: fsyncs/second dropped to the ground: what to check?

mmenaz said:
I'm pretty sure your BBU is not working,
Click to expand...

...on both nodes..? anyway:

megacli -AdpBbuCmd -GetBbuStatus -aALL | grep -i 'battery state'
one node:
Code: 
Battery State     : Operational

other node:
Code: 
Battery State     : Non Operational

megacli -LDInfo -Lall -Aall | grep -i 'Current Cache Policy'

both nodes
Code: 
Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU

so, it appears one bbu is on the other off... why both nodes have so bad fsyncs/second? isn't that strange? both server have same exact age, i'm sure.

i will make someone check bbus but in the meanwhile what are the safest settings, both in pve, vms, raid card that I can keep/apply?

Thank you so much...

Marco
 
Re: fsyncs/second dropped to the ground: what to check?

...problem found,
for completeness sake I'm reporting the output of
Code: 
megacli -AdpBbuCmd -GetBbuStatus -aALL

for both nodes, may help someone else...

Code: 
megacli -AdpBbuCmd -GetBbuStatus -aALL

BBU status for Adapter: 0

BatteryType: iBBU
Voltage: 4053 mV
Current: 0 mA
Temperature: 26 C

Battery State     : Operational

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
  [COLOR=#ff0000][B]Battery Replacement required            : Yes[/B][/COLOR]
  Remaining Capacity Low                  : Yes
  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



GasGuageStatus:
  Fully Discharged        : No
  Fully Charged           : Yes
  Discharging             : Yes
  Initialized             : Yes
  Remaining Time Alarm    : No
  Remaining Capacity Alarm: No
  Discharge Terminated    : No
  Over Temperature        : No
  Charging Terminated     : No
  Over Charged            : No

Relative State of Charge: 97 %
Charger System State: 49168
Charger System Ctrl: 0
Charging current: 0 mA
Absolute state of charge: 46 %
Max Error: 2 %

Exit Code: 0x00

Code: 
 megacli -AdpBbuCmd -GetBbuStatus -aALL

BBU status for Adapter: 0

BatteryType: iBBU
Voltage: 4058 mV
Current: 0 mA
Temperature: 26 C
Battery State     : Non Operational

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
  [COLOR=#ff0000][B]Battery Replacement required            : Yes[/B][/COLOR]
  Remaining Capacity Low                  : Yes
  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


GasGuageStatus:
  Fully Discharged        : No
  Fully Charged           : Yes
  Discharging             : Yes
  Initialized             : Yes
  Remaining Time Alarm    : No
  Discharge Terminated    : No
  Over Temperature        : No
  Charging Terminated     : No
  Over Charged            : No
  Relative State of Charge: 100 %
  Charger System State: 49168
  Charger System Ctrl: 0
  Charging current: 0 mA
  Absolute state of charge: 27 %
  Max Error: 2 %

Exit Code: 0x00
 
Re: fsyncs/second dropped to the ground: what to check?

thanks for the solution of your hardware issue and I am glad that I moved already most of my servers to a "zero-maintenance" BBU :)
 
Re: fsyncs/second dropped to the ground: what to check?

mmenaz said:
I'm pretty sure your BBU is not working, since in your above settings I see "Cache When BBU Bad : Disabled").
Check with:
Code: 
megacli -AdpBbuCmd -GetBbuStatus -aALL | grep -i 'battery state'
(or without grepping, read and check all items)
and current cache policy with:
Code: 
megacli -LDInfo -Lall -Aall | grep -i 'Current Cache Policy'
Click to expand...

How do you install megacli ? using this http://hwraid.le-vert.net/wiki/DebianPackages ?
===
OK,answer myself ,just find http://pve.proxmox.com/wiki/Raid_controller
 
Last edited:
Re: fsyncs/second dropped to the ground: what to check?

i have this in /etc/apt/sources.list

deb http://hwraid.le-vert.net/debian squeeze main

my device

#lspci -vvv | grep -i raid

01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 03)
Subsystem: IBM ServeRAID M5015 SAS/SATA Controller
Kernel driver in use: megaraid_sas

http://pci-ids.ucw.cz/read/PC/1000/0079

there is also official lsi software but not for debian... and not for pve for sure :)

http://www.lsi.com/support/Pages/Download-Results.aspx?keyword=2108

Marco
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back