Everything posted by derpuma
-
Is it possible to individualize HDD spin down?
I hear you and yes, stripping through the disks will definitely benefits speed, but I'd like at least a little bit of redundancy. I will test a few scenarios and see what fits best.
-
Is it possible to individualize HDD spin down?
So... I tried the ZFS RAIDZ with 3x 10TB HDD today, but unfortunately it seems to be very slow, esp. compared the the BTRFS RAID5. I set it up with standard settings, no special config, with only a minimum RAM setting. I have 64 GB in my Server, while I was using my VM with allocated 48GB RAM, copying files seemed to be very slow. I use a 10Gb Ethernet Connection on both machines, my Truenas and Unraid Server and with ZFS RAIDZ files of aprox. 1TB took significantly more compares BTRFS RAID5. In my actual array, I have only one NVME of 2TB, where all the system files, appdata, isos, etc. are stored. My VMs are on a second 2TB NVME, a unassigned device, where I boot my VMs from. My thinking now is, to actually use the Array possibilities from Unraid and put the 3x 10 TB HDDs in there where one acts as a parrity. Question is, if I create a new blank config, how can I restore my settings (apps, VM settings, etc.) which are then on the previous array NVME, which then becames a unassigned disk too? What is the best way to use it then, when I want the array to spin down also, when no backup job is running. So basically Uraid should not use the array when I work on the system with my Virtual machines! I really need no redundancy or security for my VM images, as they backup over to my truenas server. Does the array spin down, if these files stay there but non of these directory contains files, the VMs use? I guess performancewise the Array would be the best bet? Here is a little overview how have set it up the disk now as my daily VM workstation:
-
Is it possible to individualize HDD spin down?
Sorry, that I was not precise. I meant stopping the array and then hot swap/plug! Of course a running pool or array does not like swap or plug of running drives. My bad!
-
Is it possible to individualize HDD spin down?
Thanks, yes I know that. Is it really that bad? What would you recommend then? ZFS might not be an option, as my System is mainly a VM Server where I work from and I need the RAM for my VMs. The pool should only act as another security backup of my truenas server. And as written: I am still on Unraid 6 latest Version, as UNRIAD 7 broke my macOS VMs booting up and I did not have the time right now, to fix these problems.
-
Is it possible to individualize HDD spin down?
Thx guys for the reply. Okay, so I might stick on the 15 min. on the pool drives then. It is not RAIDZ it is btrfs RAID5 as I do not need the ZFS features here. Therefor I have a Truenas server running. I need the pool only for a cross backup of my existing truenas work folders. These backups run over nigth, so I only need the pool up on that time. I do not use the pool at all or work from it, it is only a safety backup on another device. I thought I could set it somehow, that the disks are not on at boot, as UNRAID is able to hot swap / hot plug, I thought there could have been an option for that. Thanks anyway for the replies! @tjb_altf4 Do you have a link to the scripts by hand? I searched quickly, but did not find the source so far.
-
Is it possible to individualize HDD spin down?
I have a RAID backup pool of HDDs, which I do not want to spin up at boot, as I use it only for backup tasks. Is there a manual way, to set spin down in UNRAID? Thru GUI I see 15 min. as the least amount of time after the spin down takes place. Maybe I can set the time manually to 1min or so? Thx in advance! I am on V 6.12.15
-
Problems with sftp connection (hosted with IPv6 only) when virtio network model is used...
Hi, I recently had problems with sftp connections and very slow upload speeds (only kbps) over sftp when connecting to an IPv6 only address, while my network bridge is set to virtio. That problem was present while working from a macos VM. First I thought it was a macos VM problem (EFI or kext) but I saw, that my windows vm has not had this problem at all and that it used virtio-net. After switching from virtio to virtio-net on my macos VM, IPv6 speeds are now like they should be (round about 50 Mbps in upload). Any idea what the cause of this problem could be? I also use an Intel 520x dual 10gbit NIC, bridges also set to virtio. Should I set them to virtio-net too? Are there any performance differences between both? Or is there another network model, I should use when booting into a macos VM? I am still on UNRAID Version 6.12.13 2024-08-22.
-
Problem with Windows 10 VM and 1GbE NIC - IPv4 adresse - not internet / Unraid 6.12.13
A strange observation I made is, that every Network in Windows 10 is shown aas a 10/10Gbe internet connection. I put the 10/10Gbe PCIe Card out of my mainboard, booted Unraid and installed a Windows 10 VM, only with the 1Gbe Onboard Network in bridged mode as an available network source. Even then the Redhat driver states the card as 10/10 Network Connection in Windows... I bet previously it was shown always right as a 1 Gbe connection. I even booted form a fresh installed Unraid Bootstick with the same behaviour, which drove me nuts. Am I missing something out? Or can anyone confirm this?
-
Problem with Windows 10 VM and 1GbE NIC - IPv4 adresse - not internet / Unraid 6.12.13
Hi, I have a problem with my network when I am installing a fresh windows 10. Install and everything went fine, but in Windows I see, that the internet connection is bridged via my 10/10GbE ethernetcard. My 1GbE Nic, which should handle the internet connection gets a random IPv4 address which does not macht the IPv4 range of my internet router. Deactivating the 10 GbE adapter and giving a matching IPv4 address to the 1GbE network does not work. 1Gbe adapter still stays as unidentified network. How can I force unraid to use the 1Gbe instead of the 10Gbe connection? Bridge source is br0 with virtio-net: <interface type='bridge'> <mac address='52:54:00:5e:e2:76'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface>
-
USB on AMD 6900XT with a drawing tablet Kamwas 16 (2021) > Problem getting the pen to work
I forgot to mention, this happens only in my macOS virtual machines.
-
My setup
Hey, do you mind sharing your XML you used for your 6900XT? Does yours have a USB-C Port? Mine has, and I would like to connect a drawing tablet to the USB-C Port of my AMD Founders Edition 6900XT. Unfortunately the pen does not work on the tablet, when connected with the following XML. Display so works just fine. If I connect the diplay to a regular USB-C Port, the pen works of course without display then... If I drop 0d:00.2 and 0d:00.3 from XML my virtual machine does not boot up. Any Idea how to solve that? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/disks/PNY44200029300702054/VM/macOS/AMD.RX6900XT.16384.201104.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x3'/> </hostdev>
-
USB on AMD 6900XT with a drawing tablet Kamwas 16 (2021) > Problem getting the pen to work
I have a problem getting my drawing tablet to work in Unraid via USB-C on my AMD 6900XT. It is a Huion Kamwas (2021) with a 3to1 and a USB-C only cable connection. I would like to get this working only with the USB-C Cable, cause the 3to1 cable is very bulky and a little bit short too. Hardwarewise IOMMU looks like this, which works for the display connected. Display is working, pen is not. Any chance someone could help me, how to setup the XML, that also USB-Input for the pen is working, beside the display part? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/disks/PNY44200029300702054/VM/macOS/AMD.RX6900XT.16384.201104.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x3'/> </hostdev>
-
Random crashes of UNRAID and imediate reboot
CPU temp is not a problem. I use an 360 AOI and Idle around 40°C. Under full load barely over 60°C. A long Cinebench run not nearly up to 80°C. And as said, the crashes even happen, when the VM sits and does nothing. For ex. I go for a lunch brake, come back and Unraid with VM crashed and restarted into shell.
-
Random crashes of UNRAID and imediate reboot
Hi Jorge, thx for the hint. I am on a Ryzen 5 5950X and Gigaybyte Aorus X570 Pro. I already tried the Bios setting from my screenshot on "enable". I can try to disable c-states globally. I am wondering, that I never had issues from 2019 to 2023 but I did some bios updates. Do you think it is worth to go back to an older bios? I already went back from latest beta bios to latest stable release with no changes. And fyi, I use 4 sticks of 16GB RAM in the right slots. So no messing up with dual channel mode (as dsaid also tried with single RAM stick). Even XMP on or off shows no difference regarding to the crahes.
-
Random crashes of UNRAID and imediate reboot
So I did. A new fresh install of Undraid, with only VMs, noch dockers or other plugins also leads into fatal power off the machine and reboot. The funny thing is, I do not need a heavy load or something. Sometime I only use the Browser, surfing the internet, staying up to get a coffee and come back and the machine turned of and rebooted into unraid after a powerloss. And as said, the system runs pretty stable while I am on native Windows. No crashes or poweroff there, I ran a Cinebench over night and had no hardware problems there at all. I have a last suspect: my NVME M2 Pcie Disk. I run my VMs from that NVME, my native Windows runs from a regular sata SSD. Whats wondering me, is that there is a complete power shutdown and that the machine starts and immediatly boots up again after this powerloss. Could this be due to a broken NVME? The only other thing I have in mind is, that it could it be a Bios related setting, which leads into crashes while I am using KVM? This happens regardless of windows, mac or linux VM. So I doubt that it is the XML configuration of the virtual machines, esp. because I run them since a couple of years now with this hardware and zero problems until this mess started.
-
Random crashes of UNRAID and imediate reboot
As said, nothing really changed in my system. I also put back the old GPU and used the old VM XML, but I also have crashes there with the old GPU. From hardware side, this was my only change. I also checke the NVME disks, where the VMs run from. They seem fine too. First I suspected a faulty Motherboard, RAM oder CPU. But I have as said, no crashes under native Windows. I also tested different RAM, so RAM should also not be the problem. Any idea where to start? Installing a new unraid and set it up setup by step from scratch with a demo licence and see if that helps?
-
Random crashes of UNRAID and imediate reboot
I have to come up with the problem again. First I thougt, the problem was due to a defective Power Supply, but I still have randomly crashes of my VMs while working on them. I occurs in Windows and Mac VMs. If I boot Windows nativly in a windows, I can work for days, without any crashes, so I conclude, it is not a hardware problem. Is it possible, that a defective USB bootstick leads into power down crashes? The Problem is, the system turns off, so I do not see any log entries, causing the problem. Any ideas? Worth to jump on an new USB stick? By the way, I am on latest 6.12.11, but had the problems with 6.12.10 too.
-
Random crashes of UNRAID and imediate reboot
Will try that over the weekend, as I would have to setup all my VMs. I also did a Bios Update, but if so I would blame more the GPU causing the problems. Esp. as I bought it used and for a fairly low price, marked as working like new. 😕
-
Random crashes of UNRAID and imediate reboot
I already cycled thru my 4 RAM Sticks. But that did not seem to solve the problem. Also MEMTEST did not find any faulty RAM. I know its always apita to figure out which hardware is the problem.
-
Random crashes of UNRAID and imediate reboot
I have random crashes of unraid and the fix common problems tool is reporting me hardware fault. Not sure whats causing the problem. The only update I made recently was upgrading from an older AMD 5700XT to a AMD 6900XT. I attached the diagnostics and it would be nice, if someone could have an eye on it. I guess this error from syslog is not relevant? Jul 19 08:11:46 Tower kernel: mce: [Hardware Error]: Machine check events logged Jul 19 08:11:46 Tower kernel: registered taskstats version 1 Jul 19 08:11:46 Tower kernel: mce: [Hardware Error]: CPU 19: Machine Check: 0 Bank 0: baa00000000c0135 Jul 19 08:11:46 Tower kernel: mce: [Hardware Error]: TSC 0 MISC d012000100000000 SYND 4d000014 IPID 1000b000000000 Jul 19 08:11:46 Tower kernel: Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no Jul 19 08:11:46 Tower kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1721369470 SOCKET 0 APIC 7 microcode a20102b Thx in advance! tower-diagnostics-20240719-0842.zip
-
Wi-Fi 6 Intel AX210 on macOS Sonoma
From my running macOS Monterey i've updated to Sonoma 14.3.1. With the help of @ghost82 I updated all the necessary OpenCore kext and config.plist to the newest version, replaced the old OpenCore image and was able to boot in Sonoma.
-
Wi-Fi 6 Intel AX210 on macOS Sonoma
Thx for your reply! AX210,AX211, etc. eg. Cards working very well in Sonoma, regarding to this github: https://github.com/perez987/Intel-AX210-wifi6-on-macOS-Sonoma This is my card. Wifi is running with the kext linked on github above. So I guess that there is no Issue with passthrough of the card. The only part not working is Bluetooth. I am not sure what is wrong in my setup. I tried all possible kext kombinations, others reported as working. So far no luck here on Sonoma. I am currently on 14.3.1, I updated to 14.4Beta, to see if this fixes the problem, but now my macOS does not boot up anymore. Have to go back to my 14.3.1 backup. Not sure why 14.4Beta is not booting after the update.
-
Wi-Fi 6 Intel AX210 on macOS Sonoma
03:00.0 8086 2725 8086 0024 Disabl Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz Network controller Network controller /pci8086,2725@0 pci8086,2725 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0) Looking for a Wi-Fi solution that does not require disabled SIP (e.g. Intel AX210), I found this on Github. I bought a Wi-Fi 6 AX210/AX211/AX411 160MHz card from Amazon, and pass through the card into Sonoma: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> Then I prepared my OpenCore bootloader with all the necessary kext and config.plist settings. Boting in Sonoma, the Wifi Cardworks just fine: Unfortunately Bluetooth does not work and I am not able to pair any device. I double checked the kext, but as far as I see, I don't miss anything. Anyone else out there who tried Intel Wifi/BT on Sonoma and had also success with Bluetooth? I used this three kext in EFI/OC/Kext: IntelBTPatcher.kext V2.4.0 IntelBluetoothFirmware.kext V2.4.0 BlueToolFixup.kext V2.6.9 And I deleted: BrcmBluetoothInjector.kext form EFI/OC/Kext. This should be basically enough to get Bluetooth up and running, but here it dont. Any Idea? What am I missing out? I guess the passthrough has no errors, as my Windows 10 runs flawless (wifi and Bluetooth) with the same XML code I posted above. Help would be nice!
-
[Plugin] CA User Scripts
Is there a way, to bring a script to the UNRAID top menu bar? Let's say a menu item witch by pressing runs a user script for a VM cycle?
-
How to stop .DS_STORE files and ._ files being created in shares (SERVER SIDE)
Thanks for the hint. So I guess hide files isn'T working too. This might be also the reason for my Samba syslog errors... Oct 12 13:09:49 Tower smbd[11653]: =============================================================== Oct 12 13:09:49 Tower smbd[11653]: [2022/10/12 13:09:49.358392, 0] ../../lib/util/fault.c:174(smb_panic_log) Oct 12 13:09:49 Tower smbd[11653]: INTERNAL ERROR: smbd_scavenger_parent_dead in pid 11653 (4.17.0) Oct 12 13:09:49 Tower smbd[11653]: [2022/10/12 13:09:49.358403, 0] ../../lib/util/fault.c:178(smb_panic_log) Oct 12 13:09:49 Tower smbd[11653]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Oct 12 13:09:49 Tower smbd[11653]: [2022/10/12 13:09:49.358411, 0] ../../lib/util/fault.c:183(smb_panic_log) Oct 12 13:09:49 Tower smbd[11653]: ===============================================================