Is any error count besides 0 considered abnormal for any disk? I'm testing out a new UnRaid build. I quickly noticed that one of the old drives being tested is generating errors under disk status, and when copying files from Windows to the server I suddenly get the error

 

"There is a problem accessing \\tower\Share

Make sure you are connected to the network and try again"

 

But I can access \\tower and see the shares.

 

No, disk errors are not normal.  Post a syslog.

I rebooted the machine unfortunately. I'll try to reproduce the error and post the log. Right now it's running the pre-clear script.

 

...

Probably a bad drive. Hopefully problems will go away after it's out of the system.

I seem to be having the same issue on the "There is a problem accessing \\tower..." when doing some transfers from windows.  My non-parity drive is a WD EARS 2.0TB and I have the 7-8 Jumper in place.  Sometimes it takes a while to access the \\tower but most of the time it can see it, though on large file transfers it continuously gives those errors, is that a drive issue?

I seem to be having the same issue on the "There is a problem accessing \\tower..." when doing some transfers from windows.  My non-parity drive is a WD EARS 2.0TB and I have the 7-8 Jumper in place.  Sometimes it takes a while to access the \\tower but most of the time it can see it, though on large file transfers it continuously gives those errors, is that a drive issue?

No way to know because you did not attach a copy of your syslog from the period when the transfer was not possible.

 

Far more likely to be a network issue.  \\tower would be using your network's "master browser" and it only scans the network a few times each half hour.

Joe,

 

I will try doing some transfers so I can generate the error, I can try from both my win7 Laptop via wireless N and the vista desktop connected via gige.  I also forgot to mention but I get the same error when transferring to \\ip-address\share and I have set settings to "local master" yes and no with the exact same results, I am wondering if there is something funky with my disk1 which is the EARS drive.

 

Ok, so attempt transfers, do you want to see from both laptop and desktop and then post the syslog from unmenu?  Should i attach it as a file or post to pastebin or any preferred method?

From my desktop to //tower  I was able to get the error to come up, though this time it went longer than the past 10+ tests i had done yeserday, attached is the syslog as or right now after the fail.

 

Here is a copy/paste of the last few lines on pastebin http://pastebin.ca/1934510

 

I then attempted from my win7 laptop a 1.6gb file and I copied syslog info into pastebin up until that time.

 

http://pastebin.ca/1934518

 

I hope this helps somehow.

I'm still getting the error. The server actually becomes inaccessible and I have to reboot. One abnormal thing was that after reboot one of the two data drives was taking a long time to mount before the array became ready again. This has happened a couple times. No syslog yet since I forgot you don't need telnet to get it.

I reproduced the error and the system froze with no possibility of input. Below is a picture of the message on the monitor at the time:

 

I'm guessing this is a hardware issue. But what could it be, any suggestions?

 

Attached is a syslog moments before the crash. UnMenu highlighted some questionable lines such as:

Sep 6 22:54:29 Tower kernel: ACPI Error (dswload-0781): [PRID] Namespace lookup failure, AE_ALREADY_EXISTS
Sep 6 22:54:29 Tower kernel: ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20090903/psloop-230)
Sep 6 22:54:29 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\] (Node c14760c8), AE_ALREADY_EXISTS
Sep 6 22:54:29 Tower kernel: ACPI: Marking method \___ as Serialized because of AE_ALREADY_EXISTS error
...
Sep 6 22:54:29 Tower kernel: ACPI Warning: Incorrect checksum in table [OEMB] - 22, should be 21 (20090903/tbutils-314)

syslog-2010-09-07.txt

Shawn, what mb are you using?  I had a similar issue that I resolved by disabling the onboard nic and using a slot based one.  I believe there were IRQ issues with an interrupt being shared by the onboard nic and sata controller.

 

If you have a nic lying around, might be worth it to try.

Mine does not do a total freeze, it just gives the error as described:

"There is a problem accessing \\tower\Share

Make sure you are connected to the network and try again"

 

It has a try again button and you can try again but it will eventually error as well and do the same thing, this happens on all large transfers including the backups so its rather concerning.  The shares can be seen etc, but it seems like it jams up a little bit sometimes.  Should I try uninstalling any of the packages from unMenu? Would it possibly be because of my EARS drive? Its just really annoying and I cant transfer my big files over to the unraid server because of this.

Shawn, what mb are you using?  I had a similar issue that I resolved by disabling the onboard nic and using a slot based one.  I believe there were IRQ issues with an interrupt being shared by the onboard nic and sata controller.

 

If you have a nic lying around, might be worth it to try.

 

It's a new ASUS M4A89GTD PRO/USB3, with AMD 890GX northbridge and SB850 southbridge, LAN chipset Realtek 8111E. While computer rebooted itself more than once and I suspected a memory issue. Reset the memory, ran Memtest, no problems there. I'm trying some transfers to let the problem reoccur.

...Problem reoccured.

 

I'm trying an old NIC, but unRaid doesn't recognize it even though the network light is on. I've disable onboard NIC, still can't access it from the network.

 

Question: if I simply exchange the motherboard with an identical model, will the problem likely persist?

 

Update: my supplier tested the board and concluded that it was defective.

I got the Plus version the other day and added a cache drive and that seemed to stop my issues, I think it was that EARS drive that even with the jumpers still was causing issues.  With the cache drive it now allows all the huge transfers, teh only downside is my cache drive heats up to 52c pretty easily for some unknown reason, but at least my unraid works now.