sourCream
-
Posts
69 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by sourCream
-
-
7 hours ago, Swarles said:
Do either of you get the "mover: started...mover: finished" syslog?
Also, are either of you using the "Move now button follows plugin filters" set to yes?
Robbie G78: Being able to invoke the mover from the share is strange because it calls the mover in the same way that using the move button and the schedule does.
Just and FYI I am on 6.12.3 with Mover Tuning 2023.08.22 and both the schedule and move button working for me. Strange indeed.
Also having this same issue. I can invoke mover from the share page but cannot do so from the main page or the scheduler page. I have the "Move now button follows plugin filters" set to No.
I sent some logs and all my settings being used to hugenbdd.
What I have not tried is toggling the button filter to yes the back to no or removing and reinstalling the plugin.
-
Working well now. Thank you for the help and the quick fix.
-
So I went into my flash drive and under config > plugins I deleted anything related to unassigned devices. Rebooted and installed UD and I am able to mount the remote share, however.. the share is not visible anywhere and can't be navigated to outside of unRAID's Web UI
EDIT: Took a few minutes for the share to pop up but I think its working now.
- 1
-
Just now, dlandon said:
You removed the mount by clicking on the 'X' and then created the SMB mount again? Post diagnostics.
Yes tried adding and re-adding multiple times in between reboots even.
-
1 minute ago, dlandon said:
Be sure you have updated to 2020.01.18a and then remove and re-add. It won't work properly until you have the latest version of UD.
I have.
-
4 minutes ago, dlandon said:
After the latest UD update, the SMB mounts with passwords need to be removed and re-added.
Yep I have done all that. What I don't understand is I can create a share on a separate machine or vm and I have no issues mounting the share through UD.
-
29 minutes ago, Squid said:
Not that I'm the one to help here, but a quick bit of research for dlandon results in https://access.redhat.com/solutions/450913
EDIT: do you have any weird / special characters in your credentials?
all lowercase, no caps, no specials or spaces.
-
I am trying to mount a drive that I have in another machine (windows) on my LAN but when I click the mount button it acts like it will mount then returns the following error.
Status code returned 0xc000006d STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13
Jan 19 15:23:59 Atlantis unassigned.devices: Mount of '//192.168.1.234/Network_Backup' failed. Error message: 'mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.Here's what I have tested/attempted so far:
Uninstalled Unassigned Devices/Reboot/Reinstall
Created a share on another machine on my network and it mounted right away
Checked permissions on the remote system (nothing changed)
Credentials are correct and I have no problem seeing shares on network from within Unassigned Devices
I should add I've never had this issue with this setup and was working previously. Only thing I've done recently is upgrade to 6.8.0 then back to 6.7.2 and then to 6.8.1 and back to 6.7.2
-
20 minutes ago, Squid said:
Due to recent changes in UD, all SMB mounts must be recreated.
I have removed all mounts from UD, uninstalled UD and reinstalled and rebooted between each. Still the same error.
-
I am trying to mount a drive that I have in another machine (windows) on my LAN but when I click the mount button it acts like it will mount then returns the following error.
Status code returned 0xc000006d STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13
Jan 19 15:23:59 Atlantis unassigned.devices: Mount of '//192.168.1.234/Network_Backup' failed. Error message: 'mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.Here's what I have tested/attempted so far:
Uninstalled Unassigned Devices/Reboot/Reinstall
Created a share on another machine on my network and it mounted right away
Checked permissions on the remote system (nothing changed)
Credentials are correct and I have no problem seeing shares on network from within Unassigned Devices
EDIT: I should add I've never had this issue with this setup and was working previously. Only thing I've done recently is upgrade to 6.8.0 then back to 6.7.2 and then to 6.8.1 and back to 6.7.2
-
Also fixed the problem for me too. Thank you all for the help.
-
Just updated to the new Plex Beta 1.16.3.1402 and I'm no longer getting the errors.
-
3 hours ago, drawmonster said:
I'm on the same PMS version mentioned above. And I get the errors every time I scan my music library. So I think that's where the issue is.
Same here. Version 1.16.2.1297. Happens only when I scan the music library.
-
-
http://www.crucial.com/usa/en/support-ssd?cm_re=us-support-_-main-_-firmware-update-link
Firmware M3CR022 has been tested and qualified for immediate release in the Crucial factory, including 2.5-inch and M.2 models of the MX500 SSD. The update from M3CR010 to M3CR022 is an optional update for SSDs in the field, but is recommended if the MX500 is experiencing any of the following issues:
- Improved ready time from DEVSLP low-power state.
- Improved TRIM and Wear Leveling performance.
- Improved SATA error handing.
- Improved compatibility with some TCG Opal 2.0 third-party encryption utilities (this change does not affect MS BitLocker).
[Plugin] Mover Tuning
in Plugin Support
Posted
I followed Kloudz advice and I did seem to be missing the file as well. While I was able to run mover from the dashboard again I seem to be running into another issue and that is despite "Move Now button follows plug-in filters" being set to NO unless I change my "Only move at this threshold of used cache space" to something lower than what is currently being used the mover will not run when activated from the dashboard but will run when activated from the the shares page or the scheduler page.