I've had 5.0b6a running for the last week okay, but this morning my three windows 7 machines cannot access the unraid server. When I try to navigate to it in explorer, I get a network "error code: 0x80070035. The network path was not found."

 

Actually now, the server is not even showing up in the Network places in Windows. I can't access the webui (either by typing the servername or ipaddress).

 

I did kick off 4 preclear processes last night. That shouldn't affect anything though right?

 

I'm fairly new to this, so I'm not sure where to start troubleshooting... Thanks

If you can telnet in and pull the syslog for us.  We can't really help much without it...  there are instructions in a thread above this one that is sticky'ed.

 

Also:

1. Have you run memtest?

2. What version of unRAID are you running?

3. Please provide a full hardware breakdown of your server

A couple of easy steps that may help until you get more information-

http://www.petenetlive.com/KB/Article/0000439.htm

 

 

 

If you can telnet in and pull the syslog for us.  We can't really help much without it...  there are instructions in a thread above this one that is sticky'ed.

 

I couldn't telnet it. And I tried to access the server directly in the console and I couldn't see anything. I ended up just doing a hard shut down and powered the server on again. It's doing a parity sync now. And I can see the server again from Windows, but I'm not sure what the problem was. I followed the instructions to pull a syslog of whatever I have now.

 

1. Have you run memtest?

 

No. How do I do that. And should I wait for the parity sync to finish?

 

2. What version of unRAID are you running?

 

5.0-beta6a

 

3. Please provide a full hardware breakdown of your server

 

Motherboard: MSI 880GMA-E45

CPU: AMD Sempron 140

RAM: Corsair XMS3 4GB DDR3 1333

PSU: Corsair CX430

Expansion Card: Supermicro AOC0SASLP-MV8

Hard Drives: 2 x Western Digital 2TB WD20EARS, 2 x Hitachi 2TB Desktar 5k3000

 

Those hard drives were new. They're connected to the motherboard sata slots, and I precleared them, then assigned to unraid. And things were running fine. Then last night I connected 4 hard drives from a previous computer (1 x 2TB WD20EARS, 1 x 1TB WD10EADS, and 2 x 2TB WD20EADS) to the Supermicro card and kicked off preclear processes for each . This morning was when I couldn't access the server, and I eventually just shut her down.

 

Is there something I need to do before I preclear these disks because they have been previously used in a Windows system?

 

Thanks again.

syslog.zip

I have a different MSI board, but I use the XM3 memory.  Let me share my experience.  The XM3 (at least my version) has timings rated at 8-8-8-24.  The SPD timings on the ram are 9-9-9-24.  SO basically, your MB is supposed to detect the settings from the SPD and run the RAM slower than rated, which normally makes it more stable.

 

But on my MSI board, when I would run memtest+, it would report that the timings being used were 8-8-8-20, with everything set to [Auto] in the BIOS.  This caused me to have errors in memtest, which can cause stability problems/data corruption with unRAID.

 

So I set my BIOS to set the timings based on SPD.  I wasn't looking to squeeze out every last inch of performance, so I thought slower would be more stable (usually it is).  I was wrong.  Memtest+ did report the correct 9-9-9-24, but it still gave errors (different than the previous errors).

 

So I went back to my BIOS and set the timings manually to 8-8-8-24.  There was also a bug in the BIOS where you couldn't pick 24 in the pulldown list.  It would only give you the option for [Auto] if you used the arrow keys.  But if you used +/-, you could pick 16-30.  Sort of weird, since all the other timings could be selected by arrow key.  Anyway, memtest+ then reported the correct 8-8-8-24 timing.  I ran 7 full memtest cycles and the RAM passed them all with 0 errors.

 

Since you are using an MSI board and similar XM3 memory, you may want to run a memtest to see if it is reporting the memory timings that your RAM modules are rated for.

I just finished running 3 memtest cycles with no errors.

 

Is there any reason I can't preclcear my four old drives again? I don't want the system to crash again...

I've had 5.0b6a running for the last week okay, but this morning my three windows 7 machines cannot access the unraid server. When I try to navigate to it in explorer, I get a network "error code: 0x80070035. The network path was not found."

 

Actually now, the server is not even showing up in the Network places in Windows. I can't access the webui (either by typing the servername or ipaddress).

 

I did kick off 4 preclear processes last night. That shouldn't affect anything though right?

 

I'm fairly new to this, so I'm not sure where to start troubleshooting... Thanks

 

Well, I got this error this morning, but with completely different symptoms.  At 3:15 am, I was moving files to unRAID just fine with a Windows 7 machine.  No errors at all.  At 7:15 am, I tried to access my unRAID machine, and the Windows 7 machine gave me the exact same error.  However, it still showed up in Network places.  I could also still web into the UI and into unMenu.  I just couldn't access any of the shares through samba.

 

However, the error is a bit odd.  My W7 machine could still access my two Dune players through samba shares.  My first thought was that samba had crashed on the W7 machine, but since it was working with the two Dunes, probably not the case.  That led me to think it was something in my unRAID machine.  However, my two Dune players could still access and play back from my unRAID using samba.

 

So my W7 machine could access my Dune players.  And my Dune players could access my unRAID.  But my W7 machine could not access my unRAID.  I rebooted my W7 machine and unRAID at the same time (wished I had done them one at a time) and after the reboots, everything was back to working fine.

 

There was nothing in the syslog.  Mover ran at 3:30 am and moved a bunch of files.  After the moves, my HDD's spun down.  There were no further entries in the log after the spindowns.

Okay.  So I just had this same error again, exactly as described before.

 

But now I'm thinking it could be a problem with unRAID.  No matter how many times I tried to access my user shares, I kept getting that same message.  So I tried accessing the disks, which are hidden, read only.  It accessed every disc perfectly.  When I tried the user shares again, they worked with no problem.

 

So either it was happy coincidence that everything just starting working the instant I decided to access a disk share, or something in doing so got user shares working again.

I haven't had the issue so far since I rebooted my server. I would like not to encounter this issue, but if I do, I will try to duplicate this behavior and confirm.