albinorex Posted January 30, 2017 Share #1 Posted January 30, 2017 Hi all, First off huge thanks to everyone out there that has committed so much time and effort to this project - fantastic work. I'm currently running FreeNAS and found out about xpenology from a coworker and decided to give it a shot. I demoed 5.2 in a VM and absolutely loved the feature set so started the process of rebuilding my box with it. Unfortunately I've hit a snag, I'm booting off of USB for install and with 5.2-5644.5 or 5.2-5967.1 my box pulls a self-assigned 169.x address which leads me to believe the NIC driver didn't load up properly. I've recycled some old hardware into my NAS box, and it looks like the P5Q Pro runs an Atheros L1e NIC which is on the comparability list. Anybody else running on this hardware and/or had any issues with this before? One other odd thing is that my USB keyboard goes dark after booted up to xpenology (which worked seconds before when picking the install/upgrade option). Thanks in advance for any help. Quote Link to comment Share on other sites More sharing options...
albinorex Posted January 31, 2017 Author Share #2 Posted January 31, 2017 For anyone else that stumbles upon this, I figured out the issue. I had my SATA config set to IDE and while booting up it was hanging on loading one of the components (sataii.xxx) or something like that. I read that AHCI mode was required for DSM anyway so I flipped it. After that, voila DSM booted up just fine. Easy enough to do, I just didn't think that would be the fix. Quote Link to comment Share on other sites More sharing options...
turbo21psi Posted February 7, 2017 Share #3 Posted February 7, 2017 Just wanted to say thanks! Your post saved me a ton of potential headaches. I was lucky enough to see this post before I started the build on my p5q pro. Quote Link to comment Share on other sites More sharing options...
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.