CloudBox with deleted partitions

[dr4g0nsr]

Hello,
I have this device with deleted partitions, can i install this fw with blank disk?
So far i tried to re-create partitions (found partition map in this forum) and extracted image file from cloudbox firmware which i later on copied on /dev/sda7 bit it didn't work. I also tried to run kernel with fvdw-sl console, it copied kernel sucessfully but it didn't start after booting the kernel (telnet not working)?
What should i do to make this work?

[fvdw]

yes you can
you should use the fvdw-sl console and load the standalone kernel as in prsenet in the tftp directory of the fvdw-sl console. The best is to choose as action in the fvdw-sl console "install fvdw-sl firmware" That will ask to select the standalone and give an instruction what to do next

ps besides the kernel in sda6 (as uimage) and the firmware in sda1, sda2,sda7 you also need the main database on sda5. Without the firmware cannot run.
You can all do this manually but using the fvdw-sl consoleis much easier

[dr4g0nsr]

I already tried that.
I started fvdw-sl console and chose install fvdw-sl firmware. TFTP server started and asked for file, i chosed standalone kernel - UIMAGE-395-NWSP2CL-179-standalone. In the console i saw it loaded the kernel correctly (checksum and other stuff), waited 12 secs for telnet and telnet didn't want to connect to defined ip. I tried manually to telnet again but it didn't work. Also box stopped responding to arp requests as soon as kernel is run.
I also tried UIMAGE-395-NWSP2CL-199 but same thing happened.
I figured out i cannot do this becouse kernel couldn't find root system (which is deleted)?
That's why i tried to manually re-create partition hoping it will start to boot it.

[dr4g0nsr]

UPDATE:
I have managed to make it work by creating partition like it was described in readme html file and writing image extracted from xfvdw-sl-15-1-cloudbox-18feb2014.bin to /dev/sda7 partition (or 7th partition).
After that i used clunc to manually boot to see what's happening. I saw kernel loaded fine - no errors but the box won't come up at 192.168.1.1.
I examined log file in root (boot.log) just to see that box get it's ip from DHCP.
So i fixed lease and booted box again and i see it come to this ip.
I run fvdw-cl console, set ip from leased dhcp, selected install fvdw firmware and followed the manual.
After this box come up at leased IP.
I tried to access the web but it didn't work. I don't know the password for login so i "hacked" the box and found .htpasswd which i changed later on after generating another one with htpasswd.

[fvdw]

glad to hear that you got it working
ps de standalone kernel uses 192.168.1.252 or 192.168.0.252 and it tries to get an ip from your dhcp server
Anyhow you manged to get it working

the default username for the web interface is: admin-nas and password admin
You will need it as .htpassword will be overwritten with the one set by the firmware using the one stored in the nas database

[dr4g0nsr]

Procedure does not work if disk is partitioned with fdisk and disk is >2TB so gdisk is used.
First question is about to remove fdisk partition and use only gdisk but installer does not handle it.
I solved this by manually converting disk to gdisk only before script was run.
I suggest using noatime and nodiratime as mount options (there is nothing set in fstab so it's using kernel defaults).
Can't further explore this device as it's not mine so i returned it.