SavellM

Sorry I meant emulation not passthrough. Is there any other way to get faster perf? I cant split IOMMU group as its part of my backplane

But why is passthrough so much slower?

Hi all, I created a windows VM to do some Chia storage plotting. I added a manual vDisk as: /dev/disk/by-id/ata-INTEL_SSDSC2KB019T8_PHYF016402MC1P9DGN With SATA as the Bus. But when reading/writing to the disk its going at around 100MB/s. But SATA should allow around 500MB/s. The same drive on a dedicated PC gets full 500MB/s. Is there any way I can pass it through to the VM where I can read and write at almost full speed? Windows is showing it as QEMU Harddisk if that helps anyone. Or does it need specific drivers?

Hey Saarg, I've also just run into the Tone Mapping issue. I just did the fix a few posts above, when you update the stable docker container will we need to do anything to revert our steps or will it just work correctly? Lastly how come you guys dont read these forums much anymore? Was it the 6.9 saga of not thanking devs? If so are you guys using/supporting a different platform more? All my containers are linuxserver.io ones, so dont want to lose the good work you guys have done as its blooming amazing, and I thank you guys for all your efforts.

Just happened again, when I needed to restart. I forgot to do the steps above as this time it showed it as spun up but drive had no temp. I assumed it was just missing one this one drive and then I restarted and boom it is disabled. This is very annoying and I could really do with getting a fix. Next week I'll try replicating with the step above.

I am using LSI 9300-8i SAS3008 - 17.00.00.00 i believe. Drives are on SC61 firmware.

I have ST8000VN0022 And I have a ton of issue with the drives going into disabled state! So I would include these drives too when the sleep they do not wake up cleanly.

Yea I'm fortunate that my server mess is in the loft. Can be as loud as it wants. Also part of the reason why those drives got so warm, in Summer its like a hotbox up there. I've done some extractor fan magic and chassis mods to get it under control. But that said yup, my chassis came with a pair of PWS-920P-SQ I think this chassis now with its mods will be my chassis for life. I've done all the upgrades, upgraded backplane to the SAS3 variant and did the Noctua fan mods. I also used to run a Gigabyte board in it, but just replaced that recently to a SM board, just for unity lol. Thanks for the help with the drives, I will test in the next few weeks and let you know.

Surely! I'll try this next time but as of right now I'm just not spinning down the drives. I guess I could and try then for next time I need to restart. Fortunately I have no data on these Seagate drives yet, so they never need to spin up unless I'm restarting or Parity. So those drive temps are from old Chassis... I have since upgraded to Supermicro 846 and done the Noctua fan mods. Now drives dont get much above 40 in the middle of summer. Right now they are a cool 22c

HAHA its all good! Just pointed it out as I saw it. Thanks for the constant development! You rock.

Yeah I may just do that

What about making it an option that a user can choose? As then I could have tested that, maybe bonds take a little bit extra to get fully connected. I will re-enable the bond again another day and test that further.

Kinda wish I didnt uninstall the plugin and reinstall before changing network But all good seems to be working, thanks for putting up with me. Like I say I'm not saying it is connected or this plugin, just seemed odd. Or maybe the way Bonds work on boot.

Seems to have pulled the version on boot just fine now. Interesting.

Yup changed it back to active-backup the default setting to test.

So I rebooted, got back into unraid, im now re-installing the plugin. Its pulling the latest driver as we speak. Once its back I'll try changing it down a version and back again.

While I dont disagree it seems all too connected. Can you add a wait for network before continuing or an option pause for 10 seconds before checking network to allow it to come online?

Network has been running perfectly fine for months. No other plugin gets these network related issues. Server is perfectly fine when booted, all dockers and all plugins and all VM's work. Its literally just this part during boot. Like I say I'm not sure if its related but this is the only plugin having issues. And rebooted perfectly fine until I removed this plugin and now my server doesnt get any network at all, just self assigned IP.

So I removed the plugin and restarted unRAID, oh man, now it wont connect with any network. Not sure if its related but seems to be something funky with this plugin and network.

Finally got home: cat /boot/config/plugins/nvidia-driver/settings.cfg first_installation=false driver_version=latest local_version=455.45.01 I'll try the reinstall and then test networks stuff now.

It is a dedicated physical device. So internet should always be up and running. I also believe its a network issue, just not sure why or how to resolve. I'll do some more digging today and let you know. Maybe a simple delete plugin and reinstall and see how it goes as a first step. Then look into network issues.

Yup I can download that file just fine. I am using pfBlockerNG via pfSense. Is there a way I can manually download that file and place it somewhere and reboot, and let it pick it up manually?

I mean I have a default 6.9 install. I am using bonded ethernet but thats been setup for awhile. Is there a way to say wait for internet before starting?

I did select latest, it then asks me to restart which I did twice. This is what I saw. I guess I'll try reinstall the app again too... Thanks for your efforts.

I'm having an issue pulling the latest drivers upon restart. I found this in the logs wondering if you can advise? Also FYI you spelt successfull incorrect, it's successful. Minor just noticed it now looking at these logs