Installing FVDW on a Seagate Personal Cloud

[fvdw]

ps Use a wired connection between PC and LAN

[TonyP]

Code: Select all

Marvell>> setenv ipaddr ${ipaddr}; setenv serverip ${serverip}
setenv ipaddr ${ipaddr}; setenv serverip ${serverip}
Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7
Marvell>> tftpboot 0x2000000 uImage-4.2.3-sgpc2-standalone
tftpboot 0x2000000 uImage-4.2.3-sgpc2-standalone
Using egiga1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.8
Filename 'uImage-4.2.3-sgpc2-standalone'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #############
done
Bytes transferred = 5909467 (5a2bdb hex)
Marvell>> bootm
bootm
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   linux-armada370-sgpc2.dtb
   Created:      2018-05-24  12:11:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5909403 Bytes = 5.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...


ps Use a wired connection between PC and LAN

Yes, it's cabled. Looks ok, and I can see the telnet server, just can't connect. I turned on the telnet admin console on my router and I can access it fine, just not the NAS :(

Code: Select all

Starting Nmap 7.70 ( https://nmap.org ) at 2018-05-25 19:03 AUS Eastern Standard Time

Nmap scan report for 192.168.1.8

Host is up (0.0084s latency).

Not shown: 99 closed ports

PORT   STATE SERVICE

23/tcp open  telnet

MAC Address: 00:10:75:57:90:D2 (Segate Technology)

Nmap done: 1 IP address (1 host up) scanned in 1.08 seconds


Code: Select all

Starting Nmap 7.70 ( https://nmap.org ) at 2018-05-25 19:06 AUS Eastern Standard Time

Nmap scan report for 192.168.1.251

Host is up (0.0083s latency).

Not shown: 99 closed ports

PORT   STATE SERVICE

23/tcp open  telnet

MAC Address: 00:10:75:57:90:D2 (Segate Technology)

Nmap done: 1 IP address (1 host up) scanned in 1.40 seconds


I turned off Windows firewall (but I'm certain that it's not the root cause because there is a difference when attempting a connection between 192.168.1.8/251 and a non-existent IP). Also I can't connect via JuiceSSH app (android, I know wireless isn't recommended but ok for attempting fault finding)
It's frustrating because this should be the easiest last step! I'm certain there is a problem with this kernel. Are you compiling it on the machine that hosts plugout? The site is timing out/running very slowly....

[fvdw]

bummer

:scratch

It is odd, if it can receive and set an ip then network interface is up and able to receive and send data
it should also be able to talk to you

What is the ip address pool of your dhcp server, and can you reach ip's with 192.168.1.*** in other words is perhaps your subsetmask of your NIC set in a way that it doesn't allow to speak to devices with this ip range ?
However in such case you should also be unable to upload the kernel, so that points in direction of the kernel itself.

What was the nas ip when the lacie kernel and firmware runs ?

I compiled the kernel on separate machine.

PS the kernel has net console enabled it should give when the NIC comes up give output in the console window. This indicates also that something block communication between PC and nas although it seems to be able to get an ip which is contradicting ???

Does this device has a serial port ?

You could also poke on the root file system of the seagate when lacie firmware is running to see if you can find the the config file also post the umage you found in sda2 then I can try to extract the config file from it, most of the time it is included in the kernel.
Typical locations of the kernel and config file are directory with name boot.

Also you could get it probably from the kernel itself with this command

cp /proc/config.gz /config.gz

or
cat /proc/config.gz | tar -xzvf > /running.config

[TonyP]

Please find the config.gz attached.

I'm not sure if this device has a serial connector, but I'll pass if it does. I have played around a bit much with this device already (I was a Linux noob before I got this box but have learned a lot from it, but wife and kids are not happy with I sit there for a few hours playing with it each night).

[fvdw]

Oke Tony

I will have a look at it and adapt the the kernel compile.
About wife and kids not happy. Can understand it and recognize it ;)
but we can do this without hurry, at least for me there is no hurry, so take your time.
and we will do this step by step. So no problem if I post something and need to wait for reply.
Reply or test files whenever you have time

[TonyP]

Hi fvdw,

I wanted to thank you for your time helping me with the software. I decided it would be the path of least resistance to install Debian on the personal cloud and run webmin to configure it.

Thanks for all your assistance,

Tony.

[fvdw]

Oke Tony
Done with pleasure
Hopefully you are still willing to test a few stanalone kernels. Based on the seagate config I will compile a 4.6.6 kernel. It may enable us to offer support for this device in the future. We are always intested to add a new device

Ps it may be possible to run the firmware in chrooted environment using Debian

[TonyP]

I'd be happy to test the standalone kernels. I'm running Debian on another hard drive while I make sure it's right for me, so the Seagate partitions and data are untouched. The case is open and it's very easy to swap drives. I also found some information on USB booting that you may find useful/interesting - http://lacie-nas.org/doku.php?id=usbboot .

[fvdw]

Hi TonyP

Yes I know that link but first of all we need a running kernel that we can modify.

Attached two trial standalone kernels (linux-4.6.6) based on config you posted.
Number 1 maybe a bit to large, therefor also nr 2 with a size below 6 MB, hopefully it is suffcient

Can please test them, if they load and give telnet access ?

thank you

[TonyP]

Success!

Yes, both kernels give telnet access.

Also, I have found a way, via Russian website, of how to easily reinstall the original firmware and partitions onto this Seagate Personal Cloud NAS, so I'm not worried if we break something here, plus I am working on a second hard drive now, the original is safe in a drawer. A user took a full disk image of an 80GB drive that they did a fresh wipe/install on, and you simply raw copy the image onto the drive through Windows with a very small (2 Mb) portable app. Details here (hope you don't mind external links) - http://forum.ixbt.com/topic.cgi?id=109:6:108#108 or if you want to take your own image instructions here- http://forum.ixbt.com/topic.cgi?id=109:6:157#157