JorgenK

I have the same motherboard and I recently looked at this again. On 6.11 it was enough to load the ite it87 driver from apps, it has been available since late 2022.

I was led to believe that the md driver was used when not setting up exclusive access to for the share. But I guess that I was mistaken. It's not SMR, but a slow 2.5" drive only just capable of Gb transfer rates. I will do some more tests with and without zfs. I will probably let zfs go anyway for now as the drives with zfs keep spinning up. I use the B460 chipsets SATA controllers.

I think that I see the same problem on a single pool drive, I use a 500GB 7200rpm 2.5" disk for always on services as I have a cctv software that's rumored to chew up SSD drives. The symptoms are one or two pegged cores on the dashboard but nothing out of the ordinary is shown in htop. The transfer runs at full GB speed, 112-113MB/s. But stopps drops to 0 once in a while. The same transfer to a nvme drive use much less CPU. For some reason I can't get iotop or the stats plugin to show any transfer speeds. I have not done any zfs tuning yet. I have never had to do that on a modern computer with GB ethernet but I have seen erratic performance with ZFS when using too old hardware for testing.

Thanks for your reply. I tried this but I got the same message about not being able to restart the device and the audio device could not start in windows. I think that this issue will need to be put on hold. Some testing yesterday, before trying your suggestion, make me think that something else is wrong. The VM crashes, I have tried recreating it many different way and I was able to recreate the problems in Windows and Ubuntu. This made the audio issue less important to sort out even if it will need to be fixed eventually if I want to replace my main desktop with a virtual machine. The VM fails soon after I pass through the GPU. But, it gets worse. The problems continue when changing back to VNC, but while still using the passed through USB keyboard. I could do many restarts and used newly restored virtual machines for a while. Then rebooted and added the USB keyboard to the VM. It would crash reasonably soon after that with or without a passed through GPU. Sometimes within minutes and sometimes it can work for a long time, just to fail after a restart. I have had a few VM's running over the last years without any problems and they still run fine.

Hi, I'm on 6.9.2. I have a virtual machine to which I passed through the intel onboard audio. I used the 3.5mm output. It worked the first time I tried it and has been running for a week or so. The VM did however crash hard when installing a Logitech keyboard driver of all things. It messed up the vdisk and I was unable to repair it with the windows 10 tools. I had a recent backup of the vdisk, which I started using. During the process where i tried to repair the windows WM I restarted the server. As I didn't expect a problem I ran all the windows updates after restoring the backup of the vdisk, to get the VM to the same status as before the crash. tower-diagnostics-20221024-1618.zip Can anyone see what went wrong when restoring the VM backup and restarting the server? Jörgen Extra information: I have used a passed through Quadro P400 for video, but it can not be used for audio because of how the audio amplifier present itself when the TV is on or off. Even bare metal windows 10 has problems with this amplifiers behavior when switching.

Today I have followed up on a few discoveries that has muddied the waters. Motherboard Gigabyte B460 HD3 CPU: I3-10100 Memory: 24GB GPU: Internal graphics, UHD 630 Discrete GPU: None Unraid 6.9.2 Dockers: binhex-deluge, plex ( cpu transcoding, can be removed) VMs: Win10running BlueIris with DeepStack, various Linuxes and BSD's for recreation, Win10 with SeaBIOS for IGPU testing, Win10 with OVMF for IGPU testing. At first I thought that the local screen would not wake up only used as a console, but it turns out that it was a keyboard issue that sometimes showed up when the server was left for months at a time. The screen wakes up as it should with a new keyboard if I don't try to passthrough the IGPU. I want to pass through the IGPU to a virtual machine running Win 10 with OVMF. Passing it through seem to work but the screen is blank, I can use remote desktop to access it and windows device manager reports that the UHD 630 is working properly. The screen does not detect a signal and goes into sleep mode. Win10 with seabios acts the same. The 630 looks like it's working but the screen is blank. I have disabled the onboard audio, no difference. I ticked the UHD 630 under system devices to bind it to vfio. Does anyone have an idea on how to fix this? tower-diagnostics-20211126-2103.zip

It's the original drive from an Apple Mini and the name was APPLE_HDD_HTS545050A7E362_TNS5193T15ML6H. I need to take credit for using the quote in the name when I didn't want a long name like that. I clearly remember wondering if the spaces and the quote was acceptable in the name and was a bit surprised when it was accepted. The Ohh shit, moment came minutes later.

Thanks a lot! It works now. I guess that just unplugging the drive an removing it from historical devices would have solved the problem I had.

I must be missing something. Is there a way to solve the problem after the fact? If it's to complicated I can replace the drive at a later time to be able to start from scratch. The only reason I fitted the 2.5" drive is to let the security cameras write to a silent drive. If I remove the partition and choose format I still get the same name and when it is mounted it's still at: /mnt/disks/HGST 500GB 2.5" The entry /etc/samba/unassigned-shares is named HGST_500GB_2.5".conf and contains: [HGST 500GB 2.5"] path = /mnt/disks/HGST 500GB 2.5" read only = No guest ok = Yes vfs objects = I don't see a reference to /etc/samba/unassigned-shares/HGST_500GB_2.5".conf in the .conf files in the /etc/samba directory The symptoms is that i can't see a share when browsing the server from a windows machine. I have not diagnosed it further.

Sorry for the delay. Yes, the quote was included. I expected that it would be caught if it was not allowed.

A few months ago I added a 2.5" 500GB drive with unassigned devices. When naming the mount point I was thinking that it would prevent me from using forbidden characters and HGST 500GB 2.5" was tried. I didn't think that it would be used directly without modification. The name was accepted, but would not mount and it can not be renamed. When clicking on it in the gui nothing happens. I have seen fixes which seem to prevent mistakes like this, but nothing has allowed me to rename the mount point. When removing the mount point and then formatting the drive the same mount point is used. Is there a way to solve this?