Installing FVDW on a Seagate Personal Cloud

[fvdw]

:punk good news

It means we can go on to compile a kernel to run the firmware and use the standalone kernel to install it.

I will be back in a few days with a kernel that can be used to run the firmware.

The procedure will be as follow

You use one of the two standalone kernel to run the fvdw-sl installer, we will install the kirkwood package, the package for original lacie cloudbox.
When that is done we will replace the kernel in sda6 by the armada-370 kernel that I will compile and post later
Then we modify the bootcmd in uboot environment to load the kernel and root file system at boot

After that if the firmware boots we will add the modules required for this box, does it has an usb port ? and adapt some files in the firmware to support this platform

piece of cake ;)

[TonyP]

Yes, this box has 2 USB ports, one of them is USB 3 (blue).

Thanks for the work fvdw.

[fvdw]

Attached the running kernel for fvdw-sl firmware.

whats next

1. Put the kernel in the tftp directory of the fvdw-sl console, we will need it later to upload it and replace the krikwood kernel (unzip the archive)

2. Start the fvdw-sl console and use option install firmware, Choose as standalone kernel the one I have sent previously
, start the installer program (see help text in the console) and choose kirkwood cloudbox.

3. When the installer has finished don't reboot but upload the new kernel and write it to sda6
(replace ip-pc by actual ip address of your pc running the tftp server form fvdw-ssl console, the -l is the small l from local and not the number 1)

Code: Select all

cd /
tftp -r UIMAGE-466-SGARMADA370-3 -l UIMAGE-466-SGARMADA370-3 -g  ip-pc

When up load is finished write it to sda6 (be sure you type sda6)

Code: Select all

cd /
dd if=UIMAGE-466-SGARMADA370-3 of=/dev/sda6
sync

Now poweroff the seagate

4. You still cannot boot the firmware we need to adapt the bootcmd of the bootloader
As a trial you could also boot from uboot and enter the bootcmd manually
So start the u-boot console of the the fvdw-sl console and at marvel prompt set the bootcmd

Code: Select all

setenv bootcmd 'disk 0x2000000 0:6 ; setenv bootargs console=ttyS0,115200 root=/dev/sda7 ; bootm 0x2000000;'
saveenv

5. As you tested that "bootcmd" will not be overwritten you can now reboot from uboot using command reset

Code: Select all

reset

And if you installed the firmware correctly in step 3 then the firmware should load and fvdw-sl web interface becomes accessible
There will be errors and some features will not be available as the firmware will classify this devices as unknown but it should run. (which ip to use ? see your dhcp list or use fvdw-sl assistant, it should detect the nas after some time)

ssh access should be available on port 22 (user: root pasword: giveit2me)

ps Note that in linux user, file names and passwords and commands are case sensitive !
ps2: winscp is a great program to browse the system tree and transfer file, be sure to set file transfer to binary as otherwise binaries will not be transferred correctly.

Success ! I keep my fingers crossed :mrgreen:

[TonyP]

Success, thanks fvdw. I'm having a play with it now. Looks nice!

[fvdw]

Nice :punk

Web login is
User: admin-nas
Passw: admin

You can change the password in the web interface
Every page has a help page, click help or the ? button top right

[Jocko]

Hi Tony

Currently with the unknown platform status, you should not be able to install the rollup patch for version 17.0 (https://plugout.net/viewtopic.php?f=7&t=2695).

So you need some edited files to fix this issue.
Can you post the content of cpuinfo

Code: Select all

cat /proc/cpuinfo

[TonyP]

Code: Select all

root@fvdwsl-base:/ # cat /proc/cpuinfo
processor       : 0
model name      : ARMv7 Processor rev 1 (v7l)
BogoMIPS        : 41.55
Features        : half thumb fastmult vfp edsp vfpv3 vfpv3d16 tls idivt CPU implementer : 0x56
CPU architecture: 7
CPU variant     : 0x1
CPU part        : 0x581
CPU revision    : 1

Hardware        : Marvell Armada 370/XP (Device Tree)
Revision        : 0000
Serial          : 0000000000000000
root@fvdwsl-base:/ #


[Jocko]

Hi Tony,

With the attached file, the firmware will handle your nas like a network space 2 and then you will be able to install patches or other extra-packages.
Please to note, you are not still able to upgrade the firmware.
(This will be done only if you want to keep our firmware on your nas : need to make some other changes to have a full support)

To install the new file, do :
* store the attached tarball in the share 'public' (I assume you did not yet remove this default share after installing the firmware)
* open a shell terminal and run the command

Code: Select all

tar -xf /direct-usb/public/fvdw-sl-17-0-seagate-cloud-07jun2018.tar.gz -C /

* restart the nas, your nas should be seen now as a nwsp2 (information can be got either from the system information menu or from the firmware upgrade menu)

[fvdw]

another file to load modules to activate the usb port, could be tat ehci-pci module must be loaded as well but lets try usining standard nwsp load modules script

to install put the file in the public share and in ssh terminal give command

Code: Select all

tar -xf /direct-usb/public/armada-370-466-modules.tar.gz -C /

Modules should be loaded at next boot. To check view content of the the /boot.log file to see if errors occur
After boot you can give command

Code: Select all

lsmod

to see loaded modules

plug in an usb disk to see if your usb port works

[TonyP]

Yes, the usb module works. Automount and auto SMB sharing - nice one!

Thank you for the work you have put into this fvdw.