bkastner

Members
  • Posts

    1198
  • Joined

  • Last visited

Everything posted by bkastner

  1. Perfect. Thank you for your help Jorge
  2. I have 2 drives on that particular backplane... the one with 130000 CRC errors (disk3), and the second drive that has 1 random one (disk8). Disk3 isn't in the array anymore and is being simulated. I had to do a parity check over the weekend as I inadventenly caused an unclean shutdown, and I didn't get any CRC errors on Disk8 during the check. The 130000 CRC errors on Disk3 occured while UnRAID was rebuilding the previously failed drive, but disk8 just had that one minor hiccup. Is a parity check still worthwhile in this scenario? I am guessing not, but want to confirm in case I am missing something.
  3. Okay, so I've flashed the firmware (what a pain in the ass that was), and I've replaced all my sff-8643 cables, and brought the system back up. Everything seems like it's better. The last drive that was screaming at me as 130050 UDMA CRC errors, but seems to not be moving. When I started rebuilding the last failed drive the CRC errors on this drive were skyrocketing, so I am guessing them remaining stable now is a good sign. Is there an easy way to test? I've browsed the drive through the GUI as I figured that would cause a read operation which would maybe cause the CRC errors to climb, but it's still the same. I also ran a short SMART test and it came back without error. Is it fairly safe to assume that it was a controller/cable issue, and I shouldn't have any more drive failures? Or is there another test I should run before considering this case closed?
  4. lol.. sorry. I didn't realize I'd sent that. I was going to ask about the lsi flash. I had the files on the flash drive, but couldn't make them executable, so was going to ask you, but figured I could create a MS DOS boot USB with the files and do it that way.
  5. Thank you. I've ordered replacement cables and will check the LSI firmware and see how things progress
  6. For some reason I've been having an issue since May or so. I had a drive fail, and got a RMA replacement sent from WD. I did a preclear on another machine, shut down UnRAID, swapped the drive and brought UnRAID back up to start the rebuild. However, as the rebuild started I started getting udma crc error count errors on a drive that previously reported no issues. I figured it was just a fluke that a second drive failed while rebuiding, but once the rebuild was done I RMAd the new drive and repeated the process. Then another drive failed during that build with the same thing, and this just keeps happening over and over. I am now rebuilding my 5th or 6th drive, and again, I am getting a ton of udma errors (Disk 3 (disk dsbl) in the logs). While all my previously failed drives were bought a couple of years ago, the new Disk3 drive with errors is a WD Gold I just bought back in May (just before this all started). I did preclear it with no issue originally. I don't understand what's going on, but am hoping someone can take a look at my diagnostics and provide some insights. This is happening far too frequently for me to think it's actually drive failure after failure, but I could be wrong. I know sometimes rebooting will clear the crc errors, but I'd like to try and understand root cause and see if I can do something more permanent to fix it. cydstorage-diagnostics-20221015-1520.zip
  7. I do understand what you are saying, and believe it makes sense. It's just the odds that so few disks would be hammered that confuses me. Regardless... I will just let it go. I am almost done the refresh and will manually move files around to be more balanced and upate my split settings. On the split level question is it recommended to just split any directory, or select a specific different level?
  8. That all makes sense, and yes... it's OCD behaviour around the TV shows. I know it really doesn't matter, and should likely get over it. Even with this explanation I don't understand why those 3 disks I mentioned are being targetted excessively... I understand and expect some data to be written there, but not like it has. Also, I have 500GB minimum free space required set on those disks... even if it's writing to movie folders there already I could see it using an extra 25-50GB or even 100GB, but disk 10 is down to 552MB of space and disk5 is 193GB of space... both well under that threshold. That still confuses me.
  9. Here is the diagram as well as a screenshot from my Movies share. The TV share is set up identically.
  10. So.. this server has been running for a decade with these exact same share settings, and there are Movies folders on each of the 12 data disks and this has never been an issue before. When manually copying to the Movies share the files can go to any disk. As a test I just disabled the cache on my movies share so it writes directly to the array. I picked a movie at random that was on disk8 and moved it to my local machine, and then moved it back... and it ended up on disk9 So, is it fair to say that share settings/split level are not the issue I am having right now?
  11. While I do see a number of disks have been written to, it's interested that I've gained almost half a TB on Disk4... presumably because the old version of a movie was deleted and the new version went to another disk (Other than mover I don't think I've touched any files). Though I am guessing, I don't know why else space would have gone up and not down. I do look at the cache disk. I'm constantly monitoring it to see what's been completed, what's still showing incomplete, etc. So right now I have a 173 movies in the Movies folder on the cache drive. Because the file names are different I don't think it's overwritting. It would treat them as seperate files (I've had movie duplicates this way before by accident).
  12. So, I haven't done the one off test yet, but here is the picture I posted yesterday of the drives, and then again from just now. Not absoutely everything uses those 3 disks, but it looks like the vast majority does. Yesterday: Today:
  13. I still tend to leave it at split level 1 for tv as I'd prefer to have everything related to a show in a single folder on a disk, but there is no real reason I suppose. My brain just likes things ordered like that. Movies\Movie Name (year)\Movie Name is how everything is structured, and with metadata not downloading it's only a single file in a given movie folder, so there is really nothing to split beyond the first level.
  14. This is only if the file name is exactly the same though, correct? As mentioned in my original post there is a zero % chance of this. Up until this refresh project I just used movie.mkv, but now use movie, quality, audio setup, imdb link, release group, etc. Before this project I didn't use Radarr... I manually cleaned up movies, fixed metadata with Media Companion and then moves to Unraid. I am now trying to automate this and narrow my focus on finding the best quality version that meets my criteria. So, the folder would pre-exist, but the movie file name doesn't as it seems to get deleted once the new file is in the movies folder on my cache drive. I would still sort of expect that if the folder exists on disk2 for example that the new movie would be put into the same folder.... but this doesn't look like is what's happening. As I think more about this I likely need to do a test with a specific movie and follow it through the process. Right now I've just been searching all movies in a given year, and letting the 300-400 movies update as a single batch.
  15. I don't use a media share... I have root shares for Movies & TV and they span all the disks. This is where I was confused about it being restrictive. I am not sure what change I am supposed to make to help this in this scenario
  16. What are the recommendations for split level? I have a root movies share and tv share (i.e. not under \media or anything). For movies, historically, there were always jpg files for the movie, actors, etc, so I had this set to ensure they all sat on a common disk. I could see where the restriction would cause issue with tv shows as each season will try to ensure it's on the same disk, which can (and has) caused space issues. However, with movies, it seems to just be the movie file nowadays, and Plex finds all the metadata, so if it's a single file per movie, how is this too restrictive? I'm not sure I understand (though maybe my understanding of the split level set is incorrect). As for files being replace in situ... that is what I'd expect, and some of my confusion. I will end up with 100-150 movies in the \movies cache folder that mover will need to move. As mentioned, it seems that the original file is deleted, and the only copy of the updated movie sits on cache.. however presumably the folder still exists on the array somewhere, and I would expect the new movie to be placed in the existing folder, which would distribute across the array (to some degree). The fact that it always pegs the same 3 disks and maxes them out rather than distributing across the array is not what I'd expect. There is no way those 150 movies all are from the same disk.. and even if they were by fluke, I've refreshed 4,500 movies at this point with the majority trying to write to one of three disks.
  17. Thanks for the thoughts. I just received the replacement drive from WD today and am pre-clearing it as we speak. I also have 2 parity drives so trust I should be good even with another failure (though I would rather not confirm that theory). I guess an emulated disk is still a 'disk' but would think it would be a safety feature to not write to an emulated disk, in case, as you mention, a second drive dies and you don't have 2 parity drives. You are increasing the amount of data at risk. However, I would have thought excluding disk8 from the share (for exactly that reason) would prevent the disk from being written to, but it hasn't. I see files written today, yesterday and the day before... even though it's been over a week since I excluded it after the failure. Hopefully Jorge can provide some insights into why this is happening.
  18. I am having issues with how Mover moves contents to the array, and I don't understand the behaviour. My server is on Unraid 6.11 rc4 for reference. As background, I have a really large movie library and over the last couple of weeks I've been refreshing it to ensure I have the best 1080p version available vs whatever I may have grabbed 5-10 years ago. I have a ssd cache that my nzbget downloads uses and I am also using that drive as cache for my movies share, so when radarr finishes processing the movie it unders up under \movies on the ssd. I also have hardlinks enabled (though I don't know if this is any part of the issue). I've started using trash guides to help focus on the versions I want, and have a much more detailed file naming convention than I did before. So, when I have a new version of a movie it doesn't overwrite the old file. It seems to delete the old file, and the new file is initially found in \movies on the cache drive as noted. This is all fine, however when mover kicks in to start copying the data to the array it behaves in a way I don't understand. Even though I have the share configured for most-free mover seems to target a specific disk and just keep filling it rather than distributing across the array. Even though I have 12 data disks, it only seems to target 3 of them... which are now the most full and theoretically should never be picked. One of the drives is actually failed, shows as failed in the gui and I have it as an exclusion in the movies share, but mover will still copy to it for some reason. I did post about this a few weeks back and was told if a movie exists on a disk already then the new copy will be moved to that same disk under the existing folder, which makes sense, but this is not what's happening. Mover seems to pick a single disk (one of the 3 noted) and push everything to that one disk. I had 3TB of data on my cache that I needed to move to the array today... Mover picked the most used disk and filled it to 100% capacity (even though I have 500GB free space as a minimum). Once it maxed that out it moved to one of the other 2 disks that get used. I dont' know if once Mover starts using a disk it will move everything to that disk (rather than distribute based on most-free), but I would have expected it to at least respect the minimum free space setting, as well as the disk exclusion (ideally I'd hope Unraid would not write to a failed disk at all, but this may be asking too much). I am attaching images of my movies share settings as well as the array (as well as diags). Mover is running right now, and it maxed out Disk10 (again, well beyond the minimum free disk space), and is now writing to disk5 (one of it's other favorites), even though there are other disks in the array with much more free space. I understand the theory that if a movie exists it will use the existing folder, however I am refreshing 200-300 movies at a time, and there is no way they all resided on a single disk. I'm really confused, and not sure how to fix. As an aside, I did post somewhat about this earlier this month, but the disk in question failed, and I let this linger, and now have more information, so thought I'd start a new thread. I marked the other as solved, but it's really not. Any insights would be appreciated. I usually think I understand how Unraid works, but then situations like this pop up that prove me wrong. cydstorage-diagnostics-20220919-1930.zip
  19. That makes sense, but shouldn't be the issue (I don't think). I am in the process of refreshing my movie library to get everything to 1080p, etc. I've processed around 1,300 movies, and almost 900 of them are now on disk8. I have 12 disks, so the odds of that are incredibly small I would think.
  20. I am running Unraid 6.11 rc4, though I think my issue is independant of that. I have 2 cache pools - one for appdata and the other for backups/downloads, and have the mappings in NZBGET, Radarr and Sonarr to point to /mnt/user for everything so I can take advantage of hard links, etc. When I download a movie it moves from the Downloads directory to the Movies cache folder on the same drive, however when mover starts it seems to want to move everything to a single disk (disk8) for some reason. My share is configured as Most-Free, and disk8 is actually the least free disk, and I don't understand why it keeps putting data on it. I've even set disk8 as an exclusion for the movies share, but it still keeps moving files to that disk. I've also just realized I have some funkiness with my shares (certain movies are showing up as seperate shares for some reason). I only noticed that now, but assume it's unrelated to the overall issue. I only mention as anyone reviewing my diagnostics may wonder what I am doing (I wonder myself sometimes). cydstorage-diagnostics-20220907-1320.zip
  21. The current cache drive is btrfs, so I should be good. Thank you for confirming.
  22. Hello I currently have a 1 TB nvme drive as my cache, however I've bought 2 new drives (also 1 TB) to replace as a cache pool in a raid 1 and then use the old drive just for caching share data / new downloads. My plex metadata folder is large with a ton of files, so I am trying to find an easy way to do this. I wanted to confirm if my strategy would work, and if there are any potential issues. 1) Add one of the new 1 TB drives to the existing cache pool (which I assume will start to mirror the existing one). 2) Once replicated, remove the old cache drive, and replace it with the 2nd new 1 TB drive and let the mirror rebuild 3) Re-add the old cache drive in a new pool for downloads So, a couple questions: 1) Am I correct in how the RAID 1 system will work? Do I need to do anything to make this happen? 2) Is there a way to know once the 2 drives are completely mirrored 3) Are there any issues with the above approach
  23. Sorry... as you likely noted above, this is now sold.
  24. I'd do $800 for everything, but that's about as low as I want to go