gnollo

Everything works well, solved

Yes copying the config folder across worked well, server up and running, will now test emby

Thanks Johnnie Black I will do that as soon as Rufus has done its business.

Tried to do the same on the original flash, once completed, windows announced that there were problems on the flash, and asked to scan and fix, which I did. Now trying rufus on it again, this time I added - check device for bad blocks - unticked quick format

Using Rufus, I created a syslinux 6.04 bootable flash with it, on a 32 Gig Sandisk key making sure I ticked compatibility with old motherboards. Then I copied the unraid files for a brand new installation from the zip install file. This time it has done it, so it looks like some of the files on the flash that I was using are corrupted. What do I copy across to get the server back up and running? I plan to follow the same process on the flash which is registered, so I can copy across the key for a start.

I created a new flash drive, and copied the content of the old key, also fails.

Just tried pulling each ram stick out one at a time, still getting kernel panic Sent from my SM-A520F using Tapatalk

Just tried booting in "unRAID OS Safe Mode no plugins, no GUI)", same result

I moved the server from a room to another, and now it won't boot because of kernel panic. I checked all the connection, and they seem in place. Never had this before so I am unsure what to do next. Any help appreciated. Screenshot of the screen attached

I am using the Swif2 fans, but honestly I am tempted to put the old ones back in and re-evaluate noise vs cooling

I changed the fans to make it super silent Sent from my SM-A520F using Tapatalk

I am not happy with the temps in my Norco ss-500, really considering selling the four of them and buying these instead Current temps during heavy usage almost reach 50 and its winter over here... Sent from my SM-A520F using Tapatalk

Rufus worked for one of the flash drives I have been working on. I created a syslinux 6.03 bootable flash with it, making sure I ticked compatibility with old motherboards. Then I copied all the unraid files off the old flash, and we have liftoff. Very kindly limetech support is helping me out with another key. Let's hope 4GB will last me as long as the old flash did! /saga over Sent from my SM-A520F using Tapatalk

Rebuild the second flash key with antivirus off, UEFI Boot mode NO, no change. Also tried the same with a new Sandisk Cruzer FIT 16 GB USB 2.0 Flash drive. Same difference. It is seen in the bootup but not available in the bios as hard disk. When I reboot the machine, before it scans to list the disks available, this message appears ** This version supports only Hard Disk and CDROM drives ** I am stumped. I will try next to setup the key to look like a CD ROM, using a cdrom bootloader

More testing tonight, including uninstalling antivirus, a bigger Cruzer, using Rufus to prepare the flash drive and using a cdrom bootloader Sent from my SM-A520F using Tapatalk

Yep, tried several. The old key is recognized in the bios in every port, the other one is not. Sent from my SM-A520F using Tapatalk

I restored the backup of the old key to the new key. Cleared the /previous folder on the old key. Copied the bz* files across to both keys. Rebooted the server. Now I am running 6.8. Both keys are in synch but the one recognised as the boot device is the one that is not booting on its own. Not ideal, and I wonder what will happen once the other key blacklisting comes into effect.

no difference

followed the instruction below. Run the CMD app as admin, and then J:\>make_bootable.bat Make Bootable v1.5 Volume in drive J is UNRAID Volume Serial Number is AECA-3701 Permit UEFI boot mode [Y/N]: y Ready to make disk bootable! Press any key to continue . . . J:\syslinux\syslinux.exe -maf J: Completed Press any key to continue . . . J:\> No difference

😱 What do you suggest I do next? Can you recommend any USB key that I can use with this motherboard? I will test that it can boot on its own this time, before I try to switch the permissioning. I could also try to update the OS on both keys, and see if they boot in unison, like they are doing on 6.6.6

I just emailed support to see if I can have it un-blacklisted.

Alternatively, does anyone have any ideas on how I get to fit the new version of unraid on my old 514 MB key? I tried copying the files across but it says I don't have enough space. The other problem I have is that I moved my subscription from the old key to the new one. Which doesn't boot.

I would agree with you that is booting with the old flash. When I upgraded the new key, it stopped booting half way with a number of error messages. I really want to fix this setup so I only have a key, or I would even be happy with booting from one of the disks? I am having some weird issues with the bios as well, when I change anything and save the bios, it restarts but I don't get so see the bootup screen, stays blank for ages. The only way to get to the bootup screen is to turn off at the mains, then choose last succesful boot (F12) and it then it boots succesfully

Reboot it manually, as it started extracting bizroot and I wanted to swap the keys.

Copied the pro key across, that worked, after restarting the server with CTRL ALT DEL a parity check started (I stopped it). I didnt initialise the check last time either, but I am guessing that it has to do with an unclean shutdown. Diagnostics attached. tower-diagnostics-20191213-0652.zip