own
Members
-
Joined
-
Last visited
-
when i go on unraid gui at the network graph and do a f5 the graph go back in time instead of starting from the time i do f5 i go in the gui, the graph is like that i wait some seconds the graph look like that i f5 and the graph look like my first picture again what i expect is if i wait 1 minute and f5 the graph should look like that and it's doing the same in the beta and rc of 7.0 tower-diagnostics-20241227-0457.zip
-
So starting 7.0 beta, i have ghost traffic with my unraid tower-diagnostics-20241220-0412.zip here a screen of my unraid in safemode with array stopped my netstat of my unraid is showing that (192.168.1.18 is my unraid 192.168.1.27 is my computer) and a screen from my computer showing it's not him uploading to unraid
-
use : find . -name "*.nfo" -type f so you are sure that's the files you want to delete and when you are sure the list is all files you want to delete use : find . -name "*.nfo" -type f -delete
-
in full uefi mode and if it's the gpu you boot unraid with, "video=efifb:off" is to make unraid let the GOP (Graphics Output Protocol) in a clean state so your vm can interact with it if you set your motherboard bios in full uefi (csm off), boot unraid in uefi, bind the gpu to vfio, you just need to make your vm ovmf/q35/no additional vbios and it will work ootb and if you do that the amd reset problem is non existant doing that, "video=efifb:off" is only needed if it's your first gpu because even if you bind the gpu to vfio, idk why but unraid interact with the GPO and it's no more in a clean state also, if you have a problematic HBA, flash it from the efi shell of your motherboard, if your HBA doesn't have that possibility it probably mean it's a very old HBA, only very old hardware doesn't support uefi, for ex. every gpu that have at min a hdmi output and/or displayport output is uefi compatible