Seagate Warranty & Returns - Policy, FAQ's, Warranty Status & More. License keys for MaxTo version 2.0 and up are different than they used to be. Because we have changed how license keys work in version 2.0, you will need to update your license keys to use them with version 2.0 or above. Some of our most popular programs are now available over on the website: JANUARY 5TH - PASSING DATA FROM MAX TO ARD.
Hacking a Seagate hard disk. I will document here how to hack a Seagate hard disk that ran into one of these annoying firmware bugs that affected the Seagate Barracuda 7200.11 series lately. If you want to know more about the background you may want to start with the first part of the story. The friend who brought me the disk kindly came by the. Seagate Warranty & Returns - Policy, FAQ's, Warranty Status & More. Please check the serial number entered and try again. Need Help Finding Serial Number.
I will document here how to hack a Seagate hard disk that ran into one of these annoying firmware bugs that affected the Seagate Barracuda 7200.11 series lately. If you want to know more about the background you may want to start with the first part of the story.
The friend who brought me the disk kindly came by the next day to help with the operation. According to the recipes I found here and here, we had to connect the hard drives service port to a serial console via a RS232-TTL converter. My friend prepared the RS232-TTL converter, brought a stable power supply as we needed 5V to operate. My task was to prepare the operating table, find a serial cable and a computer with a serial port, a two-pin-connector with wires and to get to know minicom.
So and here is how we did it:
First we connected the converter to the devices. The docking station of my notebook has a serial port, so I connected it via a serial cable to the converter. The three wires coming from the converter had to be connected the hard drive directly. We fixed the ground wire with a screw of the board. The Rx and Tx connectors had to be connected to the Tx and Rx connectors of the drive (so just cross them). Thats where we used the two-pin-connector. On the drive the pin next to the SATA connector is the Rx and next to this one is Tx. The other two are reserved and we did not need them.
The most tricky part was about to be next. We had to interrupt the power supply for the motor of the platters but keep everything else connected properly. And it must be possible to remove this interruption during the operation. We unscrew all screws a little and pushed a piece of paper between the contacts of the board and the connector, and fastened the screws just a bit.
So much for the preparation. Let’s start. Here is my minicomrc I used to communicate with the drives firmware:
Now we connected the the SATA power cable to the drive and let minicom establish the serial connection. And really, I got first contact with the drive:
Even the error codes the drive dumped to the screen were correct according to the recipe. So we were on the right track. Now it was just about to properly retype the commands into minicom and patiently wait for the drive to complete the commands. Here is a screenshot with some comments in it.
Then finally we were done. But we did not repair the drive, but only reactivated it. Now it can run into the same bug again any time (but only on startup, so we would notice). So we tried to prevent as many restarts as we could. The first thing I did was connect it to an external SATA-2-firewire case and use the first startup of the disk to backup all important data. The second thing I did was connect the drive to the onboard connectors of my workstation and boot from the firmware upgrade CD I downloaded from the Seagate website the day before and deployed the new firmware to finally get rid of the bug.
In the end the disk felt quite well back in its original machine. Fortunately we had nothing more to fix within the installed system (yes, it was the other operating system).
Btw. the commands we sent to the drive took serveral seconds each to process, so we had to wait for for them to finish. Disconnecting power too early would have broken the disk. Thats why I connected all vital systems to my UPS for this hack. If you happen to have such a Seagate drive, my deepest regrets to you and good luck for your recovery hack.
Supported Versions
| Brand | Model | Version | Current Release | OEM Info | Forum Topic | Technical Data |
|---|---|---|---|---|---|---|
| Seagate | GoFlexHome | 19.07.7 | View/Edit data |
Hardware Highlights
| Model | Version | SoC | CPU MHz | Flash MB | RAM MB | WLAN Hardware | WLAN2.4 | WLAN5.0 | 100M ports | Gbit ports | Modem | USB |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GoFlexHome | Marvell 88F6281 | 1200 | 256NAND | 128 | - | - | - | - | 1 | - | 1x 2.0 |
Hardware
Info
| Architecture | ARM armv5te |
|---|---|
| Vendor | Marvell |
| bootloader | U-Boot |
| System-On-Chip | Marvell MV88F6281 A0 (DDR2) with ARM926EJ-S CPU (Marvell Feroceon) |
| CPU Speed | 1200 Mhz |
| Flash size | 256 MiB |
| RAM | 128 MiB |
| Wireless | n/a |
| Ethernet | 1x GigE port / Marvell “Alaska” 88E1116R |
| USB | 1x USB 2.0 port |
| Serial | Yes |
Note: No green led working NIC / data partition (mtd3) does not seem to be 216 MiB(see serial installation wiki (french side) + command df -h)
Serial
→ port.serial general information about the serial port, serial port cable, etc.
How to connect to the Serial Port of this specific device:
Serial port
| Serial connection parameters for Seagate GoFlexHome | 115200, 8N1 |
|---|
Flash Layout
| Original FlashLayout | ||||
|---|---|---|---|---|
| mtd# | mtd0 | mtd1 | mtd2 | mtd3 |
| start | 0x000000 | 0x100000 | 0x500000 | 0x2500000 |
| size | 0x100000 | 0x400000 | 0x2000000 | 0xdb00000 |
| in MiB | 1 | 4 | 32 | 219 |
| name | u-boot | uImage | root | data |
| file system | none | ??? | JFFS2 | ?? |
Specific Configuration
Interfaces
The default network configuration is:
| Interface Name | Description | Default configuration |
|---|---|---|
| eth0 | Ethernet port | DHCP |
Crypto Hardware Acceleration
SSH
Connect device to Ethernet port. To prevent automatic updates by cloud engines (which may disable ssh access), use a separate switch or disconnect your router from the internet. If the ssh access was disabled by the automatic cloud engine update service, you need to login there and re-activate ssh.
Find IP address, BE and EF are the last two bytes of the MAC of your device (printed on the bottom of the GoFlexHome)
Connect to IP address via ssh (root / stxadmin) to see if it works.
Backup
If you want to restore the original firmware at a later point use this guide to make a backup. You need to login to the original firmware via ssh first.Another method beside using “dd” is nanddump. To be on the safe side, you should take a 2nd backup with the nanddump method.Assuming you have a USB Stick or other USB drive mapped via sda - you can try this:
Install u-boot and OpenWrt into NAND via serial cable and tftp-server
Installation
Maxto 2017 Serial
| Model | Version | Current Release | Firmware OpenWrt Install | Firmware OpenWrt Upgrade | Firmware OEM Stock |
|---|---|---|---|---|---|
| GoFlexHome | 19.07.7 | http://downloads.openwrt.org/releases/19.07.7/targets/kirkwood/generic/openwrt-19.07.7-kirkwood-seagate_goflexhome-squashfs-factory.bin | http://downloads.openwrt.org/releases/19.07.7/targets/kirkwood/generic/openwrt-19.07.7-kirkwood-seagate_goflexhome-squashfs-sysupgrade.bin |
Prepare on PC
Download files(change the 18.06.2 in the following link into whatever is the last OpenWrt release) https://downloads.openwrt.org/releases/18.06.2/targets/kirkwood/generic/u-boot-goflexhome/u-boot.kwb
Start tftp-server
Copy files u-boot.kwb, openwrt-18.06.2-kirkwood-seagate_goflexhome-squashfs-factory.bin to /tmp
Install u-boot
Hit any key to stop autoboot in the u-boot and set goflexhome ip, tftp-server ip, set your mac-address from bottom of the machine:
download from tftp-server u-boot.kwb file to RAM start offset 0x6400000
or
Bytes transferred = 607044 (94344 hex)
erase nand start from 0x0 size 0x100000
write nand from RAM start offset 0x6400000 to nand start 0x0 size 0x100000 (1MB)
reboot device
now you are rebooting in the new u-boot
Install OpenWrt
Hit any key to stop autoboot in the u-boot and set goflexhome ip, tftp-server ip, set your mac-address from bottom of the machine:
download from tftp-server file openwrt-18.06.2-kirkwood-seagate_goflexhome-squashfs-factory.bin to RAM start default offset 0x800000
Load address: 0x800000…Bytes transferred = 4063232 (3e0000 hex)
erase nand UBI partition
write nand from RAM start offset 0x800000 to nand UBI partition size 0x3e0000
reboot device
Congratulations!
Upgrading from Chaos Calmer 15.05.1 to LEDE 17.01.4 using SSH and MTD
In version 15.05.01 'sysupgrade' not available for GoFlex Home. Use 'mtd' instead to flash the firmware.Note: This is upgrade instruction from already installed OpenWrt. Also, if you have serial access you can still do the normal installation as above.
- To ssh into the OpenWrt GoFlex Home device.
output:
- Download last firmware release LEDE 17.01.4 to /tmp:
- Check extracted files:
output:
- Write 'kernel':
Seagate Serial Number Checker
- Write 'rootfs' with reboot after: