Jump to content

bastl

Members
  • Posts

    1,267
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by bastl

  1. Same here for me, started yesterday. Yesterday i clicked on "check for updates" and mariadb and collabora came up with an update. Only collabora showed not available. After updating mariadb I thought, ok, your internet has stability issues anyways, check again tomorrow. And today it shows the following. Not all are unavailable and Collabora shows a update now. Weird!

     

    grafik.png.7024250c428f0d9f1bb7b8031e1d39a2.png

     

    I've checked pihole if anything came up in the query log, but nothing is blocked. I updated all packages on pihole (on a pi4), updated unbounds local root config, restarted the pi and rechecked for updates. Now only netdata and collabora showed an update, no unavailable ones. Updating netdata wen't fine, recheck for updates and only collabora left with an update. Looks like it works again for me.

  2. 15 hours ago, mgutt said:

    alle IPs bis auf die von Let's Encrypt und lokale zu sperren

    Die Idee hatte ich auch schon. Leider gibt es keine öffentlich verfügbaren Listen aller Letsencrypt Server. Wurde nie publiziert und die IPs ändern sich leider auch. Ich hab im Pfsense nen Geoblocking drin. Beim Sperren von Nordamerikanischen IPs funktioniert die Erneuerung der Certs leider nicht mehr. Desweiteren scheinen die Letsencrypt Server auch teils in anderen Ländern zu stehen. Die kontaktierte IP heraus zu bekommen war nicht das Problem. Bei der nächsten Erneuerung wird dann aber meist ne andere IP angesprochen. Ist nicht wirklich praktikabel da IP Freigaben zu konfigurieren, die wie bereits erwähnt, ja auch nicht fix sind und sich ändern können.

  3. The ACS override changes the groupings of your PCI devices. By removing ACS you might have regrouped devices you wanna passthrough. Make sure the specific device is still in it's own group. Check under Tools >>> System Devices

     

    "28:00.0 Intel Corporation 82576 Gigabit" is grouped with lot of other devices like "26:00.0 USB controller Renesas Technology Corp. uPD720201 USB 3.0 Host Controller" and "21:00.0 Network controller [0280]: Intel Corporation Wireless-AC 9260". Passthrough only works if a device you wanna passthrough is separated in it's own group. Look at all these devices together in group 14. 28:00.0 from your error log is a part of this group.

     

    /sys/kernel/iommu_groups/13/devices/0000:01:00.0
    /sys/kernel/iommu_groups/14/devices/0000:03:00.0
    /sys/kernel/iommu_groups/14/devices/0000:03:00.1
    /sys/kernel/iommu_groups/14/devices/0000:03:00.2
    /sys/kernel/iommu_groups/14/devices/0000:20:00.0
    /sys/kernel/iommu_groups/14/devices/0000:20:01.0
    /sys/kernel/iommu_groups/14/devices/0000:20:04.0
    /sys/kernel/iommu_groups/14/devices/0000:20:05.0
    /sys/kernel/iommu_groups/14/devices/0000:20:06.0
    /sys/kernel/iommu_groups/14/devices/0000:20:07.0
    /sys/kernel/iommu_groups/14/devices/0000:21:00.0
    /sys/kernel/iommu_groups/14/devices/0000:22:00.0
    /sys/kernel/iommu_groups/14/devices/0000:26:00.0
    /sys/kernel/iommu_groups/14/devices/0000:28:00.0
    /sys/kernel/iommu_groups/14/devices/0000:28:00.1
    /sys/kernel/iommu_groups/15/devices/0000:29:00.0

     

    Best way to fix it is to reenable ACS Override. Not sure why you removed it in the first place if it worked with it enabled. An Unraid Update won't change the underlying reporting from the motherboards bios. The PCI groupings only changes if in some cases a BIOS update from your motherboard vendor reorganizes it.

  4. @DK5RAX Nested Virtualisation, quasi eine VM in einer VM wird immer zu deutlichen Performanceeinbußen führen. Du kannst dir aber wie bereits von Smolo schon erwähnt eine VM in Unraid erstellen und ihm die vhd der VirtualBox als disk angeben. Mach dir am besten eine Kopie von der originalen Virtual Disk und teste es ersteinmal damit. Gut möglich, dass die VM erst nicht booten wird, da die Virtio Treiber in der VM nicht vorhanden sind. Dafür am besten in Win7 in Virtualbox die Treiber einfach per Inf Install installieren, dann sollte beim ersten Boot in Unraid die disk auch erkannt werden. Hat zumindest bei mir mit ner Win7 VB VM vor 2 Jahren funktioniert. Dann einfach noch von dem virtio.iso die restlichen fehlenden Treiber für Netzwerk und vGPU nachinstallieren und fertig.

  5. @Xanthariel Das Windoof interne Tool zur Verwaltung der Datenträger kann nur Partitionen erweitern, wenn sich der freie Platz direkt VOR oder NACH der Partition befindet. Bei dir befindet sich halt die 500MB Wiederherstellungspartition direkt dahinter. Partition verschieben geht bestimmt auch über die Kommandozeile mit Diskpart, wüßte jetzt aber auf anhieb nicht wie. Alternativ bräuchtest du quasi nen extra Programm, was die Partitionen auch direkt mit verschieben kann. "Paragon Partition Manager" in der free Community Edition sollte das zum Beispiel können.

     

    https://www.paragon-software.com/free/pm-express/

    • Like 1
  6. @dlandon I updated the UD plugin a couple minutes ago and my UD devices (3 disks and 2 shares) disappeared fom the main tab. In the community apps section it shows as installed, same for the Plus Addon. Pressing the "go to settings" buttons opens an empty page. Any ideas? I'am on 6.9.1 and never had an issue before. I updated almost always if new updates came in. Never saw such an behaviour. What to do now?

     

    EDIT:

     

    Ok it showed a new update as I finished the post and now it's back to normal. Weird

  7. 3 minutes ago, weirdcrap said:

    I believe this is due to the size of the syslog buffer provided to the WebUI and it was mentioned in one of the beta or RC threads. The full syslog should still be available on the filesystem itself.

    Thx for the info. Is there any settings to show again the full syslog inside the WebUI?

     

     

    Edit:

    I was to quick. Noticed your edit to late. Thanks for the link

  8. Update from 6.8.3 went smooth as always. Temp sensors on TRX40 are working now. 😘

    Switching from old pci-vfio in syslinux config to the new method also went without any issues.

     

    But a small thing I noticed. Syslog isn't starting with the normal boot process entries. The first entries for me are from some plugin checks/updates

     

    grafik.thumb.png.137561cc1e4e361031fb238ce15ca767.png

     

    Is this normal behaviour? Tried it with Firefox (main Browser) and Brave (never used for my server before). Same result. Is there a max line limit now for showing the logs and I can't find the settings?

  9. 22 hours ago, salaroli said:

    You need to pass every group that they are asking for, in the XML

    @Chenhi Be careful with this. Don't blindly passthrough what is shown. If the GPU for example is in the same group with one of your NVME drives or an storage controller this will cause your server to crash and in the worste case a data loss. Only passthrough devices which really belong to the device which you want for example the USB controller and the audio part of your card. Sometimes it might help to use another PCIe slot for the device you wanna passthrough.

  10. @Jaster I bet you copied the xml of a running VM and used it for other VMs. Default entry for a none running VM for VNC looks something like the following:

        <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='de'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>

    The "port" option is set to auto and counts up with each new VM you start. If you hardcode a value in, it tries to use that port and if in use by another VM you get that error.

     

    If I look into a the same xml from that VM while online it looks like the following:

        <graphics type='vnc' port='5903' autoport='yes' websocket='5703' listen='0.0.0.0' keymap='de'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>

    This is the 4th VM on my system which uses VNC and therefore it got port 5903 starting with 5900.

     

    If you need some fixed ports, try to use higher values depending an the amount of VMs you're using to prenvent conflicts and set the rest of the VMs to auto like it's shown on the first screenshot. Make sure your keymap is for your language.

    • Like 1
  11. @frankie666 Make sure when you first create a VM to define the vdisk size in GB. If you don't enter a value a vdisk is created but only a couple MB. Also make sure not to use core0 for the VM. This core is always used by Unraid itself to do stuff in the background and can end in low performance for the VM.

     

    With the following command you can show more infos about the created vdisk. Make sure the virtual size matches the value you defined and doesn't show a couple megabytes only.

    qemu-img info /mnt/cache/VMs/Mint/vdisk1.qcow2

    grafik.png.0f0ab43a1433033792e02e3a55847f68.png

     

    Adjust the path for the vdisk. In my example it's an qcow2 disk, but doesn't matter.

  12. Small observations I noticed for a couple weeks now. Every morning at 6am I do a automated BTRFS snapshot for my VMs on the cache drive to an UD drive. This works for over a year without any issues so far. What I have noticed starting on 23.11.2020 is that the allocation of the UD drive isn't shown correctly when I visit the main page after the snapshot anymore. The snapshots are created as usual (70-80G per day) but the allocation isn't showing the new values. I see the same values as the day before. Refreshing the main page isn't triggering a rescan of the drive. I am on 6.8.3 and installing plugin updates as they come in, nothing else has changed. Almost every day I check for updates.

     

    If I do a "BTRFS sub list /mnt/disks/backupdrive" for the UD drive the values are shown correct again. If I don't do this, the old values are still shown. I never had to do this before. For me this is a small problem, because I have to clean old snapshots once every 1-2 months by hand on the 1,5TB drive to not fully filling it up. @dlandon I know it's not really a big think, but maybe someone can explain me whats the reason for this new behaviour.

  13. 12 hours ago, AlexGreenUK said:

    dies='1'

    Remove that part from the "cpu mode" section from your xml so it looks like the following and try again with more cores.

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

    Not sure how you got that option in there. I never saw Unraid adding that option by itself.

×
×
  • Create New...