Seagate local cloud 10.0.0.01 install#
Seagate local cloud 10.0.0.01 serial#
Seagate local cloud 10.0.0.01 software#
Seagate local cloud 10.0.0.01 download#

Since the Seagate devices don't have any IO device, SSH will be used for the installation. Tftpboot 0x5000000 armada-370-seagate-YOURDEVICE.dtbĮnsure you use the same IP for clunc and for the ipaddr variable. Now you can load the installer with the following commands: Open clunc, start your Seagate device and wait for clunc to open U-Boot's network console. (Even though the Seagate devices have USB ports, the boot loader doesn't support loading the files from a USB stick.)

Seagate local cloud 10.0.0.01 install#

Please install a TFTP server on your host PC and provide the files you just downloaded via TFTP. If you use a wrong DTB, your device may not function correctly.

Seagate local cloud 10.0.0.01 download#

Make sure to download and load the correct DTB for your device. Choose the DTB for your device:Īrmada-370-seagate-personal-cloud.dtb for Seagate Personal Cloud (1-Bay)Īrmada-370-seagate-personal-cloud-2bay.dtb for Seagate Personal Cloud (2-Bay)Īrmada-370-seagate-nas-2bay.dtb for Seagate NAS (2-Bay)Īrmada-370-seagate-nas-4bay.dtb for Seagate NAS (4-Bay) You also have to load one of the following DTB (a hardware description of the device). We'll also configure the Seagate device to boot Debian from disk. We'll use clunc to connect to the network console to load Debian installer. Users are advised to record the uboot IP address 'ipaddr=' setting for future uboot access. This is the temporary IP address uboot uses for 3 seconds while waiting for a lump/clunc packet, and if none arrives, the nas continues the boot process, where the IP is then governed by the linux kernel (DHCP or static, depending on user settings). It has been suggested that the issue is caused by the uboot environment setting 'ipaddr='.

Seagate local cloud 10.0.0.01 serial#

Therefore, we suggest you only install Debian if you can make a serial console in case something goes wrong. Even though we investigated this issue, we couldn't figure out why this would happen to some users.

Seagate local cloud 10.0.0.01 software#

Several users have reported that they can't connect to U-Boot with clunc anymore after installing Debian (meaning they can't restore the original software or re-install Debian). Make sure to connect the cable to port 1. The Seagate NAS (4-Bay) has two Ethernet ports. When a connection is obtained, you should be able to see the U-Boot prompt: We'll use 192.168.1.102 as the example IP address: You have to pass an IP address to clunc in order to open a network console.

If clunc is not running, your Seagate device will continue the boot process. When the Seagate device boots, it will wait a few seconds to see if clunc is requesting a network console.

You can now use clunc to connect to U-Boot's network console. Since clunc is currently not packaged for Debian (see the Request for Package), you have to obtain it from the Git repository and compile it yourself: There's a tool called clunc which can be used to connect to U-Boot's network console.

We will use this to load Debian installer and to configure the boot loader to boot Debian from disk. The Seagate Personal Cloud and Seagate NAS devices allow you to connect to U-Boot, the boot loader, via the network with the use of U-Boot's network console feature. This warning does not apply to the Seagate NAS (2-Bay and 4-Bay) on which the original Seagate software can be re-installed with a web interface even after you format the disk.

We therefore suggest you create a disk image before you install Debian. The Personal Cloud devices come with the Seagate NAS firmware pre-installed and there is no easy way to re-install the Seagate NAS firmware after you install Debian. Please note that the Seagate Central (STCG) is not supported.