Darksurf

Members
  • Posts

    166
  • Joined

  • Last visited

Posts posted by Darksurf

  1. Thanks so much guys! This instruction has been extremely helpful! I've got my cache drive emptied! I'll now halt my VMs to get them moved to SSD cache. Another question. if something is using prefer cache such as my VMs it sounds like it wouldn't be protected by the parity drive. Can you suggest a method to backup VM disks?

  2. Yep, you would be correct.  the issue occurred before moving to 6.4-rc6. I was previously on 6.3 when the issue began. I'm also not the only one who uses the shares so I'd rather not make the friends and family mad by loosing their data lol. Luckily the stuff I lost was only mine, but the rest starts getting into shared territory.

  3. Nope, didn't even give the zero size. 500G worth of crap gone due to mover refusing to move the files. SSD is a 1TB. I guess its not all bad. at least I know whats missing. I could probably just acquire it all again and reinstall pfsense on a new VM and start over there. its only a couple weeks worth of work. I still feel like I could crawl in a hole right now.

  4. OK, so I'm not having a good day. I've noticed all my shares were set to use cache and they didn't just use the cache for new files. It kept using the cache and refused to empty the cache drive. I've suspected something was going on for a while, but couldn't put a finger on it. I figured I was just improperly utilizing cache due to constant complaints of cache being full or near full. I decided it was time to start marking shares as don't use cache. I began rsyncing files over. from /mnt/cache to /mnt/user/  . I had one VM being used as a transparent bridge firewall, I decided rsyncing was taking too long and checked both /mnt/user and /mnt/cache to make sure they both had the VM. Then proceeded with deleting the VM once I noticed they were both there. NOPE! now the VM is gone completely. I'm not sure what was happening with the mover. even with the VM halted, the mover refused to empty all the files off the cache drive.

     

    Now I'm praying that the entire library of videos I used for my plex docker actually decided to move when I rsynced from the cache to the user (because invoking mover didn't move the files off). wish me luck guys. I'm thinking I'm in for a nightmare.

  5. I take it the noise you're hearing is like crackling and stuttering? I've noticed this too. I've had the exact same issue with the GTX1060 I'm passing through to a windows10VM I'm using for steam streaming. I really only have linux machines at home, so windows10+steam in VM was an ideal concept for me. I don't want windows actually being used for much anything else.

     

    So I just found the solution today. I've been getting irritated that the HDMI audio issue even occurs from straight HDMI and not just over steam streaming to steamlink, another desktop, or over remote session with nomachine! I got to thinking out of desperation "I'm not really using my server's sound card, why not pass it through too?". So I did. I now have intel HD audio + nvidia HDMI audio. I tried streaming and watching on a TV at the same time. NO MORE AUDIO STUTTER, CLIPPING, ETC! Works like magic now! I can't explain whats happening, but at least we know how to work around it now.

  6. Is your default graphics chip set in the BIOS? You cannot have the graphics card in the first slot typically as the system tends to try and use it as the default GFX card.

     

    Make sure hypervisor setting is disabled and do host passthrough for cpu.

     

    <feature policy='disable' name='hypervisor'/>

     

    I'm attaching my working config for Nvidia GTX1060 UEFI Win10 Install.

    Nvidia-Win10.xml

  7. 48 minutes ago, BRiT said:

    @Darksurf How would you transition the shares to Read-Only mode on other Linux variants? Or do you mean to make it a passive-only that monitors then when it gets tripped to send a Notification? I suppose it could just have hook-files to be executed on tripped, then leave it up to others to get the nitty-gritty for their specific situations.

    It would boil down to either editing the samba.conf file or even better, just stop the samba service 'systemctl stop samba.service' and send notifications and log problems.

  8. On 5/18/2017 at 6:46 PM, Squid said:

    It's tailored to unRaid, and takes the approach of waiting for an attack to happen against certain files and when that happens stops all smb write access regardless of how inconvenient that may be to you.  IE:  It's your absolutely last line of defense, and should never be your first and/or only...

     

    https://github.com/Squidly271/ransomware.bait/

     

    Have you ever though of making it a CLI tool and portable to other Linux distros? I know this is last line of defense material, but its lightweight and excellent for what it does. I can easily see this becoming a tool businesses would love in their arsenal. Seriously man, you've got a winner here. I love unraid, but small medium business and corporate uses other distro's. This could be a big deal!

  9. On 5/11/2017 at 4:24 PM, Squid said:

     

    Turns out a docker is extremely unnecessary. This app seriously only requires 2 files to be dropped into an apache docker. super easy. I made it out to be far more difficult than it was.

  10. 3 minutes ago, trurl said:

    If you actually use the calculator linked, you will find that you actually want "single" instead of btrfs raid0:

     

    You're right, I'll just remove the smaller 2 SSDs and leave the RAID1 settings in place for when I get the second 1T SSD. Thanks for the info. Sorry about the confusion. I should know not to jump to conclusions and post in forums after midnight.