bodhi Wrote:
-------------------------------------------------------
> balanga
>
> I expected the envs contains mtdparts definition,
> so we don't have to calculate it. But it was
> apparently not available so I need to define the
> layout.



Log in to Arch, and set mtdparts:

fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),6M(uImage),-(root)'

Reboot. Log back into Arch.

cat /proc/mtd

Now look at the mtd dumps one more time to confrimr (this time use the -h option to see the size better).

ls -larth mtd

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



Edited 1 time(s). Last edit at 08/12/2018 11:49AM by bodhi.

bodhi Wrote:
-------------------------------------------------------
>
> Reboot. Log back into Arch.
>
>

> cat /proc/mtd
>

[root@alarm ~]# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00600000 00020000 "uImage"
mtd2: 0f900000 00020000 "root"

This the same as Stock.


>
> Now look at the mtd dumps one more time to
> confrimr (this time use the -h option to see the
> size better).
>
>

> ls -larth mtd
>

Not sure I understand this.... Do I run it from /proc?

I get:-

[root@alarm /]# cd /proc
[root@alarm proc]#  ls -larth mtd
-r--r--r-- 1 root root 0 Aug 12 18:10 mtd

[root@alarm proc]# cat mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00600000 00020000 "uImage"
mtd2: 0f900000 00020000 "root"

Now do I run:-

flash_erase /dev/mtd0
nandwrite -on /dev/mtd0 mtd0
flash_erase /dev/mtd1
nandwrite -on /dev/mtd1 mtd1
flash_erase /dev/mtd2
nandwrite -on /dev/mtd2 mtd2

Presumably I need to mount the USB stick first and cd to the directory which contains mtd0 mtd1 mtd2...

I just gave it a shot running this shell script:-

/mnt/usb is my mounted USB stick containing the mtd files as well as tools

cd /mnt/usb/tools
./flash_erase /dev/mtd0
./nandwrite -on /dev/mtd0 /mnt/usb/mtd/mtd0
./flash_erase /dev/mtd1
./nandwrite -on /dev/mtd1 /mnt/usb/mtd/mtd1
./flash_erase /dev/mtd2
./nandwrite -on /dev/mtd2 /mnt/usb/mtd/mtd2

This is what I got:-

Script started on 2018-08-12 22:57:07+00:00
root@alarm:/mnt/smb/gfh
[root@alarm gfh]# sh restore
restore: line 2: ./flash_erase: Permission denied
restore: line 3: ./nandwrite: Permission denied
restore: line 4: ./flash_erase: Permission denied
restore: line 5: ./nandwrite: Permission denied
restore: line 6: ./flash_erase: Permission denied
restore: line 7: ./nandwrite: Permission denied
[root@alarm:/mnt/smb/gfh
[root@alarm gfh]# exit
exit

Script done on 2018-08-12 22:58:52+00:00

Your Arch mtds now is the same as stock. So yes, you are ready to flash the nanddumped mtds.

[root@alarm ~]# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00600000 00020000 "uImage"
mtd2: 0f900000 00020000 "root"

Now for sanity. Recall you listed the mtds in stock OS this way.

bash-3.2# ls -al mtd 
total 262424 
drwxr-xr-x 2 root root 4096 Aug 11 12:15 . 
drwxr-xr-x 5 root root 4096 Aug 11 12:04 .. 
-rw-r--r-- 1 root root 1048576 Aug 11 12:15 mtd0 
-rw-r--r-- 1 root root 6291456 Aug 11 12:15 mtd1 
-rw-r--r-- 1 root root 261095424 Aug 11 12:17 mtd2

Now repeat that with -h so that we can see the size of the mtd dumps in MBytes.

 
cd /mnt/usb
ls -lath mtd

To make the binaries executable

cd /mnt/usb/tools
chmod +x flash_erase
chmod +x flash_erase

And your script looks OK

cd /mnt/usb/tools
./flash_erase /dev/mtd0
./nandwrite -on /dev/mtd0 /mnt/usb/mtd/mtd0
./flash_erase /dev/mtd1
./nandwrite -on /dev/mtd1 /mnt/usb/mtd/mtd1
./flash_erase /dev/mtd2
./nandwrite -on /dev/mtd2 /mnt/usb/mtd/mtd2

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

bodhi Wrote:
-------------------------------------------------------
>
> And your script looks OK
>
>

> cd /mnt/usb/tools
> ./flash_erase /dev/mtd0
> ./nandwrite -on /dev/mtd0 /mnt/usb/mtd/mtd0
> ./flash_erase /dev/mtd1
> ./nandwrite -on /dev/mtd1 /mnt/usb/mtd/mtd1
> ./flash_erase /dev/mtd2
> ./nandwrite -on /dev/mtd2 /mnt/usb/mtd/mtd2
>

flash_erase: error!: no start erase block specified
flash_erase: error!: no erase block count specified
flash_erase: error!: Try `--help' for more information
Input file is not page-aligned. Use the padding option.
nandwrite: error!: Data was only partially written due to error

balanga Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> >
> > And your script looks OK
> >
> >

> > cd /mnt/usb/tools
> > ./flash_erase /dev/mtd0
> > ./nandwrite -on /dev/mtd0 /mnt/usb/mtd/mtd0
> > ./flash_erase /dev/mtd1
> > ./nandwrite -on /dev/mtd1 /mnt/usb/mtd/mtd1
> > ./flash_erase /dev/mtd2
> > ./nandwrite -on /dev/mtd2 /mnt/usb/mtd/mtd2
> >

>
>

> flash_erase: error!: no start erase block
> specified
> flash_erase: error!: no erase block count
> specified
> flash_erase: error!: Try `--help' for more
> information
> Input file is not page-aligned. Use the padding
> option.
> nandwrite: error!: Data was only partially written
> due to error
>

My bad! Try

cd /mnt/usb/tools
./flash_erase /dev/mtd0 0 0
./nandwrite -on /dev/mtd0 /mnt/usb/mtd/mtd0
./flash_erase /dev/mtd1 0 0
./nandwrite -on /dev/mtd1 /mnt/usb/mtd/mtd1
./flash_erase /dev/mtd2 0 0
./nandwrite -on /dev/mtd2 /mnt/usb/mtd/mtd2

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

Script started on 2018-08-13 07:24:14+00:00
^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]# sh restore
Erasing 128 Kibyte @ 0 --  0 % complete Erasing 128 Kibyte @ 20000 -- 12 % complete Erasing 128 Kibyte @ 40000 -- 25 % complete Erasing 128 Kibyte @ 60000 -- 37 % comple
Input file is not page-aligned. Use the padding option.
nandwrite: error!: Data was only partially written due to error
           error 0 (Success)
Erasing 128 Kibyte @ 0 --  0 % complete Erasing 128 Kibyte @ 20000 --  2 % complete Erasing 128 Kibyte @ 40000 --  4 % complete Erasing 128 Kibyte @ 60000 --  6 % comple
Input file is not page-aligned. Use the padding option.
nandwrite: error!: Data was only partially written due to error
           error 0 (Success)
Erasing 128 Kibyte @ 0 --  0 % complete Erasing 128 Kibyte @ 20000 --  0 % complete Erasing 128 Kibyte @ 40000 --  0 % complete Erasing 128 Kibyte @ 60000 --  0 % comple
Input file is not page-aligned. Use the padding option.
nandwrite: error!: Data was only partially written due to error
           error 0 (Success)
^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]# exit
exit

Script done on 2018-08-13 07:24:33+00:00

Does this look OK? Can I expect to be back in Stock when I reboot?

balanga Wrote:
-------------------------------------------------------
>

> Script started on 2018-08-13 07:24:14+00:00
> ^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]# sh
> restore
> Erasing 128 Kibyte @ 0 --  0 % complete Erasing
> 128 Kibyte @ 20000 -- 12 % complete Erasing 128
> Kibyte @ 40000 -- 25 % complete Erasing 128 Kibyte
> @ 60000 -- 37 % comple
> Input file is not page-aligned. Use the padding
> option.
> nandwrite: error!: Data was only partially written
> due to error
>            error 0 (Success)
> Erasing 128 Kibyte @ 0 --  0 % complete Erasing
> 128 Kibyte @ 20000 --  2 % complete Erasing 128
> Kibyte @ 40000 --  4 % complete Erasing 128 Kibyte
> @ 60000 --  6 % comple
> Input file is not page-aligned. Use the padding
> option.
> nandwrite: error!: Data was only partially written
> due to error
>            error 0 (Success)
> Erasing 128 Kibyte @ 0 --  0 % complete Erasing
> 128 Kibyte @ 20000 --  0 % complete Erasing 128
> Kibyte @ 40000 --  0 % complete Erasing 128 Kibyte
> @ 60000 --  0 % comple
> Input file is not page-aligned. Use the padding
> option.
> nandwrite: error!: Data was only partially written
> due to error
>            error 0 (Success)
> ^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]#
> exit
> exit
> 
> Script done on 2018-08-13 07:24:33+00:00
> 
>

>
> Does this look OK? Can I expect to be back in
> Stock when I reboot?

Not successful. Let me take a close look. Dont reboot.

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

Take a look at the MTD dumps again:

cd /mnt/usb/mtd
ls -larth mtd*

And see what option this nandwrite provides

cd /mnt/usb/tools
./nandwrite --help

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



Edited 3 time(s). Last edit at 08/13/2018 05:53AM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> Take a look at the MTD dumps again:
>
>

> cd /mnt/usb/mtd
> ls -larth mtd*
>

[root@alarm /]# cd /mnt/usb/mtd
[root@alarm mtd]# ls -larth mtd*
-rw-r--r-- 1 nobody nobody 1.0M Aug 11 12:15 mtd0
-rw-r--r-- 1 nobody nobody 6.0M Aug 11 12:15 mtd1
-rw-r--r-- 1 nobody nobody 249M Aug 11 12:17 mtd2

> And see what option this nandwrite provides
>
>

> cd /mnt/usb/tools
> ./nandwrite --help
>

[root@alarm mtd]# cd /mnt/usb/tools
[root@alarm tools]# ./nandwrite --help
Usage: nandwrite [OPTION] MTD_DEVICE [INPUTFILE|-]
Writes to the specified MTD device.

  -a, --autoplace         Use auto OOB layout
  -m, --markbad           Mark blocks bad if write fails
  -n, --noecc             Write without ecc
  -N, --noskipbad         Write without bad block skipping
  -o, --oob               Input contains oob data
  -O, --onlyoob           Input contains oob data and only write the oob part
  -s addr, --start=addr   Set output start address (default is 0)
  -p, --pad               Pad writes to page size
  -b, --blockalign=1|2|4  Set multiple of eraseblocks to align to
      --input-skip=length Skip |length| bytes of the input file
      --input-size=length Only read |length| bytes of the input file
  -q, --quiet             Don't display progress messages
  -h, --help              Display this help and exit
      --version           Output version information and exit

balanga,

Quote

[root@alarm /]# cd /mnt/usb/mtd
[root@alarm mtd]# ls -larth mtd*
-rw-r--r-- 1 nobody nobody 1.0M Aug 11 12:15 mtd0
-rw-r--r-- 1 nobody nobody 6.0M Aug 11 12:15 mtd1
-rw-r--r-- 1 nobody nobody 249M Aug 11 12:17 mtd2

This told us the dumps were fine. Without OOB data.

So change your commands to the following. And execute it one by one by copy/paste these commands. Don't run them in a script. Stop if the first command gives out error.

cd /mnt/usb/tools
./flash_erase /dev/mtd0
./nandwrite -n /dev/mtd0 /mnt/usb/mtd/mtd0
./flash_erase /dev/mtd1
./nandwrite -n /dev/mtd1 /mnt/usb/mtd/mtd1
./flash_erase /dev/mtd2
./nandwrite -n /dev/mtd2 /mnt/usb/mtd/mtd2

And please post the log of these commands execution here.

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

bodhi Wrote:
-------------------------------------------------------
>
> So change your commands to the following. And
> execute it one by one by copy/paste these
> commands. Don't run them in a script. Stop if the
> first command gives out error.
>
>

> cd /mnt/usb/tools
> ./flash_erase /dev/mtd0
> ./nandwrite -n /dev/mtd0 /mnt/usb/mtd/mtd0
> ./flash_erase /dev/mtd1
> ./nandwrite -n /dev/mtd1 /mnt/usb/mtd/mtd1
> ./flash_erase /dev/mtd2
> ./nandwrite -n /dev/mtd2 /mnt/usb/mtd/mtd2
>

>
> And please post the log of these commands
> execution here.

Looks like the typo crept in again. I take it that should have been

./flash_erase /dev/mtd0 0 0

The mtd0 worked OK, so I wrote mtd1 which also worked OK, then I got this at the end of mtd2

Writing data to block 1160 at offset 0x9100000
Writing data to block 1161 at offset 0x9120000
File I/O error on input: Input/output error
nandwrite: error!: Data was only partially written due to error
           error 5 (Input/output error)
[root@alarm tools]# exit
exit
Script done, file is typescript
script: write failed: typescript: Input/output error

Typescript got truncated so dont know how far it got. Should I try again with:-

./nandwrite -n /dev/mtd2 /mnt/usb/mtd/mtd2

balanga,

> Looks like the typo crept in again. I take it that
> should have been
>
>

> ./flash_erase /dev/mtd0 0 0
>

Right!

>
> The mtd0 worked OK, so I wrote mtd1 which also
> worked OK,

For mtd2.

Execute each command at command line, not in a script:

./flash_erase /dev/mtd2 0 0
./nandwrite -n /dev/mtd2 /mnt/usb/mtd/mtd2

If the error occur again, post output of your dmesg

dmesg

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

bodhi Wrote:
-------------------------------------------------------
> balanga,
> For mtd2.
>
> Execute each command at command line, not in a
> script:
>

> ./flash_erase /dev/mtd2 0 0
> ./nandwrite -n /dev/mtd2 /mnt/usb/mtd/mtd2
>

>
> If the error occur again, post output of your
> dmesg
>
>

> dmesg
>

Script started on 2018-08-13 17:04:05+00:00
^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]# restore^M
bash: restore: command not found^M
^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]# restore^H^H^H^H^H^H^H^G^G^G^G^G^[[1@.^[[1@/^M
^MErasing 128 Kibyte @ 0 --  0 % complete ^MErasing 128 Kibyte @ 20000 --  0 % complete ^MErasing 128 Kibyte @ 40000 --  0 % complete ^MErasing 128 Kibyte @ 60000 --  0
Input file is not page-aligned. Use the padding option.^M
nandwrite: error!: Data was only partially written due to error^M
           error 0 (Success)^M
^[]0;root@alarm:/mnt/smb/gfh^G[root@alarm gfh]# exit^M
exit^M

Script done on 2018-08-13 17:04:37+00:00

dmesg did not display anything significant.

Unfortunately I had a power cut and the GoFlex Home unit rebooted to a flashing green light, so I guess that is the end of the experiment. Now I'll have to break in and see if I can salvage anything.

Before breaking in, I thought I would try and reinstall Seagate original firmware - http://support.goflexhome.hipserv.com/en/reflash/index.html


What happens is that the flashing green light goes to steady and then starts flashing orange for 30secs and then goes back to steady green for 3osecs and this cycle goes on repeating itself ad infinitum. What could it be doing?

balanga,

> Unfortunately I had a power cut and the GoFlex
> Home unit rebooted to a flashing green light, so I
> guess that is the end of the experiment.

You have flashed mtd0 succesfully, so the box is not bricked. Without mtd2, stock OS is not running.

Connect serial console and all will be OK. Once you have console, interrupt u-boot at count down and post back.

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

bodhi,

I'm not really sure what has happened but it seems to have booted up using Stock. I have been able to ping it and would be able to ssh but can't get past the password prompt - have tried all the methods I've used before. I can access it via the GUI and have had to re-register. Am reluctant to break in because I always break a clip or two, but I'll give it a try...

balanga Wrote:
-------------------------------------------------------
> bodhi,
>
> I'm not really sure what has happened but it seems
> to have booted up using Stock.

Cool! so the error on mtd2 was not that bad.


> I have been able to
> ping it and would be able to ssh but can't get
> past the password prompt - have tried all the
> methods I've used before. I can access it via the
> GUI and have had to re-register.

That's enough to restart.

> Am reluctant to
> break in because I always break a clip or two, but
> I'll give it a try...

Can you still activate SSH through the web page?

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

bodhi Wrote:
-------------------------------------------------------
> balanga Wrote:
> -------------------------------------------------------
>
> Can you still activate SSH through the web page?

ssh is active but I just can't login. I'm still not sure what has been copied over. When copying over mtd does that include things like the passwd file?

I think I will attempt the whole process again.

balanga,

Writing data to block 1160 at offset 0x9100000
Writing data to block 1161 at offset 0x9120000
File I/O error on input: Input/output error
nandwrite: error!: Data was only partially written due to error
           error 5 (Input/output error)

mtd2 flashing was OK, because this occured at 145 MB region, and my guess is the stock rootfs is smaller!

> ssh is active but I just can't login. I'm still
> not sure what has been copied over. When copying
> over mtd does that include things like the passwd
> file?

If you can boot stock, then the passwd file must have been OK.

What did you see when trying to ssh in? what type of error?

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

I'm really confused about what's happened now. Because the system didn't boot up properly, I reinstalled the Stock firmware provided by Seagate and had to re-register and now do have GUI access, and ssh does work, ie a password prompt appears, although I can't login. I'm not really sure what the mtdx files contain... is it the full system including any passwd entries?

I'm tempted to go through the whole thing again now that I have a better idea about what is going, but I think I'd better get a serial connection set up for the target box.

balanga,

> although I can't login. I'm not really sure what
> the mtdx files contain... is it the full system
> including any passwd entries?

Yes.

>
> I'm tempted to go through the whole thing again
> now that I have a better idea about what is going,
> but I think I'd better get a serial connection set
> up for the target box.

Good idea to have serial connection. Most if not all problems are easily solved with serial console.

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

I finally managed to break in and get a serial cable connected and here is what I got. Seems OK to me...

	 -- 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
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 

NAND read: device 0 offset 0x100000, size 0x600000

Reading data from 0x100000 --   0% complete.
Reading data from 0x10f000 --   1% complete.


Reading data from 0x6e1000 --  98% complete.
Reading data from 0x6f0800 --  99% complete.
Reading data from 0x6ff800 -- 100% complete.
 6291456 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-06-17   5:37:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2095148 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................... done, booting the kernel.
Linux version 2.6.22.18 (ramang@es5x86.axentra.com) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #16 Thu Jun 17 01:37:53 EDT 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 32512
Kernel command line: console=ttyS0,115200 ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 125568KB available (3844K code, 261K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB 
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB 
PEX0_IO ....base f2000000, size   1MB 
INTER_REGS ....base f1000000, size   1MB 
NFLASH_CS ....base fa000000, size   2MB 
SPI_CS ....base f4000000, size  16MB 
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB 

  Marvell Development Board (LSP Version KW_LSP_4.3.4_patch22)-- SHEEVA PLUG  Soc: 88F6281 A1 LE

 Detected Tclk 200000000 and SysClk 400000000 
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c057b600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
RTC registered
XOR registered 2 channels
XOR 2nd invalidate WA enabled
cesadev_init(c0011854)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o SKB Reuse supported
  o SKB Recycle supported
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o  register under eth%d platform
    o eth0, ifindex = 1, GbE port = 0

Warning: Giga 1 is Powered Off

mvFpRuleDb (c7da7000): 1024 entries, 4096 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0x98, Chip ID: 0xda (Toshiba NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Using static partition definition
Creating 3 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00700000 : "uImage"
0x00700000-0x10000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            249 MiB
UBI: number of good PEBs:        1992
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1992
UBI: number of PEBs reserved for bad PEB handling: 38
UBI: max/mean erase counter: 1/0
UBI: background thread "ubi_bgt0d" started, PID 296
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:

Warning Tdm is Powered Off
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     91 MB/s
raid6: int32x2    109 MB/s
raid6: int32x4    119 MB/s
raid6: int32x8     94 MB/s
raid6: using algorithm int32x4 (119 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :  1072.400 MB/sec
   8regs     :   822.000 MB/sec
   32regs    :   803.200 MB/sec
raid5: using function: arm4regs (1072.400 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   239857664 bytes (234236 KiB, 228 MiB, 1889 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       4 (latest is 4)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem).
Freeing init memory: 128K
Failed to execute /linuxrc.  Attempting defaults...
INIT: version 2.86 booting
		Welcome to HipServ
		Press 'I' to enter interactive startup.
The Hardware Clock does not contain a valid time, so we cannot set the System Time from it.
Unable to set system clock.
Setting clock : Sun Nov  4 17:49:12 GMT-1 1956 [  OK  ]
Starting udev: [  OK  ]
Setting hostname axentraserver.balanga4.seagateshare.com:  [  OK  ]
Setting up Logical Volume Management:   No volume groups found
[  OK  ]
Checking filesystems
Checking all file systems.
[  OK  ]
Mounting local filesystems:  mount: sysfs already mounted or /sys busy
mount: according to mtab, /sys is already mounted on /sys
[FAILED]
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
HipServ startup:[  OK  ]
Starting reset:  [  OK  ]
Starting seagate-lifecycle:[  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  
Determining IP information for eth0... done.
/etc/init.d/iptables: line 42: /etc/sysconfig/networking/oe-profiles/default/ifcfg-eth0: No such file or directory
Flushing all current rules and user defined chains: [  OK  ]
Clearing all current rules and user defined chains: [  OK  ]
[  OK  ][  OK  ]Applying iptables firewall rules: 
[  OK  ]
[  OK  ]
check_igd.pl: no process killed
Starting igd-daemon:[  OK  ]error reading information on service transmission.init: No such file or directory
[  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting locator:[  OK  ]
Starting system message bus: [  OK  ]
Starting sshd: [  OK  ]
Starting cups: [  OK  ]
Starting vsftpd for vsftpd: [  OK  ]
Starting httpd: [  OK  ]
Starting appserver: [  OK  ]
Starting crond: [  OK  ]
Starting Netatalk services: 
  Starting cnid_metad:[  OK  ]
  Starting afpd:[  OK  ]

Starting SMB services: [  OK  ]
Starting NMB services: [  OK  ]
Starting OEone System Proxy: SPD starting....log level=1, uid=0

[  OK  ]
Starting access-patrol:[  OK  ]
Starting Avahi daemon... [  OK  ]
Starting /usr/sbin/minidlna ... 
Starting S99lld2: [  OK  ]
0
Starting DAAP server: [  OK  ]
Starting mynetworkd:[  OK  ]
    HipServ - Checking if RAID needs to be rebuilt
        HipServ - No RAID found
    HipServ - Bringing up iptables
    HipServ - Updating date...
[  OK  ]        success
    HipServ - Enabling swap
    HipServ - Cleaning USB mountpoints
    HipServ - Mounting USB devices

    HipServ -  Checking for FTPS certificate
        HipServ - Found vsftpd key file
    HipServ -  Ensuring that table structures are up-to-date
    HipServ - Starting usbreaderd: [  OK  ]
    HipServ - Checking for updates...
[  OK  ]        success
HipServ - boot complete
Starting spindownd.init:  [  OK  ]
Starting xMySyncMount.php:  [  OK  ]

axentraserver.balanga4.seagateshare.com login: [B  root
Password: 


-bash-3.2# printenv
HOSTNAME=axentraserver.balanga4.seagateshare.com
TERM=linux
SHELL=/bin/bash
HISTSIZE=1000
USER=root
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:
MAIL=/var/spool/mail/root
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
INPUTRC=/etc/inputrc
PWD=/root
SHLVL=1
HOME=/root
LOGNAME=root
LESSOPEN=|/usr/bin/lesspipe.sh %s
G_BROKEN_FILENAMES=1
_=/usr/bin/printenv

-bash-3.2# cd /
-bash-3.2# du -sh
353M	.


-bash-3.2# fw_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
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethaddr=00:50:43:34:33:06
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
stdin=serial
stdout=serial
stderr=serial
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
enaAutoRecovery=yes
pcieTune=no
filesize=33AA2E
bootargs=console=ttyS0,115200 root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand
bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
console2=console=ttyS0,115200
bootcmd=nand read.e 0x800000 0x100000 0x600000; setenv bootargs $(console2) $(bootargs_root); bootm 0x800000
-bash-3.2# 

If you can't SSH in, then try to start dropbear in stock OS.

/usr/sbin/dropbear

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