d.bech

Members
  • Posts

    76
  • Joined

  • Last visited

Posts posted by d.bech

  1. I keep getting the following message to the shell.

    Any ideas on the cause?

     

    Message from syslogd@phab1 at Dec 26 19:16:16 ...
    kernel:Uhhuh. NMI received for unknown reason 30 on CPU 0.
    
    Message from syslogd@phab1 at Dec 26 19:16:16 ...
    kernel:Do you have a strange power saving mode enabled?
    
    Message from syslogd@phab1 at Dec 26 19:16:16 ...
    kernel:Dazed and confused, but trying to continue

    sir1-diagnostics-20161226-1523.zip

  2. When trying to create a CentOS 7 VM on my HP DL360 G6 I get the following error:

     

    internal error: process exited while connecting to monitor: 2016-12-26T07:11:44.699209Z qemu-system-x86_64: -device vfio-pci,host=01:03.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: error, group 15 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.
    2016-12-26T07:11:44.699238Z qemu-system-x86_64: -device vfio-pci,host=01:03.0,id=hostdev0,bus=pci.2,addr=0x4: vfio: failed to get group 15
    2016-12-26T07:11:44.699247Z qemu-system-x86_64: -device vfio-pci,host=01:03.0,id=hostdev0,bus=pci.2,addr=0x4: Device initialization failed

     

    Any ideas? I have attached my diagnostics

    sir1-diagnostics-20161226-1523.zip

  3. I just did another using community apps and popped all the info in

     

    9d7c5bbef2.png

     

    including the variables as listed in https://hub.docker.com/r/turzam/zomboid/

     

    but the server doesn't appear to be running and hasn't created any files... I tried to attach to the docker via command like but I just get a blinking cursor with no response. I'm guessing as it's a couple months old that this docker might just be out of date or broken.

     

    Any ideas?

  4. Yep, much easier to use....

     

    ###
    # New map created [save.zip]
    ###
    ###
    # Launching Game
    ###
    0.000 2016-03-05 15:56:08; Factorio 0.12.25 (Build 17747, linux64)
    0.030 Operating system: Linux (Ubuntu 14.04)
    0.030 Program arguments: "/opt/factorio/bin/x64/factorio" "--disallow-commands" "--start-server" "save.zip" 
    0.030 Read data path: /opt/factorio/data
    0.030 Write data path: /opt/factorio
    0.030 Binaries path: /opt/factorio/bin
    0.036 Running in headless mode
    0.037 Loading mod core 0.0.0 (data.lua)
    0.039 Loading mod base 0.12.25 (data.lua)
    0.272 Factorio initialised
    0.272 Info Router.cpp:556: Router peerID(65535) shutting down.
    0.273 Info Router.cpp:582: Router state -> Disconnected
    0.273 Info MultiplayerManager.cpp:906: networkTick(0) mapTick(-1) changing state from(Ready) to(PreparedToHostGame)
    0.273 Info MultiplayerManager.cpp:906: networkTick(0) mapTick(-1) changing state from(PreparedToHostGame) to(CreatingGame)
    0.273 Loading map /opt/factorio/saves/save.zip
    0.279 Info Scenario.cpp:124: Map version 0.12.25-0
    0.293 Info MultiplayerManager.cpp:282: 0x2ab6a8297230, (nil)
    0.293 Info PosixUDPSocket.cpp:34: Opening socket at port 34197
    0.294 Warning PosixUDPSocket.cpp:93: Failed to open IPv6 socket (Address family not supported by protocol), continuing with IPv4 only
    0.294 Info Router.cpp:582: Router state -> Connected
    0.294 Info Synchronizer.cpp:54: NetworkTick(0) initialized Synchronizer local peer(0) latency(6).
    0.294 Hosting game at port 34197, peerID 0, session magic 1082
    0.294 Info MultiplayerManager.cpp:304: 0x2ab6a8297230, 0x2ab6a8297230
    0.294 Info MultiplayerManager.cpp:906: networkTick(0) mapTick(0) changing state from(CreatingGame) to(InGame)
    0.294 Info NetworkInputHandler.cpp:40: mapTick(0) networkTick(0) initialized NetworkInputHandler local peer(0).
    0.410 Info MultiplayerManager.cpp:1385: Received peer info for peer(0) username(<server>).
    0.411 Info MultiplayerManager.cpp:1043: networkTick(6) mapTick(0) received stateChanged peerID(0) oldState(Ready) newState(CreatingGame)
    0.411 Info MultiplayerManager.cpp:1043: networkTick(6) mapTick(0) received stateChanged peerID(0) oldState(CreatingGame) newState(InGame)

     

    Just add it via Community Applications and map /opt/factorio/saves to /mnt/cache/appdata/factorio and you should be good...

     

    Oh sick, I'll try that. Was about to try it via command line :P

  5. I thought I could just remove a 2 1tb drives and replace them with 1 4tb drive. I've been able to replace one of the drives with the 4tb but I don't appear to be able to shrink the number of drives in the array. how do I do this?

    Reducing the number of drives is slightly different to increasing the size of existing drives.  Since the process involves invalidating parity it should never be done if you think any other disk has problems (unless it one you intend to remove).

     

    The following will work:

    • Make a note of the serial numbers of the drives (in particular the parity drive)
    • Go to Tools-New Config to clear the current configuration
    • Assign the disks you wish to keep.  Do NOT check the trust parity box as removing a drive invalidates parity.
    • Start the array.    This will start a parity sync to build new parity consistent with the drives you now have left.

    Sweet, this worked. (((thank)))

  6. You can try this from an ssh terminal to unRAID

    root@MediaStore:~# docker exec -it -u nobody Dropbox /bin/bash -l
    nobody@7b62d7da15fa:~$ cd Dropbox/
    nobody@7b62d7da15fa:~/Dropbox$ dropbox.py status
    Up to date
    nobody@7b62d7da15fa:~/Dropbox$ dropbox.py ls
    

    This last command should return all green, (don't remember the unsynced color)

    then quit with logout

     

    Ah HA! yep it's saying "Dropbox isn't running!"

     

    I'll try restart it and see what happens

  7. It's because in the lsusb output you posted it's device 24 and in your pass through tag it's device 23  ;)

    Rebooting probably made it device 23 again.

     

    huh so it was. Before booting the VM though the XML is just vedor and product ids so it was picking the wrong device number somehow?

    I thought you had put in the device id, but I guess you copied the tag while the VM was running?

    Somehow your usb device got disconnected and connected again, giving it a new device id.

     

    Yea copied while it was running. Must have, it seems to do that oftenish. I do experience the lights on some devices flicer during the VMs boot. maybe they all get dissconnected and reconnected then and just that device is lucky enough to get a new number

  8. I've been trying to setup a VPN for a while now, I've tried a couple of dockers and there was a plugin I was unsure of how to configure.

     

    Anyone using one successfully currently?

     

    My main goal is to have people on the VPN to have access to my shares and ideally they would just login with a username and password via whatever VPN client they're using.

     

    any recommendations?