francishe Posted November 6, 2020 Share Posted November 6, 2020 (edited) Hello everyone. I am a rookie and very new to unraid OS which i am trying to use. After installing, i always find this message "can't find device bond0". I guess this error provented me from login to gui though an ip 169.254.x.x was given. Then i was trying to start to gui but in vain telling me connection problem. I am using msi x99a sli plus motherboard and e5 2683v3. I have looked through its bios for any clue that might reult in the connection failure but also in vain. Apprecite if anyone teaches me where it is wrong. Edited November 8, 2020 by francishe Quote Link to comment
itimpi Posted November 6, 2020 Share Posted November 6, 2020 It rounds as if Unraid is failing to find the flash drive to correctly complete the boot and load the network drivers? You may find this section of the online documentation of the Unraid boot process and it might help as it describes things to look for on boot failures. Quote Link to comment
francishe Posted November 6, 2020 Author Share Posted November 6, 2020 Thanks for the advice. I have tried my flash on another pc and it booted perfectly. So the flash was done without a problem. According to that text i will see if it boots completely on my server with necessary drivers loaded. If not I don't know what to do. Quote Link to comment
itimpi Posted November 6, 2020 Share Posted November 6, 2020 It would be useful to know if you logged in at the console and tried the ‘df’ command to see if the /boot mount point is showing. Knowing the answer to that would help limit the possibilities. If it IS showing then try using the ‘diagnostics’ command from the command line and post the file that would then be created in the ‘logs’ folder on the flash drive as that would give us something to work with. Quote Link to comment
francishe Posted November 7, 2020 Author Share Posted November 7, 2020 Thanks. I will try today Quote Link to comment
francishe Posted November 7, 2020 Author Share Posted November 7, 2020 My feedback here. Indeed the problem was caused by usb 3.0. After switching to usb 2.0, it booted with full firmware loaded and logged onto the gui. Thanks all. Quote Link to comment
itimpi Posted November 7, 2020 Share Posted November 7, 2020 1 hour ago, francishe said: My feedback here. Indeed the problem was caused by usb 3.0. After switching to usb 2.0, it booted with full firmware loaded and logged onto the gui. Thanks all. Glad to hear that it is sorted. I would love to know the exact reason why USB3 seems to fail for so many people (although not all). In theory it should be fine but experience has shown this is often not the case. Quote Link to comment
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.
Note: Your post will require moderator approval before it will be visible.