Firmware v15 for Lacie Cloudbox

[fvdw]

thts interesting info . The partition setup and xontents is quite different from previous models. need to look in more detail but it still seems to look for a kernel in on partition sda6. Thats in fact the only thing we need. Do want to back up the orginal lacie partitions ? Some are 1 GB. Those will need time to upload via tftp. maybe mounting them and copy the content in a tar archive is a quicker way

[ElBalsero]

We can give it a try to the second method then. Just I'll need some guidance.
Or if you prefer to unify everything under the same automatic script for the future and you want me to give it a try, I can also wait...

[fvdw]

No problem to do that, I will post some instructions this evening, now it is dinner time

ps an easier test could be done if you have a spare harddisk

[ElBalsero]

Unfortunately I haven't got a spare one :(
Enjoy dinner.

[fvdw]

ok let see what we can do.

first start the fvdwl-sl console and load the standalone kernel for nwsp2cl and get telnet access.
Then give command

Code: Select all

gdisk -l /dev/sda

and post the output. This to secure the partition info of the original firmware.
Then we have this info if you want to revert back. Also we will use to explore the partitions one by one

[fvdw]

in the meantime I studied the output of the printenv form tht eu-boot console

It seems this device checks what the disk layout is, if it is the new layout it uses the nexus stuff, if that fails then it tries to boot the legacy layout = the old layout as we had until now on lacie devices. So the fvdw-sl firmware will run is my conclusion.
Now backing up the original lacie images is no problem for partitions 1,2,3, 6
Partitions 4 en 5 are 1.5 GB we can not use the ram to store them (the ram is only 256 MB)
partition 7 is not necessary to back up (is swap space, it has no files)
partition 8 is the big data partition for soring user files, that also has no use to back up as you already have a backup, furthemore it will take very long time do backup 1.8 TB via tftp.

So backing up parition 4 and 5 is an issue. We can ot mount them just like that as they are of typ linux raid (FD00) :scratch

[ElBalsero]

Hi,
The requested output:

Code: Select all

root@(none):/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 48EB39C7-FA39-4315-9B4C-B7E4FE438E83
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core
   2            4096          397311   192.0 MiB   8300  boot_rescue
   3          397312          399359   1024.0 KiB  8300  nv_data
   4          399360         3545087   1.5 GiB     FD00  root_1
   5         3545088         6690815   1.5 GiB     FD00  root_2
   6         6690816         8787967   1024.0 MiB  FD00  var
   7         8787968         9312255   256.0 MiB   FD00  swap
   8         9312256      3907029134   1.8 TiB     FD00  user_data

As for partitions 4 and 5, probably I'm saying now something stupid but perhaps it might trigger some ideas. What about using something like the dd command that works without mounting the partition, to make a backup of them on for example the partition 8. So once the backup files are created they are easily accessible just letting the original firmware to boot once more and share them?

[fvdw]

lets first try if using the gzip compression is enough to store them temporarily in ram
we start with partition 1

Code: Select all

dd if=/dev/sda1 | gzip > /sda1.img.gz

if that succeeds copy it to the windows pc, the tftp server of the fvdw-sl console is still running

Code: Select all

tftp -l /sda1.img.gz -r sda1.img.gz -p ip-pc

(replace ip-pc in this command by the actual ip address of your pc running the fvdw-sl console)
If that went ok remove the file to free up space in the ram

Code: Select all

rm sda1.img.gz

Then repeat for sda2 and sda3

[ElBalsero]

Sure.
I have to go today, but I'll give it a try tomorrow.
Thanks for the help.

[ElBalsero]

OK
I've run the procedure without any problem for sda1, sda2 and sda3. Now the three backup files are in my disk.
Shall I try the rest?