truthfulie

About 90 TB of data on the array. Yeah, I've done that already. The parity has been upgraded to 12TB drive and parity sync was done. I didn't think I cared about parity because shares aren't protected while rebuild is happening, but as you mentioned, I would have the old disk in case something goes wrong while rebuild is happening. Looks like I'll just take the slow but safe route and go through the rebuild process. After passing 6TB, speed seems to have picked up a bit at around 120MBps. Thanks for the detailed response.

I'm upgrading about 12 disks to a larger ones with one parity in the system. Current disks are mostly 10TBs with one 3TB and one 6TB in the mix. Upgrading all to 12TB disks. There are two fresh new drives that was added to the array so there are fair bit of usable storage within the array. One has been replaced and going through the rebuild process right now. Been about twenty hours and still about twenty more to go. It was little faster at first but seems to have settled at about 90MBps on average. Using dockers like Plex or just reading files off the array in general (I'm not writing to the array) does make the rebuild process go much slower to the point where it's not feasible. So with 11 more to go, it'll take quite awhile to go through this process each time I replace a disk. Is there something else I could do to make the upgrade process go a little faster? I don't mind not being able to write to the array or having no parity protection for awhile if it means I can reduce the rebuild time significantly. Perhaps remove the parity from the system, move files to the new drives, replace, move back, rinse and repeat? Perhaps expand the array with the new disks, move files to it, remove old ones and shrink the array? Never done an upgrade of this scale (I've always just expanded the array but 15 is my current hardware limitation) so all this is kind of new to me. Thoughts?

Gotcha. I see the difference now. Thank you.

Good to know! And thanks for the confirmation! Just a bit unnerving doing something like this and want to double/triple check. 😅

Thank you for the quick response. I was referring to https://wiki.unraid.net/The_parity_swap_procedure, has things changed since the entry was last edited? So power down, physically replace the drive, assign the new drive as parity and start the array. The parity rebuild process runs in the background while the array is operational (assuming without parity protection until rebuild is done)?

Just doing some sanity check before replacing my old 10TB parity drive with something larger. disable docker and array auto start stop the array unassign old parity drive from parity slot start the array & stop the array power down, remove old parity drive & install new parity drive power on assign new drive to parity slot hit Copy and wait Is this about right? Also...is it possible to reduce the downtime (I expect it to be fairly long since parity is about 100TB) by adding parity2, and replacing the parity1? If so, what would by my steps?

What might cause the miner to not be able to connect to the pool? ErrorWarningSystemArrayLogin Starting T-rex miner... ============================================================ Server: us1.ethermine.org Algorithm: ethash Wallet: MYADDRESS Worker: unraid Pass: x ============================================================ 20211012 01:59:50 T-Rex NVIDIA GPU miner v0.24.2 - [Linux] 20211012 01:59:50 r.66f25c328d28 20211012 01:59:50 20211012 01:59:50 20211012 01:59:50 NVIDIA Driver v460.73.01 20211012 01:59:50 20211012 01:59:50 + GPU #0: [00:04.0] GeForce RTX 3070, 7979 MB 20211012 01:59:50 20211012 01:59:50 WARN: DevFee 1% (ethash) 20211012 01:59:50 20211012 01:59:50 URL : us1.ethermine.org 20211012 01:59:50 USER: 0x1154e73e6a147fd9642a2842518f09599c7a1649 20211012 01:59:50 PASS: x 20211012 01:59:50 WRK : unraid 20211012 01:59:50 20211012 01:59:50 Starting on: us1.ethermine.org 20211012 01:59:50 ERROR: No connection with us1.ethermine.org, retry after 10 seconds 20211012 01:59:50 WARN: API server is not bound to 127.0.0.1, consider setting up API key (see --api-key) 20211012 01:59:50 ApiServer: HTTP server started on 0.0.0.0:4067 I've added 0.0.0.0:4067 part to json file manually because it wasn't there after installation. I can access the webUI, can see my GPU, but miner cannot connect to the pool and cannot mine.

Tried your settings and I'm only getting 50 MH/s. I need to give it more power. Managed to get 60.3 MH/s with 120W (like I was originally getting on Windows) but it wouldn't hold. I am now back to 135W power limit and getting consistent hashrate of 60.4. Probably because mine is FE not AIB card. In any case, I am having the same issue as Rolucious. Updated the docker and the miner would not work. I was on older v460.67 driver (just because I was reading the older post on this thread when I first set it up) Updated to the latest driver to see if that was the cause, it wasn't. Set it to 460.73.01 like Rolucious said and it is up and running. No real benefit for me to be on the latest driver so I'll just use it but might be worth a look.

Just an update. Been playing around with the settings a bit over the weekend and I managed to get the 3070 FE to 60.45MH with lower power usage. Settings pl: 135 clock offset: -503 memory offset: 2300 fan: 70 130w can get to 60 but was struggling to keep it locked at 60. Would dip to 59 here and there. So I just gave it 5 more watts. More efficient than 150 I was using before.

Interesting. I have not checked the power usage with the same tool. I've checked with nvidia-smi with unraid and I've only tested nicehash's own miner's (when the card was plugged into a windows machine) reporting which was kind of nice. It gives wattage and efficiency rating based on wattage vs hashrate. Anyway now I mine ETH directly with a pool. 20w ain't nothing but it's also not big enough difference in power bill for me to worry about it too much. I'll fiddle with OC settings a bit more. PS. which specific 3070 model did you write those settings? I am running FE model.

Been able to get 60mh with 3070 just on 130watt through Windows. Any idea why the container needs extra 20w to get the same hashrate?

I cannot seem to get additional arguments to work for me. I want manually set fixed fan percentage, set power limit, memory OC and under-clock the core. The parameters does show up on the log when I run the docker. But GPU Stats is showing same full power draw and same stock fan curve behavior. Any idea what I might be doing wrong? EDIT: I did manage to get the power limit to work. But I'm still not getting fan control clock offset. I have checked to make sure docker is running on privilege mode. But fans still seems to be using the stock settings and my memory offset doesn't seem to work. -mclock value does not change hashrate. (I've test the card on Windows environment and got as far as 62MH but without memory OC, docker is stuck at 51MH). Not sure if core clock offset is working. I've also installed Stats docker and it seems like it cannot read GPU temp and fan speed.

I solved it by just setting network type to custom: br0. I don't have webUI in the dropdown but i can just use the url. The only thing is I won't be able to access it outside of my local network. Any ideas how to fix?

I'm having some trouble getting this up and running. Had some issue with default template values, the webUI would not load. Deleted the server port value, added a new one. container port 80 host port 8282 changed the webUI to http://[IP]:[PORT:8282] It loads fine now. But I cannot get the Home app to add the accessory through the QR and the number, I did not add any plugins just to make sure the bridge gets connected and working first. What am I doing wrong?

Is there a way to find out if my motherboard can do that or not? From just short boot test I did without GPU installed, it didn't seem to want to boot into unraid. Is that indication that this motherboard won't allow me to do that?

I know that most motherboards won't let you boot without a GPU and mine is seems to be that way since I wasn't able to get into unRAID webUI when I remove the GPU. But I thought this was more of motherboard restriction, not necessarily an unRaid restriction? I was under the impression that I am still able to passthrough the one and only GPU to VMs? Or is this incorrect? Also I forgot to mention in the post but I did test (though not extensively) the system and VM setup with a loaner GPU (I didn't want to buy one without knowing it is in fact the cause) and I was still having issue passing my RX580.

So I’ve been having some difficulty passing through my GPU to Windows VM. The system is X570 with Ryzen 3700X, no integrated GPU. RX580 is the only GPU in the system. The VM works perfectly fine with VNC and other remote desktop programs like Splashtop. But whenever I assign RX580 to the VM, it will not boot. I tried to passthrough the GPU as secondary with VNC still enabled and discovered it gets stuck in Windows logo screen with circling dots. While this is happening, one of the CPUs assigned to the VM gets to 100 percent usage and the log will shoot up and be filled. It goes back down after system reboot. I’ve also tried to pass it through to a macOS Catalina (while Windows VM is off, of course) but I’ve not had any luck with that either. I’m lost as to where my next step is. Anyone with similar issue who can point me in the right direction? Below is my XML and IOMMU groups