plugout.net

Hi to everybody,
first thanks to all this forum staff.

I had a 5BIG V2 died and I have get it alive with the installation of the fvdw-sl 15.1 firmware.

Now I would like back to the Lacie Original Firmware but.... HOW CAN I DO IT?
The problem is that I have 4 (3Tb disks).
I have tried load the firmware (LACIE CAPSULE) from the Control Panel in the 15.1 version but I get the error that the file is not the correct file.

Could anybody help to me...??

Sorry from my english... Regards from Spain.

:disapprove

why go back to this crappy Lacie firmware

anyway you cannot install it with fvdw-sl firmware.

How to get the lacie firmware back see here viewtopic.php?f=26&t=1402 (yes you need to read three pages of posts)

fvdw wrote::disapprove

why go back to this crappy Lacie firmware

anyway you cannot install it with fvdw-sl firmware.

How to get the lacie firmware back see here http://plugout.net/viewtopic.php?f=26&t=1402 (yes you need to read three pages of posts)

Hi fvdw,

we need back to Lacie firmware because we need use RAID 5.
We have followed the post that you say and using a 640Gb all go fine, but when we try do do the same with a 3Tb. HD the system doesn´t boot.

The problem is creating SDA2 (using mkfs.xfs). We don´t know why but this command is not available booting using UIMAGE-395-NWSP2CL-179-standalone.
Yes, we have upload by tftp the mkfs.xfs

Do you know what can be the issue....???

Regards... ;)

were did get mkfs.xfs ?

You will need a static compiled version for arm as libc is not present in the standalone kernel (too big). I believe I have compiled one some time ago . I will have look

seems I never compiled a static version of mkfs.xfs :mrgreen:

so you need to upload a mini version of glibc +mkfs.xfs to make this command work
I attached a zip archive, unpack you will find a tar archive glibc-mini-mkfs.xfs-25feb14.tar
Upload that to the nas using the standalone kernel and unpack in the top level directory (/) of the standalone kernel
Now the mkfs.xfs command should work

---edit
here an instruction how to upload and install it

The zip archive contains a minimal version of glibc and mks.xfs , unpack you will find a tar archive glibc-mini-mkfs.xfs-25feb14.tar
Upload that to the nas using the standalone kernel and tftp server of the telnet client of fvdw-sl console while running the standalone kernel

Code: Select all

tftp -l glibc-mini-mkfs.xfs-25feb14.tar -r glibc-mini-mkfs.xfs-25feb14.tar -g pc-ip

(replace ip-pc by actual ip addres of your pc running the tftp server of the fvdw-sl console)

unpack the tar archive in the top level directory (/) of the standalone kernel

Code: Select all

tar -xvf glibc-mini-mkfs.xfs-25feb14.tar -C /

now mkfs.xfs should work.

(note that the standalone kernel runs from RAM, so after a reboot you need mkfs.xfs to install it again if you want to use it)

fvdw wrote:seems I never compiled a static version of mkfs.xfs :mrgreen:

so you need to upload a mini version of glibc +mkfs.xfs to make this command work
I attached a zip archive, unpack you will find a tar archive glibc-mini-mkfs.xfs-25feb14.tar
Upload that to the nas using the standalone kernel and unpack in the top level directory (/) of the standalone kernel
Now the mkfs.xfs command should work

Thanks so much..!!! I'll try it tomorrow.
You'll have my feedback.
;)

here some instruction how to upload and install it

The zip archive contains a minimal version of glibc and mks.xfs , unpack you will find a tar archive glibc-mini-mkfs.xfs-25feb14.tar
Upload that to the nas using the standalone kernel and tftp server of the telnet client of fvdw-sl console while running the standalone kernel

Code: Select all

tftp -l glibc-mini-mkfs.xfs-25feb14.tar -r glibc-mini-mkfs.xfs-25feb14.tar -g pc-ip

(replace ip-pc by actual ip addres of your pc running the tftp server of the fvdw-sl console)

unpack the tar archive in the top level directory (/) of the standalone kernel

Code: Select all

tar -xvf glibc-mini-mkfs.xfs-25feb14.tar -C /

now mkfs.xfs should work.

(note that the standalone kernel runs from RAM, so after a reboot you need mkfs.xfs to install it again if you want to use it)