Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About lotekjunky

  • Rank
  1. I started off with what I thought was a powerful enough server. It's not. I have a new one built, but all of my drives are in my current array. They are all LUKS encrypted, even the cache drive. I want to move these drives to another hypervisor without losing any data. I think if I take note of which hard drive is assigned to sdc, sdd, sde, etc... and then make sure they go in the new server in the same order (scarry!), and then move the USB flash drive over... it might be good to go. That sounds dangerous, so I figured I'd ask if there is a better way, a safer way, an approved way, or a migration tool that I could use? Thanks!
  2. NEVERMIND, thank you for your help. I was being dumb about UD.
  3. Yes, that's where I wanted metadata. The metadata for my library is over 500GB and it takes up too much space on my cache drive. For UD, if I go to Shares, it now says "There are no exportable disk shares". If I go into Apps and look for UD, I can get to the UD page that shows they ARE there and they do work... and I can get there from the cli too, but they are not showing on the shares page like they were before everything went sideways this morning.
  4. For Plex, I just didn't install that container yet. I had the meta data directory mapped to /mnt/user0/appdata which didn't exist, it was supposed to be going into user instead of user0. Does that make more sense? For unassigned devices, the mapped shares are no longer present. I haven't touched that app in months. I was going to uninstall the plug-in and then reinstall it again, but like I said, I didn't want to do anything dumb that I can't revert.
  5. Thanks for your replies! This makes total sense. I think my plex MetaData directory was not mapped correctly so it was probably filling the docker image with that junk. I moved the old docker image elsewhere (just in case), restarted docker with a fresh image, and added some of the containers back. They are all working now! BUT, I have other issues like my unassigned devices are not working any longer. It's gotta be related because everything had been fine for months until last night. Should I open another thread to discuss other issues?
  6. When I woke up this morning, I noticed my internet wasn't working. I run pihole on Unraid, so that's where I went. None of my docker containers are running. I'm not sure what happened because everything was fine when I went to bed. I was previously writing my syslog to flash but Fix Common Problems told me to disable it... unfortunately I did. Also unfortunately, when I tried to copy the /var/log files to another drive to survive a reboot, it didn't work right so I don't have any logs that lead up to this. Lovely. I did reboot. I can browse my array and everything SEEMS ok so far, but docker still won't start. I see my loop0, 1 and 2 are all 100% full. Can someone give me some pointers before I do something dumb? Thanks! tower-diagnostics-20200108-1537.zip
  7. Does anyone know how to make the backups password protected?
  8. I just found this app and LOVE it. Great job! I also just searched through this whole thread for information on how to make the backup password protected / encrypted. My whole system is using luks, but my backups are out in the clear. I want to store them in my gdrive, but I don't want to put them in the cloud without a little bit of protection. Any ideas on this? I thought about wrapping the .tar.gz (I'm using compression, holy cow... it dropped my backup from 5GB to 900MB) in a passworded archive, but that seems archaic.
  9. I have ESXi running in qemu. When editing the VM settings, the network adapter type keeps changing from e1000 to virtio. ESXi doesn't support virtio and ONLY supports e1000. I have to make this change in the XML which is not a huge deal, but every time I go into edit, I have to make the same change. Please make this respect the changes AND add a way to edit the network adapter type into the simple VM config view.
  10. Fantastic! I was not aware of the user scripts plugin, this is going to make my life a lot easier... thanks a ton! On a side note, I wish the search function was better on this forum... it would probably cut down on the redundant questions. I tried searching for an answer first but kept striking out so I decided to just ask. Glad I did.
  11. I have the Fix Common Problems plugin running. every time I reboot, it tells me that write cahce is disabled on disk3. It's correct, it is disabled... when I enable it via CLI, it reports correctly but falls back to disabled when I reboot. Am I not saving the change properly? Is something else going on? root@Tower:/mnt/cache# hdparm -W /dev/sdb /dev/sdb: write-caching = 0 (off) root@Tower:/mnt/cache# hdparm -W 1 /dev/sdb /dev/sdb: setting drive write-caching to 1 (on) SG_IO: bad/missing sense data, sb[]: 70 00 01 00 00 00 00 0a 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 write-caching = 1 (on) root@Tower:/mnt/cache# hdparm -W /dev/sdb /dev/sdb: write-caching = 1 (on)
  12. Holy cow that was easy! I didn't realize I could click on the HDD/SDD when the array was stopped. Thanks so much!
  13. After going through encrypting my data drives and moving data back and forth, I'm ready for the next step- cache drive encryption. I currently have the following: 1. 128b cache SSD (sdg) drive, empty, no shares use cache for now, currently formatted btrfs 2. Several 8TB WD Red drives (sdb, c, d, e, f), all with luks encryption (this is where I'll store my docker and libvirt files) Desired outcome: 1 luks encrypted cache drive and obviously maintain my encrypted pool with no loss of data. I've stopped docker and VMs and moved all data from the cache drive. I stopped the array but it looks like I can't just remove the cache drive... it looks like I might need to go build a "new config' but that is scarry and I am asking for help in case I've missed something. TIA!
  14. I got all of my issues sorted by actually understanding what the security settings mean and how to apply a rule to NFS.
  15. Thank you so much, I have it working now! I could not figure out where the RULE field was... I have this share mounted as an ESXi datastore and it's actually working. w00t!