Repair Lacie Cloudbox after failed install of latest firmwar

Post Reply
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 Aug 07, 2015 12:15 pm

do you still have ubootenv.old ? and can you post it on plugout ?

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 Aug 07, 2015 12:29 pm

I have the file, but I think it is corrupted too.

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 Aug 07, 2015 12:48 pm

dmiyabara wrote:I have the file, but I think it is corrupted too.
why do you think that ?

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 Aug 07, 2015 12:56 pm

Tried to use the command to change saved_entry and CRC check was wrong.

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 Aug 07, 2015 12:57 pm

does this still works ?

Code: Select all

Marvell>> setenv root_part 5
setenv root_part 5
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>> run nexus_boot
run nexus_boot
Booting Nexus layout from disk 0...
boot_count=0
saved_entry=0
ERROR: There is a global environment variable with the same name.
Loading file "/boot/uImage" from ide device 0:5 (gpt5
)
7183376 bytes read

## Checking Image at 00800000 ...
   Image Name:   Linux-2.6.31.14-svn7493
   Created:      2013-04-16  10:04:39 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    7183312 Bytes =  6.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK

etc
This seemed to give a valid ubootenv file (look to the part of the output mentioning

Code: Select all

boot_count=0
saved_entry=0
that comes from the ext2get call.
During that trial it seems we had a valid ubootenv file, maybe the nexus_boot command reste it , if it does we can copy it again and see if then the content is different regarding crc checksum
.
I made a small program to calculate crc checksum of a string, for a string like in ubootenv it produces a value of 4 bytes That matches with what we see, however the crc value it calculates is different from what in the file that is corrupt. I tried all combinations of saved_entry and boot_ count (0-0, 0-1, 1-1, 1-0) but none of them gaves a CRC equal to what is in the file. Hopefully the original one gives a recognizable value

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 Aug 07, 2015 5:49 pm

I figured out :mrgreen: and can now make correct ubootenv files
The one on your system has a crc value for a file with saved_entry=0 and boot_count=1

This evening I will make the file for saved_entry=1 boot_count=0 with correct CRC value on plugout
That one should let it boot while using partition 5 as root_part
Last edited by fvdw on Fri Aug 07, 2015 7:27 pm, edited 2 times in total.

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 Aug 07, 2015 6:21 pm

Thanks a lot fvdw, I'll wait for your 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 Aug 07, 2015 7:24 pm

file is posted on plugout

http://plugout.net/viewtopic.php?f=28&t ... 351#p19351

(It is inside zip archive: ubootenv-crc-ok-1-0.zip)

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 Aug 07, 2015 7:27 pm

Thanks again fvdw, I'll try this file in a few minutes.

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 Aug 07, 2015 10:18 pm

and...any news :)

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 08, 2015 2:28 am

Sorry for the late reply, testing now... at least the red light didn't appeared by now...

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 08, 2015 2:58 am

Well, thanks again fvdw, it's working as it should be from the start. lol
Everything is working flawless.
And again sorry for the late reply, my family came to my house and had dinner late.

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 08, 2015 8:15 am

Thanks for the feedback and glad to hear that it solved the problem :mrgreen: It was nice challenge to crack this code. :D
And we discovered more about the booting proces of the lacie. I will post the crc codes of the different combinations and the code of the test program I made (on plugout.net)

stef296
Posts: 2
Joined: Sun Aug 16, 2015 10:12 pm

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by stef296 » Sun Aug 16, 2015 10:18 pm

Hi,

I am trying to register on plugout.net to get the Windows binaries for fvdw-sl-console from the link below but when registering with my gmail account it tells me email not allow. Any ideas?


http://plugout.net/viewtopic.php?f=3&t=1227

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

Re: Repair Lacie Cloudbox after failed install of latest fir

Post by fvdw » Mon Aug 17, 2015 11:13 am

this because gmail addresses are by default on the black list (ant spam measure), send an e-mail to admin@plugout.net with the e-mail address you want to use and we can create an exception

Post Reply