plugout.net

[b][b][/b][/b]After the precious help of jocko and fvdw, my Lacie has worked fine for weeks, so I made a pass that postponed for some time.
I do a firmware upgrade.
The Dashboard gave me an alert that my firmware 2.2.9.3 was old and there was the new 2.10.2.2.
A little voice inside my head kept saying, "Do noted it, do not do it", but the devil is tempting, so I started the operation via Dashboard.
The bar has continued to advance, and when arrived to 100%, a window popped up, saying that the firmware time was longer than expected, suggested to close the window and launch the operation from Lacie Network Assistant.
But obviously LNA was not possible to do anything. So I power off and on again my LaCie, but the only thing I get, is that after a while the front light blinks continuously in blue.
I can not detect the Lacie on my Lan, and I can not access it in any way.
I tried to follow LaCie manual and make a reset to factory conditions without loss of data, but I can not do it.
Following literally the instructions of the manual, while pressing the front button, the same should turn red, and then blue. which does not happen.

So my question is, how can I get my LaCie, especially without losing the data on it?

Thanks in advance

Hi Glaven Clattuck,

:pound
It is a bad new. According a quick search on http://forum.nas-central.org/viewforum. ... 743d79606d, you are not alone in this case and fix does not seems obvious

So you should read this forum and open an topic here

Jocko wrote:Hi Glaven Clattuck,

:pound
It is a bad new. According a quick search on http://forum.nas-central.org/viewforum. ... 743d79606d, you are not alone in this case and fix does not seems obvious

So you should read this forum and open an topic here

Thanks my friend.
It's incredible that just a fw upgrade can cause situation like this, but this is life.
Anyway try to read links that gently suggest.

I report back, hope with good news.

Just a little explanation on phrase that fvdw wrote on a previous topic:

Yes if you install fvdw-sl firmware using the installer all data on the disk will be lot. If you want to try to repair lacie firmware or retrieve data from the disks when lacie firmware is failing to boot then you need to use the standalone kernel that comes with the console. It runs from RAM and will give you telnet acces that can be used to investigate your disks. As you probably used a raid setup you need to assemble the raid array first before being able to mount it. There are several topics descibing what needs to be done on the forum.

What does it mean? that there is a prg that allows me to search for the NAS without losing data?
I dl the instruction, but on it i found just i php file that explains what to do.
Please can you point me on the right direction? and sorry for the dumb question...

You will find information here http://plugout.net/viewtopic.php?f=7&t=2691

fvdw-sl console runs only on a Windows OS

Thanks, to give me the right instruction.
unluckily, the console struggled waiting for u-boot, but nothings happens.
To be clear, i'll arrive to the step 4 (showed on the console window),
But, no more.

Disable your firewall or grant the console programs access to the lan and use a wired connection between pc and lan. Be sure to use eth0 connector on the 5big2

fvdw wrote:Disable your firewall or grant the console programs access to the lan and use a wired connection between pc and lan. Be sure to use eth0 connector on the 5big2

I'm on a Mac, so i run console via VmWare (Win 7).

Always stuck waiting u-boot.
So i restarted the entire cycle.

My Nas is connected on router, like my mac. Firewall on the router is on, so i turned off.

Nothing changed. If i try to ping the IP (10.211.55.252(, that the console assigned at my NAS, the response is: Destination Host unreachable.

My network lan is 192.168.2.xxx

Any suggestion?

Any suggestion?

Yes but not one you like, use a windows pc ;)
I don't know if vmware will work with the console programs that handle communication to your nas. Can you reach other devices in your lan via vmware? Important be sure to have only one (1) neteork adapter active and do not use a wireless one

I read a post on General NAS-Central Forums, where a user has a situation like mine, and on the Mac has set up a Virtual Box.
So i think that Fusion (VmWare) is better than Virtual box, but anyway i change the configuration of my Lan and on the router create a Network 10.211.55.x. I unplugged literally every device, except the Mac and the NAS.
But nothing changed.
I'm blocked on the step 4. And as before if try a ping, i reach just my router and my Mac.
The light of eth port on the Nas is green, like the led of the 5 HD.

So the problem here is that i don't reach the NAS.
And unlucky i don't have a win pc, just a corporate one, but there is installed a Symantec endpoint that block everything.

But if the router port and the NAS are connected and up, there is a way to tell if the door of nas has been assigned a local address?
Or is just an electrical connection?