Restoring GoFlex Home Stock system

If I kwboot my GoFlex Home unit, which still has the original Stock firmware on it, can I backup the system to an external device and restore it if necessary?

balanga Wrote:
-------------------------------------------------------
> If I kwboot my GoFlex Home unit, which still has
> the original Stock firmware on it, can I backup
> the system to an external device and restore it if
> necessary?

Looking at this topic seems to move me in the right direction:-

https://forum.doozan.com/read.php?3,16789,16789#msg-16789

Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions

Not sure if this can be adapted to GoFlex Home...

For each mtd on the list

cat /proc/mtd

You would do

nanddump --noecc --omitoob  -f mtd0.gfh  /dev/mtd0
nanddump --noecc --omitoob  -f mtd1.gfh  /dev/mtd1

and so on.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Just found an interesting tutorial on the subject....

https://cyanlabs.net/tutorials/recovering-a-seagate-goflex-via-serial/

Just noticed that this section:-

OK now for the software side of things, You will need to download this file (This is for Go Flex HOME and may or may not work on the Go Flex Net, Net users will have to find the .kwb file elsewhere.) and extract it to a folder.

has a broken link to https://cyanlabs.net/wp-content/uploads/2013/07/goflexhome.zip - so not really sure what this file is...

Also noticed references to PumpKIN.exe and have no idea what that is supposed to be.



Edited 1 time(s). Last edit at 03/07/2019 07:21AM by balanga.

what i find most interesting from the link provided.

Now we enter some commands in the unit (if you didn’t interupt boot then reboot the system and interupt the boot. (Replace the IP’s with IP’s appropiate for you)

setenv ipaddr 192.168.1.210 # Has to be in your ip range

setenv serverip 192.168.1.36 # IP address of your TFTP server (This computer)

Now that we have the TFTP setup, We need to run the previously extracted PumpKIN.exe With both the .KWB and PumpKIN.exe in the same folder will now type the following in to the serial console window.

tftpboot 0x800000 goflexhome.kwb

PumpKIN should pop up asking whether you want to grant access or not, Make sure to grant access. Make sure the output says “Bytes transferred = 524288 (80000 hex)” then type

nand erase 0x0 0x80000

Make sure the output contains “OK” then

nand write.e 0x800000 0x0 0x80000

Make sure the output contains “524288 bytes written: OK” then

reset

@bodhi - could we utilise this approach for other devices that have been soft-bricked or do not support the loading of kwboot from the serial console?



Edited 1 time(s). Last edit at 06/27/2018 05:24AM by Gravelrash.

@Gravelrash,

There is nothing new in that post. We covered this a few times in this forum already.

The Wiki thread "Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions" describes a similar process.
https://forum.doozan.com/read.php?3,16789,16789#msg-16789

Note that of loading uboot image (in this case, the entire mtd0 is the uboot image) from USB or tftp achieves the same thing.

Quote

3. Start the USB drive

usb start
Expected output

starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

4. Load the backup mtd0. Here the stock mtd0 backup file name was mtd0.pogo_v4

ext2load usb 0:1 0x800000 /mtd0.pogo_v4
Expected output
2097152 bytes read in 1318 ms (1.5 MiB/s)


5. Erase mtd0

nand erase 0x0 0x200000
Expected output
NAND erase: device 0 offset 0x0, size 0x200000
Erasing at 0x1e0000 -- 100% complete.
OK

6. Flash mtd0.pogo_v4 to NAND mtd0

nand write 0x800000 0x0 0x200000
Expected output

NAND write: device 0 offset 0x0, size 0x200000
2097152 bytes written: OK

7. Reset the box to boot with stock u-boot
reset

Somewhere in this forum I have shown how do this using tftp, and forgot to save that link :)

The bottom line is for this to work, uboot must be still intact on mtd0 and can be started (even if its envs are all gone or messed up). If uboot itself is messed up, then the only way to recover is kwboot or JTAG.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
Thanks for the education :)


... ill get back in my corner now... :))))

Gravelrash Wrote:
-------------------------------------------------------
> @bodhi
> Thanks for the education :)
>
>
> ... ill get back in my corner now... :))))

Not at all:) that’s a good question that cleared up a few things for some users.

We certainly need a diagram to describe all possible paths in the boot process.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/27/2018 05:53PM by bodhi.

Another useful link is this:- https://archlinuxarm.org/forum/viewtopic.php?f=53&t=4334

which show how to bypass the registration process and reset root password when installing. I think it depends on a previous version of the firmware - goflex_2_7_1_firmware.zip which no longer seems to be available anywhere. If anyone does know where to find it, please let me know.

bodhi Wrote:
-------------------------------------------------------
> For each mtd on the list
>
>

> cat /proc/mtd
>

>
>
> You would do
>
>

> nanddump --noecc --omitoob  -f mtd0.gfh 
> /dev/mtd0
> nanddump --noecc --omitoob  -f mtd1.gfh 
> /dev/mtd1
>

>
> and so on.


bodhi,

What about a restore?

I tried following http://forum.doozan.com/read.php?3,16789,16789#msg-16789

but whilst uBoot seemed to get restored it wouldn't boot. Here is a boot log:-

         -- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** QSI BOARD: NAS-PLUG LE

U-Boot 1.1.4 (Jun 10 2010 - 08:28:13) Marvell version: 3.4.27
QSI NAS version: 1.0.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
*** Warning - bad CRC or NAND, using default environment

Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  3 ... 2 ... 1 ... 0
Using egiga0 device
TFTP from server 169.254.254.254; our IP address is 169.254.254.253
Filename 'uImage'.
Load address: 0x2000000
Loading: *.T T T T T T T T T T ~
[EOT]



         -- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** QSI BOARD: NAS-PLUG LE

U-Boot 1.1.4 (Jun 10 2010 - 08:28:13) Marvell version: 3.4.27
QSI NAS version: 1.0.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
*** Warning - bad CRC or NAND, using default environment

Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  3 ... 0
NAS>> printenv

baudrate=115200
loads_echo=0
ipaddr=169.254.254.253
serverip=169.254.254.254
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
bootcmd=tftpboot 0x2000000 $(image_name); setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConf
ig) $(mvPhoneConfig);  bootm 0x2000000;
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
bootdelay=3
disaMvPnp=no
ethaddr=00:50:43:1e:1e:01
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
pcieTune=no
ethact=egiga0

Environment size: 1099/131068 bytes
NAS>> ~
[EOT]

Not sure where to go from here....

balanga,

That instruction is for Phogo V4. It is needed to be modified for GoFlex Home.

If you did exactly as the instruction stated, you have overwritten the GF Home stock kernel in NAND! so that's why it did not boot.

Please post the log of what you did, as usal, and I'll modify the commands you've made. I can modify it quicker if you post log.

Or I will come back later with new instruction for GoFlex Home eventually if you want to wait.

In the mean time list the backup mtds that you did for this box (all 4 mtds).

ls -lart mtd*

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> balanga,
>
> That instruction is for Phogo V4. It is needed to
> be modified for GoFlex Home.
>
> If you did exactly as the instruction stated, you
> have overwritten the GF Home stock kernel in NAND!
> so that's why it did not boot.
>
> Please post the log of what you did, as usal, and
> I'll modify the commands you've made. I can modify
> it quicker if you post log.
>
> Or I will come back later with new instruction for
> GoFlex Home eventually if you want to wait.

bodhi,

there's no real urgency. I did manage to reflash it with stock from what I had managed to restore.

But it would be nice to have a restore procedure as I'm sure I'll need it at some point.