Jump to content

xxbigfootxx

Members
  • Posts

    89
  • Joined

  • Last visited

Posts posted by xxbigfootxx

  1. Would this be the correct process for that?

     

    1.  Remove the 6tb parity.

    2a.  Add the 8tb as a parity drive.  Allow the array to rebuild.

    2b. Start the array Allow the array to rebuild.

    3.  Pre clear the 6th (old parity)

    4a. Stop the array

    4b.  Add the 6tb (old parity) to the array.

    4c. Start the array

  2. 11 minutes ago, JorgeB said:

    Without a disable disk there's no real need to use the parity swap procedure, but it can still be used if you disable the data disk first, like mentioned here:

    https://wiki.unraid.net/The_parity_swap_procedure

    So how would i go about inserting a disk that is larger than the current parity? Add the old drive back in, wait for the data rebuild then action the steps in the link to stop array, unassign the disk, restart array, stop again, assign new 8tb disk as parity and the 6tb as same data drive that was rebuilt? 

     

    Would that be the best way to do it? Or is there an easier/faster method?

  3. 10 minutes ago, trurl said:

    Connection problems on new parity

    What would you recommend doing? Should i leave it for another day and see how it goes?

     

    It is a brand new drive, but i haven't run a pre-clear on it. Should i cancel the parity swap and do the pre-clear then try again?

  4. I've also got this issue on mine. Server has only been running for 2 days at this point. 

     

     du -sm /var/log/*
    0       /var/log/btmp
    0       /var/log/cron
    0       /var/log/debug
    1       /var/log/diskinfo.log
    1       /var/log/dmesg
    1       /var/log/docker.log
    0       /var/log/faillog
    0       /var/log/lastlog
    1       /var/log/libvirt
    1       /var/log/maillog
    0       /var/log/messages
    0       /var/log/nfsd
    1       /var/log/nginx
    1       /var/log/openvpnserver.log
    0       /var/log/packages
    0       /var/log/pkgtools
    1       /var/log/plugins
    0       /var/log/preclear.disk.log
    0       /var/log/removed_packages
    0       /var/log/removed_scripts
    0       /var/log/removed_uninstall_scripts
    1       /var/log/samba
    0       /var/log/scripts
    0       /var/log/secure
    0       /var/log/setup
    0       /var/log/spooler
    0       /var/log/swtpm
    1       /var/log/syslog
    128     /var/log/syslog.1
    1       /var/log/vfio-pci
    1       /var/log/wtmp

     

    I seem to have two syslog files, one that is named syslog1 that is using all the log memory. Can anyone tell me what that is?

    zeus-diagnostics-20201009-2200.zip

  5. 15 hours ago, ghost82 said:

    Can you issue the following command from the vm:
    networksetup -getdnsservers ethernet

    image.png.d086d7aa1eade43d4e1546734aee65ec.png

    I get this error when trying to run networksetup

     

    When you say the network config for the device, do you mean the VM Manager settings? I'm bridging my default ethernet adapater as i only have the one network port on my mobo. 

     

    No firewall set in my modem, its a Netgear D7000v2. Are there specific ports i need to open or anything?

  6. 1 hour ago, Chad Kunsman said:

    Is there a one single location or single guide that walks through how to get GPU (Nvidia) passthrough working on Catalina? I'm referring to all the little tiny things from start to finish you have to do or might have to check on, such as tiny xml edits and adjustments, weird tweaks, etc.

     

    I've had no issues getting linux and win10 going with passthrough, including USB controllers, but even hours and hours of fiddling has gotten me nowhere with GPU passthrough and Catalina. And I know there are little bits and pieces of useful information in multiples places and threads but it's a big challenge trying to wrangle them all together. Stuff like "Oh try this..." or "Change this line in your xml". 

     

     

    Have a look at this: 

     

  7. 2 hours ago, ghost82 said:

    Ensure that the host (Unraid) is setup properly for network connectivity (test: ping from unraid).

    Ensure you created a bridge in unraid and ensure that the vm is using the bridge (test: ping from the vm, you have the terminal available during installation).

    Ensure you are using type vmxnet3 or try e1000-82545em for network connectivity.

    I've attached some screenshots below. I definitely have internet access from Unraid and have been using it without fail for a few months now. 

     

    I'm pretty sure the VM has internet becuase its not showing the 'network connection required' error but rather that it can't connect to recovery server specifically. I can't ping my modem, but i can ping google IP, 8.8.8.8, DNS seems to be an issue as i can't ping google.com. 

     

    Not sure why mine is failing but everyone else seems to run so smoothly. I am running an Ryzen CPU if that makes any difference?image.png.033de6fd65752d8c4e80e9993968ee12.png

    image.png

    image.png

    image.png

  8. Can someone please help. I'm getting an IP but can't talk to my router or ping internet.

     

    Server has internet, and is working great. I've tried reinstalling the VM about 10 times, each one following the SpaceinvaderOne MacOS installation guide. 

     

    Any help would be great. 

    image.png

  9. 12 minutes ago, ghost82 said:

    Ensure that you have vmxnet3 as virtual network, and change to e1000 only after downloading from server.

    This is my current XML file: 

        <interface type='bridge'>
          <mac address='52:54:00:a4:47:7b'/>
          <source bridge='br0'/>
          <model type='vmxnet3'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </interface>

     

    Even using the default settings from @SpaceInvaderOne VM innstall guide it seems to result the 'recovery server error'.

×
×
  • Create New...