plugout.net

Hello!

I'm trying to install fvdw firmware by fvdw-sl-console, when i select standalone kernel and "UIMAGE-395-NWSP2CL-179-standalone" the file is uploaded to nas.

At the final of process the telnet client is open and try to connect to nas, but timeout error appear ...

My Nas is a Cloudbox (white) and the led is blinking fast in blue color.
The HD is a new hd (3Tb), the original hd is briked (3Tb too) ...

The Lacie Network Assistant found the device too, send the .capsule and device reboot (solid red led) but the led continue to blinking in blue color..

The device appear when i try "arp -a" with ip 192.168.0.250 and 192.168.1.252 with fvdw-sl-console.

i'm lost ... i don't know what i do now :( .. Sorry for my english..

Hi killuabr,

There is many posts about your issue, you should read them.

For example: viewtopic.php?f=28&t=1942

Hi Jocko, Tks for reply.

I've been reading the forum posts and I've tried several things, including this.

My problem is apparently not the console, it works and the firmware is sent to the CloudBox, but nothing happens after. I do not know if it has something to do, but my hd is new, I do not have partitions.

It's necessary partitions in my hd? the firmware format the hd?

I try this, but failed too... http://lacie.nas-central.org/wiki/Insta ... space_2%29

I try to use Clunc in a linux virtual machine and i get the console! So this device is not completely dead :-D

Code: Select all

Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter

Marvell Serial ATA Adapter
Integrated Sata device found
PCIe SATA:ffffffff

Marvell>> run nexus_boot
run nexus_boot
Booting Nexus layout from disk 0...
** Bad partition 3 **
Booting Nexus layout from disk 1...
** Bad partition 3 **
Boot Nexus rescue from disk 0...
** Bad partition 2 **
Boot Nexus rescue from disk 1...
** Bad partition 2 **


printenv

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:94:41:97
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.0.250
ncip=192.168.0.123
serverip=192.168.0.123
stdin=nc
stdout=nc

Environment size: 3923/8188 bytes
Marvell>>


any idea? :thinking

Your test confirms that you have an issue with your laptop (OS settings).

So:
- Don't use wireless connection,
- Disable all firewall (custom firewall and Defender if this one is available after disabling your firewall) or add some rules for nc and fvdw-sl console (see also if your anti-virus doesn't have a firewall feature)
- Keep enable one network interface card (NIC)

Jocko wrote:Your test confirms that you have an issue with your laptop (OS settings).

So:
- Don't use wireless connection,
- Disable all firewall (custom firewall and Defender if this one is available after disabling your firewall) or add some rules for nc and fvdw-sl console (see also if your anti-virus doesn't have a firewall feature)
- Keep enable one network interface card (NIC)

Tks for reply!

I'll try to install fvdw with hd plugged and a machine with xp. I'll post the results, thx again.

You have a tutorial to install fvdw by linux?
What line says problem is in my pc?

In saturday morning i tryed to install fvdw one more time.

In a XP machine:
I disabled the firewall and the antivirus (avg).
This machine dont have a lan, only wlan (a old pci wireless B).

I plugged the lan cable of NAS in a Router and hung up the NAS.
I've Downloaded the console and select "standalone kernel" and start the nas, in first time this fail, so i close all and turn off the Nas again.
In second time, the console found the Nas and upload the kernel, but telnet fail again... BUT for my surprise the NAS received an ip :shocked, this never happened before! So, i change the ip in telnet client and this worked!

I followed all procedures in helps file and ... Great news! My Cloudbox is live :woohoo :punk :bananadance !

Tks for help! Donation is comming!

If you need a help to translate the system for pt-br maybe i can help ...

http://imageshack.com/a/img910/4100/XuUJgw.jpg
http://imageshack.com/a/img661/9075/ipH5Bq.jpg

Hi killuabr,

So glad to see that you succeeded to install fvdw-sl on your cloudbox.

killuabr wrote:http://imageshack.com/a/img661/9075/ipH5Bq.jpg

Maybe, the menu failed to load because you did not have clean the browser cache after upgrading the firmware (vers 15.3).
To clean the cache you need to close all browser windows (but for Chrome you must purge the cache manually)

killuabr wrote:If you need a help to translate the system for pt-br maybe i can help ...

Yes you can, see the topic http://www.plugout.net/viewtopic.php?f=16&t=858#p16103

Hi killuabr,

To fix your issue, you can try this patch. To install it you need to create a share 'fvdw' and save the zip file in it.

How to install the patch :
- Save the attached zip archive in the fvdw shared folder
- Go to the upload patch menu of the web interface
- Select the file in the first field (click on the small button "...")
- Put in the second field (control code) the following code : "unzip" (without quotes)

Then Click on the button Accept and you must get this success message :
Ok: Install patch successful.

Then, after installing the patch without rebooting the nas, do in a shell terminal (use for example Putty):

Code: Select all

/etc/leds_bootup     //to init rightly the LED settings in sys folder
/etc/leds_switch off    //all led should be off (front)
/etc/leds_switch on    //all led should be on (front)

If all is ok, after running the command 'leds_bootup', blue LED should stop to blink.

You should be able to switch off/on the LED in the web-interface (other settings menu).

If you select the option 'led off at boot', the LED should be off after booting.

hi Jocko!

I've tested the update and it was successful. The led stop blinking, but if i restart the led start blinking again ...

The option System settings > Information, continue not showing. I've tested in other pcs and clean the cache.

The Setup menu is not ok too...
http://imageshack.com/a/img537/4766/z8pJXh.jpg

Maybe the other options have not been translated?

---- Edit ----
I've installed the dictionary and enable it (./edit-dictionary -a) and the options appear :dontknow