Installed ver 11-0 NAS won't start

[fvdw]

I sorry to hear this but indeed something must be defective in the hardware. Beside the fact that it won't set up the netwerk interface , especially these messages you found in boot.log file are worrying.
You mentioned in your first post that it stopped working with the original firmware, was that also not being able to contact it ?

Still I wonder how these last messages
ERROR: lacfg_init fail read version
ERROR: lacfg_load_key no map defined
write_byte_storage : error loading key=power
ERROR : writing into the storage
error setting power on
ERROR: lacfg_cleanup no map defined

can come in the boot.log file as after adding the message "rcS" finished there are only these commands execute
cat /boot.log
sleep 3
exit 0
none of those can add something to the boot.log file, so who or what is adding that info....and why is it shutting down by itself

[ElectricSheep]

You mentioned in your first post that it stopped working with the original firmware, was that also not being able to contact it ?

Yes. That's the main reason why I install your firmware. I had exactly the same behaviour with the original firmware but first I thought that was a software problem. Seems it wasn't :cry:

About the message in the boot.log, nwsp never stops itself automatically, I always press the button for 5 seconds or so to get it stop. Anyway with the original firmware i've had the opposite problem.. it never stops! every time, after power down with the button it restart immediatly by its own; but, for example, hardware reset always work because i found my data in a long series of /myshare/recovery/myshare/recovery/myshare/recovery/... and so on 10 times maybe. So I think that also original firmware was working right.. and this is only an hardware problem...

Maybe this evening I will reinstall orginal partition from backup i've made and ask Lacie support if I can send it back to them even if I opened it :please :please .. I cross my finger and we will see...

P.S.
I see that every post or guide found here and on nas-central speaks about gparted as tool to deal with GPT tables. Googling around I've found gdisk which is some kind of a port for fdisk (same command line, same interface similar options) for GPT partition. Maybe could be useful to update how-tos with that tool :thumbup :thumbup

[fvdw]

I see and thanks for the gdisk link :thumbup

Success with the lacie guys, I would play the game of innocent and say that this is the way you got it and never have opened it. :snicker

[ElectricSheep]

That's f***g awesome!! IT WORKS!!
I reloaded original lacie partition table using gdisk and the backup image i've done before start. Write down my partition backup using dd command, then i reformat sdb5 to linux-swap and sdb2 to xfs like stated here. Then i plug in network and power just for a last try and IT WORKS!!

Really I can't say what was wrong but now it works again!! :punk :punk :punk

[fvdw]

thats indeed strange but if it works who cares :-D Hopefully it will keep working !!

[fvdw]

ps just out of curiosty

one question when the your nwsp2 stopped working with the lacie firmware did you use the WOL function or set sleep mode ?

The "wol" and "sleep-mode" routine of Lacie messes with an eeprom to set a flag, during boot the content of this eeprom is read and boot is dependent on what it finds there. Maybe the restore of the Lacie firmware has reset the contents of the eeprom to make it work normal again.
As the divece boots the lacie firmware loads some routines that read the eeprom content and do something dependent on what it finds. Maybe your trials with our firmware changed the settings of ths eeprom in a way that the Lacie firmware decided to reset it.
I am thinking this because the error messages you got points to that there was aproblem with writing to the eeprom.
When our firmware shutdown the nwsp2 tries to write a flag to the eeprom this to set the function of the power button properly, so you can restart it after it has shutdown by pressing the power button.

the messages
ERROR: lacfg_init fail read version
ERROR: lacfg_load_key no map defined
write_byte_storage : error loading key=power
ERROR : writing into the storage
error setting power on
ERROR: lacfg_cleanup no map defined

indicate that setting this flag failed in th eeprom failed (error: writing to storage).
I checked the binary from lacie that we use to set the power key (its the same as used by Lacie, we just copied that binary) and indeed these functions are defined and used by this binary.
This proves that something was wrong with accessing this eeprom. The question is of course why this happened :scratch but as a result of a wrong setting in the eeprom also the network card maybe deactivated, because this eeprom also contains a byte used for simulating WOL function.
I don't know if the network card is reading the eeprom as well when it is activated but it is likely when you want to save power in sleep mode or WOL mode.

So my conclusion is that restoring the Lacie firmware seems to have restored the content of the eeprom and that made the nas functional again. Of course it remains strange why it got corrupted or was no longer accesible when you were using the lacie firmware in the beginning.
Maybe a power cut while it was shutting down but not yet fully completed did it.