Lacie D2 Network VK2 Help

[macgyver76]

Hello Folks!

I am trying to recover a D2 Network VK2 following the death of the HDD. I downloaded the console (fvdw-sl-console-6-18-3-26feb2024-32bits.zip) and as the guide says I started to install fvdw-sl firmware. When I select the correct UIMAGE file (UIMAGE-3142-KIRKWOOD-171-standalone) and give the ok, I receive the error that the UIMAGE file is not in the 'tftp' folder ... and yet the file is present!
Where am I going wrong?
Thanks for the help
Bye

[fvdw]

the tftp folder should be a subfolder of the folder were you installed the console and assuming you started the console from that folder.

[macgyver76]

the tftp folder should be a subfolder of the folder were you installed the console and assuming you started the console from that folder.

I solved it by following what you said, thanks. But I can't continue, I mean it's always waiting for u-boot, so I ask you:
- I have the new hdd still "virgin", does it have to be formatted before inserting it into the LACIE? With which file system?
- With the new hdd inserted, with which mode should I start since it's totally empty? Always using 'Install fvdw-sl firmware' or another way since the hdd doesn't u-boot?
- In the fvdw-sl console I set 192.168. 0.5 which is the IP of the PC where I run the console and 192.168. 0.251 is the IP for the LACIE. Is this correct?
Thanks

[fvdw]

- I have the new hdd still "virgin", does it have to be formatted before inserting it into the LACIE? With which file system?
- With the new hdd inserted, with which mode should I start since it's totally empty? Always using 'Install fvdw-sl firmware' or another way since the hdd doesn't u-boot?
- In the fvdw-sl console I set 192.168. 0.5 which is the IP of the PC where I run the console and 192.168. 0.251 is the IP for the LACIE. Is this correct?
Thanks

A virgin disk is perfect no need to have a partition table or formatting.
Yes choose install fvd-sl firmware.
Leave the ip settings on the default values, do not change. If the pc setting doesn't match your actual pc ip then probably you have more then 1 ethernet card active. Use the ethernet card with wired connection and disable all other network interfaces.

In case it keeps waiting for uboot it means the nas doesn't detect the broadcast from the console. This can besides the issue described above also be be caused by a firewall running on your pc. You must grant access to pass the firewall
for console program and the tftp32 program. You could also temporarily disable the firewall. Also please read this topic which describes some more connection problems you may encounter https://plugout.net/viewtopic.php?f=7&t=2645

[macgyver76]

A virgin disk is perfect no need to have a partition table or formatting.
Yes choose install fvd-sl firmware.
Leave the ip settings on the default values, do not change. If the pc setting doesn't match your actual pc ip then probably you have more then 1 ethernet card active. Use the ethernet card with wired connection and disable all other network interfaces.

In case it keeps waiting for uboot it means the nas doesn't detect the broadcast from the console. This can besides the issue described above also be be caused by a firewall running on your pc. You must grant access to pass the firewall
for console program and the tftp32 program. You could also temporarily disable the firewall. Also please read this topic which describes some more connection problems you may encounter https://plugout.net/viewtopic.php?f=7&t=2645

I made a step forward and thank you. As you suggested I verified that in my win7 32bit:
- connected with the D2 only via lan cable
- Firewall completely disabled
- all additional network cards have been disabled.
After starting the console and installing the standalone firmware, the u-boot window opens and shows what you see in the attached screenshot 1.png
Immediately after, the window shows what you see in the attached screenshot 2.png
After a few seconds, the u-boot window closes and the Telnet client window opens again until the timeout and I can no longer continue. Do you have any other explanation?
Sorry for the inconvenience but I would like to understand why.
Thanks again

[fvdw]

are you sure that you have a D2 v2? In case it is a D2 v1 it needs a different kernel

[fvdw]

In addition also the ip start with 169 meaning you have no dhcp server running or the dhcp server is wring configured. How is your LAN setup?
Be sure you have a router in between your pc and nas and use ip pool for the dhcp server starting with 192.168.1 or 192.168.0

[macgyver76]

In addition also the ip start with 169 meaning you have no dhcp server running or the dhcp server is wring configured. How is your LAN setup?
Be sure you have a router in between your pc and nas and use ip pool for the dhcp server starting with 192.168.1 or 192.168.0

I confirm that it is the D2 Network V2K model.
To avoid problems with my local network, I made a restricted one ... that is to say that I took a router with its IP 192.168.1.1, I activated the dhcp. To this router I connected a PC (which assumed the IP 192.168.1.2) and the D2 which resulted in having the IP 19.168.1.252 from your console program.
All good to pass the UIMAGE, the window closed and shortly after the telnet client opened but it still does not connect and times out. Where is the problem?
A clarification, when the u-boot window is open to the Loading writing: what should appear?
I ask because sometimes a 'T' appears, other times two or three and only once even four. Perhaps I would not like the UIMAGE not to be loaded completely. Am I perhaps wrong?

Thanks

[fvdw]

When you see T's during transfer of the standalone kernel it means tfpt transfer timed out in the words the tftpd32 server didn't respond. After timeout the script tries again but if it timesout several times the nas gives up and proceed with the script but of course no kernel is loaded and as result the telnet client cannot connect.
You should see during uploading the kernel something like in this example.

Code: Select all

tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##########################
done
Bytes transferred = 3123520 (2fa940 hex)

In your case the name of the kernel and ip's will be different from this example.

Reasons why the tftpd32 server doesn't respond can be firewall blocking transfer or it was not started. You should have a tftpd32 window open on your pc. The console will start it automatically.

[macgyver76]

Code: Select all

tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##########################
done
Bytes transferred = 3123520 (2fa940 hex)

So even if there is communication between the u-boot window and my lacie, the image is not loaded..and this is the problem.

I described my network as isolated from everything, all the additional cards of the PC are deactivated, both the firewall of the PC and the router are deactivated, the TFTPD32 window also opens normally.
Looking at your example of uploading the image compared to mine that you see as 2.png, initially commands are sent with references to variable names...is this correct?
Finally I ask, I think as a last thing: Should I think that my Lacie has a hardware problem or is there an alternative way to go?
thanks for your patience