je82

Members
  • Content Count

    303
  • Joined

  • Last visited

Community Reputation

20 Good

About je82

  • Rank
    Member

Converted

  • Gender
    Male

Recent Profile Visitors

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

  1. Thanks for the info, yeah this was a great find i am happy that you guys made this thread. Something tells me many who use xfs encryption only find out about this very big flaw once it is too late, i am very happy to have found this before shit potentially hit the fan so to speak. Cheers, have a nice day!
  2. I understand the risks, but to minimize the risks with encryption what are the steps to take? I guess the best way for me to answer my own questions it to actualy just remove one my array drives and try to mount it, the problem is the software costs nearly 700$, a big price to pay for a test, i will see if the trial version can give me the answer of if the team behind the software can give me a short test period just to make sure i have a solution in case a real disaster was to happen. From what i've learned through reading the forums is: 1. Backup your luks xfs en
  3. Reading more on the subject it appears if your luks xfs header is corrupted you are screwed, there are therefor a good idea to backup your xfs headers as an extra security:
  4. Thank you, i am doing a little bit of research if disaster was to strike and to backup these headers seem essential if you do xfs encryption as if the header is broken all your data is lost on that disk because you cannot mount it even with the correct password (as i understand?) A question to an expert like yourself, is it nessecary to run the header backup as a "cronjob" do have "fresh" header backups or is this only needed to run once as the header never changes?
  5. This software seem to support luks xfs encrypted volumes: https://www.ufsexplorer.com/ufs-explorer-professional-recovery.php Does anyone have any experience in mounting a luks xfs encrypted unraid volume using this software or any software like it, is it straight forward just enter the key and it will work or does unraid apply more "strangeness" to the encryption header making an unraid luks xfs encrypted volume different from a regular one done in in something like ubuntu?
  6. I'm not 100% certain i can find a definitive answer to this question. But part of unraids safety is that if parity fails and unraid array won't work for whatever reason, you can always just mount the single disks and access precious data that way. This appears to be pretty straight forward if you don't encrypt your filesystem, but what if you do? I can't find a straight forward way how to mount a luks xfs encrypted unraid volume in windows and move the data, is it possible? What software is required?
  7. Awesome, thanks for all your hard work, love the unraid community!
  8. But will that work? Won't it be capped at 12tb if i already have one parity running at 12tb?
  9. Hey guys, should i use this docker rather then the more up to date one here: Is there any particular reasons you are running a shinobi that has not been updated in 6 months? The repo looks unactive or am i wrong here?
  10. Hello, I've been testing this docker and i've ran into some issue where when i delete files in the shinobi interface the files on unraid just gets renamed to .fuse files until i shut down the shinobi docker completely these files will not disappear. It's like the docker container is locking the files as "in use" even though they shouldn't be. My configuration is as follows: Cache only share called "CCTV Files" Stored Video Location = /mnt/user/CCTV Files I added 3 variables to make the file permissions work properly with unraid PUID 99 PGID 100
  11. Can i access this information via unraid or is that via bios only?
  12. looking at the logs from the past, apparently this has been going on for awhile, is it a bad memory module? First error was logged 10/28/2020.
  13. Yeah, thanks for the clarification, cheers!
  14. ok so best practice is to use this docker with a vpn provider that does not allow public exposure (NATed / block all incoming)?