PoMpIs

I had to transfer the license to TPM because 7.3.0 wouldn't load the GUI with the GUID of my USB enclosure containing a 120GB SSD... But once transferred to TPM, I reinstalled UNRAID 7.3.0 in the USB enclosure and it works perfectly now—well, it works with any USB drive I plug in... And if I remove the SSD from the enclosure and plug it into an internal SATA port, it also boots and works. 🤷‍♂️

UnRAID 7.3.0 doesn't like my "USB drive". I've been using a 2.5" USB enclosure and an SSD for years, 7.3.0 boots fine with the USB enclosure, but it doesn't load the GUI because it doesn't like the GUID of the USB enclosure... let's see if this happens to other people. (7.2.x does not have this problem with my 2.5" USB enclosure) I copied the contents of the case to a USB flash drive and it boots perfectly. I'll have to transfer the license to new USB if I want to use 7.3.x. 😒 Because honestly, I'm not very interested in using the internal method; I don't like using a partition in the cache, and if I switch the USB from the enclosure to a SATA port, then I'll be left without a SATA port that I can use in the array. EDIT: Once the license was transferred, I must say that version 7.3.0 of the moment works very well on my server: Regards 🙂

But if I can't access the GUI, I can't run diagnostics, right? I created a clean USB drive with 7.3.0 and it boots and reaches the GUI, but if I use my CONFIG folder, the GUI doesn't load. 7.2.6 works perfectly, so I have to go back because I need the server up and running. In version 7.3.0, everything is fine in the log, but there is no GUI.

I just updated my server from 7.2.6... it responds to ping but there's no GUI. 😅 And this computer doesn't have a GPU. I've installed a GPU, everything boots up fine, without errors, but there's no GUI I'm going back to 7.2.6

Well, it's been many years since I used a USB drive with unRAID... I had a 500GB 2.5" Seagate hard drive, one of those that came in a USB 3.0 enclosure... I took it apart, removed the mechanical hard drive, and replaced it with a 120GB SSD that I bought years ago on Amazon for €20... It's fantastic. It's been connected to a USB 3.0 port on the server for years, the updates are incredibly fast, everything works perfectly, and since it's an SSD, I can keep the unRAID registry on it if I want, which won't break down for many years despite the constant writes. But the best part is that I can have backups of unRAID on other drives because the GUID is stored in the USB enclosure. So I save a backup of unRAID, put it on any other SATA drive, turn off unRAID, and swap one drive for the other, and everything works the same. It's never failed me. But I've tested it, and unRAID boots on any drive I plug into that enclosure because... The USB case has the GUID. 👌

The same thing happens to me too. The text is barely visible. 😄

I restored a backup from the USB drive and tried again, and this time it worked fine. It's been working for a few hours now and hasn't given me any problems.

Today I tried updating to this RC version, and after restarting, my server appeared like this: It doesn't list a single one of the many disks it has 😅 After a second restart, it was fine... but it doesn't show that it's on RC1... it shows 7.2.0, and I didn't revert the version. And now, if I click "update OS," it always stays like this: I'm going to restore the USB backup 🤷

I updated from RC2 to 7.2.0 and everything is working fine. But the GUI is still slow... or is that normal? RyzenServer_Tools - Google Chrome 2025-10-31 15-19-02.mp4

Hello again...🙂 After 3 days of running my server with this rc2, the GUI has become slow... about 3 seconds or maybe a little more. I mean, I click and it takes 3 seconds, sometimes almost 5 seconds to respond... for example, if I'm in settings and I click to go to Docker, it takes a long time, about 3-5 seconds, to display the Dockers GUI. It's much slower than version 7.1.4. Regards

Hello... 🙂 I upgraded my main server to 7.2.0-rc.2 last night from 7.1.4. Everything's perfect. It updated very quickly, and everything works great. 👌

My server has been running perfectly for 2 days and 19 hours since I updated to 7.1.4.rc1 👌

Hello, I just wanted to say that this version (7.1.3) doesn't give me any problems, it's been working perfectly for over 24 hours. EDIT: Well, after about 28 hours of being on, it failed, losing internet access..... And since I'm playing, I updated to 7.1.4-rc.1 😁

Well, a couple of hours later it's back to normal, maybe there was more disk usage when it first started after the update... so far it's been 3 hours without any problems... everything works as usual. 👌

Well, in the end I updated my main server to 7.1.3... I will report if it fails or not. 😅 EDIT: This is a bit weird, the CPU usage in the GUI doesn't match the actual usage at all?¿? Until a while ago in 7.1.2 it was fine 🤷‍♂️

Hi... I have a second server for testing, and I installed this version, and it's been running for over 24 hours without issues with Shinobi and 14 cameras and two VLANs... it's the same machine as the main server, so I run tests on it before moving them to the main server... The machine is a Ryzen 1600AF, 64GB DDR4 Asus B450 motherboard with RTL8111 Ethernet and an Nvidia GT1030... I haven't updated the main server yet because reading you scared me, and on the main server I use three Realtek network cards, one RTL8111 and two RTL8125.

Updated my main and test servers to 7.1.0 without any issues, everything works perfectly. 👌

Updated without problems 👌

I imagined that with "Docker-Folder there must be some problem having the cache in ZFS, because I couldn't even reinstall 3 containers without the system failing... The problem is that in my system it ends up failing in the same way even if I use "Docker.img-XFS or Docker.img" and the cache disks in ZFS... it takes longer to fail, but it fails.. As I have two licenses, I will try with other hardware in case it is a problem of incompatibility of the motherboard with UNRAID and ZFS. This system with BTRFS is super stable, it has been used for more than a year as a 24/7 permaseed and records from 13 CCTV cameras with shinobi, and Jellyfin, sonar, radarr, immich, nextcloud, and many more, and it never failed, it started to fail as soon as I moved the cache disks to ZFS in 6.12.13... so for now I will leave it in BTRFS. Maybe Could it be that the disks I use for cache are on an ASMEDIA 1064 controller and cause problems with UNRAID when formatting the disks in ZFS? Thank you very much @JorgeB

With Docker.img-XFS and the cache disks in ZFS, the errors were the least likely to occur, but within 24 hours of operation, those errors would appear again in the LOG. With Docker.img-BTRFS and the cache disks in ZFS, I also saw those errors in the LOG in less than 24 hours With Docker-Folder, and the cache disks in ZFS, it gave me a lot of problems, I could no longer reinstall my dockers, those errors would appear in the LOG immediately. Once I moved the cache disks to BTRFS, I can use Docker.img in any format and those errors have not appeared in the LOG again, and the computer works without any problems. Now it is working wonderfully with Docker-Folder and the cache disks in BTRFS, those errors have not appeared in the LOG again, and everything works at 100%.

It can't be a RAM problem, I've tried 3 different new kits and it keeps showing up in the LOG until the server crashes.. I've run memtest, stability tests on the CPU and there's no hardware problem.... It's only when using cache disks in ZFS Once the CACHE disks are changed to BTRFS, none of that happens anymore, everything works 100% stable Thank you so much

Holaaa No soy muy asiduo por aqui, pero a ver si @JorgeB me lee por aqui, que es el que mas leo y entiende mucho de esto, que me cuesta expresarme en ingles ... Vamos al lio... Tengo un sistema con un ryzen 1600AF, placa MSI B450 Gaming Plus Max 32 gigas de ram y un porrón de discos para multimedia... Siempre funciono bien con UNRAID, pero cuando pase a 6.12.13, cambie los discos de cache a ZFS-Mirror, son 6 SSDs de distinto tamaño, pero en parejas.. es decir: -2x120Gb -2x250Gb -2x480Gb y quedaban tal que asi: Una vez cambiado el formato y vuelto a mover todo a la cache, todo parecia ir bien, pero en menos de 24 horas veo esto en el LOG: Y al final acababa por colgarse el ordenador, no respondia a nada.... Como ya tenia ganas de probar UNRAID 7 beta 2... y como tengo dos licencias PRO, pues cree otro pendrive con la otra key y meti la configuración que tenia en pendrive con UNRAID 6.12.13... Funciono perfectamente y todo parecia ir bien, pero al rato volvio a saltar esto: y si no reiniciaba en menos de 30 minutos se acababa colgando el server... Al final se me corrompio la imagen Docker.img, que estaba en formato BTRFS dentro del pool ZFS.... ya puestos, borre la imagen y cambie el Docker.img a XFS.... reinstalé todos los dockers y volvia a funcionar todo bien... pero al dia siguiente por la mañana ya volvia a tener esos errores en el LOG del sistema .... Ya le estaba echando la culpa a que el propio ordenador tuviera daño fisico de hardware, le probe varios kits de ram y seguia igual, baje la frecuencia de la CPU 1Ghz y subi el vCore y seguia fallando.... asi que el equipo funciona bien y sin fallos todo por defecto, asi que estaba claro que era algo del sistema operativo UNRAID... Al final, probe a cambiar el Docker.img a "Directorio" ... y ahi si que ya empezaron muchisimos mas problemas... con los discos de cache en ZFS, era imposible volver a reinstalar los docker, salian esos errores a destajo en el LOG, y no era capaz de instalar mas de 3 contenedores sin que se colgara el server... Al ver eso, me dije, a ver si va ser cosa de ZFS con estos discos o algo asi... Con lo cual, volvi a pasar mis discos de cache a BTRFS Raid1c3....... Y todos mis problemas se han acabado... no mas mensajes de error en el LOG no mas cuelgues nada de nada.. una maravilla y 100% estable.... Y sigo teniendo el Docker.img como Directorio en vez de imagen, y van super rápido los contenedores, tanto arrancandolos como instalandolos.. Me gustaria saber porque ZFS provoca esto en mi sistema???... porque me gustaba mucho usar ZFS_Master para las instantaneas... con BTRFS lo estoy haciendo a mano, porque el plugin que hay para hacerlas "snapshots" no se puede usar en UNRAID 7 Beta 2, porque deja el pool BTRFS en modo lectura y no queda mas remedio que vaciarlo y volver a formatearlo Muchas garcias Un Saludo

thank you so much 😄

I just saw this in the log: It is the first time it has been shown