![]() The system mounts any drive labeled UNRAID as read/write in the location for persistent storage at boot.Since this isn't really a deal breaker, I didn't look into it any further, so it may still be possible. I entertained the idea of booting from a btrfs subvolume, but the kernel panics at an early stage if trying to mount btrfs.The hard drive must boot from a fat32 partition, and can not be labelled UNRAID.It also needs to be mounted somewhere for the licensing to work. The flash drive needs to be fat32 (and possibly ntfs?) and must be labeled 'UNRAID'.Here are some of my findings while researching how to boot from hard drive, while still keeping full functionality and convenience: ![]() None of these options are acceptable for something that should just work™. Some even installed the unRAID components over a Slackware system, compiled a new kernel with Limetechs patches and ran everything straight from the disk. While I am perfectly comfortable with patching initramfs, it is still and inconvenience and it needs to be done after every new version of unRAID. Some still boots from the usb flash and shuffles the mounts around after boot. Some required that the root filesystem needs to be unpacked, some bootup scripts rewritten and repacked. The ultimate goal was to keep unRAID working exactly as usual, only from a hard drive instead.Īs it turns out, I am not the first person to entertain this idea - and I found one complicated way after another. Limetech (the makers of unRAID) do have an excellent key replacement policy and has provided me with new license keys, but downtime is downtime. However, having had two flash drives go bad, I started to look into keeping the usb flash only for the GUID and boot the system from hard drive. ![]() If it weren't for the fact that usb flash drives tend to go bad, I would happily run unRAID from a usb flash drive forever. UnRAID boots a root filesystem into ram from a usb flash drive, matches the GUID on the flash drive against the license key and uses the flash drive for persistent storage. I run an unRAID server in my home network since a few years, and I absolutely love the product. Any and all responibility for problems that may arise as a result from modifying unRAID in any way is yours, and yours alone! Run unRAID from a hard drive - the easy way. You should always keep backups of any files you absolutely can not afford to lose. This, of course, also applies to this modification. Modifying your unRAID server in any way may always put your data at risk.
0 Comments
Leave a Reply. |