August 21, 200718 yr I've been happily running on 4.0 for some while and yesterday updated 2 servers to 4.1. My Older server went just fine, however my main server got a bit confused. 3 of the drives were listed on the wrong position Disk1 was now in Disk2 Position Disk2 was now in Disk9 Position Disk9 was now in Disk1 Position And I got the status message "Stopped. Two or more disks are wrong". I simply moved them back to their correct positions and the array started just fine, however my network performance is now AWFUL, unuseable. My motherboard is an Asus P5-LD2-SE http://www.asus.com/products4.aspx?l1=3&l2=11&l3=185&model=1022&modelmenu=1 I'm going to revert back to 4.0 and see whether this fixes it, but were there any driver changes in 4.1 that could cause my network performance to drop to way below 1%? Thanks, Mark.
August 21, 200718 yr Author Switched back to 4.0 and all fine again. I did have to go back through the "Wrong Disks" situation again. BTW. Other then the parity disk Disks 1,2 & 9 are the only Satas of my current array. Mark.
August 22, 200718 yr You are not the first to see changes in the drive assignments. This thread is relevant, may or may not be helpful http://lime-technology.com/forum/index.php?topic=885.0. Also, the release notes for 4.1 mention a newer Linux kernel and some driver changes, which may have affected you. As often happens, what was meant to be an improvement for most users, could be a regression for a few. I would report your hardware, especially the networking card/chipset. Typing lsmod at a console or Telnet box will list the drivers used.
August 22, 200718 yr Author You are not the first to see changes in the drive assignments. This thread is relevant, may or may not be helpful http://lime-technology.com/forum/index.php?topic=885.0. Also, the release notes for 4.1 mention a newer Linux kernel and some driver changes, which may have affected you. As often happens, what was meant to be an improvement for most users, could be a regression for a few. I would report your hardware, especially the networking card/chipset. Typing lsmod at a console or Telnet box will list the drivers used. Module Size Used by md_mod 52200 9 sata_promise 9092 4 ata_piix 11524 0 libata 85796 2 sata_promise,ata_piix r1000 15000 0 [/list Is the LSMOD output under 4.0 which works just fine. I'm unable to go back to 4.1 and list again at the moment, but will do later if it is necessary. Does this provide sufficient info on the affected driver? I assume it's the r1000 one? Motherboard Gig Lan on my Asus P5-LD2 SE is listed as RTL8111B PCIe Gbit LAN on the Asus website. Thanks, Mark.
August 22, 200718 yr Release notes have this line: Improvement: use stock r8169 driver instead of Realtek r1000/r8168 driver And that definitely impacts you, after finding your previous thread from March: http://lime-technology.com/forum/index.php?topic=579.0. It looks like the r8169 driver is still not compatible with your board. Probably whatever you did then should help you fix it this time too.
August 23, 200718 yr Author Release notes have this line: Improvement: use stock r8169 driver instead of Realtek r1000/r8168 driver And that definitely impacts you, after finding your previous thread from March: http://lime-technology.com/forum/index.php?topic=579.0. It looks like the r8169 driver is still not compatible with your board. Probably whatever you did then should help you fix it this time too. I seem to remember that Tom added the r1000 driver back in for compatibility last time. I hope this'll happen again as I want to upgrade for the 16 disk & future NFS implementation. Thanks, Mark.
Archived
This topic is now archived and is closed to further replies.