New Member, cloudbox slowly flashing blue.

[dawnovsky]

Good evening everyone,

I am new here, unfortunately not for pleasure but because my Cloudbox does not respond anymore.
I want to warmly thanks fvdw for assistance with the forum subscription;

Quick presentation :
43 years old, not in a computer career but have been playing with almost everything since Apple-2C 4 decade ago, so comfortable with linux, networking, windows of course and able to use soldering iron.

So for my problem :
My good old Lacie Cloudbox 2To WITH LACIE FIRMWARE has been running strong since year, mainly as a media vault and Mac time capsule with wake on lan startup when needed a scheduled shutdown every night. So it spend most of it's time off waiting for wake up.
When i came back home after 15 days abroad i found the Box ON, not responding to power button (tu turn it OFF), not responding on it's web interface, not answering on shared folder, and slowly FLASHING BLUE.

1. I have tried factory reset.
2. I have then found Plugout forum, register and download Console.
3. Try to start U-boot Console : No Joy
4. Remove the drive from casing:
4.1 try the disk on my linux set : can see all partitions (8), have not try to mount RAID module yet, but it might work.
4.2 try U-boot console with disk remove : It works .
4.2.1 load KirkWood stand alone kernel : It 's loading, but not starting and freeze at "Starting Kernel ..."
4.3 restart, Hot plug the drive right after U-boot console catch the unit ("Press enter" stage) : PRINTENV can see the drive . IDE RESET can see the drive too.

What do you guys think ?

there s several thing i want to do :
1. recover my data from the drive (directly from the unit or via my linux desktop setup)
2. Save my cloudbox unit if possible either with FVDW-SL or factory firmware wathever will work.


Many thanks in advance

[fvdw]

Is this a cloudbox in a white casing?
This because there is also an older cloudbox in black casing, we support only the white casing type with kirkwood cpu.
In case you have the black one this could be the reason why standalone kernel freezes at start kernel as that device needs another kernel.

In case uboot console and standalone kernel do not load with disk installed but load without a disk this could point to a power supply issue.

You write that uboot console loads without disk installed.
Do this and post output of printenv command.

[dawnovsky]

Is this a cloudbox in a white casing?
This because there is also an older cloudbox in black casing, we support only the white casing type with kirkwood cpu.
In case you have the black one this could be the reason why standalone kernel freezes at start kernel as that device needs another kernel.

Yes, this is a white casing CloudBox.

In case uboot console and standalone kernel do not load with disk installed but load without a disk this could point to a power supply issue.

That was my initial thought, and this will be a good news. I have try another 12V/2A with no improvement. I know when disk gets old they need more Amps. I should try with a much stronger power supply and see how things are going

[fvdw]

ok, but please post also output from command printenv when being in uboot terminal (marvell>> prompt)

[dawnovsky]

ok, but please post also output from command printenv when being in uboot terminal (marvell>> prompt)

as requested , here's the drop from console

WITHOUT DISK :

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 $boot_disk -eq 1; then rootfs=/dev/sdb7; fi
legacy_nand_boot=
legacy_disk_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=${rootfs};
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_disk 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_max_count}; fi
nexus_set_root=if test $saved_entry -eq 1; then root_part=5; else root_part=4; fi
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}; ext2uuid 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 run nexus_uuid; setenv bootargs ${bootargs} root=UUID=${root_uuid}; else run nexus_bootargs; fi; run nexus_rescue_bootargs; bootm; fi
nexus_panic=panic=1; for boot_disk in ${disk_list}; do run nexus_boot_rescue; done
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 nexus_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/mtdblock0 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:96:0E:16
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.140
serverip=192.168.1.140
stdin=nc
stdout=nc

Environment size: 3923/8188 bytes
Marvell>>

WITH DISK HOT PLUGGED

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

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 $boot_disk -eq 1; then rootfs=/dev/sdb7; fi
legacy_nand_boot=
legacy_disk_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=${rootfs};
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_disk 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_max_count}; fi
nexus_set_root=if test $saved_entry -eq 1; then root_part=5; else root_part=4; fi
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}; ext2uuid 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 run nexus_uuid; setenv bootargs ${bootargs} root=UUID=${root_uuid}; else run nexus_bootargs; fi; run nexus_rescue_bootargs; bootm; fi
nexus_panic=panic=1; for boot_disk in ${disk_list}; do run nexus_boot_rescue; done
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 nexus_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/mtdblock0 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:96:0E:16
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.140
serverip=192.168.1.140
stdin=nc
stdout=nc

Environment size: 3923/8188 bytes
Marvell>>

[dawnovsky]

also,

bootm send the following answer :

Code: Select all

Marvell>> bootm
bootm
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

last time i have seen "Bad magic number" was on a broken ntfs partition

[fvdw]

printenv output seems to be normal.
How did you connect your pc and cloudbox to your lan? Is there a router were both are connected and do you use a wired connection between pc and router?

[dawnovsky]

It is usually connected via a wired switch, static Ip. Computers are both wired or wireless.
The problem does not seem to be how I access my box since the box is actually not starting and keep flashing blue (slowly) .

[fvdw]

We advise to run the fvdw-sl console on a pc with wired connection to the LAN. (Disable a wireless adapter if also present).
Transferring files via wireless connection has been proven to give problems with files going corrupt.

Lets try to do a manual upload of the standalone kernel using the fvdw-sl console (remove the disk from the cloudbox for the moment)
Start the console and choose as action start tftp server, grant the tftp server access through your firewall or disable the firewall.
Then start the uboot console and when waiting for uboot start your cloudbox and go to the marvell>> prompt
At the marvel prompt give these commands

Code: Select all

setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/


use the commands exactly as they are given so do not replace the parameters ipaddr and serverip leave them as they are in this command
PS the u-boot console window has a paste option (right click on title bar)
check if now bootargs parameter is set to this string

Code: Select all

printenv bootargs

proceed if the output confirm what you have set.

Code: Select all

ide reset
tftpboot 0x800000 UIMAGE-3142-KIRKWOOD-171-standalone


Now you should see in the uboot window that the kernel is uploaded.

It will look something like this example

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done
Bytes transferred = 3123520 (2fa940 hex)

When the kernel is uploaded give this command

Code: Select all

bootm

You should see in the u-boot window that the kernel is started, after a while you should see kernel output in the uboot window.
When loading and starting of the kernel has succeeded, connect to it using the telnet terminal from the fvdw-sl console.
If you did not change the default settings of the console you should be able to connect with ip 192.168.1.252 (assuming you use as ip pool 192.168.1.XXX)
When the telnet client has connected log in using credentials (user) root (password) giveit2me

If this works then you could repeat with disk installed or hotplug the disk before starting the mentioned commands above

ps blue flashing of the led means, according the manual, that device is booting, in your case booting seems to be failing so it will blink forever.

[dawnovsky]

Thank for your answer .

To clarify ;
All Uboot console operations have been made via wired lan as recommended on all forum how tos
Jirwood stand alone kernel has been uploaded successfully before but always freezing at the « starting kernel … » phase .

I will try again asap with the suggested argument to make sure but having doubts it will ever change anything.

What should do If I ever get to boot with the stand alone and the drive ?
I guess I will have a « functional » unit to try to retrieve my data.

Any chance to fixe the boot on the long run ?