scooterbaga

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by scooterbaga

  1. Hello, Looks like the NVIDIA_VISIBLE_DEVICES default value is "YOUR-GPU-IP". Should that be "YOUR-GPU-ID"? Had me trying to figure out which IP address to put there.
  2. Thanks for the help you two. I'm up and running. However, something is causing the system to freeze up/stall after about eight hours. So I'm off on my next troubleshooting adventure. Found a "Starting Over" list in the wiki, but hoping not to have to go that far. Half the "fun" is putting out these fires on one's own. If I don't get anywhere, I'll start a new topic. Thanks again!
  3. Okay, looks like crisis averted, lesson learned. Copied over new flash drive with CA backup (renamed the super.dat.CA_BACKUP to super.dat) and all appears to be well. Is there anything else I should be wary of in this process? My flash backup appears to only be two days old. Looks like it wants to do a parity check, but otherwise I'm up and running like normal. My only concern is with the 12 month USB key replacement. I'd much rather purchase a new flash drive and migrate to there. Does LimeTech budge on the replacement window?
  4. Managed to recover disk assignments txt from old USB. I have the drives selected in the correct order on the Main tab. However, it's saying it will wipe my parity drives even with the "parity is valid" selected? Afraid to pull the trigger on starting array. At some point I found an unraid FAQ about dual parity saying something about only staring it with one drive at first, but I'm unable to find it now.
  5. Hello, My USB failed completely and I don't have my disk assignments. I have relatively recent flash backup, but it's on the array. Somewhere along the way, I understood the data on the disks to be accessible, even if the USB fails. I thought, worst case scenario would be I have to dock each drive separately until I find the data I'm missing. This turns out to be not the case, and/or more complicated than I realized. I had dual parity and two ssds in a pool, and I'm able to differentiate these drives from the rest. However, not the order of assignment for anything. (Parity 1 vs Parity 2, cache drive 1 vs 2, etc.) I have my Unraid up and running, and the registration key reassigned. At a loss for what I can do next. Any help would be greatly appreciated. Thanks.
  6. I use exFAT for compatibility. I use this drive on Mac, Windows, and Unraid. I'm unaware of a better/easier method without installing/maintaining additional software if there is one. Did you catch my edit regarding the drive seeming to be fine? I think attempting to read/write from the disk with the partial plugin damaged the filesystem. (Could still easily/purely be a drive issue though.)
  7. Hello, Had some very bizarre behavior when trying to use Unassigned Devices after the creation of the Plus addon. My 4TB exFAT drive mounted and was usable in Krusader without the addon, but I was having issues. If I'm understanding what the addon does, I'm surprised the drive even mounted in the first place. I'm guessing the "base" plugin updated automatically, and fix common problems hadn't caught it yet to mention the addon? I was able to browse the exFAT drive in Krusader and start a Move process. However, it would get about 50GB in and freeze up. After a couple cancels and retries, Krusader crashed and I had to just reboot. Then the exFAT disks would no longer mount and I starting digging into UD to reinstall it, then noticed the addon. I was on 6.5.3, installed the addon, and was still unable to mount. (Very likely due to it not occurring to me to reboot after installing the addon.) Anyway, after misreading the minimum requirements for the addon, I upgraded to 6.8.0. All anecdotal at this point, and those logs are long gone. Just thought I'd mention how this presented for me in case it comes up for anyone else. There's also every chance that I'm just bad at unraid and a complete fringe case... and/or that drive is coincidentally failing. e.g. Disk sdp is the before mentioned 4TB drive. Not sure if it's the plugins not liking the format or the drive failing at this point. As the topic isn't lighting up with the issue, I'm guessing I'm fighting two things at once here and the plugins are fine. I'll have to look at the disk more in the morning. As for the non-disk failure issue... Perhaps, if it's possible and/or worth the effort, consider having the base plugin throw a warning sign for disks that require the addon? Thanks for your time/effort here and on the plugins. edit: After looking at and repairing the filesystem on the drive, it appears to be fine. I believe my initial Move process using the partial UD plugin may have borked the file system on the drive during the delete part of the Move. Just guessing, but I thought it was worth mentioning.
  8. Did anyone figure this out? Sorting by date is a mess.