Firmware v15 for Lacie Cloudbox

Re: Firmware v15 for Lacie Cloudbox

Postby ElBalsero » Wed Oct 30, 2013 9:59 pm

Oh, nice. Thanks a lot :-)
ElBalsero
Donator VIP
Donator VIP
 
Posts: 30
Joined: Mon Sep 30, 2013 9:46 pm
Location: The Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby ElBalsero » Wed Oct 30, 2013 10:42 pm

Hi again,
Good, it did work and I'm now able to execute the scripts.
But now when it asks what is the interface where the disk is plugged, when I say sda, it tries to format sda9 and then it fails.
Any idea what is the right interface or how to find it out?
Thanks again.
ElBalsero
Donator VIP
Donator VIP
 
Posts: 30
Joined: Mon Sep 30, 2013 9:46 pm
Location: The Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby ElBalsero » Wed Oct 30, 2013 10:56 pm

umhhhhh...
Just realized that I have actually a Linux kernel running so I tried:
Code: Select all
root@(none):/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      242252  1953514583+ ee EFI GPT

So the device is indeed sda... perhaps the structure of partitions of the cloudbox is different than the script expects or something like that?
Just trying to guess :-)
ElBalsero
Donator VIP
Donator VIP
 
Posts: 30
Joined: Mon Sep 30, 2013 9:46 pm
Location: The Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby fvdw » Wed Oct 30, 2013 11:09 pm

no it is not it is a disk with GPT partition table you should use "gdisk" to see partition table
(fdisk is for disk witk with ms-dos partition table)

Code: Select all
gdisk -l /dev/sda
fvdw
Site Admin - expert
 
Posts: 13239
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby fvdw » Wed Oct 30, 2013 11:11 pm

as it is a disk of 2TB you can either choose to use a GPT partition table of ms-dos partition table. Both should work fine
(for disk bigger then 2TB you need to use GPT)
fvdw
Site Admin - expert
 
Posts: 13239
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby ElBalsero » Wed Oct 30, 2013 11:17 pm

You are rigth, gdisk is the one to use:
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

Still when trying to use the backup uption the script fails:
Code: Select all
mke2fs 1.41.14 (22-Dec-2010)
mke2fs-ext3: No such device or address while trying to determine filesystem size

There was an error formatting /dev/sda9.
Installer will exit.
Cannot create backups formatting sda9 failed

Should I skip the backup option?
ElBalsero
Donator VIP
Donator VIP
 
Posts: 30
Joined: Mon Sep 30, 2013 9:46 pm
Location: The Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby fvdw » Wed Oct 30, 2013 11:27 pm

:shock: this is another structure then the nwsp2 or other lacie devices I have seen so far.
Is this a lacie cloudbox with with casing ?
fvdw
Site Admin - expert
 
Posts: 13239
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby ElBalsero » Wed Oct 30, 2013 11:32 pm

Yeah... LaCie Cloudbox 2TB with white casing.
If it helps, the label with the bar codes in the box says '2TB Cloudbox EK'
ElBalsero
Donator VIP
Donator VIP
 
Posts: 30
Joined: Mon Sep 30, 2013 9:46 pm
Location: The Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby fvdw » Wed Oct 30, 2013 11:47 pm

Rimoth, the other member that installed the firmware on his Lacie cloudbox never posted the original partition structure
So i am a little unsure here how to proceed
if we format your disk then there will be no way back to install the original lacie firmware. As you will not have a backup.
We can manually backup the partitions if we want

We have 3 options
(1) use another disk for testing , if you have one, just to be sure that it will work.
(2) delete the partition table and install the fvdw-sl firmware and hope it will work
(3) use the u-boot console to get some information from u-boot on how this cloudbox boots.

But this will for me not be tonight, need to go to bed as tomorrow I need to work ;)
But tomorrow evening I can assist you

If you still have time and want to try u-boot console. Switch off the cloudbox. Start he fvdw-sl console and choose u-boot console
Wait until the u-boot console windows says thatn it os waiting for u-boot, now start your cloudbox. Then start it, in the u-boot console window the following prompt should appear
Code: Select all
marvel>>

After prompt give as command
Code: Select all
ide reset

then
Code: Select all
ide part

and post the output you get (you can copy the content of the u-boot console window (right click on title bar of the u-boot console window and select from the drop down menu)

After that give the command
Code: Select all
printenv

and also post that output.
From this output we should be able to see where this cloudbox loads the kernel form and which partition it will use to load a root file system.
if we know that we can determine if fvdw-sl will run or not.

It should as Rimoth installed successfully.
But better first check things out here if Lacie made an unexpected change in setting up the devices...
fvdw
Site Admin - expert
 
Posts: 13239
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Firmware v15 for Lacie Cloudbox

Postby ElBalsero » Thu Oct 31, 2013 12:58 am

Hi,
No man, I'm not in a hurry with this and if I can provide any information and help that is useful for other people I'm more than happy to do so. Let's then check what we have in this disk.

The outputs:
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#:
 Z1E35Z1H
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
PCIe SATA:ffffffff

Marvell>>

Code: Select all
Marvell>> ide part
ide part

Partition Map for IDE device 0  --   Partition Type: EFI

Part         Start LBA           End LBA
gpt1               800               FFF
gpt2              1000             60FFF
gpt3             61000             617FF
gpt4             61800            3617FF
gpt5            361800            6617FF
gpt6            661800            8617FF
gpt7            861800            8E17FF
gpt8            8E1800          E8E0888E
Marvell>>

Code: Select all
Marvell>> printenv
printenv
bootargs=console=ttyS0,115200
bootcmd=run nexus_boot; run legacy_boot
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
boot_fail=lump
loadaddr=0x800000
console=console=ttyS0,115200
kernel_addr=${loadaddr}
disk_list=0 1
legacy_set_rootfs=if test $boot_disk -eq 0; then rootfs=/dev/sda7; elif test $bo
ot_disk -eq 1; then rootfs=/dev/sdb7; fi
legacy_nand_boot=
legacy_disk_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=${ro
otfs};
legacy_disk_boot=echo Booting legacy layout...; if test ${resetFlag_env} -ne 0;
then part_list=6; else part_list="A 6"; fi;for p in ${part_list}; do for boot_di
sk in ${disk_list}; do if disk ${loadaddr} ${boot_disk}:$p; then run legacy_set_
rootfs; run legacy_disk_bootargs; bootm; fi; done; done
legacy_boot=run legacy_disk_boot || run legacy_nand_boot
nexus_max_count=3
nexus_boot_part=2
nexus_nv_part=3
nexus_inc_count=if test ${boot_count} -eq 0; then setenv boot_count 1; elif test
 ${boot_count} -eq 1; then setenv boot_count 2; else setenv boot_count ${nexus_m
ax_count}; fi
nexus_set_root=if test $saved_entry -eq 1; then root_part=5; else root_part=4; f
i
nexus_load_flags=ext2get ide ${boot_disk}:${nexus_nv_part} /ubootenv boot_count
saved_entry
nexus_save_flags=ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv boot_count
${boot_count}
nexus_load_image=ext2load ide ${boot_disk}:${root_part} ${loadaddr} ${image} &&
iminfo ${loadaddr}
nexus_uuid=ext2uuid ide ${boot_disk}:${nexus_boot_part}; boot_uuid=${uuid}; ext2
uuid ide ${boot_disk}:${root_part}; root_uuid=${uuid}
nexus_bootargs=run nexus_uuid; setenv bootargs ${console} boot=UUID=${boot_uuid}
 root=UUID=${root_uuid}
nexus_can_boot=test ${bootfail} -eq 0 -a ${countfail} -eq 0 -a ${forced} -eq 0 -
a ${user} -eq 0
nexus_rescue_countfail=test ${boot_count} -ge ${nexus_max_count}
nexus_rescue_user=ext2get ide ${boot_disk}:3 /ubootenv rescue && test ${rescue}
-eq 1
nexus_rescue_bootargs=test -n ${bootfail} && setenv bootargs bootfail=${bootfail
} ${bootargs}; test -n ${countfail} && setenv bootargs countfail=${countfail} ${
bootargs}; test -n ${user} && setenv bootargs user=${user} ${bootargs}; test -n
${forced} && setenv bootargs forced=${forced} ${bootargs}
nexus_boot_rescue=echo Boot Nexus rescue from disk ${boot_disk}...; root_part=2;
 image=/rescue/uImage; if run nexus_load_image; then if test -n ${panic}; then r
un nexus_uuid; setenv bootargs ${bootargs} root=UUID=${root_uuid}; else run nexu
s_bootargs; fi; run nexus_rescue_bootargs; bootm; fi
nexus_panic=panic=1; for boot_disk in ${disk_list}; do run nexus_boot_rescue; do
ne
nexus_boot=test -n ${resetFlag_env} && forced=${resetFlag_env}; for boot_disk in
 ${disk_list}; do echo Booting Nexus layout from disk ${boot_disk}...; countfail
=0; bootfail=0; user=0; if run nexus_load_flags; then run nexus_rescue_countfail
 && countfail=1; run nexus_set_root; image=/boot/uImage; run nexus_load_image ||
 bootfail=1; run nexus_rescue_user && user=1; if run nexus_can_boot; then run ne
xus_inc_count; run nexus_save_flags; run nexus_bootargs; bootm; bootfail=1; fi;
run nexus_boot_rescue; fi; done; bootfail=1; countfail=; user=;run nexus_panic
run_diag=yes
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/m
tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000;
ethmtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
ethact=egiga0
ethaddr=00:D0:4B:94:7D:00
valid_product=1
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
resetFlag_env=0
bootdelay=0
pcieTune=no
ipaddr=192.168.1.252
ncip=192.168.1.12
serverip=192.168.1.12
stdin=nc
stdout=nc

Environment size: 3921/8188 bytes
Marvell>>

Now I also need to go to sleep. I have to work too and it's way later than I had planned.
I'll be out until Monday, so I will not be able to continue until then, but if you tell me what are the next things that we need to find out or try, I'll be happy to do it Monday or at least the soonest I can after that.

Thanks a lot for all your support.

Daniel
ElBalsero
Donator VIP
Donator VIP
 
Posts: 30
Joined: Mon Sep 30, 2013 9:46 pm
Location: The Netherlands

PreviousNext

Return to Lacie cloudbox (white casing)

Who is online

Users browsing this forum: No registered users and 2 guests