-
Posts
57 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by daTroll
-
-
Using version 2023.04.08 for the first time, the Action in my History page has only a hyphen ("-") for the most recent run which was completed at noon today. It was running in 4 increments according to the same page. Normally, I would expect the Action to show "Scheduled Non-Correcting Parity-Check" like it did in March.
-
Tiny cosmetic request: the next time you update this plugin, can you please remove the "v" prefix in the version designation? Most of my other plugins use the same YYYY.MM.DD format but without any "v" prefix. Occasionally I like to sort the list of plugins in the WebUI based on version, to quickly identify the oldest/newest.
Cheers,
T
-
Tiny cosmetic request: the next time you update this plugin, can you please remove the "v" prefix in the version designation? Most of my other plugins use the same YYYY.MM.DD format but without any "v" prefix. Occasionally I like to sort the list of plugins in the WebUI based on version, to quickly identify the oldest/newest.
Cheers,
T
-
20 hours ago, jaybee said:
Just realised that for some reason since the last update, when I went into the dynamix sleep plugin page on my server, it had a status in the top right hand corner to say that the plugin's status was "STOPPED". (90% sure it was stopped, off the top of my head but it may have said something else. It was orange in colour). I don't know why this was. I made a change to something in the options, clicked apply, then changed it back and clicked apply again and the status changed to "STARTED". My server then shut down as before last night and normal service resumed.
So it seems for me the latest update did something where the plugin was left in a stopped state for whatever reason. Might be worth checking this.
On my side, the status says “Running” in green. On your suggestion, because the Sleep plugin is no longer working also in my system, I changed the first setting to Disabled. This changed the status to “Stopped” in orange, and like you I seem to recall this is what it said in the past (before the most recent update) as well. I changed the setting back to Sleep, but going to sleep it does not. 🤷♂️ I’m sure I haven’t touched any configuration since it was working, except for installing a few updates including the latest Sleep plugin. -
6 hours ago, sjohnson said:
Still using 6.9.2 as I can't get my LibreELEC VM to work with 6.11 and I get warning that SSD Trim isn't installed warning via Fix Common Problems.
I encountered the same problem in September. It isn’t possible to back out 6.11 if you’re using an SSD. -
The new version of the plugin is showing the correction/noncorrection mode and the support link is working!
-
On 2/12/2023 at 6:00 PM, itimpi said:
If you cancel too quickly or look to soon after cancelling then then this might happen. The plugin runs a monitor task every 17 minutes by default if it is not specifically monitoring an increment (it is more frequent when actively monitoring an increment). You need to give this task time to spot that the check started and later that it finished.
I ran a new test for 26 minutes, cancelled, then waited 20 minutes. The history is still not showing whether I had enabled corrections or not, it now just says "Manual Parity-Check".
Secondly, installing a plugin that does a whole lot more than I want is increasing the complexity of my setup and therefore also the risk for undesirable side effects later. I only want the history display to be a little more informative. I don't have any need for incremental parity-checks etc.
Thirdly, the plugin provides a link to a support thread that is invalid: https://unraid.net/forums/topic/78394-parity-check-tuning
Cheers,
T
-
I expected something like that. After installing the plugin, I tried running manual parity checks, once with and the other without the corrective checkbox ticked. As this takes nearly two days on my system, I then cancelled the processing. Both tests say only "Parity-Check" in the Action column, just like before I had this plugin in my system. It will however be helpful to see future scheduled runs with a different Action, and then any manual run could be implicitly assumed to be corrective. Not perfect but it goes half the mile.
-
Thanks for the suggestion! I've installed this plugin and I see two additional columns in the history: Elapsed Time and Increments. Where can I see the indicator for corrective or non-corrective parity-check?
-
Please? In addition to Action, Date, Size, Duration, Speed, Status and Errors, I think it could be nice to see whether a parity-check was run as corrective or non-corrective.
Cheers,
T
-
Issue solved! This is not a request for support, only intended to help someone who is perhaps facing the same issue I was.
My server has an internal slot for an M.2 PCIe nvme SSD that I use as a cache for the appdata, domains and system shares. The server is on standby during nights using the Sleep plugin. After a wake-on-LAN ping from my iPad in the morning, the cache drive failed to mount. I saw log entries saying I/O error on dev/loop2, and mc displayed the device name in red with a question mark under /mnt. A reboot always solved it, until the next WOL. Other posts here made me double-check that my docker apps were correctly configured with all folders in place, then I suspected a hardware issue. My SSD is less than a year old, but it appears that some controller chips don't support sleep/wake modes. I replaced the SSD with a different make & model, and now the issue is fixed!
The SSD that didn't work is a GAMMIX S50 Lite 512G-CS. The replacement is an Innovation IT SSD M.2 256GB.
Cheers,
T
-
On 9/20/2022 at 3:21 PM, firedo said:
Dynamix S3 Sleep - New Feature (patch included): Array Parity Check/Rebuild
I needed a Sleep inhibitor for the array parity check/rebuild. As I don't want to use HDD spindown's and still want my PC to sleep automatically. I noticed that when going to Sleep Mode the running Array Parity Check was cancelled by the time the PC resumes from sleep. So, I made this modification to your plugin so that you can enable/disable (default: enable) a check that will prevent your PC from going to Sleep/Shutdown Mode when an Array Parity Check/Rebuild is currently running (or paused). The result of the last parity check doesn't matter to the script. Only that it has stopped or finished.
I made these modifications to the plugin, feel free to use them. If you want, you can include some or parts of it in your plugin if you want.
Others can apply it with the below command (after the plugin has started):
cd / && patch -p1 < /path/to/patchfileAnd then restart the s3_sleep script:
/usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/rc.s3sleep restart
Note: These commands must be added to the /boot/config/go script to make them persist after a reboot. An update to the plugin might make the patch not applicable anymore.I've applied your patch but I don't see any new configuration setting for the S3 Sleep plugin. Did I do something wrong, or it's normal?
-
On 10/6/2022 at 11:20 AM, Autchirion said:
did you find a solution for this yet?
Well, yes... I moved ahead to 6.11.0 stable (and .1 just now). -
I've backed out from 6.11.0.rc5 to 6.10.3. Now Fix Common Problems is complaining that Dynamix SSD Trim is missing (it is removed during the 6.11.0.rcx upgrade). I try to reinstall SSD Trim, but it fails:
plugin: installing: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.ssd.trim.plg
plugin: downloading https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.ssd.trim.plg
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.ssd.trim.plg ... done
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.ssd.trim.txz ... failed (Generic error)
plugin: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.ssd.trim.txz download failure (Generic error) -
It's been sorted out as of 6.11.0-rc3, or so I thought… Hopefully it will be fixed in the 6.11 release.
-
14 minutes ago, SimonF said:
I don't know the internal processes being used so I am not sure if there is another way to do this.
Perhaps @AndrewZ can shed some light? -
12 minutes ago, SimonF said:
It is so Unraid knows when drives are accessed, an once it will update disk status and get temp.
Ah... but the GUI doesn't display any temp for a disk that is in standby mode, it only shows * (an asterisk) instead.
It seems to me that an OS could determine whether there is any actual IO on a HDD without asking the controller for stats every second, no??
-
17 minutes ago, trurl said:
Not relevant but we weren't asking about specific dockers or VMs. Even if no dockers or VMs are running, system share still has open files if Docker or VM Manager is enabled in Settings.
Fair enough, and perhaps I wasn't expressing myself clearly. My dockers and VM are both disabled and stopped, and I can still see the activity LEDs are flashing for drives that are in standby mode (not spinning).
Side note: I suppose that UnRAID will not automatically spin down a drive that has the system share or a VM domain on it. For my external drives, the GUI will clearly show when all four drives are in standby mode, and still the LEDs are flashing.
-
7 minutes ago, SimonF said:
I think this is due the way spin ups are detected from 6.9.x onwards. All of my systems HDD LEDs blink approx every 2secs. I think reading IO stats from the controller is detected as usage, but doesn't spin up drives.
This is interesting! My LEDs are flashing about twice every second (i.e. 4 times as fast as yours).
Maybe you are onto something, but why would UnRAID want to read the IO stats from the controller of a disk that UnRAID has put in standby mode?
-
12 minutes ago, trurl said:
According to diagnostics, appdata, domains, system are all on nvme
Correct, and this is a drive that is mounted internally in my mini-PC.
-
22 minutes ago, Squid said:
Are they running or is the service disabled? There's a difference. As @trurl put it, where is the system share located? (if you're using the defaults for the locations)
VM & the Plex docker are definitely not running, and it is still happening. The system share is not on any of the disks in the external enclosure.
-
8 minutes ago, trurl said:
I guess the enclosure doesn't allow hibernate, or at least doesn't allow Unraid to spindown unused disks. Just one of many reasons USB not recommended for array or pools.
But the drives do spin down! This I can see both in the GUI and hear from the enclosure. It's just that the fans keep spinning and the LEDs are flashing. When I attach this enclosure and drives to a Windows PC, both the drives and the enclosure are successfully put into sleep mode (and the LEDs go dark). It's only with UnRAID that the enclosure doesn't sleep. In other words: UnRAID doesn't allow the enclosure to enter sleep mode and the flashing of the activity LEDs appears to be directly related to this.
A friend of mine has a similar setup, but using different brands and models of hardware. He has noticed the same thing, that the external enclosure is never put to sleep automatically when the drives in his enclosure are on standby/spun down.
-
24 minutes ago, Squid said:
If the docker image (or folder) or VM's are enabled and the libvirt image are stored on that drive, it will not sleep
It still doesn't sleep without any docker or VM enabled.
/mnt/user/system/libvert is on an internal drive, i.e. not on one of the external drives in the TerraMaster enclosure that this topic is about.
-
13 minutes ago, trurl said:
Which disk is your system share on?
The system share is on a different cache drive, which is on an internal NVMe disk. Full details (I suppose) are in the attached diagnostics.
[Plugin] Parity Check Tuning
in Plugin Support
Posted
Yeah, that could be it.. I'm running 6.12.0-rc2. The files you asked for are attached (the server hasn't been rebooted yet after the last parity check).
parity.check.tuning.progress.save parity-checks.log untroll-diagnostics-20230418-1115.zip