-
-
14TB Drive errors when passedthrough to a VM
I've fully passthrough a 14TB HDD to an ubuntu VM, I log in ubuntu and see in disks the 14TB hdd fine, but when I do any operations like creating a partition then formatting the drive parition in the VM I get errors and unable to continue with this drive. I look at unraid logs of this specific unassigned disk and it shows the below: so I've taken the disk out of the VM and ran a badblocks command on it "badblocks -wsv -b 4096 -p 1 /dev/sdh" and there's no errors. I even format and mount the drive in unassigned and can writing to the disk fine. I've also successfully passthrough 11 other HDDs of varying sizes, same brand "Seagate" to my ubuntu VM without issues. Any ideas what why this particular disk errors when passed through to a VM?
-
Unraid speed drop when copying data off multiple disks directly (no parity disk installed)
yeah I'll give this a try, though I'm running my HDDs from a netapp disk shelf connected to a HBA in the NAS. I booted up a unraid ubuntu VM with mdadm raid5 with some of my disks and it ran 180MB+ on all the disk in the raid array fine. Maybe its because I used btrfs on my unraid array disks with compression enabled could be the reason
-
Unraid speed drop when copying data off multiple disks directly (no parity disk installed)
running iperf I get over 3+ gigs a second, but yeah could be the controller though I'm running on modern motherboard and from a NetApp 24 bay
-
Unraid speed drop when copying data off multiple disks directly (no parity disk installed)
my unraid and both computers are on a intel X510 10G NICs though
-
Unraid speed drop when copying data off multiple disks directly (no parity disk installed)
I'm currently trying to move data off unraid array as fast as I can, so I've removed the parity disk which I thought was the bottleneck in the read speeds. in the array on disk1 I copy contents from it to computer 1 at 70MB/s, then on disk2 I copy contents at the same time to computer 2 then the now have both 35MB/s. I bypass fuse and access the disk directly when doing these transfers. Why did disk1 and disk2 transfer speed half in this case? Is there something hidden underneath in the unraid array where it doesn't like or work well with multiple disks being worked on at the same time?
-
Actions over SMB windows to unraid: you need permission to perform this action
sorry to reply so late, I finally tried this and had no luck, I was still getting the permission access denied issue randomly on a new VM with windows installed 🥲. I'm considering seriously moving over to something else, backing up files is taking forever as it reguarlly get error'd access denied then needing to try a couple of times. There must be some logs in unraid somewhere that tells you the reason why it denies access?
-
[PLUGIN] Disk Location
-
[PLUGIN] Disk Location
I'm on UNRAID 7.0.0 and latest version 2025.03.18 disk location. this is the config settings, and its also deleted all the Purchased and Warranty info on all the disks
-
[PLUGIN] Disk Location
I havent looked at my unraid for almost a month but noticed Disk locator now looks like this after doing the force update, did the latest update break it? The numbering is on 0 for some reason
-
Actions over SMB windows to unraid: you need permission to perform this action
I will give this a shot. But it would be ideal to use a whole another computer to isolate any old lingering settings on the host machine that will transfer over to the VM will have to passthrough.
-
Actions over SMB windows to unraid: you need permission to perform this action
starting to think maybe its my windows computer. But I don't have any other computer on hand to test the connection with unfortunately
-
Actions over SMB windows to unraid: you need permission to perform this action
I've also given this a try, took a while since it takes a while to start my array. No luck either on this side after putting this in my SMB extra configs then starting the array and giving it a test.
-
Actions over SMB windows to unraid: you need permission to perform this action
I'm not quite sure where the extra "+" permission came from, I've not modified the permission through the command line, just used it as any normal user would. I've given the new network path a try but no luck there either, I'm still getting permission errors even without going through the mapped path.
-
Actions over SMB windows to unraid: you need permission to perform this action
I tried creating a new folder and it errors as shown. But if I click try again it successfully creates the folder, this is random, you can see the new text document I created had no issues. but the folder did in this case. and here it is in the terminal: it happens with all files and all folders there is no pattern I see with their names copy/move/delete etc, it happens on random chance
-
Actions over SMB windows to unraid: you need permission to perform this action
Did a bit more testing and found it occurs even if I create a new user share and use that the error will occur randomly still on there.
Hellomynameisleo
Members
-
Joined
-
Last visited