MrMitch

Yes, the identical board.

I tried everything, including a motherboard swap to see if that was the problem. We ran memtest for days flawlessly, we duplicated the exact settings on an identical system that did boot with the latest version, we tried every boot config on the Unraid startup screen. - Nothing worked. As I said, I am running 6.1.9 and it works fine but I can't run redundant parity drives which is one of the reasons I wanted to use Unraid. Let's see if 6.3, when it's released will fix things.

Please post here if you find a solution. Did you try the beta releases that are available for download?

No, we never figured out why 6.2.4 won't run but 6.1.9 will. I have been stuck on this version since. I was working with Tomm directly to try and figure out why and we never reached a solution. I was hoping that a future release would solve this problem.

I do have the latest BIOS on the MB and I am the same person who has a friend with Identical hardware, in fact, I used his build videos to build my server.

Before I swapped the MB & CPU, I tried that. It would load the bz files and then the screen would go blank and back to the blinking cursor. I didn't try it with the new MB/CPU only because it's acting identically as the last round of hardware. And, I don't want to mess up my paid key again. Has anyone else had any luck with that solution?

I did reformat a flash drive and prepared a it with 6.3.0 rc4 and it showed the same results; will not boot unraid. I plugged in the old USB with 6.1.9 and boom. Booted fine.

Yes, before I see the blinking cursor, I watch as it runs bzroot and bzimage, then the screen goes blank and then just the blinking cursor.

Pretty sure Frank meant what happens when the boot process is unsuccessful. When the boot process is unsuccessful, the video monitor connected to the server has nothing but a blinking cursor. and It cannot be accessed remotely.

I did exactly what you suggested. I had 6.1.9 running as a trial and then used did the upgrade from inside Unraid and it would not boot. I have not tried to boot on other hardware. I run macs throughout, I run Parallels on a MacBook. As I said, I have built all 4 keys under windows and under Mac OS with no difference in results.

Frank, The MB/CPU/MEM is posted in my original message. The video connected to the server ran through about a hundred lines of code and returned a prompt. When it did, I could access the UnRaid control panel on my MacPro running Safari, no problem. I can see all the drives, the temp of each drive etc. If you want a photo, please let me know exactly what you want to see.

Hey Guys, I could really use some help. My brand new server will not boot UnRaid version 6.2.4 - BUT runs 6.1.9 perfectly. The only thing it can be is the USB key. I have 4 USB keys here, 3 of them are formatted with 6.2.4 and none of those will boot. The only one that successfully boots is the key that contains 6.1.9. I did pay for a license since I have 9 drives in this server, which is linked to the USB key that runs 6.1.9. MB = SUPERMICRO MBD-X10SL7-F-O Micro ATX Server Motherboard LGA 1150 Intel C222 DDR3 1600 CPU = Intel Xeon E3-1231V3 Haswell 3.4 GHz 4 x 256KB L2 Cache 8MB L3 Cache LGA 1150 80W BX80646E31231V3 Server Processor MEM = Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3L 1600 (PC3L 12800) Server Memory Model CT2KIT102472BD160B Back Story: This is a complete swap of the MB and CPU, I returned the first MB and CPU because I thought there was a defect that prevented the system from running the latest version. I also did a 5 hour memtest and the memory tests perfect. Now with the new system board and CPU, it appears that something is still wrong. You would think it's the USB key but I bought the exact brand and model USB key recommended on the Lime-Tech site. The keys were made on a PC formatted under Windows, the keys were also made on a mac using the MS-DOS format process of Disk Utility. Both were tested and it appears to not have made a difference either way. Any ideas?

Thanks, I am waiting now for my parity drive to finish its parity check, later this afternoon. I also notice there's a place to upgrade from inside the dashboard. Is that recommended or is the method suggested; adding the bz-* files to my existing key? Note: I did already buy the license. I am glad this is working but still baffled why my friend Andy has the EXACT SAME hardware and had none of the problems I did getting Unraid to run using the latest version. We both have the identical MBs and CPUs, same rev firmware, same memory, PS and even the same case!

I am starting my array build now on this older version, which only allows one parity drive. I am leaving one drive unassigned. I want to know how I can upgrade to the latest version without causing the problems I had before trying to load the latest version from the USB key. Can I upgrade an active Unraid array to the latest version and how would I do that if my system cannot run the latest version from a USB drive?

So I finally got the server to boot with UnRaid but NOT with the current version. When I tried everything, including hours on line with the SuperMicro support guy, we tried going back to older versions of Unraid. When we loaded: unRAIDServer-6.1.9-x86_64.zip - It worked. Not sure why the newer versions don't work. But at least I can build the server now.