no Gigabit on using 0.1RC3 nic speed only 100Mb/s

[Danny Crasto]

I can't get gigabit to work.

I changed the cable used a verified working gigabit cable.

Any ideas?

Also, the status page returns a negative count for the number of mounts for fsck to run.

# ethtool eth0

Settings for eth0:

        Supported ports: [ TP AUI BNC MII FIBRE ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: No

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: No

        Advertised auto-negotiation: Yes

        Speed: 100Mb/s

        Duplex: Full

        Port: MII

        PHYAD: 8

        Transceiver: external

        Auto-negotiation: on

        Link detected: yes

Mounted Filesystems

Dev.	Label	Capacity	Available	FS	Mode	Dirty	Automatic FSCK in
md1		2.7TB	1.1TB	ext4	RW		-38 mounts or

[João Cardoso]

On Saturday, March 1, 2014 9:10:32 AM UTC, Danny Crasto wrote:

I can't get gigabit to work.

I changed the cable used a verified working gigabit cable.

Any ideas?

Have you tried plugging the cable into another switch/router input? It has to be some hardware related issue.

 

Also, the status page returns a negative count for the number of mounts for fsck to run.

Can you please post the output of of 'tune2fs -l /dev/md1' *before* trying anything else?

This has been reported before but never fully diagnosed.

The relevant outputs are:

Mount count:              xx

Maximum mount count:      yy

Under Disk->Filesystem you can set the desired "Maximum mount count", and how that is handled depends on the fsck program (at mount time, so you have to stop all services, unmount and remount the filesystem -- or reboot):

      -c max-mount-counts

              Adjust  the  number  of  mounts  after  which  the  filesystem  will  be checked by

              e2fsck(8).  If max-mount-counts is 0 or -1, the number of times the  filesystem  is

              mounted will be disregarded by e2fsck(8) and the kernel.

              Staggering  the  mount-counts  at which filesystems are forcibly checked will avoid

              all filesystems being checked at one time when using journaled filesystems.

              You should strongly consider the consequences  of  disabling  mount-count-dependent

              checking entirely.  Bad disk drives, cables, memory, and kernel bugs could all cor-

              rupt a filesystem without marking the filesystem dirty or in  error.   If  you  are

              using journaling on your filesystem, your filesystem will never be marked dirty, so

              it will not normally be checked.  A filesystem error detected by  the  kernel  will

              still  force  an fsck on the next reboot, but it may already be too late to prevent

              data loss at that point.

       -C mount-count

              Set the number of times the filesystem has been mounted.  If set to a greater value

              than  the max-mount-counts parameter set by the -c option, e2fsck(8) will check the

              filesystem at the next reboot.

[Danny Crasto]

On Saturday, March 1, 2014 8:15:57 PM UTC+4, João Cardoso wrote:

On Saturday, March 1, 2014 9:10:32 AM UTC, Danny Crasto wrote:

I can't get gigabit to work.

I changed the cable used a verified working gigabit cable.

Any ideas?

Have you tried plugging the cable into another switch/router input? It has to be some hardware related issue.

I will am going to get my hands on another switch and try this option. Currently all other devices that are plugged into the router the nas is plugged into report 1Gbit. I will report the results

You were right. I ran tune2fs and max-mount-count reported -1 which is disabled. So I did a 

```tune2fs -c 40 -i 3m /dev/md1```

to set it to 40 mounts and 3 months respectively.

Thank you a for your quick response and I will report back on NIC speed issue. 

Cheers,

- danny 

[João Cardoso]

On Sunday, March 2, 2014 7:15:28 AM UTC, Danny Crasto wrote:

On Saturday, March 1, 2014 8:15:57 PM UTC+4, João Cardoso wrote:

On Saturday, March 1, 2014 9:10:32 AM UTC, Danny Crasto wrote:

(...)

 

Mounted Filesystems

Dev.	Label	Capacity	Available	FS	Mode	Dirty	Automatic FSCK in
md1		2.7TB	1.1TB	ext4	RW		-38 mounts or

You were right. I ran tune2fs and max-mount-count reported -1 which is disabled. So I did a 

```tune2fs -c 40 -i 3m /dev/md1```

to set it to 40 mounts and 3 months respectively.

Thanks for reporting back! I was able to reproduce it.

If however I go to Disk->Filesystems and hit the Submit button in "Set mounted filesystems to be checked every", then the situation becomes fixed and the Status page shows the correct value.

*But* if the current mount count is already greater than the maximum count, the above does not fixes it and the displayed value in the Status page continues negative. I have now fixed it.

Thanks

[Danny Crasto]

I had to do a ```tune2fs -T now /dev/md1``` to reset the time field to get the time field to not be negative. Now it looks good. Cheers 

[Danny Crasto]

On Saturday, March 1, 2014 8:15:57 PM UTC+4, João Cardoso wrote:

On Saturday, March 1, 2014 9:10:32 AM UTC, Danny Crasto wrote:

I can't get gigabit to work.

I changed the cable used a verified working gigabit cable.

Any ideas?

Have you tried plugging the cable into another switch/router input? It has to be some hardware related issue.

Ok. So I got my hands on a gigabit switch that I verified works. I route the NAS through there and the network doesn't even come up. (network status is orange).

Also, I don't know if it's related, DHCP will not work if I set it on the NAS. I have to statically specify the IP address.

[João Cardoso]

On Sunday, March 2, 2014 5:01:32 PM UTC, Danny Crasto wrote:

On Saturday, March 1, 2014 8:15:57 PM UTC+4, João Cardoso wrote:

On Saturday, March 1, 2014 9:10:32 AM UTC, Danny Crasto wrote:

I can't get gigabit to work.

I changed the cable used a verified working gigabit cable.

Any ideas?

Have you tried plugging the cable into another switch/router input? It has to be some hardware related issue.

Ok. So I got my hands on a gigabit switch that I verified works. I route the NAS through there and the network doesn't even come up. (network status is orange).

it seems that you box has some marginal hardware specs. Try several cables. Yes, I know...

Let me share my oddest experience with network cables (copied from another post):

Let me share my oddest experience with network cables (copied from another post):
I have an HP network printer at my home.I always was able to print and scan from it using my linux box, but my wife always had trouble using it with her MS-Vista computer.
Every two or three months the printer software was re-installed, hot-fixes and updates applied, quirks done... but printing was always slow, some pages where not fully printed... and problems returned after a while. Two or three months latter I feel "pity" of my wife and retried everything again.  F#$! MSW, I often scream
And printing and scanning from my linux computer and laptop always without a problem!
One day I decided, don't know why, to change the printer network cable and voilá! the printer started printing fast and without problems from MS-Vista.
I'm now using the defective network cable (yes, it is defective!) with my linux laptop, without any problem.
Most people must think "he's nuts, the network cable was just fine, how could it get damage suddenly? I didn't mess with it!". But they don't think that it's strange that a light bulb stops working suddenly!
So, I think I know how do you feel, it looks like network-cable problems defy logical reasoning :-)

 

Orange network led? 10Mbps? Never heard. What hardware rev do you have?

 

Also, I don't know if it's related, DHCP will not work if I set it on the NAS. I have to statically specify the IP address.

Must be related.

 

# ethtool eth0

Settings for eth0:

        Supported ports: [ TP AUI BNC MII FIBRE ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: No

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: No

        Advertised auto-negotiation: Yes

        Speed: 100Mb/s

        Duplex: Full

        Port: MII

        PHYAD: 8

        Transceiver: external

        Auto-negotiation: on

        Link detected: yes

As you can see everything is OK regarding capabilities. You could use 'ethtool' to disable autonegotiation and force a given speed, but I doubt it's advisable.

[Danny Crasto]

On Sun, Mar 2, 2014 at 10:39 PM, João Cardoso <whoami...@gmail.com> wrote:

>
>
> On Sunday, March 2, 2014 5:01:32 PM UTC, Danny Crasto wrote:
>>
>>
>>
>> On Saturday, March 1, 2014 8:15:57 PM UTC+4, João Cardoso wrote:
>>>
>>>
>>>
>>> On Saturday, March 1, 2014 9:10:32 AM UTC, Danny Crasto wrote:
>>>>
>>>> I can't get gigabit to work.
>>>> I changed the cable used a verified working gigabit cable.
>>>> Any ideas?
>>>
>>>
>>> Have you tried plugging the cable into another switch/router input? It
>>> has to be some hardware related issue.
>>
>>
>> Ok. So I got my hands on a gigabit switch that I verified works. I route
>> the NAS through there and the network doesn't even come up. (network status
>> is orange).
>
>

> it seems that you box has some marginal hardware specs. Try several cables.
> Yes, I know...
>

> I have a network printer that worked fine with linux but with occasional
> (sometimes frequent) MS-Win failures; after replacing/trying several cables
> the issue with MS-W disappeared (the *defective* cable is still working fine
> connected to another equipment)

>
> Orange network led? 10Mbps? Never heard. What hardware rev do you have?

It's running revision B1.

>
>>
>> Also, I don't know if it's related, DHCP will not work if I set it on the
>> NAS. I have to statically specify the IP address.
>
>

> Must be related.

Will try and do some on the device debug ... and keep the thread updated.

>
>>>>
>>>> # ethtool eth0
>>>> Settings for eth0:
>>>> Supported ports: [ TP AUI BNC MII FIBRE ]
>>>> Supported link modes: 10baseT/Half 10baseT/Full
>>>> 100baseT/Half 100baseT/Full
>>>> 1000baseT/Full
>>>> Supported pause frame use: No
>>>> Supports auto-negotiation: Yes
>>>> Advertised link modes: 10baseT/Half 10baseT/Full
>>>> 100baseT/Half 100baseT/Full
>>>> 1000baseT/Full
>>>> Advertised pause frame use: No
>>>> Advertised auto-negotiation: Yes
>>>> Speed: 100Mb/s
>>>> Duplex: Full
>>>> Port: MII
>>>> PHYAD: 8
>>>> Transceiver: external
>>>> Auto-negotiation: on
>>>> Link detected: yes
>>>>
>

> As you can see everything is OK regarding capabilities. You could use
> 'ethtool' to disable autonegotiation and force a given speed, but I doubt
> it's advisable.
>
>
>

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Alt-F" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/alt-f/l9nmh_9bBFc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> alt-f+un...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/alt-f/9788f7a8-eb0d-4cc1-ae06-1f08596fd20f%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[João Cardoso]

On Sunday, March 2, 2014 6:57:15 PM UTC, Danny Crasto wrote:

(...) 

>>>> I can't get gigabit to work.
>>>> I changed the cable used a verified working gigabit cable.
>>>> Any ideas?
>>>
>>>
>>> Have you tried plugging the cable into another switch/router input? It
>>> has to be some hardware related issue.
>>
>>
>> Ok. So I got my hands on a gigabit switch that I verified works. I route
>> the NAS through there and the network doesn't even come up. (network status
>> is orange).
>
>
> it seems that you box has some marginal hardware specs. Try several cables.
> Yes, I know...

(...)  

> Orange network led? 10Mbps? Never heard. What hardware rev do you have?

It's running revision B1.

My box is a rev-B1 and I never saw the network led in any other color than blue. Sure it's a rev-B1? sure isn't an amber disk led that glows through?

Even when using

ethtool -s eth0 speed 10 duplex half

ethtool -s eth0 speed 100 duplex full

it's always blue.

[Danny Crasto]

Yup, it's B1 for sure. There is no color bleed through. It's
amber/orange and when I do a ```ethtool -s eth0 speed 1000 duplex full
&& ethtool eth0``` the network doesn't come back up and then I have to
restart the device.

>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Alt-F" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/alt-f/l9nmh_9bBFc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> alt-f+un...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/alt-f/5922350f-8d35-46a7-8e82-49aef0991335%40googlegroups.com.

[Danny Crasto]

So I tried several cables with the same result. I can't get gigabit.

The attached picture is an image of the orange/amber NIC when I either connect the nas to a gigabit switch, or ethtool set the speed to 1000. I also tried to ethtool set autoneg off and it network didn't comeback up. Anymore ideas? Does RC4 have any NIC fixes?

Cheers,

> alt-f+unsubscribe@googlegroups.com.

[João Cardoso]

On Wednesday, March 5, 2014 5:17:03 PM UTC, Danny Crasto wrote:

So I tried several cables with the same result. I can't get gigabit.

You can power-off the box, remove the disks, power-on and see if the issue persists.

You can then, without disks (just to be in the safe side), flash the D-Link firmware and see if the issue persists.

Neither the Alt-F nor D-Link fw needs disks in order to work.

 

The attached picture is an image of the orange/amber NIC when I either connect the nas to a gigabit switch, or ethtool set the speed to 1000. I also tried to ethtool set autoneg off and it network didn't comeback up. Anymore ideas? Does RC4 have any NIC fixes?

No, can't fix what isn't damaged (for most of us)

 

> alt-f+un...@googlegroups.com.