KokomiCat

I'm now using HP ProLiant MicroServer Gen8, and successfully set my IPMI(using iLO, the IPMI has a different IP from the unRAID's network). When I try ipmi-sensors it says: ID | Name | Type | Reading | Units | Event 18 | UID Light | OEM Reserved | N/A | N/A | 'OEM Event = 0001h' 19 | Health LED | OEM Reserved | N/A | N/A | N/A 20 | 01-Inlet Ambient | Temperature | 17.00 | C | 'OK' 21 | 02-CPU | Temperature | 40.00 | C | 'OK' 22 | 03-P1 DIMM 1-2 | Temperature | 34.00 | C | 'OK' 23 | 04-HD Max | Temperature | N/A | C | N/A 24 | 05-Chipset | Temperature | 47.00 | C | 'OK' 25 | 06-Chipset Zone | Temperature | 37.00 | C | 'OK' 26 | 07-VR P1 Zone | Temperature | 50.00 | C | 'OK' 27 | 08-Supercap Max | Temperature | N/A | C | N/A 28 | 09-iLO Zone | Temperature | 41.00 | C | 'OK' 29 | 10-PCI 1 | Temperature | N/A | C | N/A 30 | 11-PCI 1 Zone | Temperature | 33.00 | C | 'OK' 31 | 12-Sys Exhaust | Temperature | 39.00 | C | 'OK' 32 | 13-LOM | Temperature | N/A | C | N/A 33 | Fan 1 | Fan | N/A | N/A | 'transition to Running' 34 | Power Supply 1 | Power Supply | N/A | N/A | 'Presence detected' 35 | Memory | Memory | N/A | N/A | 'Presence detected' Seems fine, but in the Reading section of the plugin, it only has 127.0.0.1 99 HDD Temperature N/A N/A N/A 35°C Temperature 45.00 50.00 N/A Seems directly read from the unRAID itself. What happened? Is it possible to import the sensors data got from the 'ipmi-sensors' command?

Got it. Does it means that as soon as I use disk for parity, this speed(write at 40MB/s, read at 170MB/s) is the maximum speed I can got actually? But what is the bottleneck? Most of my CPU cores has quite low usage. btw, can enabling turbo write give me continued speed up(eg. 150GB single file write)? And do I need to have a UPS connected in case the reconstruct process was interrupted unexpectedly? And can I get higher performance by changing the filesystem from btrfs to ext4 or other fs?

My configuration: hp microserver gen8 cpu: e3-1265l v2 memory: 16g ddr3l storage: WDC_WD10EZEX(1t hdd) x4, 2 x data, 2 x parity WDC_WDS120G2G0A(120g ssd) x1, as cache way to produce this problem: I use Dynamix System Statistics to monitor the memory utilization and disk stats. I use command below to test write speed. dd if=/dev/zero of=/mnt/user/test/test.dbf bs=8k count=800000 conv=fdatasync I use command below to test read speed. dd if=/mnt/user/test/test.dbf of=/dev/null bs=8k count=800000 I have two shared folders, /mnt/user/test1 has cache set to No, and /mnt/user/test2 has cache set to Prefer.(write to SSD first) Both of these partitions are btrfs. I found that: a) When the memory is enough Both of them have 600MBps read and 600MBps write. b) When the memory is fully occupied for cache test1 has 170MBps read, test2 has 300MBps read the write speed is werid. test1 has only 40MBps write, test2 has 70MBps write Dynamix System Statistics says that the size of memory cache is the same, but disk has both read and write at 100MBps. I thought it might be a problem of the memory cache. When the memory is full and new files are writing, it writes to both the memory for caching and the HDD. As the memory is full, out-dated memory cache writes to HDD, which takes up half of the HDD write speed. However, as the file is too large, the memory cache is useless(not going to be used), instead it write back to the HDD again, which causing the low writing performance. In my opinion, memory cache may be the source of the problem, thus memory cache should be stop, or manually stop on this occassion. This didn't happened on other OS on my server.