Zonediver

Thats the APIPA Adress range (Automatic Private IP Adressing) - normal, if there is no DHCP-Server... https://www.techtarget.com/whatis/definition/Automatic-Private-IP-Addressing-APIPA

Dann nimm ein Farctal Define 7 - kann ich nur empfehlen 👍 Beim Rest kommts immer drauf an... Transcoding, sonstige Dinge die laufen sollen usw.

What is the purpose of this post? 🤔

Updated from 7.3.0 - no issues so far 👍

Never mind... it doesnt work...

Yep Comes and goes...

Yep ...thats the next point.. it comes and goes...

In my case, it looks completely different...

What plugin is this? I installed unraid Connect but there is no "Unraid-API"...

FYI: The old 12 series CPUs cant encode AV1 - only the new Core Ultra (S1851) can handle this (if transcoding is an option for the future). So the 245K is the better choice.

Maybe this helps

Just a question for understanding: Why do we have 7.3.0 out and now comes 7.2.7? Is this a different branch?

Thanks for testing - i didnt test it because my server is working now and all is fine. The strangest thing for me was this: Lexar_JD_FireFly_AADEO33DRWIDXKE6-0:0 (sdj) 512 15663104 => no partitions no partition... thats really weird...

After a somewhat bumpy start, everything is running now as it should - thanks for the help JorgeB and thanks to the developer team for the good work 👍

So - i did the installation with the USB Creator Tool and all is working again. It seems, there must be some weird stuff going on with the format function of Windows 11 PRO...

This test is still pending - i will do this tonight because my unraid is a livesys 👍 I will also test the method with rufus.

I already did this... with no luck - boot yes, but without the WegGUI and only with ssh. Thats the "strange" part...

I know - thats why i said "mandatory". My system is running in legacy mode.

No - this step is mandatory - otherwise unraid will not boot.

Nothing unusual - just a single FAT32 partition - thats it... Yesterday, i created a new USB-Flash with the USB-Tool for unraid (to see, how it works) and this stick shows exactly the same infos under Win11 - a single FAT32 partition (active, primary) There is no (obvious) difference - thats the confusing part...

I did it like the past 16 years over Windows - i am not really sure, what else i could do... I tried it a second time - i took the USB-Stick out of the server, connected it on my Win PC and did a "real" format. After copying the Files back and startet unraid, i got the same result... no WbGUI (but ssh). So this must be a deeper problem - either from Win 11 or something else...

Interesting... For the older past unraid versions the docs said, format the USB under Windows with FAT32 and copy the Files to the Flash. If this process is no longer working, it should be mentioned at the docs that the new USB-Tool is a "mandatory requirement".

Of corse there are no partitions - the whole stick was formated as FAT32 and had a running 7.2.4 on it. How is it possible that an update destroys the whole funktion of the USB-Flash?

What "exactly" does this mean??? Its FAT32 formated with only one partition... How is 7.3.0 handling this? In the past, i unziped the new version, copied it to the USB-Flash, executed "make_bootable.bat" as admin and done! USB was FAT32 formated and labled "UNRAID". Is this procedure not longer working with 7.3.0?

Done - hope an expert can see whats going on 😉