imt17 wrote:OK so steps seem:
1) Download fvdw-sl Console 5.5 correct.
2)Re-install all the current drives back in the Lacie is the original order. (i.e. way it was when crashed)
**Do I just remove the one disk that I know makes noise and seems dead? or put them all back in anyway.
Install all original disks, when assembling the raid array you wil see which disks fail
3) Connect a LAN cable from port 1 to my router. Leave NAS powered off.
4) On the XP machine run FVDW-sl console
yes correct
but next step should be after startint the console
5)choose action and "standalone kernel load and start"
6) follow the instructions in the popup window, select the correct standalone kernel (UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone)
7) wait until the a command window opens mentioning "waiting for u-boot"
8) after that start your nas
In the command window the text waiting for u-boot should change, can take several seconds, 5big2 bootloader takes its time, if it change you will see in the command window the uploading progress of the kernel and starting of it.
Then the command window closes automatic and after about 12 seconds a telnet client is started and you can try to login.
Now do I need to be on a specific lan for this to work? My IP address scheme at home is 192.168.17.x. If I need to I can find an older router and set that to 192.168.1.x or 192.168.0.x if necessary.
Yes but that is done in the fvdw-sl console, see main window, it will also show the ip of your PC
You can change the default value if you wish but I would leave it unless the ip spefied for the nas is already in use in your lan.
Note, be sure that the first three octets of the IP are corresponding with those used in IP pool your router is using (for example 192.168.1) typically choose them equal to the three octets of your PC's ip address.
Of course your router must allow access to the ip addres used