January 6, 20206 yr Ok so I am in the middle of swapping out my cache drive, and I started doing it as if it was a drive in my array before I realized it didn't work the same and I found this article: https://wiki.unraid.net/index.php/Replace_A_Cache_Drive So here is what I did: Shutdown the unRAID server, installed new SSD, left old one in there still connected. Booted up, stopped the array, unassigned the old cache drive, and assigned the new one, started the array back up (including dockers and VMs). At this point I tried clicking the button to invoke the mover and nothing really happened and that's when I realized I was doing something wrong. Found the above article, stopped the array again, set all my shares to Cache: Yes that were using the Cached drive and started the array and invoked the mover and it started moving stuff, however... I was keeping track of how this was progressing so I could get a rate of how quickly stuff was moved off the cache drive, and it stopped moving at 88.7%, should I be concerned? 88.7% - 6:26 PM 88.7% - 6:15 PM 88.8% - 5:12 PM 89.8% - 4:51 PM 90.4% - 4:41 PM 90.8% - 4:31 PM
January 7, 20206 yr Community Expert Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.
January 7, 20206 yr Author dataserver2-diagnostics-20200107-0338.zip I left for a few hours to get dinner and drinks, and now it's moved, it's at 67.1% now, I'll keep an eye on it. Logs are attached, maybe it was just a fluke. And yes I was refreshing the the web page when I was doing my checks
January 7, 20206 yr Author Ok, I also just noticed that the mover had stopped. I just started it again, not sure if it will help. Looks like the appdata folder is all that needs to be moved, should I just do this if the mover stops again? root@Dataserver2:/mnt/cache# mv appdata /mnt/user
January 7, 20206 yr Community Expert 14 minutes ago, LumberJackGeek said: root@Dataserver2:/mnt/cache# mv appdata /mnt/user You absolutely must NOT do that. You should never mix disks and user shares when moving or copying files. Cache is a disk and cache is also part of user shares. That is scenario #1 I talk about here: https://forums.unraid.net/topic/61985-file-browser-in-webui/?do=findComment&comment=723474
January 7, 20206 yr Author 59 minutes ago, trurl said: You absolutely must NOT do that. You should never mix disks and user shares when moving or copying files. Cache is a disk and cache is also part of user shares. That is scenario #1 I talk about here: https://forums.unraid.net/topic/61985-file-browser-in-webui/?do=findComment&comment=723474 So thoughts on what I should do? It's still at 67.1% full, but the mover says it's still running.
January 7, 20206 yr Community Expert I'm not sure it will help anything at this point, but go to Settings - Scheduler - Mover Settings and Enable Mover Logging. If that results in new syslog entries, post syslog. Let me know either way.
January 7, 20206 yr Author dataserver2-diagnostics-20200107-1537.zip It's still running, but I noticed that it's trying to move a bunch of files that already exist in the destination?
January 7, 20206 yr Community Expert You have duplicates as expected. You really need to have your appdata and system share completely on cache and set to stay on cache. That will require several steps. We can get to that. Let it go for a while and see if it gets to the end. Keep checking syslog to see that it is making progress. As long as you don't run out of log space.
January 7, 20206 yr Author Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 20 Mover says it's still running, but the syslog is throwing an allocation error. Is there a way to increase the log size?
January 7, 20206 yr Community Expert Might be simpler and save time to just reboot, if you can do so cleanly from the webUI.
January 7, 20206 yr Author Ok, but is there a way to increase the log size so I don't run into this again?
January 7, 20206 yr Community Expert Might as well turn off Mover logging since it isn't telling us anything useful. You might delete some old logs, var/log/syslog.1, syslog.2, etc. and get that space back but not sure if it would help since the error has already occurred. I have this in my go file, but it is commented out: mount -o remount,size=384m /var/log
January 7, 20206 yr Author Do you have a link for what a "go file" is? And so what are the next steps you want me to perform? 1. Turn off mover logging (or leave it on and increase log size?) 2. Delete old syslogs 3. Reboot machine Now what?
January 7, 20206 yr Author My server has been down for 24 hours trying to do this, so if anyone else can contribute ideas I am open to it.
January 7, 20206 yr Author Ok, I rebooted, set my shares to Prefer on cache. Seeing this in the mover log now, shouldn't it be trying to move stuff to the cache folder instead of "disk1" ? Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-request Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-request File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-status Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-status File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-status-file Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-status-file File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-url-info Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/show-url-info File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/toggle Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/toggle File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/toggle-mini Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/toggle-mini File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/untrusted Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/untrusted File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/url-info-osd.xml Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/templates/url-info-osd.xml File exists Jan 7 18:30:17 Dataserver2 move: move: file /mnt/disk1/appdata/binhex-delugevpn/privoxy/config Jan 7 18:30:17 Dataserver2 move: move_object: /mnt/disk1/appdata/binhex-delugevpn/privoxy/config File exists
January 8, 20206 yr Community Expert Post diagnostics. Then disable mover logging so you don't fill log again. I didn't really intend for you to start mover again until we had a look and probably changed some things. Mover can't move open files, which means it won't be able to move anything associated with your dockers and VMs while they are going. And it won't overwrite existing files, so the duplicates will have to be taken care of separately.
January 8, 20206 yr Author Ok, well my entire Plex library is gone, and my thumbnails are regenerating. I am guessing I am screwed or is there something I can do?
January 8, 20206 yr Community Expert 2 minutes ago, LumberJackGeek said: Ok, well my entire Plex library is gone, and my thumbnails are regenerating. I am guessing I am screwed or is there something I can do? Do you mean you started over with plex already?
January 8, 20206 yr Author Yes because as helpful as you are trying to be, you aren't really giving me guidance here. I laid out steps and asked what do I do after a reboot, and you didn't respond so I asked if anyone else can help and you replied back again with "reboot". I have been asking for help and you've been giving me short answers. This is a forum, not a live chat. Give me steps, not a single step. I wait hours for answers being given 1 step at a time.
January 8, 20206 yr Community Expert Practically everyone you will encounter on this forum are just users like yourself. Some of us try to help out when we have time by volunteering our time and knowledge. Sometimes I am not at the computer, many times I am helping on other threads. Sorry I let you run mover logging so long it caused problems of its own, that was a mistake on my part. You have some things that need to be changed before you try to setup your dockers again. There will likely be a number of things that have to be done, and some of them may require working at the command line. For example 22 hours ago, trurl said: Mover can't move open files, which means it won't be able to move anything associated with your dockers and VMs while they are going. And it won't overwrite existing files, so the duplicates will have to be taken care of separately. For another, your user shares aren't really set correctly for docker to work with cache. Getting all this straightened out will take some time and patience from both of us. One of the reasons I haven't given you everything all at once is because it is helpful to see the results from one thing before proceeding to the next. Post new diagnostics just so I can make sure I have the latest situation and then let me review them and see if I can get some organization into this.
Archived
This topic is now archived and is closed to further replies.