fvdw wrote:1. From the console install fimrware will not work and can't connect via terminal.
2. Tried to write image to disk from the console and successfully formatted drive with MSDOS not the GPT. Reboted Lacie but i can't find it on my network, tried Assistant but nothing :(
(On the first chose from the console i have chose UIMAGE-26394-2BIG1-47-1-1-4-standalone ) and via de terminal Kirkwood big2
At the first chose via the console UIMAGE-3142-KIRKWOOD-171-standalone i can;t connect via the terminal..
What is wrong here?
I don't understand what you are doing.
What kind of machine do you have ? a lacie 2big-vs2 or 2big-vs1. You mention before it is a vs2, in that case you must use as said the
UIMAGE-3142-KIRKWOOD-171-standalone kernel when it is a vs1 then indeed you need the UIMAGE-26394-2BIG1-47-1-1-4-standaloneOn the first chose from the console i have chose UIMAGE-26394-2BIG1-47-1-1-4-standalone ) and via de terminal Kirkwood big2
what do you mean with "via the terminal" ? Is this after you have logged in with telnet using username : root and password: giveit2me ?
Where you able to login with telnet client using the UIMAGE-26394-2BIG1-47-1-1-4-standalone ?
What i have: Lacie 2big network v2
I have just 2 scenarios with no luck:
1. Via FVDW console click on Write firmware image to disk and chose UIMAGE-3142-KIRKWOOD-171-standalone
Result: No luck to connect using terminal.
2. Via FVDW console click on Writefirmware image to disk and chose UIMAGE-26394-2BIG1-47-1-1-4-standalone
Result: Succesfully connected using TFTP and from there via that blue screen formatted the drive and there chose the Kirkwood 2big2 image.
-> But after reboot the NAS no luck to get an IP..
Another thing is when i chose from de FVDW console install firmware instead of Write firmware image to disk, also no luck to connect via TFTP.