Repair Lacie Cloudbox after failed install of latest firmwar

Post Reply
dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Wed Jul 22, 2015 6:31 am

Well, I'm really happy now :D :D :D . Just wake up in the middle of the early morning, to take care of my children and I saw my Lacie with a blue light working the way it should be.
Was a little bit cautious when I started the LNA, and then I saw it connected to my Lacie Cloudbox... then started the first configuration in the dashboard. Everything worked the way it should be, mounted the HDD and found all my files, inside the folder RECOVERY.
I just want to say THANK YOU to the guys fvdw [/ b] and Mijzelf [/ b] by the patience (wrong commands, some silly questions ...: oops :) and for help with the support I had in these forums (NAS-Central and plugout.net).
I will write again (maybe tomorrow) all the commands that worked and helped me to find again the Cloudbox in the network. I think that it will help a lot of users that had the same problem with their Lacie Cloudboxes.

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by fvdw » Wed Jul 22, 2015 8:35 pm

:D nice to hear that you finally could get it working again

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Thu Jul 23, 2015 2:45 am

To try to repair your Lacie Cloudbox you need to use these tools:

1st Part
fvdw-sl console
Download at http://plugout.net/viewtopic.php?f=7&t=1271

Config your network to make the address 192.168.x.252 avaliable (x depend on your network, eg: 192.168.0.0, 192.168.1.0, etc)

Unrar starting with the first file, in a folder easy to remember inside your PC connected to the network.

Run as administrator this file 'fvdw-sl-console.exe', enter the password provided in the website you downloaded the files.

Accept all to connect to the network if asked by your firewall.

Go to the tab Action, and choose 'Standalone kernel, load and start'

Choose the right file, in this case
UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone
(the Cloudbox file is the KIRKWOOD)

Follow the instructions on the screen.

Remember to turn off the NAS before you start the tool fvdw-sl console.

When asked for a U-boot, turn on your NAS.

It will find your NAS and start the console:

Enter login 'root' and password 'giveit2me'


2nd Part

Use the command

Code: Select all

gdisk -l /dev/sda
(to see the partitions inside your NAS)

You should see something like this:

Code: Select all

cloudbox original partiton table

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
If you find something similar or identical we are good to go.

Part 3

Turn off your Lacie Cloudbox again, and restart the fvdw-sl console.
But in the Action tab you must choose U-boot console and write the commands below.
Use these commands to reset the Lacie Cloudbox to the factory install.

Code: Select all

setenv root_part 5
ide reset
setenv image /boot/uImage
run nexus_load_image
run nexus_bootargs
bootm
Summarizing what happens in these commands:

You load the partition 5 of your NAS, resets the physical connection with the IDE hard drive, says where the is image to boot, load the image, load the flags (don't ask me about this, I guess it is something about which partition it should load after a reset) and starts the boot.

And wait a few hours. After that look if the blue light starts to blink the way it should be. Then close the fvdw-sl and the other windows. Start your LNA (Lacie Network Assistant), it should find your NAS again. Run like it was the first time, insert your password, then let it configure. Mount the Cloudbox, and look for a folder named Recovery. All your files should be inside it.

Enjoy your precious files again. :D

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Fri Jul 31, 2015 1:39 am

Hi all,

I'm back. When I restarted my Lacie, the red light came back. I think maybe it happened when I changed these commands:

Code: Select all

# create a copy:
cp ubootenv ubootenv.old
# Exchange all 0 by 1
sed -i 's|0|1|' ubootenv
# Have a look
cat ubootenv
I tried to use:

Code: Select all

cp ubootenv.old ubootenv
But the configuration is changed:

Code: Select all

root@fvdw-sta-kirkwood:/media/sda3 # cat ubootenv
áëösaved_entry=1boot_count=1root@fvdw-sta-kirkwood:/media/sda3 # 
The original code was:

Code: Select all

root@fvdw-sta-kirkwood:/media/sda3 # cat ubootenv
áëösaved_entry=0boot_count=1root@fvdw-sta-kirkwood:/media/sda3 #
How can I revert back to the original ubootenv file?

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by fvdw » Fri Jul 31, 2015 1:08 pm

So your backup version is not the same as the original content?
If you post your file on plugout I can modify it for you using a hex editor. Put the file in a zip archive otherwise you cannot upload it to the plugout forum.(nas central doesn't allow file uploads)

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Fri Jul 31, 2015 3:24 pm

How can I copy the file from the NAS and send to my PC?

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by Mijzelf » Fri Jul 31, 2015 6:37 pm

I think the file is the same as the original, and the original didn't work either. The original had saved_entry=0, which means partition 4 is used. You manually loaded partitiion 5, but that setting was never saved.

Looking at the environment I think you can save the parameter with

Code: Select all

ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv saved_entry 1 boot_count 0

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Fri Jul 31, 2015 10:23 pm

I tried the command, but it didn't work, still the red light when it boots. But I wrote this code in
root@fvdw-sta-kirkwood:

Code: Select all

ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv saved_entry 1 boot_count 0

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by fvdw » Fri Jul 31, 2015 10:30 pm

you need to give that command in the u-boot console ;) (so not with the standalone kernel)

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Sat Aug 01, 2015 2:50 am

Received this message:

Code: Select all

Marvell>> ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv saved_entry 1 boot_count 0
ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv saved_entry 1 boot_count 0
Usage:
ext2set - set variable in an environment file

Marvell>>[code]
[/code]

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by Mijzelf » Sat Aug 01, 2015 8:59 am

Maybe you can only write one variable a time. And boot_disk isn't filled yet. So try

Code: Select all

ext2set ide 0:${nexus_nv_part} /ubootenv saved_entry 1
and maybe you have to execute

Code: Select all

ide reset
first.

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Sat Aug 01, 2015 12:56 pm

I think it tried to use partition 3 instead of 5.

Code: Select all

Marvell>> ext2set ide 0:${nexus_nv_part} /ubootenv saved_entry 1
ext2set ide 0:${nexus_nv_part} /ubootenv saved_entry 1
** Bad partition 3 **
Marvell>>

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by Mijzelf » Sat Aug 01, 2015 2:32 pm

It is supposed to.
dmiyabara wrote:

Code: Select all

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
You have two rootfs partitions, 4 and 5. U-boot chooses between them, based on a configuration file /ubootenv stored on partition 3. (I think this is the only purpose of partition 3).

"Bad partition 3" suggests that it can't find it. Did you try a 'ide reset' ?

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by fvdw » Sat Aug 01, 2015 2:38 pm

** Bad partition 3 **
this message indicates to me that you did not give the command

Code: Select all

ide reset
before ext2set...

dmiyabara
Posts: 61
Joined: Thu Jul 09, 2015 9:33 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by dmiyabara » Sat Aug 01, 2015 3:44 pm

Another error, :oops:

Code: Select all

Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter

Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (5)
  Device 0 @ 0 0:
Model: ST2000DM001-1CH164                       Firm: CC44     Ser#:             Z2F0VEJ3
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
PCIe SATA:ffffffff

Marvell>> ext2set ide 0:${nexus_nv_part} /ubootenv saved_entry 1
ext2set ide 0:${nexus_nv_part} /ubootenv saved_entry 1

** bad crc : env data may be corrupted
Marvell>>

Post Reply