I recently changed out the motherboard, processor, & RAM on my system.  The system boots up fine and I can get to the web interface and I've reassigned the drives to the logical locations they were on the previous system.  The problem I'm having is that I can access the shares from my desktop and see the files and folders, but I'm unable to open any of them.  Windows Explorer and my media play both hang up when I try to open a file.  I've also tried bypassing the user shares and tried accessing them through the disk shares, but that has the same result.

 

I don't know if it matters, but with the motherboard change came a different Ethernet adapter. Something else I might add is that in the process of changing the board, I accidentally reversed the pins on my internal USB adapter and fried my flash drive.  Thankfully I had recently made a back up and Tom issued me a new key for the new flash drive.

 

As a test to see if I could access the files using any method, I accessed the system using WinSCP and was able to successfully copy some files to my desktop and them open them from there.

 

Also, I'm running unRAID version 4.7 and I've attached the syslog.

 

Let me know if I need to provide more information and I really appreciate any input anyone may have.

 

Thanks.

syslog.txt

run a memtest on the system at least overnight.  Preferably as long as 24 hours.

The memtest ran for more than 24 hours with no errors.  The problem persists. 

 

I've attached an error message I got from Windows when I tried accessing a file from one of the shares.  I've also attached an up to date syslog.

 

Would a fresh install of unRAID run a risk of corrupting the data on the drives.

 

Thanks.

syslog.txt

run a resiserfsck --check on every drive and see if there is any disk corruption.

Got the checks completed.  As per the instructions on the Check Disk Filesystems page, I checked all of my drives except for the parity drive.  All tests came back as "No corruptions found"

 

I haven't run a parity check on this array since swapping out the hardware.  Should I or shouldn't I let the parity check run?

 

Anything else I can check?

 

Thanks for the help.

I haven't used an Atheros nic myself but it seems the Atheros driver included with 4.x isn't terribly robust. Somewhere between "good luck" and "might work". Your syslog doesn't show anything interesting. Could you grab another after a few failed accesses? Are you seeing any errors at the console? Do you have another nic you could try?

Many thanks to both of you!!!

 

I installed the same NIC I was using in the previous system and my new system now works great.  Would it be possible to update the Atheros driver so I might be able to use the on-board interface?