• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by jonathanm

  1. Close, but not correct. You have to write zeros to the entire capacity of the drive, which is WAY more time consuming. It's faster to rebuild parity.
  2. Did you put your original license key file in the config folder on the new USB?
  3. So, if you don't use macvlan, does it still crash?
  4. Remove both cache devices from pool, start array to force Unraid to forget them, stop array and assign both as they were, the all existing... message should go away.
  5. Root should always have a strong password.
  6. Try reducing to 8096. Unraid needs resources to emulate the hardware for the VM.
  7. If you select the option stating parity is already valid, then nothing will be erased, and a parity check will be started.
  8. No, only the disk in the parity slot. The screen you just posted is different than what you had in your previous post, is it current?
  9. Read through that section and see if that answers your questions.
  10. Assign the disks as they were, assuming you haven't changed any disks since.
  11. Just don't mix /mnt/user paths with /mnt/diskX or /mnt/<poolname> paths when manipulating files manually. Typically I only use /mnt/user paths to consume media or files, and disk paths to manage stuff in the background, but less technical users are encouraged NOT to directly access the disks, just use the user shares and the accompanying settings to allow Unraid to manage the initial and final file locations. Much work has gone into removing the need to directly use disk paths for almost any scenario. One of the ways I manually manipulate the system is to use the
  12. That's the issue then. Requests sent to your WAN IP on port 80 MUST be redirected to port 180 at the server's IP. You will need to talk to your ISP and get instructions on how to accomplish that, or look up the make / model of that router on google and see if anyone posted instructions. It's also possible that your ISP blocks port 80 on your WAN IP, which means you can't use that method to get certificates. BTW, this thread should NOT be here in general support, there is already a support thread specifically for SWAG that addresses these and other issues. You can find t
  13. Parity doesn't have anything to do with file data, and it doesn't effect share behavior. If you change a share from prefer to no, all existing data files will stay on the existing drive, new data files will be written to the parity array to whichever drive meets parameters. Reads happen from whichever drive currently contains the file. If you change the share back to prefer, files that aren't open will be moved to the designated pool when mover runs. Cache no disables the mover for the share, and mover can never move open files. What are you trying to accomplish? If you
  14. yep. just make sure not to use /mnt/user paths in the cp command. only /mnt/cache and /mnt/newpoolname
  15. Depends on your experience level. The main thing to keep in mind is vdisks are created by default as sparse, so whichever method you land on needs to take that into consideration. Also, if the paths in your XML definition files are referencing /mnt/cache instead of /mnt/user, those paths will have to be changed as well.
  16. If they were originally in a single pool together at some point you will probably have to remove both pools, blkdiscard /dev/sd(whatever) on both SSD's, and then try again.
  17. couple scenarios off the top of my head 1. You set up some subdomains that have since been removed, so those specific certs are no longer being renewed because they aren't needed. 2. Your authentication method isn't working properly, so renewal is failing. 3. Something else is preventing the overnight scheduled renewal check from completing. What does the container log show?
  18. mc at a terminal. Midnight commander is a two pane file manager, GUI-ish. Just be sure you stay out of the /mnt/user tree since you need to work with /mnt/cache and /mnt/diskX
  19. You can use the "open files" plugin to see which files are still in use when you try to stop the array.
  20. Which shares are staying on the cache? Read the help descriptions for the cache usage on one of the shares configuration page, you probably have the wrong settings for one or more of your shares.
  21. Yes 😁
  22. Unless you can figure out a way to get a SAS external connector in the laptop, and I don't know of any, there really is no good way to do multiple drives. USB doesn't work consistently with a parity array. Some laptops have an eSATA port that would be good for 1 more drive.