jammsen

Arent thoose true for Btrfs Raid in a Pool?

For me it was like the first 2-3 hours'ish. But the would fit your scenario, just another timeframe. Could you put that "initial delay information" please in the "Information-Text" off the app? That would reduce false positives.

Eh ... im glad and sorry at the same time, to report the error is gone? 😕 Now it says "Current server • Connected to Mothership" just 1 night went by. Sorry for the trouble i guess? 🤐 I could still generate a report, but im not sure that helps you to nail down the problem. Please let me know.

Still got this problem. This is what i did today: Updated 6.10.1 to 6.10.3, after that installed the "my servers" app from CA and logged in. Directly it said at my servername "Current server • Not Connected to Mothership" even relogging did not stop this

Im on 6.10.4 and its bugs around

Could please provide a 6.10 version? I get only javascript errors in the console:

Im developing Docker images and hosting containers on my unraid systems. I would love to see that in the "Docker" page next to the title "Docker Containers" a tab or switch feature to separate "containers" from "images" because sometimes you loose overview. I already asked in Discord and @OmgImAlexis recommended to try open a feature request for this. Here is some visual content to make more clear what i would love to see: I added on my clean unraid servers some nginx images to make more clear what i mean when the system with docker is used for development. Cool would be a feature like Bootstrap's "Tabs" to split "Containers" from "Images" and maybe make the title more clear on top: Hope i explained it well, please let me know if there are any questions.

Yeah @Meannekes i totally agree and get your point, i should have gone with my 2 other highspeed "SPCC_M.2_PCIe_SSD" Silicon Power SSDs. I have 2 Unraid systems and the one with 2 of thoose disks in it, isnt mission critical, its more like hold some Docker Settings for plex or so and while its set to cache only, the settings are not that important. It runs raid1 anyway and its been barley used as a file cache. So failure rate should be low to extremly low. Next time the better ones

Hey @JorgeB, oh ..... i even know the old thread, so the message isnt whats important, the SMART number 197 is the key here? Good to know, but afaik they should have fixed it in smartmontools according to this: https://www.smartmontools.org/changeset/5061 Just looked into my hostname/Main/Device?name=cache link for the cache drives and disabled 197 which is onr row below 188 which is also disbaled, maybe i missclicked or so and disabled 188 by accidient? Or is 188 disabled by default?

I needed to update my plex docker instance on my NAS Unraid system. So i loggedin into the system via the web gui and i was presented with a lot of thoose messages about this error, going into yellow and green again, see screenshot please. After some searching via google with quotes and without i didnt really found an exact post about what this could mean, the closest i got to find something was this medium.com post ( https://satyeshukumar.medium.com/how-to-fix-current-pending-sector-count-warning-d9232220366e ) which bascially states Is this for my message also true? Did anyone already have this message/error and help me to understand whats needed for my system? About the SSDs: Thoose "Crucial MX500 250GB CT250MX500SSD1(Z)" are bought from 12/2020 so they are fresh ones, and i did invest a bit more money for them as a Raid1 Cache then go with the lower BX series. Please help :X

Is this warning from an old harddisk era or is there a reason why its used on ssds? If i turn that off, can it come to disk errors and me loosing data unknowingly?

Hey guys, i just bought 2 of these "Crucial MX500 250GB CT250MX500SSD1(Z)" for a raid1 cache, because they are in-expensive in Germany (~35 Euro a piece) and have at least a bit of a DRAM Cache, sadly within 2 days i got the first error ... do any of you have any recommendation for an alternative while i still can return both of them? (My scenario, at least raid1 of 2 identical ssds, about 250GB in size, should have DRAM Cache; Usage: a bit of copy-cache, a few dockers 5-15 and maybe a vm in the future with gpu-passthrough, just set and forget as a home-lab, the array has 16TB of space with 1 parity disk) Following the example of @allanp81 - Its 12-2020 and still happening, did no firmware upgrade.

This one "did you set the unRAID DNS to the IP address of Pihole (not recommended)" I had it for 2 weeks running with only static dns entries, not dhcp and router stuff, it worked like a charm on selected clients, but now where its in the broad, inronically the unRAID system suffers from that, i kinda think off just setting the unRAID IP settings to static and use 1.1.1.1 as DNS from unRAID, seems like a easy fix.

Hey guys, i followed the guide from SpaceInvader, here and there are a few hickups to feel compared to an AdBlock extension but i can live with that. What i cant live with is that i setup'd it like in the video with DNS via DHCP over my router and the DNS address to my docker container and the unRAID server cant resolve any internet domains anymore, the resolv.conf states my DNS is right, but i cant do anything with unRAID in that state. Any ideas? I really thought it wouldnt matter that much that unRAID tries at bootup to get a DNS when the container isnt started yet but now, nothing is working. Regards.

Hey guys, ive seen a few topics of this topic leaning more to questions about tech/config like raid0 or 1 on cache or what disks are TRIM compable and stuff, but after reading other posts im still unsure on how to do my usecase. So please help me out here guys 😣 My Setup: ASUS Prime B450M-A Ryzen 5 3400G 2x8GB Corsair 3000MHz RAM Sticks Disks: 3x1TB SSDs (1 ADATA SU800, 2 Crucial BX500) My Usecase / Whats my plan: I would use this server as a homelab, meaning: Some Plex (about 400-800G) Mostly dev stuff & virtualization (so heavy VMs and Docker Containers and Coding) Aside a bit personal data backup (like 150gb or so) Rest is for trying out new stuff The question are now: How to setup the 3SSDs at best, considering my usecase. I thought of just normal 2 ssd array and 1 parity, or just 2 ssd and 1 cache Im unsure in what ways ssds might die in the way unraid uses them, compared to a normal software raid (md) like under ubuntu Am i missing something?