• Unraid OS version 6.9.0-beta25 available


    limetech

    6.9.0-beta25 vs. -beta24 Summary:

    • fixed emhttpd crash resulting from having NFS exported disk shares
    • fixed issue where specifying 1 MiB partition alignment was being ignored (see 1 MiB Partition Alignment below)
    • fixed spin-up/down issues
    • ssh improvements (see SSH Improvements below)
    • kernel updated from 5.7.7 to 5.7.8
    • added UI changes to support new docker image file handling - thank you @bonienl.  Refer also to additional information re: docker image folder, provided by @Squid under Docker below.
    • known issue: "Device/SMART Settings/SMART controller type" is ignored, will be fixed in next release

     

    Important: Beta code is not fully tested and not feature-complete.  We recommend running on test servers only!

     

    Multiple Pools

    This features permits you to define up to 35 named pools, of up to 30 storage devices/pool.  The current "cache pool" is now simply a pool named "cache".  Pools are created and managed via the Main page.

     

    Note: When you upgrade a server which has a cache pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of disk.cfg and into a new file, config/pools/cache.cfg.  If later you revert back to a pre-6.9 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache.  As long as you reassign the correct devices, data should remain intact.

     

    When you create a user share, or edit an existing user share, you can specify which pool should be associated with that share.  The assigned pool functions identically to current cache pool operation.

     

    Something to be aware of: when a directory listing is obtained for a share, the unRAID array disk volumes and all pools which contain that share are merged in this order:

      pool assigned to share

      disk1

      :

      disk28

      all the other pools in strverscmp() order.

     

    As with the current "cache pool", a single-device pool may be formatted with either xfs, btrfs, or reiserfs.  A multiple-device pool may only be formatted with btrfs.  A future release will include support for multiple "unRAID array" pools.  We are also considering zfs support.

     

    Something else to be aware of: Suppose you have a 2-device btrfs pool. This will be what btrfs calls "raid1" and what most people would understand to be "mirrored disks". Well this is mostly true in that the same data exists on both disks but not necessarily at the block-level.  Now suppose you create another pool, and what you do is unassign one of the devices from the existing 2-device btrfs pool and assign it to this new pool - now you have x2 single-device btrfs pools.  Upon array Start you might understandably assume there are now x2 pools with exactly the same data.  However this is not the case. Instead, when Unraid OS sees that a btrfs device has been removed from an existing multi-device pool, upon array Start it will do a 'wipefs' on that device so that upon mount it will not be included in the old pool.  This of course effectively deletes all the data on the moved device.

     

    1 MiB Partition Alignment

    We have added another partition layout where the start of partition 1 is aligned on 1 MiB boundary. That is, for devices which present 512-byte sectors, partition 1 will start in sector 2048; for devices with 4096-byte sectors, in sector 256.  This partition type is now used for all non-rotational storage (only).

     

    It is not clear what benefit 1 MiB alignment offers.  For some SSD devices, you won't see any difference; others, perhaps big performance difference.  LimeTech does not recommend re-partitioning an existing SSD device unless you have a compelling reason to do so (or your OCD just won't let it be).

     

    To re-partition a SSD it is necessary to first wipe out any existing partition structure on the device.  Of course this will erase all data on the device.  Probably the easiest way to accomplish this is, with array Stopped, identify the device to be erased and use the 'blkdiscard' command:

    blkdiscard /dev/xxx  # for exmaple /dev/sdb or /dev/nvme0n1 etc)

            WARNING: be sure you type the correct device identifier because all data will be lost on that device!

     

    Upon next array Start the device will appear Unformatted, and since there is now no partition structure, Unraid OS will create it.

     

    Language Translation

    A huge amount of work and effort has been implemented by @bonienl to provide multiple-language support in the Unraid OS Management Utility, aka, webGUI.  There are several language packs now available, and several more in the works.  Thanks to @Squid, language packs are installed via the Community Applications plugin - look for a new category entitled Language.

     

    Note: Community Applications must be up to date to install languages.  See also here.

     

    Each language pack exists in public Unraid organization github repos.  Interested users are encouraged to clone and issue Pull Requests to correct translations errors.  Language translations and PR merging is managed by @SpencerJ.

     

    Linux Kernel

    Upgraded to 5.7.

     

    These out-of-tree drivers are currently included:

    • QLogic QLGE 10Gb Ethernet Driver Support (from staging)
    • RealTek r8125: version 9.003.05 (included for newer r8125)
    • HighPoint rr272x_1x: version v1.10.6-19_12_05 (per user request)

    Note that as we update the Linux kernel, if an out-of-tree driver no longer builds, it will be omitted.

     

    These drivers are currently omitted:

    • Highpoint RocketRaid r750 (does not build)
    • Highpoint RocketRaid rr3740a (does not build)
    • Tehuti Networks tn40xx (does not build)

    If you require one of these drivers, please create a Bug Report and we'll spend some time looking for alternatives.  Better yet, pester the manufacturer of the controller and get them to update their drivers.

     

    Base Packages

    All updated to latest versions.  In addition, Linux PAM has been integrated.  This will permit us to implement 2-factor authentication in a future release.

     

    Docker

    Updated to version 19.03.11

     

    It's now possible to select different icons for multiple containers of the same type.  This change necessitates a re-download of the icons for all your installed docker applications.  A delay when initially loading either the dashboard or the docker tab while this happens is to be expected prior to the containers showing up.

     

    We also made some changes to add flexibility in assigning storage for the Docker engine.  First, 'rc.docker' will detect the filesystem type of /var/lib/docker.  We now support either btrfs or xfs and the docker storage driver is set appropriately.

     

    Next, 'mount_image' is modifed to support loopback formatted either with btrfs or xfs depending on the suffix of the loopback file name.  For example, the file name ends with ".img", as in "docker.img" then we use mkfs.btrfs.  If file name ends with "-xfs.img", as in "docker-xfs.img" then we use mkfs.xfs.


    We also added the ability to bind-mount a directory instead of using a loopback.  If file name does not end with ".img" then code assumes this is the name of directory (presumably on a share) which is bind-mounted onto /var/lib/docker.

     

    For example, if "/mnt/user/system/docker/docker" then we first create, if necessary the directory "/mnt/user/system/docker/docker".  If this path is on a user share we then "dereference" the path to get the disk path which is then bind-mounted onto /var/lib/docker.  For exmaple, if "/mnt/user/system/docker/docker" is on "disk1", then we would bind-mount "/mnt/disk1/system/docker/docker".  Caution: the share should be cache-only or cache-no so that 'mover' will not attempt to move the directory, but the script does not check this.

     

    Additional information from user @Squid:

     

    Quote

    Just a few comments on the ability to use a folder / share for docker

     

    If you're one of those users who continually has a problem with the docker image filling up, this is the solution, as the "image" will be able to expand (and shrink) to the size of the asigned share.  Just be aware though that this new feature is technically experimental.  (I have however been running this on an XFS formatted cache drive for a while now, and don't see any problems at all)

     

    I would recommend that you use a share that is dedicated to the docker files, and not a folder from another existing share (like system as show in the OP).  

     

    My reasoning for this is that:

    1. If you ever have a need to run the New Permissions tool against the share that you've placed the docker folder into, then that tool will cause the entire docker system to not run.  The folder will have to be removed (via the command line), and then recreated.

    2. All of the folders contained within the docker folder are not compatible with being exported over SMB, and you cannot gain access to them that way.  Using a separate share will also allow you to not export it without impacting the other shares' exporting.  (And there are no "user-modifiable" files in there anyways.  If you do need to modify a file within that folder, (ie: a config file for a container and that config isn't available within appdata), you should be doing it via going to the container's shell)

    You definitely want the share to be cache-only or cache-no (although cache-prefer should probably be ok).  Setting it to cache:yes will undoubtedly cause you problems if mover winds up relocating files to the array for you.

     

    I did have some "weirdness" with using a Unassigned Device as the drive for the docker folder.  This may however been a glitch in my system.

     

    Fix Common Problems (and the Docker Safe New Permissions Tool) will wind up getting updated to let you know of any problems that it detects with how you've configured the folder.

     

    Virtualization

    libvirt updated to version 6.4.0

    qemu updated to version 5.0.0

     

    In addition, integrated changes to System Devices page by user @Skitals with modifications by user @ljm42.  You can now select PCI devices to isolate from Linux upon boot simply by checking some boxes.  This makes it easier to reserve those devices for assignment to VM's.

     

    Note: If you had the VFIO-PCI Config plugin installed, you should remove it as that functionality is now built-in to Unraid OS 6.9.  Refer also @ljm42's excellent guide.

     

    In a future release we will include the NVIDIA and AMD GPU drivers natively into Unraid OS.  The primary use case is to facilitate accelerated transcoding in docker containers.  For this we require Linux to detect and auto-install the appropriate driver.  However, in order to reliably pass through an NVIDIA or AMD GPU to a VM, it's necessary to prevent Linux from auto-installing a GPU driver for those devices upon boot, which can be easily done now through System Devices page.  Users passing GPU's to VM's are encouraged to set this up now.

     

    "unexpected GSO errors"

    If your system log is being flooded with errors such as:

    Jun 20 09:09:21 Tower kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66

    You need to edit each VM and change the model type for the Ethernet bridge from "virtio" to "virtio-net".  In most cases this can be accomplished simply by clicking Update in "Form View" on the VM Edit page.  For other network configs it may be necessary to directly edit the xml.  Example:

    <interface type='bridge'>
          <mac address='xx:xx:xx:xx:xx:xx'/>
          <source bridge='br0'/>
          <model type='virtio-net'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

     

    SSH Improvements

    There are changes in /etc/ssh/sshd_conf to improve security (thanks to @Mihai and @ljm42 for suggestions):

    • only root user is permitted to login via ssh (remember: no traditional users in Unraid OS - just 'root')
    • non-null password is now required
    • non-root tunneling is disabled

     

    In addition, upon upgrade we ensure the 'config/ssh/root' directory exists on the USB flash boot device; and, we have set up a symlink: /root/.ssh to this directory.  This means any files you might put into /root/.ssh will be persistent across reboots.

     

    Note: if you examine the sshd startup script (/etc/rc.d/rc.sshd), upon boot all files from the 'config/ssh' directory are copied to /etc/ssh (but not subdirs).  The purpose is to restore the host ssh keys; however, this mechanism can be used to define custom ssh_conf and sshd_conf files (not recommended).

     

    Other

    • AFP support has been removed.
    • Numerous other Unraid OS and webGUI bug fixes and improvements.

     


    Version 6.9.0-beta25 2020-07-12

    Linux kernel:

    • version 5.7.8

    Management:

    • fix emhttpd crash resulting from exporting NFS disk share(s)
    • fix non-rotational device partitions were not actually being 1MiB aligned
    • dhcpcd: ipv6: use slaac hwaddr instead of slaac private
    • docker: correct storage-driver assignemnt logic
    • ssh: allow only root user, require passwords, disable non-root tunneling
    • ssh: add /root/.ssh symlink to /boot/config/ssh/root directory
    • syslog: configure to also listen on localhost udp port 514
    • webgui: Added btrfs info for all pools in diagnostics
    • webgui: Docker: allow BTRFS or XFS vdisk, or folder location
    • webgui: Multi-language: Fixed regression error: missing indicator for required fields
    • webgui: Dashboard: fix stats of missing interface
    • Like 2
    • Thanks 3


    User Feedback

    Recommended Comments



    Just to add some context - my VM DOES work in windows 10 on this beta.  I have created a new template (by deleting the VM without deleting the disks) and created a new one - pointed back at the disks etc.

     

    So that might be why it works, though personally I've always had to do this delete vm template dance in unraid since at least 3-4 versions ago.  At leat with windows.

     

    Networking isn't great though.  Even downloaded the latest virt-io drivers but no difference.  I've just passed through a physical Nic for now as connections were dropping.

     

    Anyway. hopefully that works for you as an alternate option.

    Link to comment
    Share on other sites
    10 hours ago, Marshalleq said:

    Just to add some context - my VM DOES work in windows 10 on this beta.  I have created a new template (by deleting the VM without deleting the disks) and created a new one - pointed back at the disks etc.

     

    So that might be why it works, though personally I've always had to do this delete vm template dance in unraid since at least 3-4 versions ago.  At leat with windows.

     

    Networking isn't great though.  Even downloaded the latest virt-io drivers but no difference.  I've just passed through a physical Nic for now as connections were dropping.

     

    Anyway. hopefully that works for you as an alternate option.

    Just guessing, could be because you had your old template on 4.1/4.2 etc.? Creating a new template would immediately bring it to 5.0.

     

    Networking default to virtio-net adapter with beta25. That has performance limitation. Try editing the xml and change virtio-net to virtio.

     

    I was told the next 6.9.0 version will have the option to pick virtio or virtio-net.

     

    Link to comment
    Share on other sites
    33 minutes ago, Thorsten said:

    How can i downgrade from Beta 6.9 - 25  to the stable version 6.8.3?

     

    If you updated from 6.8.3 then go to Tools -> Update OS. You should see Unraid OS (previous) which should have 6.8.3 in the version column.

    Note that there are things not backward compatible e.g. 1MiB alignment, multiple pools etc. Read the beta release notes for more details.

    Link to comment
    Share on other sites
    38 minutes ago, Thorsten said:

    How can i downgrade from Beta 6.9 - 25  to the stable version 6.8.3?

    Might be useful for us to know why you want to downgrade. Might even be useful to you in case you have some problem that you have incorrectly attributed to this version.

    Link to comment
    Share on other sites

     

    I have some problems with VMs. I can´t passthrough my grafic card anymore. When i change something with the VM Ui i get this Error.  (Fehler.png)

     

    If i change this to vnc i get the same error. 

     

    The second error is that when i change vnc password and vnc keyboard (e.g. German) the changes are not saved. 

    (Fehler2.png)

     

    VM.xml

    https://forums.unraid.net/applications/core/interface/file/attachment.php?id=88599

     

    Sorry for my english... 🙂

    Fehler.png

    Fehler2.png

    Edited by Thorsten
    Link to comment
    Share on other sites
    16 minutes ago, Thorsten said:

     

    I have some problems with VMs. I can´t passthrough my grafic card anymore. When i change something with the VM Ui i get this Error.  (Fehler.png)

    Fehler.png

     

    It looks like you changed your machine type from Q35 to i440fx?

    Changing machine type cannot be done through the GUI. The only way is to create a brand new template. This applies to ALL Unraid versions so downgrading won't fix it.

     

    Why do you want to change machine type to begin with? That is rarely if ever required (if anything, "modern" Windows VM should be using Q35 and not the super outdated i440fx)

     

    And please attach diagnostics for any queries. (Tools -> Diagnostics -> attach the full zip file to your next post).

     

     

     

    Link to comment
    Share on other sites

    I just answered in another thread about the "unexpected GSO type" where someone claimed that using Q35-5.0 would solve the issue, Ill just paste that post here:

     

    "I just tried yesterday with 2 newly created VM Q35-5.0 machines (Windows 10), on Beta25 and I still get the "unexpected GSO type" flooded in my logs when i use "virto" so I don't see how using Q35-5.0 would be a solution.

    Only way I get rid of that in the logs for me is to use "vitio-net" with the severely diminished performance.

     

    Edit: 

     

    Just tried again and still same results, attaching my diagnostics if you wish to see for yor self."

    unraid-diagnostics-20200821-0848.zip

    Edited by Koenig
    Link to comment
    Share on other sites

    So I got curious and did some more testing with the "unexpected GSO type" bug.

     

    Changing VM to 5.0 (Q35 or i440fx) fixes the issue when there are a small number of dockers with static IP on the same bridge as the VM (e.g. br0 custom network).

     

    In my particular server, "small number" is about 2-3 dockers.

    In my tests (with reboot in between), the error happened after the 3rd or 4th dockers with static IP were started (not sure why sometimes 3rd, sometimes 4th).

    The error seems to depend strictly on number of dockers and not number of VM. I started 5 VM with 2 static IP dockers and no error but 1 VM + 5 dockers guaranteed error.

     

    So conclusion:

    1. If you only have a few dockers with static IP, try changing machine type to 5.0 first. That may fix it without the need of any further tweaks.
    2. If you have many dockers with static IP (i.e. (1) doesn't fix it for you) then:
      • If you have multiple NIC's then connect another NIC (different from the one on the VM bridge), don't give it IP (important to not have IP, otherwise chances are your VM access to the shares will be done through the router i.e. limited to gigabit), add it to a different bridge (e.g. br1) and use it instead of br0 for your docker static IP.
      • If you only have a single NIC then you will have to change your VM network to virtio-net.
        • I think VLAN also fixes it but I have had no need for that so have no interest to test.

     

    And I think the errors are harmless, other than flooding syslog. When I started with 6.9.0, I didn't realise there were errors until my syslog filled up and there was no other issue at all.

     

    @Koenig: see above.

     

     

     

     

     

    Edited by testdasi
    Link to comment
    Share on other sites
    10 minutes ago, testdasi said:

    So I got curious and did some more testing with the "unexpected GSO type" bug.

     

    Changing VM to 5.0 (Q35 or i440fx) fixes the issue when there are a small number of dockers with static IP on the same bridge as the VM (e.g. br0 custom network).

     

    In my particular server, "small number" is about 2-3 dockers.

    In my tests (with reboot in between), the error happened after the 3rd or 4th dockers with static IP were started (not sure why sometimes 3rd, sometimes 4th).

    The error seems to depend strictly on number of dockers and not number of VM. I started 5 VM with 2 static IP dockers and no error but 1 VM + 5 dockers guaranteed error.

     

    So conclusion:

    1. If you only have a few dockers with static IP, try changing machine type to 5.0 first. That may fix it without the need of any further tweaks.
    2. If you have many dockers with static IP (i.e. (1) doesn't fix it for you) then:
      • If you have multiple NIC's then connect another NIC (different from the one on the VM bridge), don't give it IP (important to not have IP, otherwise chances are your VM access to the shares will be done through the router i.e. limited to gigabit), add it to a different bridge (e.g. br1) and use it instead of br0 for your docker static IP.
      • If you only have a single NIC then you will have to change your VM network to virtio-net.
        • I think VLAN also fixes it but I have had no need for that so have no interest to test.

     

    And I think the errors are harmless, other than flooding syslog. When I started with 6.9.0, I didn't realise there were errors until my syslog filled up and there was no other issue at all.

     

    @Koenig: see above.

     

     

     

     

     

    Well, I only have the one docker with static IP....

    Link to comment
    Share on other sites
    2 minutes ago, Koenig said:

    Well, I only have the one docker with static IP....

    YMMV then.

    Link to comment
    Share on other sites
    29 minutes ago, testdasi said:

     

    1. If you have many dockers with static IP (i.e. (1) doesn't fix it for you) then:
      • If you have multiple NIC's then connect another NIC (different from the one on the VM bridge), don't give it IP (important to not have IP, otherwise chances are your VM access to the shares will be done through the router i.e. limited to gigabit), add it to a different bridge (e.g. br1) and use it instead of br0 for your docker static IP.

     

    @Koenig: see above.

     

     

     

     

     

    I do have a Gibyte Aorus Xtreme with dual 10Gbe NIC so I might just test this suggestion, thank you, I had some other plans for the second NIC but that comes further into the future and perhaps this issue is ironed out until then.

    Link to comment
    Share on other sites

    New beta user.  I've finished making the switch which was time consuming as I've created new pools for my appdata (mainly Plex) and VMs, which meant moving a lot of data around, formating drives etc. 

     

    It all went fairly smoothly, but there's one new addition that really didn't help me.  I passthrough my primary GPU to a VM AND also run a pfSense VM.  If my array doesn't start, I have to stop it, unplug the USB, undo the VFIO-bind edits so that I have a screen, and then reboot to be able to access the server, as I can't use another computer to access the server because of the VM.

     

    In 6.9.0 it looks like if there's a unclean shutdown it turns off the disk auto start option - I'm sure this is a new feature.  This means I have to go through the steps above every time which is a pain.  Is it possible to make this optional or to remove as it's a real pain for people with headless servers AND a pfsense VM who can't get into the server over the LAN.

    Link to comment
    Share on other sites

    Also, there's a problem with the logic on the green 'All Files protected' icon in shares. 

     

    I have two shares (domains and iso) setup as cache only that use my 'Computers' pool that is configured as a JBOD.  They show up as 'protected' shares - the files aren't protected as it's a single pool.

    highlander-diagnostics-20200822-1021.zip

     

    Link to comment
    Share on other sites

    Had the error with a disk not decrypting after shutting down to install an additional NVME.

    Not sure that has any relevance but its a change to the system from the previous boot.

    If memory serves me right, I got the same behaviour when removing an old SSD last time this happened, so it could have something to do with a hardware change from the previous boot, or a disk addition\removal in particular?

     

    1st attempt at starting the array disk1 didn't want to decrypt, although all other disks did. 

    Stopped the array and tried again (no reboot), and disk5 didn't decrypt the second time. All other disks were fine though.

     

    Rebooted and everything is happy again.

     

    Logs attached.

    unraid-diagnostics-20200822-1247.zip

    Edited by billington.mark
    Link to comment
    Share on other sites

    Thought I'd bring this up, my routing table is wrong or is this the new behavior of 6.9? I don't have any /25 networks. So why did it add a /25? Also can't delete those /25 either. On 6.8.3 there was a no /25 networks on my routing table.

     

    image.thumb.png.811c17be1fdbba5cf0f75f3ed6e1b804.png

    Link to comment
    Share on other sites
    14 minutes ago, Cobragt88 said:

    Thought I'd bring this up, my routing table is wrong or is this the new behavior of 6.9? I don't have any /25 networks. So why did it add a /25? Also can't delete those /25 either. On 6.8.3 there was a no /25 networks on my routing table.

     

    image.thumb.png.811c17be1fdbba5cf0f75f3ed6e1b804.png

    Those usually result from enabling the "Host access to custom networks" option for Docker

    Link to comment
    Share on other sites
    17 minutes ago, Cobragt88 said:

    Thought I'd bring this up, my routing table is wrong or is this the new behavior of 6.9? I don't have any /25 networks. So why did it add a /25? Also can't delete those /25 either. On 6.8.3 there was a no /25 networks on my routing table.

     

    image.thumb.png.811c17be1fdbba5cf0f75f3ed6e1b804.png

    Settings -> Docker -> untick "Host access to custom networks"

    Link to comment
    Share on other sites
    On 8/16/2020 at 5:36 PM, Cobragt88 said:

    Got a small problem with beta 25. My log file gets to 100% in a few days. This never happened before on 6.8.3. Just thought i'd say something, other than that, I don't have any problems with this version.

    Ok here is the log at 100%.

    root@LoweNAS:~# df -h /var/log
    Filesystem      Size  Used Avail Use% Mounted on
    tmpfs           384M  384M     0 100% /var/log
    root@LoweNAS:~# du -sm /var/log/*
    1       /var/log/apcupsd.events
    1       /var/log/apcupsd.events.1
    0       /var/log/btmp
    0       /var/log/cron
    0       /var/log/debug
    1       /var/log/dmesg
    0       /var/log/docker.log
    0       /var/log/faillog
    0       /var/log/lastlog
    1       /var/log/libvirt
    0       /var/log/maillog
    0       /var/log/messages
    0       /var/log/nfsd
    1       /var/log/nginx
    0       /var/log/nvidia
    1       /var/log/nvidia-container-runtime-hook.log
    1       /var/log/nvidia-installer.log
    0       /var/log/packages
    1       /var/log/pkgtools
    0       /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
    1       /var/log/scan
    0       /var/log/scripts
    0       /var/log/secure
    0       /var/log/setup
    0       /var/log/spooler
    0       /var/log/swtpm
    371     /var/log/syslog
    12      /var/log/syslog.1
    2       /var/log/syslog.2
    0       /var/log/vfio-pci
    1       /var/log/wtmp
    root@NAS:~# 

    I have no clue why syslog is filling it up???? I have attached the diag file for review.

    lowenas-diagnostics-20200822-1020.zip

    Link to comment
    Share on other sites
    8 minutes ago, Cobragt88 said:

    I have no clue why syslog is filling it up????

    Known issue. "unexpected GSO type" issue flooding your syslog.

    Read the release note (search for virtio-net).

    Also read my post here for some alternative fixes.

    Link to comment
    Share on other sites

    hmmm. OK so i switched the one VM to 5.0 from 3.0. Is there a way to clear the log minus doing a full reboot?

    Link to comment
    Share on other sites
    On 7/20/2020 at 2:17 AM, ctab579 said:

    Hello,

     

    Today I attempted to upgrade to Beta25, and unfortunately, the only VM I run would not start. The VM is a Ubuntu server 18.04.4. This VM has my iGPU from my 8700K passed through used for jellyfin.


    I am currently running 6.8.3 and it works. I am not isolating this GPU via VFIO. My go file has the following at the bottom:

    
    modprobe i915
    chmod -R 777 /dev/dri

    This currently allows 6.8.3 the iGPU to be used by unraid when the VM is not running, and by the VM when it is running.


    After upgrading, I attempted to both use the existing configuration, I upgraded the configuration (for network configuration as shown in spaceinvader one's video), and tried to rerun. I attempted to isolate the iGPU via VFIO, rebooted, and tried to rerun. In each case the core 0 of the passed through cores was pinned at 100%, but the VM never started. The VM log did not throw any warnings.

     

    I also noticed that despite being in the go file /dev/dri did not exist until after manually entering modprobe i915 into the console.

     

    I have reverted back to 6.8.3 for the time being, but I am wondering if I missed something, or if there is something I need to do to resolve this issue.

     

    Thank you.

    Hi,

    is there a solution to this issue yet? 

    i have the same problem: iGpu vm stays with black screen, if i switch to VNC the vm works

    also tried creating a new vm with newer i440fx version and still have the same issue

     

    Thank you

    Link to comment
    Share on other sites
    19 hours ago, Cobragt88 said:

    hmmm. OK so i switched the one VM to 5.0 from 3.0. Is there a way to clear the log minus doing a full reboot?

    Reboot is the best way but you can try this. Also from command line go to /var/log and delete the old syslog.1 and 2 and so on.

    echo "$(date "+%d.%m.%Y %T") Log was cleared." > /var/log/syslog

     

    2 minutes ago, francesco995 said:

    Hi,

    is there a solution to this issue yet? 

    i have the same problem: iGpu vm stays with black screen, if i switch to VNC the vm works

    also tried creating a new vm with newer i440fx version and still have the same issue

     

    Thank you

    You should post a separate bug report with Diagnostics. Also perhaps try Q35 machine type (but I doubt it would help). And ask SpaceInvader One if he has any tips.

    Link to comment
    Share on other sites

    Hey all I’m in same position only way I can get the VM to boot is via vnc and using a command line. I get no signal through hdmi when trying to boot Vm driving me crazy!!!!!

    Link to comment
    Share on other sites



    Guest
    This is now closed for further comments

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.