wibble

Hmm. After a load of tests on unraid (to various disks and shares) and locally I figured out that the speeds I get from there are either normal or extremely slow on different attempts - not even varying greatly during the download. Not a great mirror. I don't think it's any sort of rate limiting by IP because this post was prompted by two one-off downloads a week or more apart. virtio-win-0.1.240.iso 100%[==========================>] 598.45M 27.5MB/s in 27s 2023-12-19 22:06:21 (22.0 MB/s) - ‘virtio-win-0.1.240.iso’ saved [627519488/627519488] --------------------------------------------------------------------------------------------------------------------------------------------------- virtio-win-0.1.240.iso 0%[ ] 4.80M 60.8KB/s eta 2h 36m --------------------------------------------------------------------------------------------------------------------------------------------------- virtio-win-0.1.240.iso 0%[ ] 736.00K 68.9KB/s eta 2h 39m --------------------------------------------------------------------------------------------------------------------------------------------------- virtio-win-0.1.240.iso 100%[==========================>] 598.45M 27.0MB/s in 31s 2023-12-19 22:08:58 (19.2 MB/s) - ‘virtio-win-0.1.240.iso.1’ saved [627519488/627519488] --------------------------------------------------------------------------------------------------------------------------------------------------- virtio-win-0.1.240.iso 100%[==========================>] 598.45M 26.4MB/s in 32s 2023-12-19 22:10:35 (18.4 MB/s) - ‘virtio-win-0.1.240.iso’ saved [627519488/627519488] --------------------------------------------------------------------------------------------------------------------------------------------------- virtio-win-0.1.240.iso 0%[ ] 5.58M 49.5KB/s eta 2h 18m --------------------------------------------------------------------------------------------------------------------------------------------------- virtio-win-0.1.240.iso 5%[> ] 34.75M 78.1KB/s eta 2h 36m The ones I cancelled there were done early but I've found them consistently slow during this testing, matching the times I triggered it from the webui that prompted this post. wget showed the same IP address each time.

Did anyone manage to resolve "MOVE" and "MOVE NOW" buttons in the webUI not running mover with the plugin installed?

The missing image was an "avatar" in the plugin config file. Signed out of Connect and back in and now the avatar line in the config is empty and things look fine.

Attached screenshot, the link in the post 404ing is the issue.

See attached screenshot. The image that isn't loading is https://forums.unraid.net/uploads/monthly_2021_03/Untitled-1.png.99e811e706c3d539040b9b9963f4a6ca.png (404) Today's update did not fix it and I've cleared out browser cache and cookies.

^ Good information about disk shares being far faster. I tried this myself and a disk share directory of 1,500~ directories took a second or two to display rather than 30s+ for a user share. So is FUSE the problem and is this fixable?

I tried those, no effect.

Thank you! I've been having a *nightmare* with a new machine (Mini M2 Pro, Ventura) and these settings have given me the 'best' results so far of 24s~ to open a directory of 1,100 files/folders down from 1 minute+ (stock "Enhanced macOS interoperability"). I know that's still very slow but I only have a few directories like that so it's bearable. Another machine (MBP 2016, Mojave) manages the same in 12s~ and that's over wifi rather than ethernet. For reference not having anything in /etc/nsmb.conf (including the classic signing_required=no) made both a few seconds faster. "ls" in Terminal gives a result in <2s (4s~ for "ls- la") which makes Finder's sloth so frustrating - fyi unchecking "Show icon preview" as a default didn't help. This really does need more investigation. NFS was quicker (can't be bothered to go back and time it), but for every item Finder displayed "Date created." of "1 Jan 2001" and I'd like both created and modified times ideally. Anyone know a way to do this? I found this article but I don't know about Unraid/macOS supporting it.

"SSD TRIM allows the creation of a cronjob to do regular SSD TRIM operations on the cache device(s). The command 'fstrim -v /mnt/cache' is executed at the given interval." Does it do all cache drives/pools or only /mnt/cache? Thank you

IOMMU group 3: [8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub [8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) It sounds really important yet I did "BIND SELECTED TO VFIO AT BOOT" and rebooted expecting failure but Unraid seems fine. I've yet to setup a VM to pass it through to, if it's vital would I only experience problems once it's actually passed through or does binding to VFIO alone make it unavailable to the host? It's hard to Google up anything besides lists of devices but there was this success story. I have a separate PCIe USB controller I could passthrough instead (used for the Unraid USB presently) but it's only bus-powered and the ports are less conveniently located. The motherboard's Intel controller would save me needing a different card / powered hub / longer cables.

Yes, I had all ready done the chkdsk /f and reboot into Windows twice * 2. Same issue with two other disks on another controller also. Just the 1 simple basic volume per disk, nothing else going on. No kind of RAID or anything. Can block size be a problem? They're all 64K. But I'd have thought there would be some relevant search results somewhere if it was an issue.

I have a couple of NTFS disks that don't seem to be recognized properly and can't be mounted. Simple basic volumes with a single partition, look and function normally in W10, chkdsk /f is clean. There is this: fdisk -l | grep NTFS Partition 1 does not start on physical sector boundary. Partition 1 does not start on physical sector boundary. Relevant files attached. Any ideas? log.txt u-diagnostics-20210402-1647.zip fdisk.txt

That worked just fine, thank you.

I've copied the contents of 2 NTFS disks to my array (2 disks, no parity - will add later), and now I want to add these NTFS disks to the array but I could use a little affirmation. I understand I don't need to preclear since there's no parity and think the steps are: enable "destructive mode" in the unassigned devices plugin, delete partitions, now I should have the format option, format to btrfs to match the disks in the array, assign to array, start array, enjoy. Is this correct? Or can I just assign them, start the array, they'll appear as unmountable disks and I'll have the option to format them under "Array Operation"?