Jump to content

JQNE

Members
  • Posts

    57
  • Joined

  • Last visited

Posts posted by JQNE

  1. On 10/26/2021 at 11:20 PM, Frank1940 said:

     

    @JQNE, When you put the flash drive in to the other computer to update, make a  complete copy of the contents of that drive before you do anything else.  You will need files and folders from the   config    folder to preserve the present configuration of your server.   Plus, a backup is never needed when you have one!!!

     

    In the past you could just copy over the bz* files in the root of the zip file to do an upgrade.  I know this is still required but I am not sure that is all that is required today.

     

    Hi!

     

    Thank you @Frank1940 for these instructions.

     

    I was able to update to version 6.9.0 and Unraid is running happily.

     

    BUT...

     

    I still have same problem. Community aplications "Download of appfeed failed". Can't update plugins. Can't udpate OS (there is version 6.9.1 available)

    image.thumb.png.eec8f23f9cc0f6be39ba3528b408d47c.png

    image.thumb.png.6c338de7e55715349214bf267f1eda8f.png

     

    So I think that old version of Unraid was not the problem. 

     

    In version 6.9.0 there is new update assistant test capability. Also that test suggested I should be okay to update...

     

    1536588800_ScreenShot2021-12-11at12_24_47.thumb.png.ec08c931a53f4e00eb7dc87566df2d29.png

     

    I also did reset my router to factory settings. No help.

     

    Any other ideas? Or do I have to start thinking new build...

     

     

    image.png

    unraid-diagnostics-20211211-1233.zip

  2. 4 minutes ago, Frank1940 said:

    Did you setup Notifications?  Is that working?

     

    @trurl mentioned that you were on 6.8.3.   Does this mean that you have been hesitant about doing any upgrades?   The reason that I am asking is that the addresses are hardcoded into each app.  Somewhere in the back of my now hazy mind is the thought that these addresses were changed a while back...

     

    I would be happy to update, but it seems that I have lost the possibility to update... I have not been interested at all about my server or updating it. It has been working very nicely as my local network storage.

  3. 22 hours ago, Frank1940 said:

    from the Unraid terminal (Icon on Toolbar), type the following:

    ping 8.8.8.8

     

    Use a <CTRL-C> to terminate the process.   IF that works, type the following:

    ping google.com

     

    If first command works, you  have Internet access.

     

    If the second command doesn't work, you do not have a DNS server that is accessible from the Unraid server. 

     

     

     

     

    Thank you for this idea. For me this seems everything is okay. And internet is working. 

     

    image.png.c696fc428064fcf2272c43dc3f9c6da0.png

     

    Still I can't connect to community applications.

     

    image.thumb.png.b307c36709c275052498302fccb31510.png

     

    And update os "Check for updates" does nothing.

    image.thumb.png.0ec8715bd9bd8cef0ec9a1fb5ddf6756.png

     

    Any ideas for internet? Could this be some bug in unraid os?

  4. 12 hours ago, John_M said:

    Is it a vdisk? You can increase the size of a vdisk simply by stopping the VM and increasing the allocation to the vdisk in the template editor. You'll need to use the Storage Manager in Windows to make use of the newly available space.

     

    Or are you talking about adjusting the boundaries of the three partitions in the original post? That will need a partition editor and it's a dangerous process as it's very easy to lose data or make a bootable partition unbootable. The safest approach is to backup the contents of all active partitions, repartition from scratch and then restore the contents. Even that approach isn't foolproof.

    I understood it is not vdisk. It uses clover to boot from nvme, but isn't booting from nvme now supported by Unraid?

     

    So when I boot that wm, nvme drive dissapears from unassigned device list. I think it's like passed throuhg to vm.

     

    So I will start by copying my wm image to array and start tinkering about nvme...

  5. On 8/8/2019 at 7:31 PM, testdasi said:

    Start a new template and redo it. That will save you more time than stumbling your way through the xml without knowing exactly what to look for.

    Thanks for advice!
     

    I did create new VM and added vm to boot with custom clover that will boot windows from nvme drive. That have been working nice for me. 

     Now VM will boot only to clover boot manager main window and sits there. On the right bottom corner there is number 3974. VM is not frozen, I can access clover setup menus.

     

    I have done this clover nvme boot setup same as on this SIOs video: 

     

     

    And to be clear my system has been working and booting without problems on nvme. What could be the problem?

    unraid-diagnostics-20190817-1354.zip

     

  6. 20 hours ago, JQNE said:

        <hostdev mode='subsystem' type='pci' managed='yes'>

          <driver name='vfio'/>

          <source>

            <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

          </source>

          <rom file='/mnt/user/Setup_files/GTX_file/asus1070.dump'/>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

        </hostdev>

    At this part there is my GPU. On adress type line there is that slot='0x05'  Could that be okey if I change it to GPU slot number, which I can look at system devices? Or could something bad occur?

  7. I have looked a while my XML and I can't figure this out.

     

    Here is VM start error:

    Execution error

    Device 0000:05:00.0 not found: could not access /sys/bus/pci/devices/0000:05:00.0/config: No such file or directory


    I have added pcie card to my rig and I think it has moved my usb controller from 05 to 06. I have checked usb controller is know at 06. I have my VM running from NVMe drive.

     

    Here is my XML:

    <?xml version='1.0' encoding='UTF-8'?>

    <domain type='kvm'>

      <name>Joonas Windows 10</name>

      <uuid>xxxxxxxx-48c7-bb18-431a-8b07bd737733</uuid>

      <description>Gaming</description>

      <metadata>

        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>

      </metadata>

      <memory unit='KiB'>12582912</memory>

      <currentMemory unit='KiB'>12582912</currentMemory>

      <memoryBacking>

        <nosharepages/>

      </memoryBacking>

      <vcpu placement='static'>4</vcpu>

      <cputune>

        <vcpupin vcpu='0' cpuset='2'/>

        <vcpupin vcpu='1' cpuset='3'/>

        <vcpupin vcpu='2' cpuset='4'/>

        <vcpupin vcpu='3' cpuset='5'/>

      </cputune>

      <os>

        <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>

        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>

        <nvram>/etc/libvirt/qemu/nvram/xxxxxxxx-48c7-bb18-431a-8b07bd737733_VARS-pure-efi.fd</nvram>

      </os>

      <features>

        <acpi/>

        <apic/>

        <hyperv>

          <relaxed state='on'/>

          <vapic state='on'/>

          <spinlocks state='on' retries='8191'/>

          <vendor_id state='on' value='none'/>

        </hyperv>

      </features>

      <cpu mode='host-passthrough' check='none'>

        <topology sockets='1' cores='4' threads='1'/>

      </cpu>

      <clock offset='localtime'>

        <timer name='hypervclock' present='yes'/>

        <timer name='hpet' present='no'/>

      </clock>

      <on_poweroff>destroy</on_poweroff>

      <on_reboot>restart</on_reboot>

      <on_crash>restart</on_crash>

      <devices>

        <emulator>/usr/local/sbin/qemu</emulator>

        <disk type='file' device='disk'>

          <driver name='qemu' type='raw' cache='writeback' discard='unmap'/>

          <source file='/mnt/cache/vdisk_ssd/Joonas Windows 10/vdisk1.img'/>

          <target dev='hdc' bus='scsi'/>

          <boot order='1'/>

          <address type='drive' controller='0' bus='0' target='0' unit='2'/>

        </disk>

        <disk type='file' device='cdrom'>

          <driver name='qemu' type='raw'/>

          <source file='/mnt/user/isos/virtio-win-0.1.160-1.iso'/>

          <target dev='hdb' bus='ide'/>

          <readonly/>

          <address type='drive' controller='0' bus='0' target='0' unit='1'/>

        </disk>

        <controller type='usb' index='0' model='ich9-ehci1'>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>

        </controller>

        <controller type='usb' index='0' model='ich9-uhci1'>

          <master startport='0'/>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>

        </controller>

        <controller type='usb' index='0' model='ich9-uhci2'>

          <master startport='2'/>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>

        </controller>

        <controller type='usb' index='0' model='ich9-uhci3'>

          <master startport='4'/>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>

        </controller>

        <controller type='scsi' index='0' model='virtio-scsi'>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

        </controller>

        <controller type='ide' index='0'>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>

        </controller>

        <controller type='virtio-serial' index='0'>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>

        </controller>

        <controller type='pci' index='0' model='pci-root'/>

        <interface type='bridge'>

          <mac address='52:54:00:25:2c:0c'/>

          <source bridge='br0'/>

          <model type='virtio'/>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>

        </interface>

        <serial type='pty'>

          <target type='isa-serial' port='0'>

            <model name='isa-serial'/>

          </target>

        </serial>

        <console type='pty'>

          <target type='serial' port='0'/>

        </console>

        <channel type='unix'>

          <target type='virtio' name='org.qemu.guest_agent.0'/>

          <address type='virtio-serial' controller='0' bus='0' port='1'/>

        </channel>

        <input type='tablet' bus='usb'>

          <address type='usb' bus='0' port='1'/>

        </input>

        <input type='mouse' bus='ps2'/>

        <input type='keyboard' bus='ps2'/>

        <hostdev mode='subsystem' type='pci' managed='yes'>

          <driver name='vfio'/>

          <source>

            <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

          </source>

          <rom file='/mnt/user/Setup_files/GTX_file/asus1070.dump'/>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

        </hostdev>

        <hostdev mode='subsystem' type='pci' managed='yes'>

          <driver name='vfio'/>

          <source>

            <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>

          </source>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>

        </hostdev>

        <hostdev mode='subsystem' type='pci' managed='yes'>

          <driver name='vfio'/>

          <source>

            <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>

          </source>

          <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>

        </hostdev>

        <memballoon model='none'/>

      </devices>

    </domain>

    unraid-diagnostics-20190806-2028.zip

  8. 20 hours ago, johnnie.black said:

    Looks more like a connection problem, but since the disk dropped offline there's no SMART report, power down, check/replace both cables and post new diags.

    I did run smart shot test after. And it's completed without error state. 

     

    Power on hours 10089 (1y, 1m, 24d, 9h) on old laptop(cheap) hdd is really good amount of time... I think ;)

     

    I also checked cables.

     

    unraid-smart-20190724-2137.zip

  9. I installed couple days ago new expansion card to my Unraid server (LSI SAS9211-8i). I installed LSI card and one new drive to it at it worked fine. I did preclear new drive. Then expanded/added it to my array. Then just after that another disk went in error state, I installed new drive and did preclear. Then I removed old drive and did rebuild at new drive. Then I installed new drive and did preclear to add that drive as second parity. I normally started array, but at very first I got another drive in error state. So I didn't got to set new drive to parity2, I just wanted to get array running first to see everything is working normal. Now I'm scared to do anything, I stopped the array. Would it be wise to replace error drive with new precleared drive, or add it as second parity?

     

    Could this be normal random two drive failures in a row, or can you find something bad at my diagnostics? Thanks in advance! I'm very concerned if there's something really wrong on my server...

    unraid-diagnostics-20190724-2103.zip

×
×
  • Create New...