Riddles/Enigmas - Goflex Net (3 replies)

My dad found me a Seagate GoFlex Net....

Before opening it up, i'd like to know more about it (like will it work)

So...
No hard drives or usb dongle doohickies plugged in..
I foolishly plugged it into my home network and gave it power...
.... after a few seconds... I got a green light...
(No magic smoke escaped...)

I found its ip address from my router and tried connecting via browser...

Nada/zilch/no web...

Port scanned it
23 - telnet
80/443 - http(s)
3333 - dec notes? (Really....hmmm)

No output on web...(either port)
Okay
Telnet in...
I gotta prompt!
5 minutes of googling and I have a 'stock' root account - root/stxadmin

About all I canfind on this is busybox/dropbear and a few cloudengine files
(Cue Peggy Lee - 'Is that all there is...')

No web, no dropbear config, no www dir, nada...

bash-3.2# uname -a
Linux Pogoplug 2.6.22.18 #81 Tue Oct 19 16:05:00 PDT 2010 armv5tejl

So, to test if it will 'work' - I would think the simplest thing would be to flash back to factory..

Everything I've read says pogo does this automagically

I've seen posts here and elsewhere that indicate mtd2 holds the 'pogo magic'

The /proc/partitions are

mtdblock0 - mtdblock3

1k,4k,32k,224k in sizes
=-=-=-=-=-=-=-=-=-=-=-=-=-=
EDIT=-=-=-=-=-=-=
there are no firmware tools...
No fw_printenv, fw_setenv, nanddump, etc.....
I grabbed the files from
http://forum.doozan.com/read.php?2,11663,11713#msg-11713
None of them work...
Fw_printenv returns
'Cannot parse config file: no such file or directory'
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
END EDIT------------
==================
EDIT MARK 2
==================

I found blparam in /usr/local/cloudengines/bin
--------------
bash-3.2# bin/blparam
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
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
pcieTune=no
ethaddr=00:10:75:26:5C:06
cesvcid=xxxxxxxxxxxxxxxxxxxxx
ceserialno=Xxxxxxxxxxxxxxx
ceboardver=DISCOVERY:0.1
bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000

==================

.....

If I tinker too much - not sure it could be returned...(if it doesn't work)
So with that in mind - what should my next step be to either factory resurrect it, or toss my hat in and go for a full 'jessie'/'wheezy'/'squeeze'/openmediavault build?

(Is there a magic 'poke' that will tell it to phone pogo and ask for a reload?)