• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About bkastner

  • Rank
    Advanced Member
  • Birthday 08/07/1971


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well what do you know... that fixed it. Thank you for the suggestion. I'm glad it was an easy fix.
  2. Okay... I enabled Mover logging and ran the mover. I'm assuming the logs still get captured in the diagnostics so have attached the new one. cydstorage-diagnostics-20210408-2329.zip
  3. I noticed a couple of weeks ago that my cache drive was getting full, and then realized that my mover isn't doing anything. I'm guessing it's been about a month, which (roughly) coincides with installing 6.9.1, but I have no idea if the two items are related, or just generally grouped together in my memory. Regardless, the mover has stopped working, and I have no idea why. I have TV & Movies set to yes:cache but I have to manually move them right now which is annoying. If anyone can review my logs and tell me why I would definitely appreciate it. cydstorage-diag
  4. I'd agree with that. I'm still struggling with this as well as noted in the other thread Energen linked. I thought I had it sorted out by copying most of the data, and then migrating the last bit while Plex was down, but once copied Plex wouldn't start. I'm currently compressing the Plex data into a tar file and trying to copy over that way. It looks like I will need around 2 hours to tar the data, but it's not quite done, so I dont' know what the rest of the process will look like. I don't know what NVMe drive you have, but unless it's a high end SLC or maybe MLC driv
  5. Lol... no chance... I probably haven't seen more than 20-25%.. though my father-in-law lives with us and is retired and has likely watched a pretty good chunk. But I do provide media for a number of friends and family and Plex is awesome for that.. so much better than filling external HDDs which I used to do for everyone... that got really annoying quickly.
  6. I had been thinking about that, but the NMVe drive *should* be much faster when people are browsing libraries, and ideally I'd rather have it stored on the cache drive vs unassigned devices. A few weeks ago I was doing something with the array - I think it was a drive replacement - and it looked like unassigned devices didn't come up until the array was back to normal.. not sure if that was normal but plex was down until the unassigned device was visible... I figured that having it all on the cache drive should eliminate this risk/issue - though again, not sure how normal behavior that was.
  7. Thanks. One additional question... if I am looking at doing this in 2 passes as mentioned where I pre-stage as much data as possible prior to turning Plex off for the final pass... will this command skip files that are already copied and haven't been updated? Or will I need additional switches on the second pass to skip identical files? I sort of remember something like this in Windows with archive bits being set / unset, but not sure how this works in the Linux world.
  8. Thanks, that's good to know. I like MC as it's easy, but will try the command line approach. I know the 'r' is for recursive, but what does the 'a' do? I see it's for archive, but I am not sure I understand what that does in this context
  9. I was using MC to do the copy from /mnt/disks/CachePool to /mnt/cache
  10. That's some interesting information... I knew QLC is slow but has the SLC cache to help, but didn't think that applied to MLC or TLC NVMe drives as well, which is why I was surprised at the performance. I am thinking I will do a copy of the plex folder so I don't have to take it down, and will hopefully have 99% of the overall data on the NVMe and then when I take plex offline and redo the move, skipping files that exist it should be a minimal copy that won't overwhelm the NVMe... definitely more complicated than I was expecting. I also realize that I now need to figure
  11. I have a pretty large plex metadata folder (250GB / 1.5M files), which is currently sitting on a SSD drive using Unassigned Devices. I recently built a new system and installed a Corsair MP600 1TB to act as a cache drive and have been moving the appdata over to it, but the issue is when copying the plex metadata folder. Before the NMVe drive I was using a 1TB WD Black HDD and copied the plex directory from it to the SSD in 7-8 hours (I think... it finished while I was asleep). Now I am coping the folder from the SSD to the new NVMe Cache drive, and it's taking FOREVER.
  12. Okay... one more question... I am 99.99999% positive I reformatted the new cache drive as btrfs, but just noticed it's showing as xfs in Unraid.... I am almost done moving the 250GB of Plex data back over (1.5M files) which take such a long time. Am I screwed now for adding a second cache drive and getting the raid1 pool? Does it need to be btrfs to support that? Or does xfs work? I really hope the answer is that I am good, but I am guessing I am likely not.
  13. Thanks for the info. I've reformatted my new drive as BTRFS and finished the standard migration to it. Am I correct that if I add a second BTRFS NVMe drive to the system I can add it to the cache as well and they will automatically sync data between the two providing redundancy?
  14. I currently have 3 SAS2LP controllers that tie into my Norco 4224 backplanes, but the new motherboard I have only has 3 x16 and 1 x1 PCIE slots. I am hoping to add a 10GB NIC, and possibly a transcoding video card down the road. I have bought a RES25V240 which I've seen I don't even need to mount in a PCIE slot which is kinda cool, but I am wondering what sort of throughput I am going to see if I use that. Given that I still need 1 HBA I am assuming I'd remove 2 SAS2LP, and have one with a direct connection to a backplane and the other to the RES24V240 with it's other 5 ports connecting to the