bramley4600 Posted February 10, 2018 Posted February 10, 2018 I have upgraded my old Unraid v6 to a brand new spanking dual core Xeon processor macine. Never built a server before from scratch but everything went reasonably well, moved my hard drives and the unraid memory stick. Booted up ok in to the bios, checked everything was fine, then loaded Unraid, takes me to the login then to the root@Tower prompt, but then nothing. I can't see the box on the network. Can't ping it, tried to ssh via Putty, tried filezilla, nothing. Checked a few other things that have been suggested in these pages but still can't see it. i have enclosed the diagnostics file. I can see that one of my drives has some read/write errors but I have some new drives ready to install. Have tested the network cable which is ok, the lan port on the server is enabled in the Bios, really can't think what to do next. Nothing has changed on my system apart from this new server. Anyone had any similar problems? Probably something obvious that I have completely overlooked. Any help would be greatly appreciated as I have nothing to watch! tower-diagnostics-20140209-2033.zip
trurl Posted February 10, 2018 Posted February 10, 2018 Please always post the diagnostics zip file instead of posting each of the files in diagnostics zip separately.
trurl Posted February 10, 2018 Posted February 10, 2018 Are you trying to access it over the network by IP or by name? Looks like you have assigned a static IP of 192.168.1.10. Are you sure your other computers are on that subnet? It is easier to just use DHCP at least until you get things working.
John_M Posted February 10, 2018 Posted February 10, 2018 From your ethtool.txt file, your Intel NIC is being found and the driver loaded but there is no link to the switch detected. Check your cable and switch port.
bramley4600 Posted February 10, 2018 Author Posted February 10, 2018 Have checked the cable on my Windows laptop - works fine. Checked the switch port, changed it several times as well - works ok. Tried to access it by name and IP address. Also checked the memory stick was called UNRAID as per a post. Thanks for the replies
bramley4600 Posted February 10, 2018 Author Posted February 10, 2018 Also checked the subnet several times.
John_M Posted February 10, 2018 Posted February 10, 2018 You have three four network ports. Are you using the right one?
bramley4600 Posted February 10, 2018 Author Posted February 10, 2018 I have 5 network ports on my server, will try them all. It's in port 1 at the moment. One of them I think is a diagnostics port for the motherboard, this works ok.
bramley4600 Posted February 10, 2018 Author Posted February 10, 2018 Well bugger me. It works now. Just assumed it would be port 1, instead it's number 3. Many, many many thanks. I owe you a beer. Cheers.
John_M Posted February 10, 2018 Posted February 10, 2018 Unfortunately "port 1" means very little. You have given a static IP address to what Linux sees as eth0 but there is no physical link on that port.
John_M Posted February 10, 2018 Posted February 10, 2018 On the Settings -> Network Settings page near the bottom you can set Network Rules so that each of eth0, eth1, etc maps onto whichever physical port you want by specifying the MAC address.
BobPhoenix Posted February 10, 2018 Posted February 10, 2018 That port 1 is probably the IPMI network port. On the ASRock - EP2C602-4L/D16 the IPMI nic port is definitely not intuitive where it is placed. Highlighted port is the IPMI port on the IO backplane. Also with unRAID 6.x I was never able to get the onboard marvel 9230 controller to work acceptably and disabled it and removed all drives connected to it. That is the other graphic with the marvel ports highlighted. Note the EP2C606-4L/D16 which is in my graphic is the same layout as the EP2C602-4L/D16 - opps!
bramley4600 Posted February 11, 2018 Author Posted February 11, 2018 Hi Bob I have the EP2C602-4L/D16 and just assumed (incorrectly) that the correct port would be port 5 (LAN 1).
Recommended Posts
Archived
This topic is now archived and is closed to further replies.