whipdancer

Docker gives your container a randomish name if you don't name it. If you get into them, you can get some idea what they are. You can try checking the docker logs.

Check if anyone has had issues with the MB chipset you're looking at. Same with CPU and Memory. I just repurposed my 10 year old Dell laptop (Latitude 7390, 8gig ram, i5-8350U cpu, busted screen) to be my Frigate NVR. I'm running 6 cameras (2x 1080, 4x 4K) with a Coral TPU and the Intel UHD620 iGPU. I mapped shares from my Unraid server to the laptop (using NFS) for storage needs. No issues, detections working great, notifications being sent. I had thought about buying something, but thought I'd give this a try. Glad I did, and doubly so, because the iGPU in my server can stay dedicated to Plex.

I use Unraid for my home and as a NAS. My homelab is separate. My homelab uses Unraid for NAS storage, but runs its own stack of containers. I expose a very limited slice of Unraid using tailscale now. I used vpn + reverse proxy previously. Frankly, if you're to the point where you want to use Unraid in a way that they expressly warn not to do ("don't open Unraid to the internet") and you're worried about vulnerabilities - then you need to use Compose with containers that meet your standards. You can start rolling your own containers so you can lock them down. Getting it right and keeping the app you're trying to deploy working correctly isn't always straight-forward or easy. I write some docker files on my own, that I keep in Github. I've never tried to automate maintenance in Unraid (other than the plugins that are available). I use scripts and chron jobs on my homelab server that help to manage containers running there. I use dependabot on my github repo where I keep all my docker files. If I can find something like Snyk to also scan my repo for free, I will add that. I'm looking at adding a Claude review bot to my repo, which would also provide CVE checking. Claude/ChatGPT/whatever can give you pretty solid guidance on how to write a docker file. If you don't use those tools often, then start with OpenAI Academy and one of their beginner tutorials. Learning the basics on how to use them is the difference between solid, basic guidance and hallucinations of unicorns doing it for you. Something you need to accept & remember - you can't control vulnerabilities in the App you use, regardless of what container you use. If something in the *arr stack or immich or whatever has a vulnerability because they use a library or package that is vulnerable - you either quit using that app or you upgrade once they've addressed it. The truth of using nuget/npm/pypi/gems (or any other public source of code) is that there is a chaotic mess of upstream entanglements for a lot of apps we use. You can't fix those issues. You can only choose how you respond to those issues.

What's your question?

I've only encountered this once. It was a cheap, no name SSD I bought on Alibaba. It was recognized by my server, but the information didn't match anything on the label. The information my server reported was correct.

Is there a specific issue you are trying to address?

You’re mistaken here. Commercial just offers you someone to will ignore you or miscommunicate for weeks on end and still get no actual help. Software companies like Unraid manage to split the difference, with actual help coming from both sides, but you still will have to handle the work yourself.

It is highly unlikely that using a molex to sata adapter killed anything. Something else is wrong. If you have another way to test each of the drives, that will tell you for certain if they are dead or not. I keep a usb dock connected to my regular pc that allows me to quickly determine if a drive is (most likely) dead or not.

How do you know your 3.3v mod is still good? Does the system you tested with use the same power supply as your new setup? Do you have a molex to sata power adapter you can test with in your new system?

I shop on price, so I have a mix of Seagate, Western Digital, HGST, Toshiba - but mostly Seagate.

As it turns out, both of the drives were on a single power splitter. Reworked the power cables a bit and running sync to rebuild everything. I'll update once complete.

I had 1 drive in the array suddenly show up as "device is disabled". I pulled diagnostics, rebooted, ran a short Smart-Test, no issues show up. Dropped it out of the array, then added it back and started a sync. Then I had a different drive in the array suddenly show up as "device is disabled". I canceled the sync, pulled diagnostics, and kicked off a long smart-test on both drives. I'm attaching both sets of diagnostics here. This is a new build that I just completed. New PS, cables, case, etc. The first drive was in use in my prior build. The 2nd drive is a warranty replacement that just came from WD. Both were precleared (x3) since neither had data to worry about on them prior to going into the array. I've looked at the logs but I don't think I know enough to be confident about what's going on. First_bluesmaster-diagnostics-20251020-0944.zip Second_bluesmaster-diagnostics-20251020-1052.zip

They sound like they are treating it as if they are building a regular desktop PC. That's the wrong approach. They should test the components by using a trial of Unraid, booting from a thumb drive as you would.