August 9, 200916 yr Hi As in the subject, I tried to upgrade from 4.3.3 to 4.4.2 today by copying the bzroot and bzimage files accross to the USB key. Boots ok and I can log on as root from the console but I cannot telnet in nor can I see the box on the network. I haven't made any configuration changes to workgroups, IP addresses etc. Keen on upgrading to giving unraidweb a go, hence the upgrade, but I'm not particularly technical when it comes to unRAID so I'm nervous about doing something wrong. Can someone give me some pointers? Many thanks
August 9, 200916 yr Hi As in the subject, I tried to upgrade from 4.3.3 to 4.4.2 today by copying the bzroot and bzimage files accross to the USB key. Boots ok and I can log on as root from the console but I cannot telnet in nor can I see the box on the network. I haven't made any configuration changes to workgroups, IP addresses etc. Keen on upgrading to giving unraidweb a go, hence the upgrade, but I'm not particularly technical when it comes to unRAID so I'm nervous about doing something wrong. Can someone give me some pointers? Many thanks Sure... post a syslog, it will provide clues to what is happening. Otherwise, your question is the equivalent to "my car is making a funny noise... can you tell me what part I need to buy?"
August 10, 200916 yr The syslog shows no "link beat" detected. In other words, it does not think a cable is plugged in. Check the cable between the server and your router. Aug 10 21:19:43 Tower_2 logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Aug 10 21:19:43 Tower_2 logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Aug 10 21:19:43 Tower_2 ifplugd(eth0)[1307]: ifplugd 0.28 initializing. Aug 10 21:19:43 Tower_2 kernel: skge eth0: enabling interface Aug 10 21:19:43 Tower_2 ifplugd(eth0)[1307]: Using interface eth0/00:11:D8:30:38:6F with driver <skge> (version: 1.13) Aug 10 21:19:43 Tower_2 ifplugd(eth0)[1307]: Using detection mode: SIOCETHTOOL Aug 10 21:19:43 Tower_2 ifplugd(eth0)[1307]: Initialization complete, link beat not detected. Joe L.
August 10, 200916 yr You have 2 LAN chipsets on your nForce board. The first chipset is a Yukon-Lite rev 7, uses the skge driver, is assigned to eth0, with no info about its speed (gigabit or 10/100 only). The second is the standard one most nForce boards are equipped with, and uses the forcedeth driver, is usually a gigabit chipset, and is currently assigned to eth1. unRAID always uses eth0 for all networking, so it is using the Yukon chipset, but the syslog reports "link beat not detected" (as Joe just said!), so it is possible that you have your network cable attached to the wrong connector. If you want to use the other one, then you may have to disable the first one in your CMOS setup, which would make the remaining chipset (using forcedeth driver) be eth0.
August 10, 200916 yr Author You have 2 LAN chipsets on your nForce board. The first chipset is a Yukon-Lite rev 7, uses the skge driver, is assigned to eth0, with no info about its speed (gigabit or 10/100 only). The second is the standard one most nForce boards are equipped with, and uses the forcedeth driver, is usually a gigabit chipset, and is currently assigned to eth1. unRAID always uses eth0 for all networking, so it is using the Yukon chipset, but the syslog reports "link beat not detected" (as Joe just said!), so it is possible that you have your network cable attached to the wrong connector. If you want to use the other one, then you may have to disable the first one in your CMOS setup, which would make the remaining chipset (using forcedeth driver) be eth0. The cable is connected 'correctly' as far as 4.3.3 is concerned (i.e. can access accross the network fine) but when I close down, remove USB & copy new bzroot and bzimage accross, re-insert USB and reboot I get no network connection. Reverse the process and everything works fine again. Disabled each 'eth' in CMOS alternately - the first time with the same result and the second time (very curiously) wouldn't get past the MB's stock RAID screen. Ended up reversing everything and letting the box complete a parity check (data is fine). Maybe I'll give it another go when I've built up some more courage (I'm very nervous about playing with something I know so little about)!! Cheers
August 11, 200916 yr The cable is connected 'correctly' as far as 4.3.3 is concerned (i.e. can access accross the network fine) but when I close down, remove USB & copy new bzroot and bzimage accross, re-insert USB and reboot I get no network connection. Reverse the process and everything works fine again. Different versions of Linux will scan the hardware in different order. Probably on the older version, the network connector you are currently using was found first, and it is assigned eth0, and subsequently used. Alternatively, it is possible the second network chipset was not supported on your older release, not seen, so you only could use the one you did. (I did not check, but it is equally possible, as network driver modules are constantly updated as now Linux releases are made) In either case, just move the LAN cable to the other connector (if you want to leave both network interfaces enabled in the BIOS) or, disable the one that is being detected first so the older one will get used as eth0. Joe L.
August 11, 200916 yr Author Success! I wasn't keen on swapping to the other network port because I only got 100Mb speed. Turns out that there was (presumaby) some sort of conflict as I turned off the Yukon in the CMOS and tried again and it worked (with full Gigabit speed)! Running a parity check now but looks ok. Thanks for your help (both)
Archived
This topic is now archived and is closed to further replies.