January 9, 200917 yr I am in the "try before buy" phase evaluating unRAID as a WHS replacement. I built my test server using a Tyan Tomcat i7210 (S5112) mobo with a 3.2GHz CPU and 4GB of RAM. SATA storage is connected using a SuperMicro AOC-SAT2-MV8 (for two data disks) and the on-mobo SiI3114 (for the parity disks). I scribbled 4.4.1 onto a USB stick (4.4.1 was the current release at the time) and installation/operation *seemed* to be going properly... but then I started noticing network anomolies. After the second or third reboot my LAN interface wasn't working at all. I turned on PXE boot in the BIOS and was surprised to find the system reporting that the LAN BIOS was corrupted. Hitting Google, I discovered (unfortunately too late) the sad saga of the 2.6.2x Linux systems and corrupted e1000 NIC EEPROMs. I can't state this 100% conclusively, but it looks as though unRAID 4.4.1 caused this problem to occur on my test system. Unfortunately, all attempts I have made to revive the onboard LAN EEPROM have failed. :'( I may be able to salvage another one of these mobos from another system, but of course I don't want to brick that one too... so my questions: - Have you seen this before? - Is the problem *definitely* fixed in any version of unRAID (or, more specifically, the distro release that comes with a particular release of unRAID)? If so, which one(s)? - Any tricks, tips, or advice for avoiding this problem? Thanks! KoB
January 9, 200917 yr The problem was in a linux kernel 2.6.27 "release candidate" (ie, beta). Fix was put in 2.6.27.1. unRAID 4.4.x uses linux 2.6.27.7, so should not be the cause of this problem. See also: http://lwn.net/Articles/303390/#Comments
January 9, 200917 yr Author Thanks for the quick reply. I wasn't dissing unRAID -- quite the contrary, it looks very nice. I just wanted to ensure that the corrupt EEPROM problem was addressed in current unRAID builds before I try again with that mobo. KoB
Archived
This topic is now archived and is closed to further replies.