colins2

Thanks for the confirmation. Sadly, apart from the current boot USB drive, the rest are internal HDDs. When running unraid, I don't need them or even want to see them. They are there for the occasional times I may want to boot into another system. It's a very old bios on a very old HP workstation so I don't think there is any easy way to turn off the extra disks, short of unplugging them.

I have just finished my trial and was happy with the setup , shares etc. so I bought the starter license. I understand that it limits me to 6 devices. My question is how does the unraid system count the devices? I have 1 x parity disk, 3 x storage disks, 1 x cache drive and currently a boot USB. As far as I can see, that is 6 devices but after installing the key I am told that I have exceeded the allowed devices? Now, I also have 6 other drives on the system but they are just unassigned as far as unraid is concerned. One of them will be the boot drive when I install it but that is just swapping 1 device for another. These other drives have other OSs on them and are bootable. Unfortunately, the error message does not say how many devices unraid thinks I have - that would be helpful. Is it seeing 7 or 12 devices? One other point is that the number of slots allocated to the array is set at 5 and I cannot reduce it. It should be 4. There is an entry for a 2nd parity drive but I don't have one so it is just shown as unassigned. Is that being counted? The cache drive has its own slot and, although not named as such, the boot drive must have a slot. There is nothing of any importance on the array as I have just been experimenting, so I could delete everything and start over but I don't want to do all that and find I have still exceeded the license. Can someone please shed some light on this? EDIT: OK, I clicked on a registration link and that told me that I have 11 out of 6 devices, so that means that unraid is counting everything attached to the system even though unassigned. That is no use to me at all so I either forget the $50 just spent or cough up another $60....... Rock and a hard place......

I did try tower.local but got address not found. I'm looking through the log files and I can see why the GUI failed to start - modules not found etc. OK, I have web access using the IP, tower.local just says server cannot be found. I will go through the guide now that I have access.

I am brand new to this, so please bear with me. I tried the online installer but it didn't like my usb stick so I found the alternative (manual) way to get a bootable stick. That worked fine and I can boot the computer to a CLI prompt and I can login as root. Following the instructions, I tried to boot to a GUI, both regular and safe mode but neither worked. It looks as if it is trying to start the xserver but then just sits there with a blinking cursor in the top left. I am able to open a new tty, login as root and reboot. I am trying to set up my old HP Z420 Workstation with Unraid. It has a Xeon v2, 64GB ram and an Nvidia 1050ti GPU. Currently it has 2 small SSDs with TrueNAS installed, a 3 drive ZFS pool and a couple of other drives that aren't relevant here. Obviously, I want to be able to boot a GUI so that I can look at the system. Once I find that I can use Unraid, assuming I do, then the TrueNAS setup will be replaced and some larger drives added. I am just experimenting at the moment to see which system suits me best. FWIW, the TrueNAS setup works fine but I only have storage set up, no apps or VMs. I also tried to boot my desktop from the Unraid USB and got the same result. I have looked through the log file but can't see anything wrong. My desktop is a Xeon v3, 24GB ram and an Nvidia 3060 and has 2 bootable btrfs drives but this was just to test, I have no intention of running Unraid on there. Lastly, I tried booting 2 laptops and failed miserably. These have ext4 formatted drives with Linux and I saw on the screen that ext4 is not recognized. They both triggered a timeout that said they couldn't access /dev/... I guess because of the format? Anyway, they don't matter, it was just a test. Do you know any reason that will prevent the system booting to a GUI? I have re-downloaded the zip file and re-written the USB drive but that didn't change anything.