D2 Network 2 telnet refused.

D2 Network 2 telnet refused.

Postby Aled72 » Mon Feb 12, 2018 6:17 am

Hi to all.
I have a problem with firmware install on my D2 network 2.
When I try to connect it always answer telnet refused. Reading on internet I see that is the original firmware the problem.

I'm thinking is I can solve disassembling and formatting the hard drive.

There is another way or another solution for solving?

Thanks to all.
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby fvdw » Mon Feb 12, 2018 8:46 am

Which firmware do you want to install? lacie or fvdw-sl?

And please describe exactly what you are doing to install firmware, it seems you are not using the fvdw-sl console, is that correct?

If you want to install fvd-sl you must use the fvdw-sl console on a pc running windows connected wired to the same LAN as your D2 network and follow the instructions as given in the fvdw-sl console. If is a D2network vs2 you must use the kirkwood standalone kernel.
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: D2 Network telnet refused.

Postby Aled72 » Mon Feb 12, 2018 9:22 am

Yes I use fvdm-sl console via windows computer.
I tryed both, directly etherneth and lan.
I want install fvdw firmware. Searching on google seems that lacie firmware don't permit telnet connection.

Yes i follow istruction and use Kirkwood.
Is the same procedure that used for cloudbox but in this case wont work.
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby fvdw » Mon Feb 12, 2018 1:59 pm

What happens if you use in the fvdw-sl console as action uboot console. Does the D2net interrupts boot and can you access the uboot window?

PsSwitch power off of your D2 and do not start (power on) your D2 until the fvdw-sl console window mentions "waiting for uboot"
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: D2 Network telnet refused.

Postby Aled72 » Mon Feb 12, 2018 5:13 pm

Nothing, nas start and uboot window don't close.
I don't know, if I disassemble the disk and format it? Maybe a solution?
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network 2 telnet refused.

Postby Jocko » Mon Feb 12, 2018 5:36 pm

Hi Aled72,

I think you should check if you have really a d2nw2. See this page : http://lacie.nas-central.org/wiki/Category:D2_Network_2
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: D2 Network telnet refused.

Postby Aled72 » Mon Feb 12, 2018 5:58 pm

yes is D2 Network 2

Verified also in Lacie website. can be the original firmware updated?
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby fvdw » Mon Feb 12, 2018 10:07 pm

Aled72 wrote:Nothing, nas start and uboot window don't close.
I don't know, if I disassemble the disk and format it? Maybe a solution?


the uboot window should not close, the text should change from "waiting for uboot...." to "click and hit enter to.."
When the text changes click on the uboot window and hit te key "enter"
You should get a prompmpt "marvel>>"

If you get that prompt type behind it
Code: Select all
printenv

and post output
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: D2 Network telnet refused.

Postby Aled72 » Tue Feb 13, 2018 3:05 pm

Hi, yesterday night I try to disassemble the hdd and try to install fvdw in a blank disk. (I have another one).
The fvdw-console work and install the firmware.
Then I delete 2t disk and try to install again but now it tell me installation incomplete, disk will not boot.

The drive is ok because if I connect to pc with adapter it work.

Where I wrong?!?!
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby fvdw » Tue Feb 13, 2018 5:51 pm

I don't know what is happening without more information. There seems to be an issue with this disk.

Even with a non blank disk the standalone kernel should run and you should get telnet access. From your post I assume you get telnet access as you mention you get incomplete installation. At which point does the installation fails? The installer gives info when it aborts.

Anyhow we can also check the disk by just loading the standalone kernel.
So put your problem disk in the nas and load and start standalone kernel using the fvdw-sl console. When you have telnet access postboutput of these commands
Code: Select all
fdisk -l

And
Code: Select all
gdisk -l /dev/sda
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Next

Return to Lacie D2 network vs2

Who is online

Users browsing this forum: No registered users and 1 guest