Azreal

for anyone else that finds this - firmware update took ~1 minute on my old very dated win 10 pc - maybe not even that long. it didn't make me reformat or anything. threw me off at first because it wasn't appearing in my computer next to the boot drive but them remembered it's not formatted in windows compatible format. when i looked at the utility from crucial it saw it just fine. automatically identified the firmware is out of date and prompted to update it. one thing i probably could have avoided was starting the array after i removed the drive from the cache pool. lessons learned, pretty sure that was unnecessary but i was thinking it would need to rebuild anyways.... biggest headache was just pulling drives and bouncing between machines. everything else appears to have performed as expected.

thank you for the link. looks like the scrub fixed it this time, it did not earlier. not sure i understand why, reboot helped there? firmware update looks like it will be fun. i have a windows pc i can put this in to do the udpates but man what a hassle. not seeing any way to do this with it hooked into the unraid machine but please let me know if that's wrong and there is a way. i'm probably mediocre in my linux skills and understandings at best so leveraging windows utilities probably is the path of least resistance here. thanks again for the assistance today.

Thank you for jumping in quickly. See updated diagnostic. Also worth mentioning - one of my array drives shows as missing. I don't think this is related but maybe it is. It was fine until i turned the array off prior to making the earlier post, then it said it wasn't detected and contents emulated. I have had some issues iwth this happening time to time and changing / reseating cables had helped stop that until today. Maybe relevant to the SSD issue maybe not. I had been planning on pulling that drive and replacing with a larger one but just hadn't gotten to it, the drive is empty anyways. rlyeh-diagnostics-20230427-0905.zip

Noticed logs filling up this morning so started to investigate and looks like i'm getting errors on one of my cache ssd's for at least the last couple of days. I have pool of 2*1TB Sata SSD's, the one erroring is a bit older but only couple years i believe. I did flush edit:scrub the drive and continued to get errors it said were uncorrectable. is this a bad/dead drive? what can i do / check next to verify or try to repair this? any other suggestions for next steps? My other drive in the pool is ~6 months old so i'm not too worried on using that by itself while i wait for a replacement if i have to. diagnostics attached rlyeh-diagnostics-20230427-0737.zip

don't take my word for it but i believe it's because there's no host to container port mappings. it gets an IP (or uses the host) and it uses what it uses and you don't map the ports between them, believe even the readme for the container says you don't change ports. i found a comment somewhere along these lines recently. and compared to the other containers i do have with mappings this seems to be the case. as for the other problem. i had that as well but i cannot remember what i did to fix it. double / triple check all your parameters, paths, permissions, etc... if it comes back to me i'll reply

Does PlexAmp work with this container? I have the container up and running but i'm unable to connect plexamp to it on local network and remotely. having issue both on my android phone and on my windows pc (not unraid pc or vm, physical pc). Plexamp just doesn't show this server as an option. When i had plex on my physical machine (another device on same network) it was working fine, local and remote, server appears etc... I can access plex remotely, ports are forwarded, it even shows it under authorized devices but maybe that's more account auth related than the device actually hitting the server(?), server settings shows it's reachable and i can hit my music library from the plex app on mobile and from desktop, plexamp just being moody. any help or suggestions are appreciated. edit: network setup is using it's own assigned ip address, not host - there are no IP or port conflicts and secure connections is at preferred, not required Edit2: Resolved - same issue on my desktop, logged out / in manually and still didn't work - logged out and back in but this time using the "login with browser" and it connected... it was the same email / user account both times, not sure what or why this mattered but interesting to see. I noticed in the debug logs that it was calling for connection to devices at IP's that don't exist anymore either (recent redo of entire network, subnets, addresses used for those subnets etc...) maybe it needed some things to refresh?

system is crashing and showing MCE errors logged on restart. I can't find a consistent pattern to the crashes or other activities going on when it does. tends to mostly happen overnight - the last couple of times were ~3-330AM timeframe. Any assistance or suggestions would be appreciated. Diagnostics attached. Some background on the hardware: this is my "old" pc with some new storage added after i built a new machine earlier in the year. I never had issues with it when running windows throughout its numerous upgrades over the years (more ram, hdd-> ssd, numerous video card upgrades). When i set this up for unraid i reapplied thermal paste since it had been 5-6 years since i last did it and it seemed to be running hotter than it did previously (when i was running windows on it still). I didn't realize there was an issue with the mounting bracket that was keeping the baseplate from fully hitting the cpu and of course my thermals were worse afterwards. I had a couple instances where it hit 100F when i was tryign to setup a VM and it would recover if i quickly shut it down. Finally opened it back up and discovered the issue with the mount of the cooler and fixed it. now average idle temps are 28-35 more or less and when i'm really hammering the system it tops out in the 60s. Cooler is a Corsair 240 AIO set to max pump and fan speeds full time. Did i potentially fry somethign during the instances where it hit the 100F? any other utilities or tools i could leverage to test this? CPU: i7-4770k - overclocked to 4.4Ghz with small voltage bump - this overclock has been in place and stable 6-7 years - pretty standard practice and capability for this processor generation RAM: 8GB DDR3 - i don't recall the speed - it's on the XMP profile - again it's been stable for years on windows and it's in line with the hardware it's on - probably just ddr3-1600 I'm currently running a handful of containers that all run fine. the reboots are killing me though since i'm running DNS and pi-hole containers that knock the internet offline until i can login to start the array and docker again. nevermind the ~30 hour parity check :-(. any suggestions are appreciated. rlyeh-diagnostics-20230112-0700.zip