Greg Posted January 5 Posted January 5 I don't know how long this post will end up being but with all the struggles I went through to get to the point I am not at, I figured others could learn from my mistakes. I tried following the directions in https://developer.isy.io/blog/eisy-way For setting up my NVMe. First off my eisy box did not have the screw on top of the post to mount the card in the box...something I still need to fully address. Other than that the installation of the card itself went off without a hitch. Next following the above referenced instructions I worked on creating the partion on the NVMe. I should have read the instruction more carefully as I went though step 1 and then tried to proceed onto step 2. With step 1 being to use the full NVMe and Step 2 to partition it out. Lesson here: You only need to do EITHER Step 1 or Step 2 trying to do both with lead to hours of confusion. Now onto the more important lesson: I read through several threads here and on other forums and sites about the error of not being able to get the correct repository when executing the script to install HA. pkg: No packages available to install matching 'vm-bhyve' have been found in the repositories pkg: No packages available to install matching 'edk2-bhyve' have been found in the repositories pkg: No packages available to install matching 'wget' have been found in the repositories pkg: No packages available to install matching 'qemu-tools' have been found in the repositorie This took me several hours to solve and I tried all the solutions listed in the different threads about this, none of them worked for me. What finally solved it was finding this thread: https://developer.isy.io/docs/getstarted/dev_env In it I saw some references to something I had seen in the installing the NVMe thread about being in the Staging vs. the Production repository. Following those instructions I had to go into the Staging repo and then back into the eisy admin console and hit the Upgrade packages button, allow that to run to reboot then go back in and change it back to the Production repo. I think it said to do most of that in the first link but it was not clear to me about having to go into the admin console to upgrade the packages there and not just from the command line interface. Anyway I hope this helps someone in the future. It appears the script completed successfully so I am off to they and see if this thing actually runs now.....one more thing....you need to cd to the storage directory before using most of the commands after you get the NVMe partitioned. $ cd \storage Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.