s1l3nce

I suppose this card already has the right firmware to work with Unraid, right? https://es.aliexpress.com/item/1005008153594284.html I wouldn't mind having to flash it but it is not for me but for a client which does not want to bother with this stuff.

St Strangely enough, after rebooting the system I can format all of them.

Sorry for resurrecting this post but I'm on version 7.2.0 and I can't format drives that have been precleared, even though I have destructive mode enabled And the reason why I want to format is because if I simply create a new config, select the drives and format them, they always get formatted in XFS, even tough I also have this option enabled Am I doing something wrong or this is completely bugged? PS: Btw, what's the reason for precleared disks so complicated to format them? What's so special about a precleared disk?

Well, not so fast. I managed to get rid of the error I described above but now I just can't make it work. As soon as I start installing drivers for the GPU, the VM freezes. I've tried with an AMD R9 270 too but it didn't work either.

ChatGPT just gave me the answer to my issue: set PCIe ACS Override to either Both or Downstream (under VM Manager, advanced settings) (I selected downstream). That fixed it 👌

Hello everyone! I've recently saw a video about the upcoming features on version 7 and I'm doing some testing with the beta. I'm testing passing through a GPU to my Windows 11 VM and I'm getting the following error: Execution error internal error: QEMU unexpectedly closed the monitor (vm='VM-WIT'): 2024-10-29T22:44:30.060155Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:01:00.0","id":"hostdev0","bus":"pci.7","multifunction":true,"addr":"0x0"}: vfio 0000:01:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. This are my GPU settings on my VM And this is what I have in Sytem Devices section: My motherboard is old (Asrock Z87 Extreme4) but it has Intel Virtualization Technology and VT-d and they are both enabled. What am I missing?

Considering that the SanDisk MobileMate is a highly recommended product in this and other threads, I'm sure some people will appreciate the fact that I'm sharing this awful experience. I highly doubt I was unlucky; it's probably a manufacturing issue that has affected loads of units, judging from what I've seen in different online shops. On a different note, the SanDisk QuickFlow does not seem to have a unique GUID. This is what the SanDisk support responded to my question:

What should I look for to find out if these card readers have a unique GUID? https://www.kingston.com/en/memory-card-readers/mobilelite-plus-microsd-reader https://www.kingston.com/en/memory-card-readers/mobilelite-duo-3c

I've just tried it. This fixed my issue! Thanks 🙏

Thanks for pointing that out!🙏 I did not see it. I will check it out and report back 👍

This is just unbelievable. I just got the SanDisk QuickFlow and it came like this: And, as you might suspect, it does not work with any of my microSD cards. I'm either the unluckiest person on the planet or these devices are shit.

Does the SanDisk QuickFlow have a unique ID? It's a bit more modern than the shitty MobileMate. Here is a comparisson: https://shop.sandisk.com/tools/product-compare?ids=SDDR-B531-AN6NN:mobilemate-uhs-i-usb-3-0-microsd-reader-writer,SDDR-B731-GN6NN:sandisk-quickflow-microsd-usb-a-memory-card-reader I might give it a try. I hope they've improved the contact mechanism.

I just got the SanDisk MobileMate and it came like this; with bent pins: So the microSD cards sometimes works and sometimes doesn't, depending on weather the contact want's to work or not. Judging by the comments on the Amazon product page, it seems that it is not an uncommon issue, so I'm definitely not getting this usb adapter again. Any recommendations of a good card reader with unique GUID? I really do not understand why SanDisk would make such a weak contact mechanism. PS: I've been reading this thread and I can't believe people are still buying and recommending this shitty adapter. Read the bad comments on Amazon, for god sake. This card reader could damage your cards and even your PC if you are very unlucky. Terrible recommendation guys.

Deleting torrents from a Qbittorrent docker (this one) creates the infamous .Trash-99 folder, containing 2 folders: Files: this folder contains the deleted torrents. Info: this folder contains the same files but with *.trashinfo extension added at the end, although these files are very small (couple of hundred bytes). These folders can't be access through samba because of lack of permissions but you can access them through Unraid web UI, using Dynamix File Manager. Isn't there a way to prevent these folders from being created or being deleted automatically? Thanks.

Awesome! Thank you so much for your incredible help and interest 🙏😄 Try the latest UD update. It worked for me so it will probably fix it for you too 👌

Excellent @dlandon! It works But after updating, when I rebooted the system, I got this command in console right before it posts the Unraid Version: modprobe: FATAL: Module ntfs3 not found in directory /lib/modules/6.1.74-Unraid I'm on version 6.12.8, in case that helps.

It wasn't automounting but I added this delay to the script and now it's working perfectly. #!/bin/bash sleep 5 # Delay execution for 5 seconds bash -c '(echo >/dev/tcp/ZENO.LOCAL/445) &>/dev/null'

Correction: the command bash -c '(echo >/dev/tcp/ZENO.LOCAL/445) &>/dev/null' is not mounting the share but simply making it available; it goes green and the mount button is no longer grayed out. I've tried adding that command to a custom script that runs at Startup of array but it doesn't work, unless I run it manually, which makes me think that maybe if I could delay the script for a few seconds, that might fix the first issue, which is making the shares available. The second issue would be to make the shares automount.

This one returns a 0 after 4-5 seconds but I have observed that a few seconds later, the share gets mounted 👌 This one returns a 1 instantly This one returns a 0 instantly. ZENO: Unknown server error ZENO.local (192.168.82.20) at {ZENO's Mac address} [ether] on br0 The fact that the first command mounts the share is really interesting.

During the boot process, after the samba initialization (Starting Samba:) I have 3 messages that I do not understand: Starting mcelog daemon: /usr/sbin/mcelog --daemon chmod: cannot access '/dev/dri': No such file or directory logger: send message failed: Bad file descriptor The system seems to be working just fine but I would like to know what are those extra messages in the console (that slow down the boot process a few seconds). I'm using Proxmox v8.2, I'm not passing through any GPU or iGPU and these are my VM settings: Btw, regarding the instructions on how to boot from the Unraid pendrive, I'm just passing through the USB Vendor/Device ID and in the boot options I select the USB and it works like a charm. I'm using Proxmox 8.2 though. Maybe the usb boot is something that wasn't available before. edit: If I passthrough my Intel HD 4600 iGPU to the Unraid VM, the chmod: cannot access '/dev/dri': No such file or directory message goes away but the other two messages are still present. edit 2: I fixed those messages. The chmod: cannot access '/dev/dri': No such file or directory went away by simply deleting the Intel-GVT-g plugin, which I didn't even remember having (I haven't used Unraid in a while). The message logger: send message failed: Bad file descriptor I think went away when I disabled "Mirror syslog to flash", but I'm not sure. The remaining one, Starting mcelog daemon: /usr/sbin/mcelog --daemon, I still don't know what's about but I guess it's related to some plugin also.

BTW, I don't know if this is relevant or not but I'm using Unraid inside Proxmox.

Here it is. ud_diagnostics-20241001-215048.zip

I've tried that but it did not do anything. Only removing it and adding it again works. Is there a log somewhere that might be showing some problems that I can share? I do not recall having this issue a while back (I'm still not using Unraid on a daily basis; I'm just experimenting with it to get comfortable when I move from my old Synology NAS). -------- Edit: I've just rebooted the UNRAID server and I found this in the system log: Oct 1 21:23:09 UNRAID unassigned.devices: Mounting Remote Share '//NameOfMyNAS/data'... Oct 1 21:23:10 UNRAID unassigned.devices: Remote Server 'NameOfMyNAS.LOCAL' is offline and remote share 'data' cannot be mounted. So apparently it's not able to find the share but it does find it when I re-add it. I don't get it. Btw, I have downloaded the ud_diagnostics zip and the only relevant thing that I could find are those lines from the syslog.

I'm having an issue with SMB shares. Every time I boot, my SMB share is not mounted and the button to mount is grayed out, as shown in this picture: If I delete the share and add it back, it works without any issues. But as soon as I reboot, I have to do it all over again. Is this a known issue? Or is an issue on my side?

Btw, I'm also getting the logger: send message failed: Bad file descriptor error on boot but the system boots just fine (at least that I know of). What does that error imply? PS: I'm using Unraid inside Proxmox.