eagle470

Here are the docker logs pertaining to the issue everyone is now having: {"log":"Starting T-rex miner...\n","stream":"stdout","time":"2022-05-24T22:10:01.954287645Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:01.954332541Z"} {"log":"Server: stratum+ssl://eth-us-east.flexpool.io:5555\n","stream":"stdout","time":"2022-05-24T22:10:01.954347379Z"} {"log":"Algorithm: ethash\n","stream":"stdout","time":"2022-05-24T22:10:01.954353981Z"} {"log":"Wallet: 0x744CfD337cbe2175f3dC0F369A9B40CddFb04D25\n","stream":"stdout","time":"2022-05-24T22:10:01.954359642Z"} {"log":"Worker: unraid1\n","stream":"stdout","time":"2022-05-24T22:10:01.954365243Z"} {"log":"Pass: x\n","stream":"stdout","time":"2022-05-24T22:10:01.954370693Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:01.954376154Z"} {"log":"20220524 22:10:02 ERROR: Can't start T-Rex, can't initialize CUDA engine, cuda exception: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE. Is NVIDIA driver installed?\n","stream":"stdout","time":"2022-05-24T22:10:02.178396068Z"} {"log":"Generated api-key: bwAAAAAAAAAMVvqFtuzhr1G9X7rHZhWjh7W/c9Zs6o7KvMgk5Zwimj+t4+Ox8c/CpFhwS8CJ0apqkcUckLdN25Hx8Z0HNzBuKV9QrCP72Uo=\n","stream":"stdout","time":"2022-05-24T22:10:02.19009478Z"} {"log":"Saved into config file: /config/config.json\n","stream":"stdout","time":"2022-05-24T22:10:02.190113195Z"} {"log":"20220524 22:10:03 T-Rex finished.\n","stream":"stdout","time":"2022-05-24T22:10:03.156518532Z"} {"log":"Starting T-rex miner...\n","stream":"stdout","time":"2022-05-24T22:10:07.256706542Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:07.256727412Z"} {"log":"Server: stratum+ssl://eth-us-east.flexpool.io:5555\n","stream":"stdout","time":"2022-05-24T22:10:07.256733514Z"} {"log":"Algorithm: ethash\n","stream":"stdout","time":"2022-05-24T22:10:07.256738874Z"} {"log":"Wallet: 0x744CfD337cbe2175f3dC0F369A9B40CddFb04D25\n","stream":"stdout","time":"2022-05-24T22:10:07.256743883Z"} {"log":"Worker: unraid1\n","stream":"stdout","time":"2022-05-24T22:10:07.256748833Z"} {"log":"Pass: x\n","stream":"stdout","time":"2022-05-24T22:10:07.256755125Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:07.256761998Z"} {"log":"20220524 22:10:07 ERROR: Can't start T-Rex, can't initialize CUDA engine, cuda exception: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE. Is NVIDIA driver installed?\n","stream":"stdout","time":"2022-05-24T22:10:07.455440372Z"} {"log":"Generated api-key: bwAAAAAAAACLTQnFHU/sgwiRlGE0BCNlpwjz8Oj2u2MAiDsLax5DXM/5fUs4D/0SQQhOMtJnjiiq6/h9jIsaaqPoWdPSfLDykzgdLB0zLRM=\n","stream":"stdout","time":"2022-05-24T22:10:07.471937166Z"} {"log":"Saved into config file: /config/config.json\n","stream":"stdout","time":"2022-05-24T22:10:07.471962635Z"} {"log":"20220524 22:10:08 T-Rex finished.\n","stream":"stdout","time":"2022-05-24T22:10:08.439527512Z"}

@ich777 I corrected the API_KEY error and got more out of the logs: {"log":"Starting T-rex miner...\n","stream":"stdout","time":"2022-05-24T22:10:01.954287645Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:01.954332541Z"} {"log":"Server: stratum+ssl://eth-us-east.flexpool.io:5555\n","stream":"stdout","time":"2022-05-24T22:10:01.954347379Z"} {"log":"Algorithm: ethash\n","stream":"stdout","time":"2022-05-24T22:10:01.954353981Z"} {"log":"Wallet: 0x744CfD337cbe2175f3dC0F369A9B40CddFb04D25\n","stream":"stdout","time":"2022-05-24T22:10:01.954359642Z"} {"log":"Worker: unraid1\n","stream":"stdout","time":"2022-05-24T22:10:01.954365243Z"} {"log":"Pass: x\n","stream":"stdout","time":"2022-05-24T22:10:01.954370693Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:01.954376154Z"} {"log":"20220524 22:10:02 ERROR: Can't start T-Rex, can't initialize CUDA engine, cuda exception: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE. Is NVIDIA driver installed?\n","stream":"stdout","time":"2022-05-24T22:10:02.178396068Z"} {"log":"Generated api-key: bwAAAAAAAAAMVvqFtuzhr1G9X7rHZhWjh7W/c9Zs6o7KvMgk5Zwimj+t4+Ox8c/CpFhwS8CJ0apqkcUckLdN25Hx8Z0HNzBuKV9QrCP72Uo=\n","stream":"stdout","time":"2022-05-24T22:10:02.19009478Z"} {"log":"Saved into config file: /config/config.json\n","stream":"stdout","time":"2022-05-24T22:10:02.190113195Z"} {"log":"20220524 22:10:03 T-Rex finished.\n","stream":"stdout","time":"2022-05-24T22:10:03.156518532Z"} {"log":"Starting T-rex miner...\n","stream":"stdout","time":"2022-05-24T22:10:07.256706542Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:07.256727412Z"} {"log":"Server: stratum+ssl://eth-us-east.flexpool.io:5555\n","stream":"stdout","time":"2022-05-24T22:10:07.256733514Z"} {"log":"Algorithm: ethash\n","stream":"stdout","time":"2022-05-24T22:10:07.256738874Z"} {"log":"Wallet: 0x744CfD337cbe2175f3dC0F369A9B40CddFb04D25\n","stream":"stdout","time":"2022-05-24T22:10:07.256743883Z"} {"log":"Worker: unraid1\n","stream":"stdout","time":"2022-05-24T22:10:07.256748833Z"} {"log":"Pass: x\n","stream":"stdout","time":"2022-05-24T22:10:07.256755125Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T22:10:07.256761998Z"} {"log":"20220524 22:10:07 ERROR: Can't start T-Rex, can't initialize CUDA engine, cuda exception: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE. Is NVIDIA driver installed?\n","stream":"stdout","time":"2022-05-24T22:10:07.455440372Z"} {"log":"Generated api-key: bwAAAAAAAACLTQnFHU/sgwiRlGE0BCNlpwjz8Oj2u2MAiDsLax5DXM/5fUs4D/0SQQhOMtJnjiiq6/h9jIsaaqPoWdPSfLDykzgdLB0zLRM=\n","stream":"stdout","time":"2022-05-24T22:10:07.471937166Z"} {"log":"Saved into config file: /config/config.json\n","stream":"stdout","time":"2022-05-24T22:10:07.471962635Z"} {"log":"20220524 22:10:08 T-Rex finished.\n","stream":"stdout","time":"2022-05-24T22:10:08.439527512Z"}

here you are: Sorry for the delay, I've had issues with chrome new quic UDP function, figured out I had to turn it off.

Looks like it is the cuda driver {"log":"Starting T-rex miner...\n","stream":"stdout","time":"2022-05-24T14:51:10.171567297Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T14:51:10.171609317Z"} {"log":"Server: stratum+ssl://eth-us-east.flexpool.io:5555\n","stream":"stdout","time":"2022-05-24T14:51:10.171620428Z"} {"log":"Algorithm: ethash\n","stream":"stdout","time":"2022-05-24T14:51:10.17162656Z"} {"log":"Wallet: 0x744CfD337cbe2175f3dC0F369A9B40CddFb04D25\n","stream":"stdout","time":"2022-05-24T14:51:10.171632311Z"} {"log":"Worker: unraid1\n","stream":"stdout","time":"2022-05-24T14:51:10.171637931Z"} {"log":"Pass: x\n","stream":"stdout","time":"2022-05-24T14:51:10.171643422Z"} {"log":"============================================================\n","stream":"stdout","time":"2022-05-24T14:51:10.171650655Z"} {"log":"20220524 14:51:10 ERROR: Can't generate api-key, password must contain at least one uppercase letter\n","stream":"stdout","time":"2022-05-24T14:51:10.39060052Z"} {"log":"20220524 14:51:10 ERROR: Can't start T-Rex, can't initialize CUDA engine, cuda exception: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE. Is NVIDIA driver installed?\n","stream":"stdout","time":"2022-05-24T14:51:10.413411961Z"} {"log":"20220524 14:51:11 T-Rex finished.\n","stream":"stdout","time":"2022-05-24T14:51:11.39009576Z"} @ich777

I'm running t-rex, plex and unmanic. All three share the same 3060 LHR, with plex having the priority IMO. Plex starts and runs, but I can't see it using the GPU even when HW transcoding. T-Rex will NOT stay running. May 23 08:08:17 Unraid1 kernel: docker0: port 4(veth4c78202) entered blocking state May 23 08:08:17 Unraid1 kernel: docker0: port 4(veth4c78202) entered disabled state May 23 08:08:17 Unraid1 kernel: device veth4c78202 entered promiscuous mode May 23 08:08:17 Unraid1 kernel: eth0: renamed from veth136d6db May 23 08:08:17 Unraid1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4c78202: link becomes ready May 23 08:08:17 Unraid1 kernel: docker0: port 4(veth4c78202) entered blocking state May 23 08:08:17 Unraid1 kernel: docker0: port 4(veth4c78202) entered forwarding state May 23 08:08:19 Unraid1 avahi-daemon[8346]: Joining mDNS multicast group on interface veth4c78202.IPv6 with address fe80::d480:b2ff:fef4:76bb. May 23 08:08:19 Unraid1 avahi-daemon[8346]: New relevant interface veth4c78202.IPv6 for mDNS. May 23 08:08:19 Unraid1 avahi-daemon[8346]: Registering new address record for fe80::d480:b2ff:fef4:76bb on veth4c78202.*. May 23 08:08:19 Unraid1 kernel: docker0: port 4(veth4c78202) entered disabled state May 23 08:08:19 Unraid1 kernel: veth136d6db: renamed from eth0 May 23 08:08:19 Unraid1 avahi-daemon[8346]: Interface veth4c78202.IPv6 no longer relevant for mDNS. May 23 08:08:19 Unraid1 avahi-daemon[8346]: Leaving mDNS multicast group on interface veth4c78202.IPv6 with address fe80::d480:b2ff:fef4:76bb. May 23 08:08:19 Unraid1 kernel: docker0: port 4(veth4c78202) entered disabled state May 23 08:08:19 Unraid1 kernel: device veth4c78202 left promiscuous mode May 23 08:08:19 Unraid1 kernel: docker0: port 4(veth4c78202) entered disabled state May 23 08:08:19 Unraid1 avahi-daemon[8346]: Withdrawing address record for fe80::d480:b2ff:fef4:76bb on veth4c78202. Unmanic does nothing any more, but I have yet to delete the database and let it rebuild. @Squid @Josh.5 @PTRFRLL @lnxd In place of t-rex miner, I've tried Phoenix miner and it does not stay running once started either. I've seen other people with similar issues with the same card, if it's the card, fine. But it came up with my jump from 6.10-rc7 to 6.10-rc8 unraid1-diagnostics-20220523-0923.zip

I'm having the same issue. externally, it looks like there is a process that has the GPU locked up.

I patched to rc6, last night while drunk. So no logs. Question though, is there a way to convert the meta data to single drive mode and remove the mirror?

The issue is the frequency of updates. After 30 minutes I already had 8+ million writes due to a balance kicking off immediately. There is ZERO way that a parity drive could keep up with that, unless it was an SSD and I'm not that well off. So either the parity drive would slow the system to a near halt OR the system would start to drop parity writes as the queue grew past the buffer. I'm betting on the latter.

Also, it's good to know that even though I left the admin world, I can still find new and interesting ways to break things!

That was my initial urge to do, but I'm holding off on the off chance someone has advice on this. I was thinking about this and I'm pretty sure the only reason this worked is because I DON'T have a parity drive. I'm pretty sure things would have stopped if I had a parity drive, because the parity drive would not be able to keep up the the changes. I also think it would have corrupted parity, but that is a guess and nothing more.

This is my chia server, I had the last four drives in a disk pool on another server. I yanked them out and stuffed them into my cable spaghetti server. Obviously, I didn't think through the single drive mode and didn't change the metadata parity settings. Obviously it's just chia plots, but I'd rather not blow them away as it costs money to replot.

I have a group of three disks in a cache pool that I want to write to regularly, but I would like to front that with a write cache. It would be nice to make cache pools configurable so that you can call out a Final Storage and a Caching location.

The google all white UI is dead, few like to use it. it would be nice if the default ui was dark OR if it asked you BEFORE your blinded with an all white screen

Or make pause persist through shutdown (if it doesn’t)

I have this up and running, but the UI isn't giving anything and I can't tell whats going on.

There are a number of pass that facilitate privacy already in the app pool, but it would be nice to be able to see the things that are recently published that I'm unaware of. Current apps I can think of: pihole adguard VPN tools Privoxy These are tools to hide who I am from the world. I'd like to see more of that.

Here are the logs unraid1-diagnostics-20220213-2115.zip

Disk 3 (sdk) just failed out for the second time in two weeks. Last time I replaced the SATA cable and it came up with no issues. Please advise.

Can't read the mandarin, what does this pull seeds for?

see title unraid1-diagnostics-20220204-0921.zip

try adding this line to your go file: modprobe k10temp force_id=0xd120 may require a reboot

@Squid fair enough

@squid I can install a VM, I was concerned after macinabox said that it couldn't find the virtualization engine to connect to.