OK I am having a very serious problem that is making me doubt my switching to Unraid.

 

Basically if I attempt to move any files from one folder on the server to another through windows the system automatically give a kernel error and hard locks.

 

I can move data TO and FROM the server and I can move data around on the server through MC in Putty. But if I attempt to move so much as a single file via windows the whole system crashes instantly.

 

So WTF could be causing this? If I cannot get this fixed fast I will need to look into alternatives as I cannot go without access to the data on the server.

 

If you need any logs or something to help please tell me what you need as I'm not sure how to troubleshoot Linux very well.

Have you run Memtest (Memory Test) on that system? It could be the cause of your problems.

 

Yes I checked the memory.

 

As I already said I can do anything with the server but move a file from one folder to another via windows, how could that be bad memory?

Yes I checked the memory.

 

As I already said I can do anything with the server but move a file from one folder to another via windows, how could that be bad memory?

 

ombraweb -

 

Sorry you are having problems.  I looked back through your prior posts and saw that you've had problems with poor performance copying data.  Were you able to resolve that problem?

 

It seems very unlikely that your problem is related to a bug in unRAID.  Virtually every user here has used their workstation to move files around on unRAID.  No one in my over 3 years here has reported the symptoms you are describing.  It is much much more likely to be a problem with your machine/environment than a problem with unRAID.

 

You should capture a syslog just before attempting to move your files with Windows (follow the troubleshooting link in my sig for instructions).  Then, open a telnet session and enter this command:

 

tail -f /var/log/syslog

 

(This will display the last few lines of the syslog and, as new things are logged, display them in real time.)

 

Then do your Windows operation.  (Assuming server will lock, but you may get some additional syslog lines in your telnet sessoin). 

 

Post the captured syslog and the additional messages logged from the tail on the syslog.

 

Also post all relevant info about your system - motherboard, CPU, memory, add on controllers.  And post unRAID version you are using.

 

Tonight you should run an overnight memory test.  Bad memory can cause almost any imaginable weirdness.  It is the first place to start in looking at hardware problems because it is easy to test and frequently turns out to be a problem.  Running memtest for 5 minutes isn't enough.  Overnight is the minimum.

 

If it is a hardware problem other possibilities include incompatible motherboard, or some type of hardware failure (bad motherboard, USB stick, PSU, CPU, controller, etc.).

 

Hope this is helpful.  Please post your results and we can discuss next steps.

 

One final comment, please realize that the forum consists of users like you.  Many here will offer helpful advice, free of charge.  Threats to move to another NAS aren't very effective in this setting.  And if you are having a hardware problem, moving to another NAS may result in similar problems.  Please treat us as peers and not a company support organization and you'll get a lot of help here.

 

Good luck!

 

Kernel errors are most frequently affiliated with bad memory, but a corrupted file-system can also result in a kernel error.

 

As already described, a memory test is the first step.  memory strips need specific timing, voltage and clock speed based on their individual model/brand.

 

Most BIOS get it right and automatically set the correct values, some do not, especially if you have premium memory that requires special value for optimal performance.

 

Since the file-transfer via the LAN would use different memory possibly than copies on the server, it is worth a check.

 

It might also be a driver issue with the chipset used for your LAN connectivity.  Are you using the newest version of unRAID?  If not, you might check to see if a newer driver is included in it.    if you have an old LAN card it might be worth a try. (you'll have to disable the built-in NIC on the motherboard to use the alternate one)

 

Any clue you can give will help.  A picture of the "crash" on your screen will possibly help to identify what was involved in causing it.

 

Joe L.

Ok first I never thretand anything. I simply stated a fact that my data is critical and I need it fast. If I need to move to a new OS temporaraly till this issue is solved then I will.

 

Second I already said I tested my memory. I also would like to point out that a memory problem does not make any sense in this situation as it would show up when I move data via putty. It would also show up when I transfer data TO and FROM the server.

 

Moving on here are the awnsers to your questions:

 

1. Yes the data transfer problem went away when I updated Unraid to 4.6. I have no problem tranfering data TO and FROM the server at over 50mps a second. The only problem arises when I attempt to move data from one folder to another on the server via windows.

 

2. My system is as follows:

Mother Board: Asus M4A89GTD Pro/USB3

CPU: AMD Athlon II X4 600e

RAM: Kingston HyperX 4GB (2*2GB) KHX1333c7ad3k2/4g

USB Hub: NZXT Internal USB Hub

Flash Stick: Lexar that came from Unraid.

SATA Controler: Supermicro AOC-SASLP-MV8 1 SAS cable conected

 

Hard Drives:

1 2TB WD Green for Parrity

2 2TB WD Green Storage

3 1.5TB WD Green Storage

2 1TB WD Green Storage

 

3. My Unraid Pro stick came with Unraid 4.5 installed and I used the istructions on this fourm to install 4.6. I also installed allot of programs mostly following the guide here:http://lime-technology.com/wiki/index.php?title=Configuration_Tutorial

 

4. I did as you asked and crashed the system well logging the syslog tail. Please keep in mind it will take nearly 9 hours to recheck parrity now, so further tests will have to wait till tommorow. I have attached the log, and here is the tailings from putty:

 

login as: root

[email protected]'s password:

Linux 2.6.32.9-unRAID.

root@Candle-Keep:~# cp /var/log/syslog /boot/syslog.txt

root@Candle-Keep:~# chmod a-x /boot/syslog.txt

root@Candle-Keep:~# tail -f /var/log/syslog

Dec 31 05:43:46 Candle-Keep kernel: mdcmd (31): spindown 7

Dec 31 05:43:47 Candle-Keep kernel: mdcmd (32): spindown 8

Dec 31 06:37:13 Candle-Keep ntpd[1598]: no servers reachable

Dec 31 09:28:03 Candle-Keep ntpd[1598]: synchronized to 209.17.190.116, stratum      2

Dec 31 09:59:26 Candle-Keep sshd[3027]: error: Could not get shadow information      for root

Dec 31 09:59:26 Candle-Keep sshd[3027]: Accepted password for root from 192.168.     1.101 port 49321 ssh2

Dec 31 09:59:26 Candle-Keep sshd[3031]: lastlog_filetype: Couldn't stat /var/log     /lastlog: No such file or directory

Dec 31 09:59:26 Candle-Keep sshd[3031]: lastlog_openseek: /var/log/lastlog is no     t a file or directory!

Dec 31 09:59:26 Candle-Keep sshd[3031]: lastlog_filetype: Couldn't stat /var/log     /lastlog: No such file or directory

Dec 31 09:59:26 Candle-Keep sshd[3031]: lastlog_openseek: /var/log/lastlog is no     t a file or directory!

Dec 31 10:05:30 Candle-Keep kernel: r8169: eth0: link up

Dec 31 10:06:01 Candle-Keep last message repeated 52 times

Dec 31 10:07:02 Candle-Keep last message repeated 95 times

Dec 31 10:08:03 Candle-Keep last message repeated 96 times

syslog.txt

Another thing I can point out is that I used the system to watch a 1080P DTS Losless 5.1 blueray rip on my boxee box just last night. So a problem with memory or LAN card just does not seem even remotly logical to me.

 

However the Motherboard uses a Realtek RTL8111L Gigabyte Lan Chip. If anyone ahs heard of a problem with this chip let me know.

the massive number of liink status messages indcatews an issue with the NIC. It could be aan interrupt conflict on your MB, or an actual hardware fault.  I suspect a IRQ  conflict.

Can you possibly attach a full syslog immdiately after a fresh boot?

So a problem with memory or LAN card just does not seem even remotly logical to me.

 

And yet here we are... Your syslog indicates otherwise. It shows massive issues related with your NIC. Computer issues never have to be logical, so before you simply dismiss others troubleshooting advice you need to discard any preconceived notions you have.

So a problem with memory or LAN card just does not seem even remotly logical to me.

 

And yet here we are... Your syslog indicates otherwise. It shows massive issues related with your NIC. Computer issues never have to be logical, so before you simply dismiss others troubleshooting advice you need to discard any preconceived notions you have.

 

I thank you Joe L for actually being helpful and not calming that I'm insinuating something.

 

As for the rest of you people, you are very defensive first saying I'm threatening you and now implying I "dismiss others troubleshooting advice you need to discard any preconceived notions you have." harassing someone like that for no reason when all they are doing is asking for help for software they paid for is not only unhelpful but detrimental to your community, and the company.

I'm sorry BRiT if you and me are butting heads simply because we are not understanding each other. When I say I think something does not make sense and say why I am just explaining my logic which is part of my trouble shooting. I am not trying to belittle your trouble shooting.

 

My logic says if I can transfer 10TB of data to a server then the NIC must work. But Transferring a 1meg file from one folder to another crashes the entire system because the NIC is crap? There is a serious logic flaw there which is why I posted my logs and asked for help.

 

When my parity check is complete I will post the log. If it is the NIC, what NIC should I buy? I will most likely have to special order and it will take  a week or more (thanks to the holiday) to get here so I need to make sure what I get will work.

I'm sorry BRiT if you and me are butting heads simply because we are not understanding each other. When I say I think something does not make sense and say why I am just explaining my logic which is part of my trouble shooting. I am not trying to belittle your trouble shooting.

 

My logic says if I can transfer 10TB of data to a server then the NIC must work. But Transferring a 1meg file from one folder to another crashes the entire system because the NIC is crap? There is a serious logic flaw there which is why I posted my logs and asked for help.

 

When my parity check is complete I will post the log. If it is the NIC, what NIC should I buy? I will most likely have to special order and it will take  a week or more (thanks to the holiday) to get here so I need to make sure what I get will work.

 

Did your problem get resolved?

 

Personally, when I'm looking for help, I try to do each and every step requested, even if I have done the tests before OR I see little value in the test, and then I report the results factually without trying to interpret.  It double checks that my tests were valid and gives the other person the datapoints to perform their independent troubleshooting process, without me interjecting my own biases.  While there are certainly limitations (I'm not likely to take out my soldering iron), this has proved pretty effective to me over the years.  YMMV

OK I am having a very serious problem that is making me doubt my switching to Unraid.

 

Basically if I attempt to move any files from one folder on the server to another through windows the system automatically give a kernel error and hard locks.

 

I can move data TO and FROM the server and I can move data around on the server through MC in Putty. But if I attempt to move so much as a single file via windows the whole system crashes instantly.

 

So WTF could be causing this? If I cannot get this fixed fast I will need to look into alternatives as I cannot go without access to the data on the server.

 

If you need any logs or something to help please tell me what you need as I'm not sure how to troubleshoot Linux very well.

 

What version of Windows and how are you doing the move?  I'd like to try and reproduce what you are doing.  For example, I opened two windows here on an Win7 PC, one shows files on server disk1, the other on server disk2.  Then did a drag of some video files from disk1 to disk2.  The transfer worked ok.  Are you doing something like that?