dabl

Members
  • Posts

    306
  • Joined

  • Last visited

Everything posted by dabl

  1. This has been requested by multiple people in this thread. One user came up with a client side browser script and posted the recipe but of course that (and presumably the plugin to process it) would need to be installed on all browser clients that access the server to be effective on them. I suppose making use of typical browser plugin syncing features would make copying the initial install to other clients using the same browser easy though.
  2. So about this script to move the plugin as requested, thanks cinereus! Should it simply be executed after boot? Will a reboot reset it if the result after running the script doesn't work out?
  3. +1 I hadn't noticed or thought to look until I read this thread.
  4. Ok, well then this may or may not apply but I had the same sort of thing happen with my Supermicro motherboard which has a feature in the bios that cannot be shut off that wants to try and control the fans. For unknown reasons after updating to unraid 6.8.2 my fans started behaving like yours. This is a known problem with some Supermicro motherboards caused by the bios thinking the fan (now otherwise being controlled by another piece of fan control software) has started spinning at too low an rpm and taking over to make it run faster. Then the other fan control software sees this and combined with an otherwise ok temp it tries to slow the fan down. Rinse and repeat. So the bios is fighting the other fan control software, in this case the dynamix plugin. I solved it by running a Supermicro specific utility (IPMITOOL) to lower the threshold of the fan rpm that would cause the bios to worry and take over. No idea why I needed to do that all of a sudden though after a long time of things running fine using the dynamix plugin. Per previous reports it seems changes in unraid can cause different behavior with the dynamix fan plugin. I'm currently running unraid 6.8.2 and reverted back to the 2019.11.03 dynamix.system.temp and 2017.10.15 v1.5 dynamix.system.autofan for the same good fan behavior I had before. I wanted to at least get a sanity check before updating to unraid 6.8.3
  5. Is your motherboard made by Supermicro?
  6. Same here except I have a SuperMicro X9SRL-F and am on Unraid 6.8.2 and the bad behavior started after updating dynamix.system.autofan from the previously working 2017.10.15 version. It's worth noting I saw and reported this kind of behavior before last year. In those cases it seemed to be related to changes in Unraid (6.7.0) Either way none of the reports here were acknowledged. See posts 1, 2, 3, 4 Same as before I am reverting to unraid-fan-speed.sh called from the User Scripts plugin. The best and most helpful write up I found implementing unraid-fan-speed.sh from another user also noting the broken Dynamix System AutoFan, is here. One additional oddity in behavior with dynamix.system.autofan 1.6 on my system is that after entering a stopped state I set the plugin to disabled and sometime after that the plugin state changed to running again.
  7. Thanks for the awesome work on the scripts, greatly appreciated!
  8. Awesome thanks! Yep, works great after making the required changes. Would absolutely be interested in the 2 scripts that do the same with all disks and shares.
  9. If you'd be willing to share these scripts they sound really useful. I understand they'd have to be tweaked to work on another system.
  10. I did. I definitely looked at the available SuperMicro 4U 24 bay models on ebay at the time and didn't find one that seemed to be a match but if I had I would have certainly considered it. One of the big draws of the one I picked is the quiet power supplies. I have an existing 3U SuperMicro chassis so was used to that and now I'm thinking of making that one an off site backup to the new one. There's a part of me that hopes I won't regret getting a 4U with more drives though.
  11. To the ebay seller's great credit they immediately de-activated that listing and later found me a real one with the rear drives installed. Woo hoo, squeeky wheel and all that
  12. Thank you johnnie.black for answering so many questions here, it is greatly appreciated! So given what you've said so far it sounds like I should use a single IBM M1015 with one of the SFF-8087 connectors cabled to the first of the 3 primary SAS connectors on the BPN-SAS2-836EL1 backplane (PRI_J1) and the other SFF-8087 connector on the IBM M1015 cabled to the second of the 3 primary SAS connectors on the BPN-SAS2-836EL1 backplane (PRI_J2)? I'm curious what PRI_J3 would typically be used for? I have to admit I find the BPN-SAS2-836EL Backplane guidance pretty confusing with regard to cabling. Maybe part of the problem is that manual covers both BPN-SAS2-836EL1 and EL2 backplanes. The only scenario in the manual where I see discussion of using the second of the 3 primary SAS connectors on the BPN-SAS2-836EL1 backplane is when connecting to a 'lower backplane in cascaded a system' (see below pic) but I may well be missing something. When choosing a PCI-E slot on the X9SRL-F for the IBM 1015 card, which from the below would you recommend given that I will (probably) have no other PCI-E cards in the system. It's an outside possibility I'd put a graphics card in at some point to do gaming or video transcoding. PCI-E 3.0x8 (in x16 Slot), PCI-E 3.0x8 (in x8 Slot), PCI-E 3.0x4 (in x8 Slot), PCI-E 2.0x4 (in x8 Slot) The X9SRL-F manual chipset configuration starting on p78 has some discussion of Data Direct I/O, DCA Support and PCIe Port Bifurcation Control that I'm not familiar with. Any guidance on how these should be set for the IBM 1015 greatly appreciated. I presume for the SATA Mode I want AHCI correct? Data Direct I/O Select Enabled to enable Intel I/OAT (I/O Acceleration Technology), which significantly reduces CPU overhead by leveraging CPU architectural improvements and freeing the system resource for other tasks. The options are Disabled and Enabled. DCA Support This feature accelerates the performance of I/O devices using Direct Cache Access. The options are Enabled and Disabled. IIO 1 PCIe Port Bifurcation Control This submenu configures the following IO PCIe Port Bifurcation Control settings for IIO 1 PCIe ports to determine how the available PCI-Express lanes to be distributed between the PCI-Exp. Root Ports. CPU1 Slot2 PCI-E 3.0 x4 (IN x8) Link Speed This feature enables the user to select the target link speed for this slot. The options are GEN1 , GEN2, and GEN3. .... SATA Mode This item selects the mode for the installed drives. The options are Disabled, IDE Mode, AHCI Mode and RAID Mode.
  13. Thanks! I decided to get the SuperMicro CSE-836BE16-R920B Chassis with a BPN-SAS2-836EL1 backplane for use with a SuperMicro X9SRL-F motherboard and initially at least one of the 2 IBM M1015 controllers I have. I'm moving from an older SuperMicro chassis with 16 drive slots currently loaded with all sata drives. I've been using the Western Digital WD100EMAZ drives that come in the EasyStore external enclosures. If I move those sata drives to the new chassis using and find that a single IBM 1015 card connection to the BPN-SAS2-836EL1 backplane doesn't have enough bandwidth for the 16 drives can anyone recommend a good choice for a better controller? I don't know anything about sas drives at the moment but would like to learn and if those seem to be a better bet for the future I'd be interested in a recommended controller that would handle those.
  14. As I expected the seller got back to me with the admission the chassis in this listing was mis-identified.
  15. Can anyone please confirm/deny this listing for a SuperMicro CSE-836BE16-R920B looks to be the real thing with the 920W SQ power supplies and the option of adding two hot-swap 2.5" hard disk drives accessible from the rear of the chassis using the MCP-220-83605-0N kit? I've seen comments saying that when one sees the grounding lug on the panel below the power supplies in the seller's picture that indicates it is not in fact a B chassis. I also noticed the manual that covers all the 836 models shows a cable routing port near the power supply for the B chassis that doesn't seem to be present in the seller's pics. I have an inquiry into the seller.
  16. Thanks! I'm also looking at a CSE-836 or SC836E1-R800B chassis both with SAS-836TQ Backplane I've seen comments from people who seem to want to avoid expanders in favor of direct connect so would be interested in any comments on that with regard to this specific hardware. One thing I really like about the CSE-836BE16-R920B chassis is the capability to run two 2.5" hot swap drives in the rear so I'd be inclined to try the expander on that model unless there are reasons to avoid it.
  17. I am looking at a SuperMicro CSE-836BE16-R920B Chassis with a BPN-SAS2-836EL1 backplane for use with 2 IBM 1015 HBA controllers in IR/IT mode. The motherboard will be a SuperMicro X9SRL-F. Maybe I'm misunderstanding the specs in the chassis and backplane manuals but it seems like the backplane has 3 primaray SAS connectors PRI_J1, PRI_J2 and PRI_J3. Each IBM 1015 HBA controller has 2 SFF-8087 connectors so I'm confused on how I'd use 4 total connectors from the 2 1015 cards to control 16 drives and connect those to the 3 primary SAS connectors available on the backplane?
  18. These should be removed from Community Applications so others aren't misled into installing non-working plugins where support for them has been abandoned
  19. After becoming disabled again very shortly this time after getting it restarted I gave up on the Dynamix plugin for now and returned to using unraid-fan-speed.sh with the user scripts plugin to start at boot. I forgot the 'cron' part was built into the script. I disabled the Dynamix fan auto control plugin but the speed of the fans shows up on the dashboard 'Airflow' section which is good.
  20. Same thing again, guess I'm an idiot to keep trying this vs returning to good old fanspeed.sh and cron....... raid-01-diagnostics-20190724-2155.zip
  21. Since the above post from 6/26/2019 and re-enabling per above the plugin maintained a Status of 'Running' for 12 days then stopped again for whatever reason. Re-enabling this time per above took many attempts to get a Status of 'Running'. Hopefully the attached diagnostics will be of some use. raid-01-diagnostics-20190709-1749.zip
  22. Another user after updating to Unraid 6.7.0 seeing the Dynamix Auto Fan Control plugin behavior broken but in my case not all the way. From a Status: Stopped state I can reset using the Default button and enable, detect and apply and it will run for some period of time, still not sure what length of time that is exactly but it seems to be longer than 12 hrs but shorter than 24 hrs. Diagnostics attached. raid-01-diagnostics-20190626-1220.zip
  23. Here's the original request at the top of the page with a link to the details.
  24. Yep, I too am still very interested in DSD support