SFN wrote

Model : T2600G-28TS

Hardware Version : 1.0

Firmware Version : 1.0.1 Build 20160412 Rel.57988(s)

ISP :

Hello

since a few time , this switch did not worked anymore, which led to much confusion and angry customers.:mad:
We are running the latest, available FW:

T2600G-28TSv1_en_1.0.1_[20160412-rel57988]_up.bin

A deeper view into switch via console at startup , shows the following messages:


Hit any key to stop autoboot: 0

Begin to startup system, please wait a moment...
chmod: /tplink/exe/app/sbin/app_to_scm_channel: No space left on device
chmod: /tplink/exe/app/sbin/cli_server: No space left on device
chmod: /tplink/exe/app/sbin/core: No space left on device
chmod: /tplink/exe/app/sbin/httpd: No space left on device
chmod: /tplink/exe/app/sbin/monitor.cfg: No space left on device
chmod: /tplink/exe/app/sbin/rmso.sh: No space left on device
chmod: /tplink/exe/app/sbin/routed: No space left on device
chmod: /tplink/exe/app/sbin/scm: No space left on device
chmod: /tplink/exe/app/sbin/scm_to_app_channel: No space left on device
chmod: /tplink/exe/app/sbin/scm_to_monitor_channel: No space left on device
chmod: /tplink/exe/app/sbin/snmpd: No space left on device
chmod: /tplink/exe/app/sbin/tpsyslogd: No space left on device
chmod: /tplink/exe/app/sbin/tpsystemd: No space left on device
mknod: /dev/linux-bcm-diag: File exists
mknod: /dev/linux-uk-proxy: File exists
mknod: /dev/linux-user-bde: File exists
mknod: /dev/linux-kernel-bde: File exists
mknod: /dev/tp-eth: File exists
ln: /usr/bin/fw_setenv: File exists


And this repeats until infinity.

Any remedies available?

And will this happen again in future?

I think , this is a big bug and we are afraid, that it will happen to our other T2600G-28TS V1 switches as well
(which we have to setup soon)

BR

Edit: the same issue happens even after doing a 'Reset' in the Boot-Utility.

Weired and unbeliveable unsatisfying!!!

Is there any update on this issue, or can someone help with providing a way to recover the unit. We've had several of these units do this but usually it's possible to switch images.

We'll be looking at replacing at least 15 of these units and NOT with TP-Link as they are proving to be not fit for purpose.

Gus..@SFN 

@Andone 

I can access the BootUtil but being an older version I don't believe I have the option to perform an update.

I'm presented with these 6 options:

0 -Print this menu

1- Reboot

2- Reset

3 - Start

4 - Activate backup image

5 - Display image(s) info

6 - Password recovery

Unless there's a backdoor technique to access more option all I can do is reset (that doesn't seem actually do a reset, as it say it's done reboot and no change)

Gus..

@BoffinGus67 

Hi 

Sorry to let you meet the issue. We want to confirm some information about your problem. 

Do you mean you have 15 T2600G-28TS V1 and all switches will show the below error message when boot?

Begin to startup system, please wait a moment...
chmod: /tplink/exe/app/sbin/app_to_scm_channel: No space left on device
chmod: /tplink/exe/app/sbin/cli_server: No space left on device
chmod: /tplink/exe/app/sbin/core: No space left on device
chmod: /tplink/exe/app/sbin/httpd: No space left on device
chmod: /tplink/exe/app/sbin/monitor.cfg: No space left on device
chmod: /tplink/exe/app/sbin/rmso.sh: No space left on device
chmod: /tplink/exe/app/sbin/routed: No space left on device
chmod: /tplink/exe/app/sbin/scm: No space left on device
chmod: /tplink/exe/app/sbin/scm_to_app_channel: No space left on device
chmod: /tplink/exe/app/sbin/scm_to_monitor_channel: No space left on device
chmod: /tplink/exe/app/sbin/snmpd: No space left on device
chmod: /tplink/exe/app/sbin/tpsyslogd: No space left on device
chmod: /tplink/exe/app/sbin/tpsystemd: No space left on device
mknod: /dev/linux-bcm-diag: File exists
mknod: /dev/linux-uk-proxy: File exists
mknod: /dev/linux-user-bde: File exists
mknod: /dev/linux-kernel-bde: File exists
mknod: /dev/tp-eth: File exists
ln: /usr/bin/fw_setenv: File exists 
 

@Anderson 

Just to confirm we have at least 15 units, and several of them (at least 5) have had this fault & multiple time too.

Before this instance we've been able to recover by using the backup image option, but this time we can't recover at all.

Gus..

@BoffinGus67 

Hi

You said couldn't recover the switch by using  the backup image option. Is there any error messages?  

@Anderson 

I'll have to double check when I get back to the office but from memory it doesn't respond with anything, not even an 'Ok'

Gus..

@BoffinGus67 

Hi

The information returned by console port is important for analysis. Please help to double check. And please check the system LED status at the same time. Thanks for your cooperation. 

@Anderson 

Hi,

Sorry for the delay, below is the console output for request to use backup image:

-- Boot Menu

0 - Print this boot menu

1 - Reboot

2 - Reset

3 - Start

4 - Activate Backup Image

5 - Display image(s) info

6 - Password recovery

Enter your choice(0-6)

tplink> 4

Are you sure to set the Backup Image as Startup Image?[Y/N]:y

Images in system:

index Attribute Size Filename

----- --------- ---------- ---------------------

1 (b) 10485760 image1.bin

2 (*) 10485760 image2.bin

----- --------- ---------- ---------------------

(*) - with the Startup attribute

(b) - with the Backup attribute

tplink>

--

Here's the console output for Password recovery:

--Boot Menu

0 - Print this boot menu

1 - Reboot

2 - Reset

3 - Start

4 - Activate Backup Image

5 - Display image(s) info

6 - Password recovery

Enter your choice(0-6)

tplink> 6

This will delete all the previously created accounts. Continue?[Y/N]:y

Operation OK!

tplink>

--

The only displayed activity is a solid "PWR" led.

Gus..