Popular Content

Showing content with the highest reputation since 05/24/18 in all areas

  1. 1 point
    Like every other project in the world, documentation always lags behind. The help text however tends to be up to date (but not always) The copy to / copy from are for copying the share settings from one share to another
  2. 1 point
    Which Intel NIC is it? Model? You can try to deactivate the Onboard NIC at the BIOS and see, if unraid will use the new Intel NIC.
  3. 1 point
    I just like to see that everything is as expected after booting.
  4. 1 point
    Once you have that running, highlight the folder you wish to analyze and go to Tools, Disk Usage.
  5. 1 point
    You need to replace that disk: https://lime-technology.com/wiki/Replacing_a_Data_Drive
  6. 1 point
    Sure, but if you want the extra safety while you do the parity build, you can do them one at a time to keep the array protected continuously. Safest (but longest) would be to add new bigger disk as parity2, let parity build, do a parity check, do a long smart test, replace parity1, let parity build, do a parity check, do a long smart test. With that sequence of events I personally would be comfortable putting untested drives straight out of the box in service, as the build, check, smart test sequence would be plenty of testing and burn in, all while maintaining your current level of protection with one parity drive being kept valid during the whole procedure. I recommend going as large as the budget allows, 8 or 10TB drives would be my preference. Even better, get just one new drive, add it as 2nd parity as described above, run for a few weeks, THEN source the second new drive so it's hopefully from an entirely different shipment of drives. I don't like adding drives to an array that all experienced the same shipping and handling chain.
  7. 1 point
    Docker image is corrupt, delete and recreate.
  8. 1 point
    @dnLL Would you mind trying something for me, please? Go to Settings -> Network Settings in the GUI, and under the heading Interface eth0 set Enable bonding to Yes. You'll need to stop the Docker and VM services first to be able to do this - probably the easiest way is simply to stop the array. Leave the bonding mode set to active-backup and leave eth0 as the sole member of bond0, like this: Now click the Apply button, then restart the array. Now do your ping test again and report back. I notice your motherboard has two main NICs (plus the IPMI one). At the moment you're only using eth0 (the one using the i210 chip), and eth1 is unplugged. Have you decided how you want to use this second port? EDIT: I should add that my reason for suggesting that you enable bonding is because that appears to be the default unRAID setting, even if only a single NIC is present. One of my servers has only one NIC and has bridging enabled, but it also has bonding enabled (per the screenshot) and I have no problem pinging.
  9. 1 point
    I have increased the size of my Windows VM disk successfully, used this procedure: Shutdown the VM truncate -s40G /mnt/disk1/VM/winxp.img where -s40G is the new total size for the disk Then in Windows just use the disk manager to increase the disk size using the new free space
  10. 1 point
    There actually is a way to accommodated for situations like this. You can use disk utility to create a sparse image on your server, mount it, and then store your database in that. The sparse image will have the exact same HFS+ file system as your Mac does and therefore not cause the corruption issues you speak of. It will also expand automatically as you add more data to it. I use this sparse image method to make a clone of my Macs for backup purposes. This way if I ever have to reformat my Mac I can restore it directly from the sparse image on my server over the network with the OS X installer. I prefer a 1:1 clone versus a Time Machine backup. As to the original poster. All my computers except my HTPC are Macs and I have no issues. You can browse the shares using Samba (or AFP if you enable it) just like on a Windows PC. When you go to access a share it will automatically mount the share just like if you were browsing the files on a Windows computer over the network from your Mac.

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.