• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About johmei

  • Rank
    Advanced Member
  • Birthday 10/03/84


  • Gender
  • Location
    Roanoke, VA
  1. [CONTAINER] CrashPlan & CrashPlan-Desktop

    Can anyone else please confirm that it did not delete their archived over 5TB?? Because I'm getting some pretty solid, very clear, "Your data WILL be deleted" messages and warnings. It's not saying it might, it's saying it WILL. Did you get these warnings when you migrated, Shadowrunner? I'm trying to decide if I should delete enough data to bring it below 5TB or risk having to reupload it all. Granted, it's not near the size of yours, but I would still rather not have to upload over 2 TBs of data if possible. Also, something to add that's confusing me; it's reporting my backup as 5.8TBs on the migration page, however, the CrashPlan app (I'm using gfjardim's) says completed 7.3TB of 7.7TB. Anyone have any ideas about that? (Just checked my last backup report email and it says confused)
  2. Thank you very much for the information! I'll look into both of them! Very happy to see that unRAID is going to be offering encryption in the future too!
  3. So first off, an apology. I searched and found no information that seemed very definitive or helpful, and this is a bit of an emergency, so please forgive me. I need to completely obliterate certain files for security reasons and I have no idea how this is possible. I had one idea; after deleting said files, copy a massive file over and over until there is no free space left, and then copy a bunch of smaller files to get the last bit and then delete them all, theoretically replacing any of the sensitive files with something else. But I am not confident in this procedure as there are too many variables that I am not immediately aware of. So will that work at all? And if not, is there ANY way at all to secure erase select files, or even better, a way to write 0s to every single sector that is not in use, or even random patterns. And finally, is there any way to encrypt data, either selectively, or the entire array? This would make the secure erase option unnecessary if I understand encryption properly. So really, either or, I just need to somehow, completely destroy the sensitive files. Again, I apologize if this is in the wrong category, if it's been covered, if it's in the wiki. I did search and wasn't able to find a crystal clear answer, just some discussion on the topic and I'm kind of in a panic for a solution. Thank you very much for your time!
  4. Strictly speaking the position of the script in the go file isn't critical. It is just good practise to have the network ready before the service (emhttp) is started. I got ya, that makes sense. I'll move my lines before that. Speaking of which... I don't understand what you mean...don't those commands have to be executed in that order? I don't see any other way for it to work (I mean, the correct file has to be copied, then the interfaces need to be unloaded and reloaded for the new names to be applied). Do you mean to say that I should instead have those commands in their own file, and call on that? Or something else? I'm not very experienced with scripts
  5. Thank you! Your script looks awesome That'll be a lot easier and better than doing it manually! I just have a question real quick. You mentioned the execution of your script happening before the start of the webgui, but I put all my lines after that. Should I move all my lines of commands before the webgui loads? It seems to be working, but I'm not experienced enough to know what kind of issues it could cause. Thanks! And thanks again for making that script!
  6. Boy I screwed up! I think this should have been posted in the subsection, Containers. In addition, there seems to actually be a thread answering this very question at however, that thread is not stickied...shouldn't that be stickied? Can we vote for threads to stickied? I had plex setup and working fine (among other things), then I decided to upgrade my cache drives and well it's been none stop fun ever since!! Among the issues I've had, Plex has disappeared a couple of times. I don't remember how I got it back exactly but all seemed well until I needed to add another Container Volume and now it's gone again...honestly, I do not understand nearly well enough what is going on to be able to piece things together and figure them out, so I'll be checking out the sticky's here and the FAQ very soon. But for right now I do have a specific question about plex that I can't seem to find an answer to I have the Community Applications Plugin, and when I search Plex, it has about 8 different plex Apps that look like they all do the same thing and...I just don't get it. Since I'm starting over with the entire docker thing, I'd like to know why there are 8 different plex apps to choose from, and what the difference is between them? I'll list them out here: Author: linuxserver. plex Author: pducharme. PlexConnect Author: PhAzE. PlexConnect Author: needo. PlexMediaServer Author: limetech. PlexMediaServer Author: PhAzE. PlexMediaServer Author: binhex. binhex-plex Author: binhex. binhex-plexpass Thank you very much for your time!
  7. YEAH!!!!!!!!!!!!!!!!!!!!!! Figured it out and I am freaking ecstatic!! :D so how does one rename the interfaces with unRAID when everything outside the /boot directory is apparently wiped clean in between boots? It took me several days, lots of hours but I pieced together how to make this work and I'm putting it here so that hopefully anyone else that has this issue will find the solution in a nice tidy little package and save them hours of frustration. The first thing you'll need to do is create a copy of the "/etc/udev/rules.d/70-persistent-net.rules" file in a place that will stick around everytime unRAID reboots. I created a directory under /boot called CustomConfigFiles. Open this copy and configure it so that the network interface that you wish to use for unraid is named eth0 and any others named eth1, eth2, etc. etc. The most important one is eth0 as unRAID uses that interface and will not use any other (as best as I can tell anyway) You'll need to figure out which MAC address is the one for the interface you wish to use as your primary network interface. There's several ways to get the MAC address, but the method I used was the command, "ethtool -p eth0" to get the interface's lights on the back of the server to flash. My methodology for this was as follows: use ifconfig to see a list of eth* devices and their addresses. use "ethtool -p eth0" to see which one flashes. When I find which card is flashing on the back of the server, I use Control + c to stop the command and take note of it's MAC address. I did this for each interface to find the MAC address of the two different interfaces I needed to use, and then using vi (if you're not familiar with vi, I know I wasn't, google how to use vi in linux and you'll find plenty of documentation) I opened and configured my newly copied, "/boot/CustomConfigFiles/70-persistent-net.rules" file so that the correct interface had the name eth0. Check out for more information on this (the information on this page is also used in a later step below) Next I edited the go config file at "/boot/config/go" to copy the correctly configured "70-persistent-net.rules" file to overwrite the generated file at "/etc/udev/rules.d/70-persistent-net.rules" using the following command: yes | cp -rf /boot/customconfigfiles/70-persistent-net.rules /etc/udev/rules.d/ That will copy and overwrite, without prompt, the generated config file that is not correct. The next line pauses the go script to make sure it had time to finish copying the file. I used 10 seconds, but that's probably a bit excessive. Use this command to pause the go script for 10 seconds: sleep 10s Next two lines will remove and reload the kernel modules for the network interfaces. See for instructions on this that are clearer than what I could type out. My next two lines looked as follows, but yours will be different: modprobe -r ixgbe e1000e modprobe -a ixgbe e1000e and then finally I configured my network interfaces. I'm not using DHCP here, because I couldn't figure out how, but I have the IP reserved in my DHCP server so there should be no issue. After you reload the kernel modules for the interfaces you need renamed (no idea of that terminology is correct, I'm just going on what that webpage said), you'll need to bring the now correctly named interfaces up. My config files look as follows. ifconfig eth0 up ifconfig eth0 netmask route add default gw echo nameserver > /etc/resolv.conf echo nameserver >> /etc/resolv.conf ifconfig eth1 up ifconfig eth1 netmask Obviously, plug in your own numbers there. eth1 is my 10 Gbit network card, but if you're just trying to rename a single interface so that it stays eth0 across boots, you won't have anything past specifying the name servers to mess with. Now I play the waiting game where I see if any other issues arise from this solution, and cross my fingers that they don't
  8. I am glad to hear that at least. However, unRAID had the correct interface named eth0 not only a few days ago. Something has caused the interfaces to be renamed and I can't figure out what. While there is not support for multiple interfaces, there should be a relatively simple work around considering that it's all linux and with some creativity, lots of stuff can be accomplished with it The thing about my issue is that I know what the problem is, and how it needs to be fixed. I need to configure or otherwise manipulate whatever it is that names the interfaces when unRAID boots up so that they will always have the same name across reboots and power downs. Figuring out how to do this, however, has been far more difficult than I would have imagined. So while I do appreciate the heads up that this will no longer be an issue at some point officially, would you happen to know how I could tell it to rename these interfaces on boot up using a command set or a script or some other method? Thanks!
  9. I'm on the verge of crying here. This is what hopelessness feels like. When you search all over Google and all you find are articles talking about editing the 70-persistent-net.rules file, but that will not work because unRAID generates this on each boot it seems, or articles saying to use ip link set eth1 name eth0 to rename interfaces without rebooting, but being met with an, "RTNETLINK answers: File exists" message...then Googling that to find more confusion and mess. All I want is consistency with network interfaces and I just don't understand why this is apparently is not possible? Please, if someone can help...I don't even know where to look anymore to try and solve this.
  10. If I were to place a file on the flash drive, and use the go script to copy that file, would it be too late in the boot cycle? I would need to have a custom 70-persistent-net.rules copied but whether or not this works would depend on when the go script is ran. Thanks! I just tried this and it does not work....sigh.
  11. If I were to place a file on the flash drive, and use the go script to copy that file, would it be too late in the boot cycle? I would need to have a custom 70-persistent-net.rules copied but whether or not this works would depend on when the go script is ran. Thanks!
  12. Before I say anything else, a little background information. About 10 hours ago I embarked on what should have been a very simple journey of upgrading my cache drives. I won't get into details, but I've ran into problems left and right and I finally am booting the server back up and now I'm having network issues. Please understand that I have been trying my best to get this working, I've been on google looking up everything I can. I do not just jump right into the forums and ask my questions without attempting to figure things out on my own. That being said, is the documentation out there to answer my question? Probably, but I have not been able to find it and it is not for lack of trying. I ran a direct 10 Gbit connection to my unRAID box not too long ago to take advantage of my cache drives, but I also needed this connection to work in tandem with my network for streaming and other networking services (I didn't want unRAID to rely on my main system being up to have internet and network access). Because of this, I had to unbridge all my network interfaces and this caused some frustrating issues, but I got around them and ended up manually configuring both interfaces in the go script. This worked well...that is until I realized the names of the interfaces can and will change. So now eth0, eth1, and eth2 are not the same anymore and the go script no longer works. I can simply change the name of the interface in the go script, but I would very much like to fix this so that it never happens again. What I really would like to do is either configure interfaces based on their MAC address instead of their interface name, or find a way to make sure the interface names do not change in between reboots and in between anything else that might happen. I found information on the interwebz that spoke of the file: /etc/udev/rules.d/70-persistent-net.rules and I edited that with vi, however, the comments at the top of the file and one of my google search results (that took me to a post in this forum) gave me little confidence that it would stick. It seems that this file is generated on each boot with unRAID and so editing it is pointless...unless of course I did something wrong. Either way, I can't imagine this solution should be anything difficult, but I just cannot find the answer I'm looking for anywhere online. Can someone please point me in the right direction? Thank you very much!
  13. GTX 580 passthrough code 12

    There is a very good chance you'll simply have to get a newer graphics card. I was having your exact issues with my GTX 580; nothing coming out of the video out and a device manager conflict. I was frustrated to find out that it's simply a compatibility issue. I purchased a GTX 950 for about $150 ish and it worked right away. The unRAID wiki states that, "NVIDIA GTX-series GPUs should work fine as of the 600 series or newer, but not all models have been tested." You can read more about it here: It's worth a shot to try the suggestions on that page for passing through your GPU, but just be prepared that they very well may not work.
  14. I'm not sure why, but when I wiped my vdisk to make it smaller and reinstalled windows, it worked this time. *shrugs*. I'm still not sure what the issue was, but I'm now reconsidering that it was an unRAID issue. Which to be honest, unRAID passed it through as far as I could tell, so I didn't know how it could be an unraid issue in the first place. It's working now, either way, so I'm happy about that.
  15. I've got an Auzentech X-Fi Prelude 7.1 from some time ago and I'm trying to pass it through and haven't been able to get it to work. I've been through a lot with this card, and tried several things, but the most success I've had leaves me with a device that windows Device Manager sees, but I'm unable to install drivers for. The exact error I get is, "Windows found driver software for your device but encountered an error while attempting to install it." then it has the name of my device below that, "Auzentech X-Fi Prelude 7.1" and then below that, "There is no driver selected for the device information set or element." To be sure that this was unRAID and not something else (I had not installed this card on Win10 yet), I booted a win10 install directly from a hard drive, instead of booting unRAID, and attempted to install the driver in the same way, only it was successful. This leads me to believe that it's an unRAID issue, but I just can't figure it out. I've tried searching the forums for everything I could think of, but I wasn't able to find anything that would help me. The most recent and most successful attempt enovled stubbing the vendorID:deviceID in Syslinux config "pci-stub.ids=1102:0005" and adding it's address to the XML of the VM <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> It actually behaves the same with or without stubbing, so I just left it in the syslinuxconfig. Now, it is in a group with one other IOMMU Group, but it says it's a PCIe to PCI Bridge so I'm not sure if that would have anything to do with it or not. I know that I tried passing it through as well to see if passing both through would help, but it wouldn't even start that way, stating that it couldn't find a device at 06:00.0. Here is a list of my devices: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4) 00:1c.4 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4) 00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4) 00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1402 (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 06:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03) 07:00.0 Multimedia audio controller: Creative Labs SB X-Fi 08:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) 09:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller And here are my IOMMU Groups (PCIe ACS Override is enabled) /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.1 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.0 /sys/kernel/iommu_groups/5/devices/0000:00:16.0 /sys/kernel/iommu_groups/6/devices/0000:00:19.0 /sys/kernel/iommu_groups/7/devices/0000:00:1a.0 /sys/kernel/iommu_groups/8/devices/0000:00:1b.0 /sys/kernel/iommu_groups/9/devices/0000:00:1c.0 /sys/kernel/iommu_groups/10/devices/0000:00:1c.1 /sys/kernel/iommu_groups/11/devices/0000:00:1c.3 /sys/kernel/iommu_groups/12/devices/0000:00:1c.4 /sys/kernel/iommu_groups/13/devices/0000:00:1c.6 /sys/kernel/iommu_groups/14/devices/0000:00:1c.7 /sys/kernel/iommu_groups/15/devices/0000:00:1d.0 /sys/kernel/iommu_groups/16/devices/0000:00:1f.0 /sys/kernel/iommu_groups/16/devices/0000:00:1f.2 /sys/kernel/iommu_groups/16/devices/0000:00:1f.3 /sys/kernel/iommu_groups/17/devices/0000:01:00.0 /sys/kernel/iommu_groups/17/devices/0000:01:00.1 /sys/kernel/iommu_groups/18/devices/0000:02:00.0 /sys/kernel/iommu_groups/19/devices/0000:03:00.0 /sys/kernel/iommu_groups/20/devices/0000:04:00.0 /sys/kernel/iommu_groups/21/devices/0000:05:00.0 /sys/kernel/iommu_groups/22/devices/0000:06:00.0 /sys/kernel/iommu_groups/22/devices/0000:07:00.0 /sys/kernel/iommu_groups/23/devices/0000:08:00.0 /sys/kernel/iommu_groups/24/devices/0000:09:00.0 It's IOMMU Group 22. 06:00.0 and 07:00.0 I don't know what else, if anything, I can do if the windows Device Manager is actually seeing it. I'm completely stumped and can't find anything that has helped. Thank you very much for your time!
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.