[SOLVED] After a firmware upgrade, blinking blue, lost 5Big2

[fvdw]

I edited my last post

[Glaven Clattuck]

before i go in this way. why do you think that the dir /4 is the right place?
They are all my files. I fear that put the Update directory can do them something wrong Perhaps it is better to create it in /md4/shares/1.
What do you think?

[fvdw]

what did the reboot bring ?

before i go in this way. why do you think that the dir /4 is the right place?
They are all my files. I fear that put the Update directory can do them something wrong Perhaps it is better to create it in /md4/shares/1.
What do you think?

Look to the dates of the folder 1...4 seems it creates every time you recover date or update that it it creates a new one, and probably the firmware will use the last folder. In other lacie's users described to unpack a capsule you need to create a folder with name "Update" (note the capital U at start of the name) and put there a capsules. The lacie firmware will then install this capsule when it finds the Update directory and a capsule file inside. If it will affect your files...normally not but I am not 100% sure.

Your data is it really 14TB or is that the total size of the disks together. If you want to avoid taking risk to loose the data then there are a few ways.
Copy them to the free space in the raid array (if there is enough free space) using another folder name, transferring them to an external usb disk or via network to another PC

[fvdw]

the capsule (I made a rar archive instead of zip, you need to extract to get the capsule

[fvdw]

another option we have is overwriting md0(sdx7) , md1(sdx8) and sda6 containing the kernel and we wipe md2 (sda9) to remove the snaps that are not working and write if it doesn't boot lacieFirstBoot to beginning of sda. What this will do with the existing shares... unsure

[Glaven Clattuck]

something different is happening, but do not reach the NAS and now redo the whole procedure to reactivate the console would take too long.
Tomorrow I'll try again the way that you have proposed, but one last thing, the capsule that I extract from your upload, I put it into the TFTP dir?

[fvdw]

yes to upload it with the standalone kernel put in the the tftp folder of the fvdw-sl console
(ps I downloaded the capsule from lacie website)

[Glaven Clattuck]

Ok.
Thanks for now, i really appreciated your support and time that you spend for me.

i have lot material from think and experiment, tomorrow will see what happens.

have a good night!

[Glaven Clattuck]

ok.
I tried everything I could, but nothing seems to fix my problem.

Created the Update directory and put inside the capsule file that you provided.

First attempt: Put directory Update under / mdv4/shares/4 and reboot, nothing changed.

Second attempt: Put directory Update under / mdv4/shares/1 and reboot, nothing changed.

Third attempt: Put directory Update under / mdv4/shares and reboot, nothing changed.

Fourth attempt: Create directory /Share under /md4 and put Update on it, reboot, nothing changed.
:cry:

what more?

[fvdw]

at least we know this is not the solution
what next

We know that on md0 (array sdx7) and md1 (array sdx8) the default firmware is present.
This should be able to boot your nas but md2 (sdx9) must be empty
Furthermore I think we need to install the kernel belonging to this firmware in array sdx6
Did you try to assemble an array for sd[a...e]6 ?

So we could write the kernel belonging to the default firmware to the array containing the kernel (sdx6) and erase content md2 (sdx9)
What this will do for your data when rebooting is unsure, however because you initiated a recovery your files may pop up in the recovery folder when the nas is running, but I never tried this with a nas containing data.

Are you prepared to take the risk of data loss if we perform these actions ?