Jump to content

CS01-HS

Members
  • Content Count

    45
  • Joined

  • Last visited

Community Reputation

7 Neutral

About CS01-HS

  • Rank
    Advanced Member

Recent Profile Visitors

485 profile views
  1. I just updated and tested. (1) and (3) are fixed but re: (2) it looks like PAUSE (correctly) references the highest temperature disk but RESUME references the lowest temperature disk (it should be highest). Still, plenty good enough. Thank you. Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 12:20:01 NAS parity.check.tuning.php: TESTING: parity temp=38 (settings are: hot=40, cool=35)) Aug 1 12:20:01 NAS parity.check.tuning.php: TESTING: disk1 temp=40 (settings are: hot=40, cool=35)) Aug 1 12:20:01 NAS parity.check.tuning.php: TESTING: disk2 temp=41 (settings are: hot=40, cool=35)) Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Aug 1 12:20:01 NAS parity.check.tuning.php: Paused Non-Correcting Parity Check (86.5% completed) : Following drives overheated: 40 41 Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: written PAUSE (HOT) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd nocheck PAUSE Aug 1 12:20:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 12:20:01 NAS kernel: mdcmd (169): nocheck PAUSE Aug 1 12:20:01 NAS kernel: Aug 1 12:20:02 NAS kernel: md: recovery thread: exit status: -4 Aug 1 12:20:02 NAS parity.check.tuning.php: TESTING: Heat notifications disabled so Pause Following drives overheated: 40 41 not sent Aug 1 12:20:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Aug 1 12:35:01 NAS parity.check.tuning.php: TESTING: parity temp=38 (settings are: hot=40, cool=35)) Aug 1 12:35:01 NAS parity.check.tuning.php: TESTING: disk1 temp=40 (settings are: hot=40, cool=35)) Aug 1 12:35:01 NAS parity.check.tuning.php: TESTING: disk2 temp=41 (settings are: hot=40, cool=35)) Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=2, warm=1, cool=0 Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: Array operation paused but drives not cooled enough to resume Aug 1 12:35:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: parity temp=36 (settings are: hot=40, cool=35)) Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: disk1 temp=34 (settings are: hot=40, cool=35)) Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: disk2 temp=38 (settings are: hot=40, cool=35)) Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: array drives=3, hot=0, warm=2, cool=1 Aug 1 12:40:02 NAS parity.check.tuning.php: Resumed Non-Correcting Parity Check (86.5% completed) as drives now cooled down Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: written RESUME (COOL) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd check RESUME Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 12:40:02 NAS kernel: mdcmd (170): check RESUME Aug 1 12:40:02 NAS kernel: Aug 1 12:40:02 NAS kernel: md: recovery thread: check P ... Aug 1 12:40:02 NAS parity.check.tuning.php: TESTING: Heat notifications disabled so Resume Drives cooled down not sent Aug 1 12:40:02 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end-------
  2. I noticed my drives getting hot during a parity check. It had been a couple of months since I cleaned my fan filter and it was pretty dirty. Cleaned it, reinstalled, and drive temps dropped 8°C ! Maybe monthly or even weekly maintenance is common knowledge but this is my first case with a filter (Silverstone CS01-HS) and it's news to me.
  3. Happy to. Attached with identifying information anonymized (I think.) If I had a nickel... Ha! Yeah I realized I confused you two and edited my post but not in time (my apologies.) disks.ini.txt
  4. First, thanks for this very handy plugin. I think there are minor bugs in the temperature-pausing code: The assigned-slots check (which I believe you just added) reports an incorrect total. I have 3 array disks, 2 cache disks and 4 Unassigned Devices disks. The plugin shows 4 total (I assume array) disks Parity check is paused with hot=1, warm=2, cool=1 and resumed with hot=1, warm=1, cool=2. Seems like pause/resume should be based on hot alone The PAUSE debug reports the label of the overheated drive as "temp" Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: Parity check appears to be paused Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: drives=4, hot=1, warm=2, cool=1 Aug 1 07:50:01 NAS parity.check.tuning.php: Resumed Non-Correcting Parity Check (57.8% completed) as drives now cooled down Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: written RESUME (COOL) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd check RESUME Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 07:50:01 NAS kernel: mdcmd (162): check RESUME Aug 1 07:50:01 NAS kernel: Aug 1 07:50:01 NAS kernel: md: recovery thread: check P ... Aug 1 07:50:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end------- Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: drives=4, hot=1, warm=1, cool=2 Aug 1 07:55:01 NAS parity.check.tuning.php: Paused Non-Correcting Parity Check (58.4% completed) : Following drives overheated: temp Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: written PAUSE (HOT) record to /boot/config/plugins/parity.check.tuning/parity.check.tuning.progress Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD start------ Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: detected that mdcmd had been called from sh with command mdcmd nocheck PAUSE Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MDCMD end------- Aug 1 07:55:01 NAS kernel: mdcmd (163): nocheck PAUSE Aug 1 07:55:01 NAS kernel: Aug 1 07:55:01 NAS kernel: md: recovery thread: exit status: -4 Aug 1 07:55:01 NAS parity.check.tuning.php: DEBUG: -----------MONITOR end-------
  5. Thanks, I meant the Grafana pane settings, maybe a screenshot of the query and customizations if you don't mind? I'm collecting the relevant data with the HDDTemp docker and have everything displaying properly except for spin-up which I couldn't figure out.
  6. Just to follow up on my earlier post re: configuring the plugin to only keep 1 weekly backup, I hacked the code to accept "6" in the Number of days to keep backups field (7 was the lowest non-zero limit) and it's working as expected.
  7. I've got PCI passthrough working for a USB controller (Renesas uPD720202) with the following XML. Mojave recognizes it but performance is terrible, it can't even keep up with mouse movements. Is there a known solution or path to investigate? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev>
  8. Rebuild-DNDC will automatically restart the main container (qBittorrent) as well so it'd help if you lose connectivity but it looks like you haven't since the curl command returns your VPN IP. I don't see any inactivity timeouts in my log just a series of successful curl commands to portchecker.co Sorry I can't help more.
  9. I switched from AFP to SMB in preparation for 6.9. In my environment (High Sierra, Mojave and Calatina) with regular shares and Time Machine, SMB is reliable but with consistently worse performance, and yes I've made the recommended client tweaks. It's Apple's fault for dropping AFP without improving SMB, can't blame Unraid.
  10. Next time it happens test container connectivity by running something like: docker exec -it vpn curl ipinfo.io I renamed my container vpn. Substitute whatever name you have in the command above. If everything's working it should return your VPN IP and additional details. To test the connection and restart containers automatically you can run Rebuild-DNDC available in the Community Apps. Detailed description here: https://github.com/elmerfdz/rebuild-dndc
  11. I'm using what I suspect is an H1110 knock off, $30. So far so good. https://www.ebay.com/itm/133308217106 If I'd known I'd have sprung for real deal: https://www.ebay.com/itm/IBM-81Y4494-H1110-SAS-2-6Gbps-HBA-LSI-9211-4i-P20-IT-Mode-for-ZFS-FreeNAS-unRAID/163937114433 Plenty of cheap no-name/knock offs on ebay. Factor in the price of a cable.
  12. I use a User Script to spin mine down. It works although I see occasional unexplained wake-ups which I haven't tracked down.
  13. Can you post your grafana drive spin-up section so I can steal it?
  14. Smart caching. Pull frequently-accessed files into cache dynamically. Saves power, wear and tear on the array, reduces noise (if your fans vary with HDD temps.)