NASLite Network Attached Storage

Well, thats why we need the rest George, there may be a interrupt conflict with the nic card.

Which may be causing :

Feb 20 20:34:48 [5] atl1c 0000:02:00.0: Unable to allocate MSI interrupt Error: -1
Feb 20 20:34:48 [2] atl1c 0000:02:00.0: atl1c: eth0 NIC Link is Up<1000 Mbps Full Duplex>

I was tongue-in-cheek and should have used a

Anyway ... glad to help the OP investigate ...

I also have had many more issues with AMD based boards rather than Intel. The issues have been more of the I just refuse to boot or don't see the NIC type than corrupted packets.

Mike

This issue is most likely network related. The services will not run if the hardware was flawed. My bet would be that server, router or client is not full duplex.

I will start by isolating the server with a single client using a switch or crossover. That way there is no variables other than the attached elements.

Then verify that the nas and the client are both using full duplex.

That would be where I start and will follow with a different NIC in the nas. Another item of importance may be to reset the BIOS to defaults in case there are strange or incompattible setings.

Hope the above helps.

Replaced mainboard & CPU

Board: ECS MCP61PM-HM
CPU: AMD Athlon

Now it works

interesting - in doing that did you effectively change the network card - are they both onboard - or is it the same card transferred from one motherboard to the other

if they are onboard then a new card could have resolved it

Asus (original) board: I tried both onboard GB NIC and added GB NIC.

I could not get the added card to work at all. It is a known good D-Link card. I do not know what the problem was with this card. I tried NL "First" and "Last" eth settings but perhaps I didn't know what I was doing there. There did not seem to be anything in the BIOS that needed to be changed for an added NIC.

Elite CS (working) board: Onboard 10BaseT.

i would have thought bios would be to turn off the onboard nic rather than a setting to add the new one

In looking at the Asus manual I see that there is such a setting and I missed it.

I may add the faster NIC to the ECS board.

When turning off on-board NIC ... it may affect "First" versus "Last" eth settings; confirm by checking SYSLOG. Also don't forget to SAVE CONFIGURATION and reboot.

In the past I have had to move the NIC from one PCI slot to another to get it to work. In some cases it just wouldn't work at all and I ended up changing the NIC or the motherboard. Glad to hear that you got it working.

Mike

And thumm up to Tony for having found that it was a LAN problem He knows his software

Robby

To set the record straight, we do not know that the LAN was the cause of the problem. This thread had several posts about the NIC card because I was asked about it. I did no test that established NIC as the cause.

Rather than continuing to experiment with the Asus board, and trying to determine whether its NIC was the issue, I replaced it with an older board (ECS) that I had in the closet. The cause of the problem may well have been the Asus NIC or other LAN elements, but it remains unidentified.

If the problems were internal (CPU, RAM, Logic), then your system would likely fail during the boot process. The data corruption you are seeing is therefore caused during communication to/from the client, so the most-likely cause would be the NIC.

There was some sort of interrupt problem with the nic from the snippet of syslog, without seeing the rest, we couldn't tell if it was a IRQ conflict, or just a bad NIC.

IRQ conflicts will still let the NIC function, but with unexpected results.