Fireball3

Members
  • Posts

    1355
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Fireball3

  1. That was after I started it manually. See attached. in /etc/cron.d is the attached file "root" Because it says "Status: stopped". There is nothing cached. Once the drives spin down I have to wait for the drives to spin up when browsing the cached smb shares. Is there a way to check how many entries are actually cached? I'm checking the memory chart within the stats. When using 2.1.1 almost all of my 8GB RAM is "cached". When starting with 2.2.0j there is nothing cached. The only difference is the plugin version. This might not be a good approach though. Not sure about the log snippet you posted. I don't see any cache_dirs entry. Also attached a diagnostics after 10 hours uptime. No abnormal CPU load registered yet. root ps.log pstree.log tuerke-diagnostics-20180927-2014.zip
  2. Here you go. Attached both logs. 1. right after reboot, plugin doesn't start automatically 2 enabled logging, manually started the plugin Now waiting for the CPU load event to happen. tuerke-diagnostics-20180927-1012_fresh_start_after_plugin_install.zip tuerke-diagnostics-20180927-1021_logging_enabled_plugin_manually_started.zip
  3. OK, I'll install the new version, enable logging and give it a reboot. The plugin won't start presumably, then I will start it manually and after a couple of minutes I will dump the logs. Not sure about this one, it's intended to find the process that's keeping the CPU load pinned? If so, I have to wait for the "event" to happen, then I'll dump that info.
  4. Yes, because it is not running! Issue #1 Thanks, definitely a dynamix entry. You mean: crontab -l I will give your modified logging a try when I have a couple of minutes. Maybe the other guys with the same issue can also contribute...
  5. I agree. I would even suggest to have an extra thread for each dynamix plugin... Starting is the one issue. The second is the locking up and using 100% CPU on one core after some time (when manually started). I reverted to v2.1.1 which doesn't have that issues for now.
  6. Sometimes the sas plug will not fit correct. I also got fooled that way, especially if you dont have enough space to fiddle around.
  7. I'm a bit confused. Alex, are you maintaining the new Dynamix CacheDirs plugin or is your talk about some other plugin? Anyway, the Dynamix CacheDirs seems to have some other issues too. Me and some others posted in the Dynamix support thread.
  8. Are you referring to the card BIOS? If your card is operating in IT mode, there is nothing to check/change.
  9. The DELL IT firmware is an intermediate step on the way to the LSI version. Thus, it is incuded in that toolset. Check the readme file to get familiar with the procedure.
  10. Welcome to the unRAID forums. Yes, correct. The H200A is not the integrated version I suppose. See the link in my sig if you need the toolset for crossflashing. It will flash the card to the LSI IT firmware which is more up-to-date then the DELL IT fw. But the DELL firmware will also work. Haven't heard of any issues with unRAID yet. I can't tell, but if either solution is fine for you, there should be no problems. Unless somebody with exactly the same equipment chimes in with his experience, there is no other answer than: "give it a try" unRAID needs IT mode. No answers with regard to your cables, sorry.
  11. For some reason my server didn't shut down last night (as usual). This evening I found it running with one cpu pinned @100% After stopping cache_dirs the cpu load returned to idle. tuerke-diagnostics-20180914-2316.zip
  12. Not sure how Windows determines what Vendor the card is. Maybe the device ID that is not touched during crossflash? How is unRAID recognizing the card? No experience in other OS' here but my guess is: yes, it should
  13. See my sig where it says "xflashing PERCS". If you're on P19 the effort is probably not worth it, although it is just one step and not the whole procedure. BIOS is just increasing boot time. Never heard of any other useful purpose when used with unRAID.
  14. Same issue with cachedirs here. Attaching my diagnostics. tuerke-diagnostics-20180913-2047.zip
  15. System boots obviously, so no need to do this. Can you upload that diagnostics file? I guess there is a NIC driver issue with your onboard NIC. Syslog will hopefully tell us more.
  16. Imho it's better to start with an extended smart test smartctl -t -long /dev/sd... If this test is not positive, you can stop all other actions. If you consider RMAing the drive you need proof that something is wrong. WD insists on a test with their Data Lifeguard Diagnostics Tool. IIRC the improvement of the preclear speeds affected the post-read phase but I might have lost track at some point. You can give the comandline-script a chance and see if it makes a difference. Edit: You can check the progress smartctl -a /dev/sdx or look for the "remaining" smartctl -a /dev/sdx | grep remaining
  17. 9207 is an HBA, that means, sold in IT mode. The download page suggests it can be flashed to IR mode though. The equivalent card in IR mode is obviously called 9217 \firmware\HBA_9217_4i4e_IR\9217-4i4e.bin
  18. The correct syntax, according to the manual, is: -o -sasadd 12344567890
  19. Hi @Oldtimer, welcome to the unRAID forums. See this post.
  20. Hi, I think you have to be able to set this in your software. Otherwise I would expect you to run into errors. https://www.hikvision.com/en/Support/Downloads/User-Manual#prettyPhoto
  21. I wonder what unRAID is doing when we set the "drive spindown"!? Is is also using the drive's apm settings or is it handled different?
  22. I don't know. Edit: Some additional info on APM levels. https://www.freeminded.org/index.php/2012/04/hdparm-power-down-drives-when-not-in-use/
  23. His SMART report says: APM level is: 164 (intermediate level without standby) It can also be set with smartctl -s apm,255 Some testing is required: