Hi.

 

I have just spent the past weeks building an unRaid server basically completely head-over-heels in love with unRaid after discivering it around christmas.  

 

So - building a server and migrating data was seemingly successful. I have also been succesful playing video and music from the RAID. I have used the excellent preclear-script to add space as data has been migrated to the RAID freeing up the disks at their old location.

 

I just now realised, that apparently my data has gone corrupt :'(  Actually - it seems that I have about 3,5 TB of more or less corrupt data. <aaaauuugghhhhh>    :'(

 

Please let me hear your input and suggestions as to what's wrong, the extent of the damage i should prepare myself on, and any suggested remidies.

 

I have attached my syslog along with two of the corrupt txt files if that helps any at all.

 

I'm a not an IT newb (been a 'nerd' since my 1986 '286), but definitely a linux newb!  

 

Help  

 

CorruptFiles.zip

Oh My - it's not very clear at all.

 

Some files are corrupt - some are not. Even on the same disk.

 

It has hit mpg, jpg, txt, all types of files. But not possible to see from the outside. But opening a photo is a lottery.

 

Really really bad :-(

 

ANY suggestions welcome!!!

Oh My - it's not very clear at all.

 

Some files are corrupt - some are not. Even on the same disk.

 

It has hit mpg, jpg, txt, all types of files. But not possible to see from the outside. But opening a photo is a lottery.

 

Really really bad :-(

 

ANY suggestions welcome!!!

Step 1.  Run a memory test. 

Step 2.  Are the files really corrupt, or the networking when trying to read them.  Use md5sum to try to determine.

 

Step 3.  How did you move the files to unRAID.  (If using "ftp" then did you use "binary" mode?)

But not possible to see from the outside. But opening a photo is a lottery.

You might have a network interface issue.  What do you mean "not possible to see from outside"

 

But not possible to see from the outside. But opening a photo is a lottery.

You might have a network interface issue.  What do you mean "not possible to see from outside"

 

Sorry for being unclear - it was late (3AM) and i was in a state of panic 

 

What i was trying to say was, that the file size and date looks to be OK. However, some files are good, some are partially OK (and some are unreadable). Some of the mpg2 files had different content in them (still movies, but different ones, and usually with stuttering). Jpg's empty or with part of the image OK, rest missing.

Oh My - it's not very clear at all.

 

Some files are corrupt - some are not. Even on the same disk.

 

It has hit mpg, jpg, txt, all types of files. But not possible to see from the outside. But opening a photo is a lottery.

 

Really really bad :-(

 

ANY suggestions welcome!!!

Step 1.  Run a memory test. 

Step 2.  Are the files really corrupt, or the networking when trying to read them.  Use md5sum to try to determine.

 

Step 3.  How did you move the files to unRAID.  (If using "ftp" then did you use "binary" mode?)

Thank you Joe.

 

1) I'll do that when I get home - unfortunately that's the one thing that cannot be activated remotely. I actually added some memory a couple of days ago (last reboot). Maybe that is a very good place to start indeed.

 

2) I will look for a way to figure out md5sum. I'll also replace network cable and test it in the 100Mbit router in stead of the Gbit switch.

 

3) Primarily to SMB-shares using a Windows Explorer replacement called "DirectoryOpus" version 8. It has been good to me over the years, never ever messing up (and I have moved many TB with it). But SMB hares are new in my environment.

 

In fact - everything was appearing fine until after last boot. I will definitely look at the RAM I added (2*1GB brand new Kingston). I think my very first move will be to remove the added RAM and see how things look then.

 

I also added a PATA disk at the same time, but so far it has only been precleared, not added to the raid.

 

Does the system save previous versions of syslog, and how do I get to them? Are the preclear logs integrated into syslog or also saved separately (and in that case where)?

 

HUUUUGE sigh of relief 

 

It was the RAM that was the culprit. 

 

I removed the two new Kingston ValueRam (CL3) from the machine. Ran a MemTest on the remaining G-Skill 2GB (no errors), and after a reboot everything is back to its normal self again!

 

I guess the Kingstons very poorly matched the G-Skill CL2 RAM already in there. The poor RAM matchup simply made everything look like something out of a very bad film ... Weird, and nothing I would have ever expected being the result of a RAM issue.

 

Happy ending: No corruption. No data loss. 

 

Thank you for the swift and helpful response. Back on track - and still in love ;-)

 

Ya I never mix ram. I used to in the past (10 years ago lol?) but I haven't attempted that at any point since then. It can lead to some very bad karma as you have experienced.

I'm about to add 2 extra sticks of 256 Mb of ram of another manufacturer. I'll be sure to run extensive memtest ebfore starting the array.

I'm about to add 2 extra sticks of 256 Mb of ram of another manufacturer. I'll be sure to run extensive memtest before starting the array.

What will probably happen is that the BIOS will try to set the memory voltage, timing, and clock speed based on one of the memory strips.  It might be entirely wrong for the other brand/model of strips, it could conceivably even damage them if it thinks it can apply 2+ volts and the second set of strips have a max of 1.8.

 

If you are going to mix memory strips, I think it is best to manually set the memory voltage, timing, and clock speed based on the slower/lower voltage of the sets of strips involved.  If you leave the BIOS to set it automatically, it might work, it might not, it could ruin a perfectly good set of memory. 

 

A lengthy memory test is always in order.

 

Joe L.