October 7, 200916 yr Author OK... down to a single stick of ram. disabled the original NIC and enabled the secondary NIC booted up. copied 6 files from the USER share and the DISK share. each of them have the same file signature when copied to my desktop... I'm going to shut the server down and swap the nic back to the old one as it's easier than putting the ram back in blind (i pulled three sticks out by putting my hand in through the DVD drive slot...) i'll report back when im back on the old NIC again. Tony.
October 7, 200916 yr OK... down to a single stick of ram. disabled the original NIC and enabled the secondary NIC booted up. copied 6 files from the USER share and the DISK share. each of them have the same file signature when copied to my desktop... I'm going to shut the server down and swap the nic back to the old one as it's easier than putting the ram back in blind (i pulled three sticks out by putting my hand in through the DVD drive slot...) i'll report back when im back on the old NIC again. Tony. Interesting... now, to attempt to figure out which is the cause of the corrupt bits as you revert to the older configuration that was failing. Joe L.
October 7, 200916 yr Author OK... This is getting tedious. Back to 4GB and original NIC and now I'm getting some curruption from the user shares... (althoguht not every file) I'm going to pull 2 of the sticks out, so im back down to 2GB. I'll then try pulling a much much larger selection of files accross and see what happens with regards to curruption. Is there a known 4GB bug? it's odd that it passed 13 passes of memtest and yet the memory seems to be the issue...
October 7, 200916 yr Frankly I would have stayed with the secondary NIC and started adding RAM sticks in one by one. The is no known bug with 4GB of RAM and from what I can tell so far this is some weird fluke with your hardware. There are a couple members here using more then 4GB of RAM and they have not said anything about there being problems.
October 7, 200916 yr Author Test number 6... 2GB still Marvel NIC. 41 files, 18 from disk1 25 from Disk2 copied to desktop from both DISK shares and USER shares. All 41 files matched DISK<-->USER share Md5 hash... probably to early to say... but i guess we might have found the issue...
October 7, 200916 yr As you said, too early to know for certain. But... it might still be some interaction caused by the simultaneous access of memory and the disk drives. (The disk drives were idle during the memory tests) It could even be the power supply... feeding noise from the disks power use to the circuits feeding the memory strips... Or it could be a memory strip sensitive to voltage variations when the disks are accessed. So many variables.... (and you will never be able to isolate one... or odds are you will not, especially if the MB self tests, and memory tests, and disk SMART tests all point to no problem... but you know better.) Worst case, you run with 2Meg of RAM. That's 4 times what I have in my server... you'll be fine. Joe L.
December 1, 200916 yr I've been following this thread because I've been having similar strange issues with my Aperture library (I'll be the first to admit that I was hoping to cash in or your root cause analysis - I don't like taking my server apart if any more often than I have to). Has there been any further activity on this? Did you isolate a single hardware change that "fixed" the problem? Thanks.
December 1, 200916 yr Author DrOpping from 4 to 2 gb of ram seems to have done the trick. I don't know why or what it's changed but my share reliably work now so that's all I cared about. T (sent from phone please forgive the typos)
December 1, 200916 yr OK - I'll start with JoeL's memory-related advice then (double check voltage, timing, mem tests, etc.). ...it just happens some of the time...weird Thanks
Archived
This topic is now archived and is closed to further replies.