princ3ssa
Members-
Posts
13 -
Joined
-
Last visited
princ3ssa's Achievements
Noob (1/14)
2
Reputation
-
CRAZY: I had a miraculous break through as well. I kept trying to use UEFI, but when I made the unRAID 6.9-rc2 image with the Unraid Flash Drive Tool and as BIOS and CHANGED my R710 to BIOS instead of UEFI it booted this time! I know I've read somewhere where using BIOS instead of UEFI for R/710 is a bad idea (whether for drives space, which apparently is false for an HBA controller; or for some other reason, I do not recall).
-
See also this "working" thread where I'm trying to work out the exact procedure before posting it on the bug report and other thread:
-
Alright, so this is making some more sense, but can you give some explicit stepwise instructions as to what you did? I tried with both "Allow UEFI Boot" and not with it. So here for example are my steps that I tried (that have not worked): 1) insert flash drive into Windows computer 2) run Unraid USB Flash Creator with these settings (this is for the MBR/BIOS attempt that also failed): 3) took USB flash drive out of Windows computer 4) inserted USB flash drive into Linux computer (Pop!_OS in this case) 5) wrote your MBR image with this command: sudo dd if=MBR_HardDisk4.dat of=/dev/disk/by-label/UNRAID bs=446 count=1 6) took out USB flash drive 7) inserted USB flash drive into R710 with BIOS boot turned on 8 ) started R710 server and waited for it to try to boot - failure to detect a boot device.
-
It may be possible to use Rufus to generate a syslinux 6.04 version of the unRAID USB flash drive. Does anyone have experience making Rufus built drives? Do you generate it with normal options and then copy the files onto it? How can you ensure GPT for UEFI boot? Even after I made a GPT USB flash drive with gparted Windows is trying to say it's a MBR partition scheme for the drive I built with linux....
-
Additionally it appears that the important point from the post that @JorgeB shared is that it takes a recent version of syslinux (likely beta) to make this work. Can we please get a new Windows and macOS boot drive builder that inserts this new version of syslinux so we can more easily test to see if this DOES solve the issue? There are a lot of us who would be happy to test!
-
@n1L and anyone else working on this, there is serious interest in addressing this and fixing this bug/inadequacy of unRAID (see bug report and post: ) Could you please either 1) document the process of creating the USB in Linux with details or 2) share a currently bootable version of the image that we can test and dissect? It appears the most recent version of syslinux is 6.04 from https://mirrors.edge.kernel.org/pub/linux/utils/boot/syslinux/Testing/ but I don't see any beta here. (Changelog) There might be some new development here: https://wiki.syslinux.org/wiki/index.php?title=Development but I don't know how to compile that to be used in our case. I believe the developers will implement the fix if we can get sufficient details and steps here.
-
I'm glad you created this! The first step we need to address here is to ascertain what the method for making a bootable USB drive was 11 months ago. I wish @n1L would have documented their work more thoroughly! Can you document the process of creating an unRAID USB drive from that time (11 months ago) from within Linux? From the one I had found on reddit it looks like the logical version of Pop!_OS would have been either 19.04 or 19.10 at that time....
-
I, like many others, need to use unRAID on older Dell servers. After some digging I found someone that got it to work. They said they couldn't use the normal USB boot creation tool, but instead built the bootable flash drive in Pop!_OS Linux on an old laptop. This appears to be from 11 months ago. I'm not entirely sure what steps would be followed on Linux to make this work. I did install Pop!_OS 20.04 and tried the `make_bootable_linux` script from 6.8.3-x86_64, but that didn't work so I opened the script and ran the commands manually. I got to the last step of inserting syslinux onto the USB and got the following output ($TARGET is /dev/sdb): $ sudo /tmp/UNRAID/syslinux/make_bootable_linux.sh $TARGET INFO: Installing Syslinux bootloader on /dev/sdb1 sh: 1: mcopy: not found INFO: Writing MBR on /dev/sdb 0+1 records in 0+1 records out 447 bytes copied, 0.00694731 s, 64.3 kB/s INFO: the Unraid OS USB Flash drive is now bootable and may be ejected. I also did this on a 64gb flash drive that was prepared in gparted as FAT32 on a GPT partition with the label and name both set to UNRAID. Is the missing mcopy in the above message a problem? What else could be going on here? I'm trying to contact the original author of that message to see if they can share exact steps, but the bottom line is that a version of Pop!_OS from at least 11 months ago was able to make a bootable version of the unRAID boot USB flash drive. This is really important and I'd like to work with anyone who may know more to get this working for everyone who needs this functionality.