Jump to content

SSMI

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SSMI

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm wonder if there is anyway to link the unraid web ui to various docker web uis using the url. Let me explain. So my unraid box is called nas on my home network. I can get to the webui by typing "nas" or the ip (192.168.1.200 for ex) into my browser. I also have owncloud installed. I would like to get to owncloud by using "nas/owncloud" or even "192.168.1.200". Is there some kind of plugin or something to set this up? I would be much easier than having to remember a bunch of ports or click through 2 or three pages on the unraid ui. Let me know.
  2. SSMI

    Windows 7 VM virtio problem

    The windows iso comes from an old installation disc that I've used for years. I believe it was originally a MSDNAA image. Would that be the problem though? It seems like windows at least started loading fine. The virtio image I downloaded today.
  3. SSMI

    Windows 7 VM virtio problem

    It is 64 bit professional.
  4. SSMI

    Windows 7 VM virtio problem

    I install all 4 in the order on the wiki as shown below. But nothing happens after installing the fourth. I am left with the attached screen. They all say no new devices found. Loading the VirtIO Drivers During Installation During the Windows installation process, you will reach a point where "no disks are found", this is expected behavior. Click Browse on this screen, then navigate to the virtio-win CD-ROM. You will need to load the following drivers in the following order: Balloon NetKVM vioserial viostor (be sure to load this one last) For each driver that needs to be loaded, you will navigate to the driver folder, then the OS version, then the amd64 subfolder (never click to load the x86 folder) After each driver is loaded, you will need to click the Browse button again to load the next driver. After loading the viostor driver, your virtual disk will then appear to select for installation and you can continue installing Windows as normal. After Windows is completely installed, you can install the guest agent, which improves host to guest management Open Windows File Explorer Browse to the virtual CD-ROM for virtio-win again, and then open the guest-agent folder Double-click to launch the qemu-ga-x64.msi installer (this process will be rather quick) And that's all there is to it! If you have questions on this procedure, please post in the Lime Technology forums.
  5. I can't seem to get the virtio drives to install. I am getting the error shown in the image. Is this normal? What am I doing wrong? I am trying to install windows 7 professional. Here is the xml from the VM setup. <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>HTPC</name> <uuid>bb1a18cc-7ef9-bc16-d1c5-b9daf7e343a5</uuid> <description>WIndows 7 on the TV</description> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VMs/HTPC/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/appdata/VM ISOs/Windows7Prof.ISO'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/appdata/VM ISOs/virtio-win-0.1.102.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:b4:1d:7b'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/HTPC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain>
  6. SSMI

    Docker Crashing unRaid

    So I'm am finishing up setup but I completly cleared my unraid box and started over from scratch. Now it shows the following under Docker Label: none uuid: 8fd80e0f-fde6-4b81-8bbd-4acbabe2df41 Total devices 1 FS bytes used 627.23MiB devid 1 size 20.00GiB used 3.04GiB path /dev/loop0 btrfs-progs v4.0.1 I think that has fixed things. I will post again after a week or so of uptime.
  7. SSMI

    Docker Crashing unRaid

    So there is no kind of reset or clean install I can do then?
  8. SSMI

    Docker Crashing unRaid

    Here is what it shows under Settings/Docker
  9. SSMI

    Docker Crashing unRaid

    btrfs-progs v4.0.1 scrub gives ERROR: getting dev info for scrub failed: Inappropriate ioctl for device
  10. SSMI

    Docker Crashing unRaid

    No one else is having this problem? Since it doesn't ever crash when docker isn't running could the docker on the USB be messed up somehow? Is there any way to 'clean install' like on windows without losing my data disks?
  11. SSMI

    Docker Crashing unRaid

    Alright. Set everything up again with owncloud and MriaDB. Evefrything worked like it was fupposed to for between one and a half and two days. Then it crashed again. I had a monitor and keyboard plugged in. I left it at the login screen. After the crash I can't access the web ui. On the physical device the login screen is gone. I will copy what was left as best I can. [<ffffffff8111b671>] ? pin_re,pve+0x15/0xae [<ffffffff8111b671>] drop_mountpoint +0x1a/0x2a [<ffffffff8111b671>] pin_kill +0x6a/0xec [<ffffffff8111b671>] ? wait_woken+0x7d/0x7d [<ffffffff8111b671>] mnt_pin_kill+0x2e/0x30 [<ffffffff8111b671>] cleanup_mnt+0x39/0x74 [<ffffffff8111b671>] __cleanup_mnt+0xd/0xf [<ffffffff8111b671>] task_work_run+0x93/0xae [<ffffffff8111b671>] do_notify_resume+0x40/0x4e [<ffffffff8111b671>] int_signal+0x12/0x17 ---[ end trace 163b45793ad5a3d0 ]--- mdcmd (44): spindown 2 mdcmd (45): spindown 0 mdcmd (46): spindown 1 mdcmd (47): spindown 0 mdcmd (48): spindown 1 mdcmd (49): spindown 0 mdcmd (50): spindown 1 mdcmd (51): spindown 0 mdcmd (52): spindown 1 mdcmd (53): spindown 0 mdcmd (54): spindown 1 I entered that by hand so there may be an error or two there. Escape doesn't do anything and enter scrolls a blank line. Any ideas what is causing this?
  12. SSMI

    Docker Crashing unRaid

    I understand. For deluge everything is outside of the docker.img. I am pretty sure MariaDB is as well. I need to double check owncloud because that one is new for me but I was using a template from here on the forum so it was probably setup correctly as well. I will double check them though because maybe I was missing something.
  13. SSMI

    Docker Crashing unRaid

    There are a couple of containers I like to be able to access all the shares. Do I need to do something special to allow this? Right not I am just including /mnt/user/ (I might have that wrong as I'm at work) as a volume mapping. Edit: I do put those types of storage on volume mappings. When I set everything up again I will try a lager img size as well.
  14. SSMI

    Docker Crashing unRaid

    Alright. I'll work on getting a syslog. It seems like the crash does corrupt the docker.img because I have to re-add the container from scratch to get them to start again.
  15. SSMI

    Docker Crashing unRaid

    I don't have it setup with those attached. It would take at least a few days to do so. Anything else I should try and get when I do the memtest? Docker shouldn't be able to crash unraid should it? From what I understand it is similar to a virtual machine. Could the docker install on my box be corrupted somehow?