HardwareHarry

I dug into this specific problem yesterday and installed the SSD individually in a spare PC, actually burned a CD as it is hard to get the specific Evo Plus firmware ISO working from a USB stick. (works with ventoy starting the iso in memdisk mode if someone wants to experiment with that) It still did not update one of my 970 Evo Plus. Then I found out that There are 2 revisions of the 970 Evo Plus with two different controllers on it. The Firmware update site or the product site does not consider that. (2020 chip shortage issue For me that means my 2nd Evo Plus is a different one with a differernt controller and no firmwareupdate above "2B.." (same version as the EVO (not Plus) on the Samsung website) My other Evo Plus has a different controller and a newer Firmware starting with "4B..." For the one with "2B.." this is not even revognized as compatible drive by the firmware update tool, no matter what you do. Trust this might help others

Did you find a solution? I have the exact same SSDs in the exact same configuration and exact same firmware issues with the exact same firmware version for drive 1 and 2

Updated my Backup Server from 7.1.4 to 7.2 2 days ago (No docker, no VM) I found no issues Updated my main Server a few minutes ago from 7.0.1 to 7.2 ( 2 VM, several dockers) no issues found so far.

Updated my Backup Server from 7.0.1. to 7.1.4 without problems...however my backup server is a very uncomplicated setup. No Dockers, No VM, etc.

Hi folks, I can no longer find the Update Assistant. on two Servers. Already removed and reinstalled fix common problems. Did I miss something? Ist that feature deprecated? Or ist it just moved somwhere I no longer find it. P.s.: Yes I searched a lot before I asked that question and read through this thread but I did not find any hint

A little bit of everything (no Gaming) but the main points are -NAS -Windows VM -Docker

@landS The 32GB Version doing their work in 2 Servers. Only issue I had: It needed manual FAT32 formatting and manuall install with the "make bootable" batch file. Since 2022 no issues at all

Downgraded to 6.12.10 again as the networking seems somehow broken

But I'd also assume most from existing customers Exactly my point as this in my opinion is this is the big part of the base which is then no longer buying

In my understanding that is not what the sytem is designed for. Just use an old PC and throw in the disks you have. ANd there are not thousands of high end youtuber buying unraid- (most of then are not even high end ) They could also use OMV or Truenas or Proxmox with different systems etc. I don't see that new customer base for unraid. First rule of the fight club sales: Know your customer base

I also hope that never happens, but given the structure of the members of this Community (= Customer base structure) I somehow doubt there will be many new users and I somehow doubt many of the current user would actually have choose this system as new users (including myself and a buddy of mine to whom I recommended Unraid (and who has 2 Plus licenses now).) When I was thinking about it some time ago my limit was something about the psychological "199 USD " limit and even that would be hard to swallow for me. But 250USD ....would not be an option for me. For my server and backup server thats 500 USD !!! Even the 2 Pro Licenses I have bought is a lot of money but 500USD for 2 Lifetime. Yes I could do one lifetime one unleashed and updatd the backup only from time to time and so on but would I want to fiddle with something like that? No. Given that I would predict LT will struggle with that model

OK under the new System I would not have chosen Unraid as Lifetime would be to much for me as a private person in many cases and I'd rather buy an additional HDD and use e.g. OMV . Any Licenses I would have to update regularely, I just personally don't ike that.....OK user can strech it for some time but this is all a little sketchy. Business users...i somehow doubt there are many for Unraid who don't really care about 250 bucks. Basically I doubt this is a sustainable model,.....however time will tell. My suspicion would be that this leads to the rise of OMV and Truenas and Unraid might beginn to struggle in 2-4 years but who am I to say

Same problem here. IPVLAN is not an option since I have a Fritzbox. Problem is existing on my Server AND my backup Server Switch is a unmanaged switch Using 10G SR Tranceiver and LC-LC Om5 cable Disable/anable NIC Flow Control does not change anything Out of curiosity I played with rx/tx buffer sizes which also has no effect eth1 is not connected nasng-diagnostics-20240221-1632.zip

I have 2 Servers and none of them had that happen. Also just showing the DOT Files does not mean the sever deletes files. Do you have some sort of mirroring backup?

That answer is not adressing the above point that such a bug might be an issue for a warning but not an issue to delete the download archive

Yepp, I second that. Some versions take forever to get updated 6.11.5 was around 7 months I think and 6.9.2 für 13 months while some just never see daylight (6.12.7) or get updates within days, weeks or 1-2 months. Since we don't know when 7 is ready I would start tinkering with 6.12.8

In my experience WD in general gets much hotter than Seagate or Toshiba without propper cooling. Perhaps it's a cooling issue? I have 5x 3TB WD RED (working since 9 years now) 6x 8TB WD White label shucked from WD Mybooks(working since perhaps 5 years now) and 6x 16TB Toshibe (working since 3 years now), a 10Tb WD white label shucked from WD MyBook also working since perhaps 5 years now. None of them failed (knock on wood). I stil reccomend my method mentioned above and I think the critisism is pretty construed for what the data is actually providing.

Which is "a corner case bug" which should be a warning but just deleting everything?

Why is the download archive gone? I'd still love to have the option to manually downgrade if something went wrong. https://unraid.net/download https://docs.unraid.net/unraid-os/download_list/

THANKS !!! First I want to mention that I really get that you need more cash to get new employees and it's absolutely fair and I like that you are so honest about it. Second as someone who bought 2 Pro licenses (Server and Backup) for my private data (so non business use) despite a "Plus" or a Basic"License would have been sufficient but I liked the license model you provide so I wanted to support that. Third an most important: All fears I had were clarified. Please keep your promises. I also want to mention that If you keep it that way you said above I really think you are doing everything right. My experience, with Vuescan from hamrick [btw this is a really fantastic software for scanners and I highly recommend it!]) of which I also have a lifetime license and the changed the license model in a similar way,- was that 1. Grandfathering old licenses is the 100% correct way to go and it sounds like you really seems to embrace that in every aspect. I really appreciate that. 2. The game of "we'll just rename it to make it EOL" is a brazen, unfair and dubious move, so I think it's 100% right not to do that. It also encourages me to continue supporting Unraid (and by the way, to recommend you very often) 3. I prefer paying one time, even it it's higher priced, and get a lifetime license (which for example I can't get with Vuescan anymore) therefor thanks a lot for still providing this option

New years eve is currently noon in my timezone (12:40 CET) and i have three little kids (1/1/3) so I'm babysitting and messing around with my server 🙂 You have the same issue I had: vhost0 is missing in the routing table. I show you my config and my issues and how I solved it: The Network settings should be: - Network, Bridging off - Network, bonding off (optional, if not really needed ...) - Docker, host access on - Docker, macvlan - VM, vhost0 AND thet here is the kicker: This was my routing table without vhost0 in it....like yours After - enabling docker Services AND -Setting IP Custom Network to my standard Ip settings in the Docker Setting: - Vhost0 showed up in the routing table: Right after that I restarted the VM and everything is working as expected I personally think this is a dseign flaw in the current network settings.

@vw-kombi I "think" I got it solved, thanks to @alturismo Can you share a screen of your routing table ind the network settings? Also a screenshot of your complete Docker Settings

Neustart des servers kann ich gerade nicht machen da der Parity Check läuft... ABER Ich hab in den letzten Tagen den VM Service mehrfach deaktiviert und neu gestartet, mehrfach docker Service deaktiviert und neu gestartet und gefühlte 20 mal den Server komplett neu gestartet. Hat nichts gebracht. Unclean shutdowns gibbet bei mir nicht. Jetzt hab ich mal weiter gespielt und in Docker das Custom Network aktiviert und es nicht Docker überlassen Seither taucht Vhost0 im Routing auf Nach einen Neustart der VM hab ich kontakt: Problem gelöst, vielen lieben Dank für die Hilfe und den Schubs in die richtige Richtung!!

VM network nasng-diagnostics-20231231-0952.zip