dabl

Members
  • Posts

    316
  • Joined

  • Last visited

Everything posted by dabl

  1. I started seeing the below running update assistant with the last couple of revisions of the plugin for whatever reason. Diagnostics attached. I'm aware of the need to get rid of the preclear and statistics plugins and the underscore character in my server name before updating from 6.3 to 6.5 Checking for plugin updatesOK: All plugins up to date Checking for plugin compatibilityIssue Found: ca.backup2.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: ca.cleanup.appdata.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: ca.update.applications.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: community.applications.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: dynamix.cache.dirs.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: dynamix.local.master.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: dynamix.ssd.trim.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: dynamix.system.autofan.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: fix.common.problems.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: NerdPack.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: preclear.disk.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: speedtest.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: statistics.sender.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: unassigned.devices.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: unbalance.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.Issue Found: user.scripts.plg () is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues.OK: All plugins are compatible raid_01-diagnostics-20180317-1247.zip
  2. For another opinion I'd never consider running more than one preclear cycle or waiting more than than the 45 hours it takes for a single preclear cycle to complete on an 8 TB drive on my system. In my view the perceived benefits of multiple preclear cycles outweigh the cost but I agree that everyone has to decide for themselves the degree to which they want to pursue this sort of piece of mind.
  3. Same here. Found this which is an older but good discussion and includes references to preclear.
  4. FWIW I have a Supermicro MBD-C2SEE-O and found I had to use the below in the go file (now moved to user scripts plugin) for the Dynamix fan plugin to work modprobe coretemp modprobe w83627ehf I have 4 fans in a SuperMicro SuperChassis 933T-R760B 3U Rackmount case. I'm just seeing this thread now in prep for upgrading to 6.4 I'll be pretty bummed if I can't use PWM with 6.4 since running my fans full speed is super noisy.
  5. I updated to the 2018.01.20 version this morning and now see no results when using the apps tab no matter which section or category I select. Is it just me?
  6. Here is one specific issue mentioned ... If you want to keep the preclear plugin installed, go to the Settings>Unassigned Devices and set the "Enable Preclear rc.diskinfo daemon?" to "No" so it is not used to update the UD status. The rc.diskinfo has not been updated to support the UD mounting of encrypted disks. @gfjardim will need to update the preclear plugin. ...
  7. I'm interested in DSD support as well. binhex, would it be possible to include the file modifications described in this thread?
  8. FYI a sampling of serial numbers for the external packaging and what drives they have been reported to contain List of Serials found so far for BB Easystores
  9. Thanks for posting that. I wonder if anybody might know if the same might apply with the sata backplane in Supermicro SuperChassis 933T-R760 case and those drives with regard to the 3.3v reset issue.
  10. FWIW a reddit resource on these drives WD Easystore 8TB Compendium
  11. Thank you, I look forward to trying this. I seem to remember it was not possible to automatically re-start the HDHomerun DVR engine when the unRAID server was rebooted. Is that no longer a problem or is there a workaround?
  12. Yes I noticed this as well.
  13. I'm interested in DSD support as well. Would it be possible to include the file modifications described in this thread?
  14. My latest preclear of a Western Digital 8 TB WDC_WD80EFAX got stuck at post read 94% I'm using Preclear Disks 2017.07.10, Unassigned Devices 2017.07.09c and unRAID 6.3.5 Attached are the logs. I had a similar failure with a WD 8TB Parity WDC_WD80EFZX using an earlier version of the plugin. I noted back in July that based on several similar posts the WDC_WD80 seemed problematic with the preclear plugin. I don't know if there have been any posts noting success with the plugin and these drives since. My last successfull preclear was on a Seagate Archive 8 TB ST8000AS0002 using Preclear Disks 2017.07.05c, Unassigned Devices 2017.07.04a and unRAID 6.3.3 Also please note the below previous recent posts reporting similar behavior with HGST 4TB and 8TB as well as a Hitachi HDS5C4040ALE630 4TB. 13-AUG-2017 Vibe HGST 4TB 13-AUG-2017 JarDo Hitachi HDS5C4040ALE630 4TB 16-AUG-2017 bbcorn88 8TB HGST raid_01-diagnostics-20170830-0912.zip RAID_01-preclear.disk-20170830-0859.zip
  15. Did you have any success with subsequent attempts on your new drive or HGST 4TB drives using the plugin with default gfjardim-0.8.9-beta script? What about with a modified script run from the command line? One thing that would be hugely helpful is posting with any modified working preclear scripts that can be run from the command line in unRAID v6. Thanks!
  16. Sorry, at the time of the problem CALCULATE run I did not know to look for the log and have since successfully run CALCULATE. For what it's worth, attached is my latest unbalance.log from a successful run after fixing some permissions on my disabled disk 3 per the OPERATION FEEDBACK screen. Also attached are screenshots from the successful run of CALCULATE with the OPERATION FEEDBACK and the run after fixing the permissions. I wanted to avoid any kind of system wide newperms run so ran it manually from an ssh session with newperms /mnt/disk3 After doing that I now seem to be getting a 'clean' CALCULATE with no orange OPERATION FEEDBACK screen. One thing I don't understand is in the unbalance.log after running newperms /mnt/disk3 it still seems to be showing a (group?) [dabl] for some files but when I look at those via ssh ls -l it shows the group as 'users'. Maybe I'm just confused on that. EDIT: also attaching the unbalance.log generated during the run with the OPERATION FEEDBACK screen since I had saved that one. EDIT: Hmm comparing the .log files I see the second run just got appended so that was probably uneccessary (duh) Also what I was seeing with the [dabl] group was actually from the first run and was NOT in the second run...... unbalance.log unbalance log from CALCULATE results OPERATION FEEDBACK .log
  17. Thanks, that's what I figured but for whatever reason when click the CALCULATE button nothing is happening except the CALCULATE button then as expected becomes disabled. I get no console as shown in the doc. Nothing shows in the Log page and the REFRESH button on that page is disabled. Attached is a screenshot. The reason I want to do this is I was headed down the path of converting my reiserfs drives to xfs using a new empty 8 TB drive. The disk 3 that just became disabled is 1.5 TB and I have space available on the 8 TB disk 8. The 8 TB disk 9 is my new empty drive. I'd prefer not to have to rebuild the 1.5 TB reiserfs disk 3 using disk 9 but perhaps that is the best thing to do at this point and then move the data to disk 8 and start the reiserfs to xfs conversion again. To complicate matters disk 6 was showing signs of going bad so I moved the data off that disk using the krusader docker. Disk 6 is now empty and I would like to take it out of service so things don't become even worse if/when disk 6 gets disabled, right in the middle of a move operation for example. I'm open to any/all suggested approaches. EDIT, UPDATE: I turned notifications on and restarted the plugin and am now seeing the console on CALCULATE and output on the Log page so the plugin does appear to at least be working for me now. Am still interested in general input on suggested approaches to my situation.
  18. Is it possible to use this plugin to move files from a disabled disk to a good disk?
  19. Maybe an obvious/not particularly useful observation but it seems there is something about the WD Reds that give the current preclear routine(s)/and or plugin fits. I had the same kind of failures with one of those with an earlier version of the plugin (almost makes it to the end then stalls). The last disk I tried, a Seagate Archive precleared successfully. I wonder if running the one of the preclear routines standalone/independent of the plugin would yield different results. Obviously it is time consuming and frustrating to test this kind of failure.
  20. I wanted to report a successful preclear with the below. I did not see any unexpected behavior. The preclear was started before the latest updates. Thank you to gfjardim and dlandon for these plugins. ====================== Seagate Archive 8 TB ST8000AS0002 Preclear Disks 2017.07.05c Unassigned Devices 2017.07.04a unRAID 6.3.3
  21. So, I see your post in the plugin thread indicating that when you stop the array messages occur every second in your log, presumably due to problems with the plugin?