Vr2Io

Just FYR, my 1700 on previous release must disable C-State, otherwise it will hang within 24hrs. But after later release, enable C-State seems no issue. Yesterday, I just upgrade lartest BIOS ( new AGESA 1071 ) and RC13, just let it running for a period to check. Due to I never turn-on for 2 days or more, so I can't say stable or not. Update : With lartest BIOS (3203) & RC13, found Syslog have below message. I try change in BIOS ( auto / enable /disable ) same. BIOS version can't down grade. Does that means Kernel won't control C-State Nov 23 04:25:26 X370 kernel: ACPI Error: Needed [Integer/String/Buffer], found [Region] ffff88081e872318 (20170531/exresop-424) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Nov 23 04:25:26 X370 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)

The plugin exclude means exclude for generation hash, so if a file already hash and export, then it will hash_check every time. You may modify the hash file and remove those entry, then execute clear / import once.

Thanks for the update

Thanks for the modify / update, it is a good news for QNAP/Synology NAS user to share the UPS.

Thanks, a good guide.

I also use same MB, but I turn on EPU with C-state off before. This MB also have C-State control. Anyway both on now and stable.

I also notice turn on C-states have save ~10+ w in idle, keep it on now.

Just try update UD with Preclear install, in general no issue found, but my NVMe show again in UD. And then try uninstall Preclear, rc.diskinfo also gone, but UD still show my NVMe. BTW, its minor and once refresh UD won't show it. Thanks your work !!

Sorry for the not clear !! The story was - The NVMe (PLEXTOR PX-512M8PeG) was new add after 6.4rc2 - 1st problem (minor) was NVMe assign to cache and disply as "eui.002303563000fe74 - 512 GB (nvme0n1)", but UD also show "its serial no." with grey colour. If refresh, then it will disappear as expect. UD can mount NVMe if unassign it to cache. - 2nd problem (major) was unRAID bootup always need wait longtime, Syslinix prompt already show, it need wait more ~4min then all disk start mount and GUI up. But you may found the cache disk will be missing. To fix this major problem, you may stop/start the array or reboot again. From the log "rc.diskinfo process" will show several times. To minmise 2nd problem happen, I found set Syslinux prompt waiting longer, i.e. 10s instead 5s, cache missing problem will be gone. But long bootup problem sometime will happen too. After yesterday UD update, UD won't show the NVMe (cache) again. And I also found long bootup and cache missing problem also gone, "rc.diskinfo process" just show one time, the Syslinux prompt also can return to 5s.

Update from 2017.06.23a to 2017.06.28a, my nvme (cache) disk missing and UD identification problem in booting unRAID (6.4rc6) seems gone. Sometimes, this drive me crazy because if problem occur, I need to wait GUI start up ( 6 min instead 2 min ) and stop / start array to fixed.

Yes, I think both may have same function. so I didn't try and I don't want system hang again.

Do you think NOHALT in Syslinux boot loaders would help? http://www.syslinux.org/wiki/index.php?title=Config#NOHALT I haven't try NOHALT but confirm global C-stats disable still need when system in light load. For how much power consumption save I haven't idea, but I think just little. BTW, I running R7 1700 with stock cooler and config one of my case FAN would stop if CPU lower then 45c ( CPU fan running in silent profile ~1200rpm). I found the case FAN always in stop condition, I setting this so I can easy got CPU temp status. NOHALT § NOHALT flag_val If flag_val is 1, do not halt the processor while idle. Halting the processor while idle, significantly reduces the power consumption, but can cause poor responsiveness to the serial console, especially when using scripts to drive the serial console, as opposed to human interaction.

Thanks, I am using same MB too, keep for ref.

May be. Suggest OP check if mainboard BIOS "Interrupt 19 caputre" enable and add-on card BIOS show or not. Usually, I will disable it, this can reduce the boot time.

I have try ASM1061 before, just plug and work. Not sure require or not, I have enable BIOS mainboard AHCI function even no any SATA connect to mainboard. ASM1061 work stable and cool

Just join Ryzen party with R7 1700, Asus Prime X370 pro. The build and test already complete. Thanks @Pauven for the C-State tweak, this save lot of time troubleshoot. - Whole system power draw have some increase, but check not a big deal. ( I have UPS, Socket meter, clamp meter, quick measurment ) - RGB LED mode config retailn in main-board , power-off won't lost. (setting first under Windows) - Quite disappoint the storage throughput, it celling at ~700MB/s. ( LSI 2308, 6 data + 2 parity disks ), CPU usage ~20%, in this moment it seems SW bottoleneck rather then HW issue.

Nice build

@ufopinball Thanks your reply, due to you own ASUS Prime X370-PRO, so I already add you to follow member sometimes before. I have consider a upgrade plan for a long time, I use a rather low end system w CPU G3250, just 2 core. A low cost and easy way was just upgrade to a 4 core CPU and cost ~$167, but this won't be long term, so I consider Ryzen 1700, but need ~$642 and lot of work / risk. Hope I will make it success soon, btw I also target a coming soon GPU gtx1030. I am not a gamer/VM fans, so I still not sure upgrade a storage system to 8C16T worth or not.

Thanks for the update. I am planning upgrade to Ryzen and target same mainboard. Does anyone know Ryzen i.e. 1700 will greatly improve mulitiple file hash throughput, I can't found the answer, thanks

I just thinking those abnormal result and try to reproduce. I belive those relate some calculation bug, but not sure only happen in 6.3.3 or not. ( BTW this may not be same as OP case ) Say short in long, I force unRAID belive the array ( with 6TB parity ) was clean, then I make a 3TB disk disable and add again, so it will perform sync on that 3TB disk. In fact, the max speed just ~110/MB/s ..... after complete, the result will be like that. The calculation wrongly count by 6TB instead of 3TB.

May I know below update will affect any access of built-in Syslog, thanks enhanced.log 2017.02.19 Replace the built-in Syslog with the enhanced Syslog.

Thanks, love this plugin .

Just new apply UD, that is great feature. Is it possible UD follow the Display setting "Used / Free columns" & center alignment the number , thanks.

Thanks a lot for your report. Please update and try again. The running preclear sessions won't stop because of the update. Just have update, it work now, thanks a lot.

Just install this beta plugin @ my 6.2 beta23 server, it can run in the PLUS licence server but not in the TRIAL licence server. The web console just show "Starting", but in fact "dd" not running. 1.jpg After some troubleshooting, it seems to be problem on "usr/bin/tmux" root@Tower:/usr/bin# /usr/bin/tmux new-session -d -x 140 -y 200 -s preclear_disk_sdb /usr/bin/tmux: error while loading shared libraries: libutempter.so.0: cannot open shared object file: No such file or directory BTW, I can run preclear if execute script directly /bin/bash /usr/local/emhttp/plugins/preclear.disk.beta/script/preclear_disk.sh --notify 1 --frequency 3 --cycles 5 --skip-preread --skip-postread --no-prompt /dev/sdb 2.jpg Thanks