ombraweb

I am currently using a NORCO RPC-2212 as my secondary case and am looking to replace it with a 2U 6-12 drive chassis but am having difficulties finding something that is actually available in stock at stores. 2 alternatives I have been looking at are: Chenbro RM23608 Chenbro RM245 But of course I cannot find these to purchases. Can anyone suggest a good case for this?

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.

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.

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.

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

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?

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.

OK thanks, that's at least one problem solved easily.

I am getting the error "Could not get shadow information for root (Errors)" what does this mean?

One question about doing this. If I re-enable the onboard SATA drives can I move the hard drives currently on the SAS to the Onboard ports? I would do this just to make it easy for me to follow which drives are 1, 2 and so on. So can you move a drive to a new port? If you can do you need to do anything special? How would this effect a share split across multiple drives?

I could have sworn that NCIX did not have any. Now I see they do, but $40 for something I was paying $5 for :-( As for the problem I am having with AMD chipsets, michellembrodeur is my roommate so the problem she is talking about is my problem. I work all ay and did not know they had found a solution. If it works I'm sending the second sata board back.

Yes I'm in Canada and no one here has it in stock. Thats why I need an alternitive. But if anyone can find it avalable at a reputable canadian source that I could get ASAP I'd be gratefull.

I set up my system with only one breakout cable assuming I could use the onboard SATA to cover all my drives. Unfortunately the onboard SATA had to be disabled since Supermicro cards do not work with newer AMD chips. So now I need 3 more breakout cables, but of course they are now backordered until the new year. So can someone recommend a good alternative, and one that wont cause any compatablity issues, to this 4 connector breakout cable: 3Ware CBL-SFF8087OCF-05M SFF-8087 to Discrete Forward Breakout Cable

Thanks I will try updating. But is there a guide to how to update?

I attempted to capture the panic, but the dam pic did not turn out :-( The version I am using is 4.5.6 as that is what came on the stick when I bought it. My currect plan is to wait for a parity check, then I will load up SMART software and duble check the drives. Shuld upgrading fix the problem? normally I do not use RC on my working server but if it would correct the issue I would be willing.