OpenFSG

A forum where users help other users with troubleshooting their Freecom NAS device
It is currently Wed Jul 30, 2014 01:54

All times are UTC + 1 hour




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Sun Jul 02, 2006 21:42 
Offline
Regular User
Regular User

Joined: Tue Jun 27, 2006 18:08
Posts: 10
Just in case someone is intrested what FSGA recovery process does.

* Start FSGA and select "Start recovery procedure"
* Power-on FSG with Reset button pressed, release reset after a while
* FSG send bootp requests to LAN (timeout 30 seconds) [1]
* FSGA replies to bootp request [2]
* FSG loads "zImage-recovery" from computer running FSGA using TFTP [3]
* FSG executes "zImage-recovery" [4]
* FSG send another bootp request [5]
* FSGA replies to bootp request [6]
* FSG starts recovery process and sends status messages to FSGA using UDP protocol (source port 5004, destination port 5004)
- FSG Recover V1.1.7 started!
- Installing system on /dev/hda
- This can take several minutes
- formatting system partitions
- loading firmware via network
* FSG loads "fsgimage.bin" using TFTP from FSGA
* FSG sends status messages to FSGA
- decoding firmware image
- unpacking and installing image
- flashing new Linux Kernel
- Firmware Version 3.1.26 installed
- checking home partition for errors
- FSG Recover successfully finished! FSG is rebooting.
- -= NOW YOU CAN PRESS <OK> BUTTON =-

BTW. Recovery does NOT work if your partition table is corrupted or filesystem is broken beyond repair. FSG recovery image drops to shell with "out of disk space" error because recovery image attempts to load firmware to data partition that doesn't exist. Would be nice if Freecom would improve recovery image so it repartitions HDD if there's no proper partitions or filesystems present.

It's also possible to netboot FSG by starting it with reset button pressed for few seconds, waiting ~25s and hitting ^C repeatedly until it drops to RedBoot. In recovery mode it's possible to assign IP and load images over net using TFTP.

Another way is setting up bootp server and tftp server to serve zImage-recovery.

Code:
[1]
0000  ff ff ff ff ff ff 00 01  db 00 40 da 08 00 45 00   ........ ..@...E.
0010  01 48 00 00 00 00 40 11  79 a6 00 00 00 00 ff ff   .H....@. y.......
0020  ff ff 00 44 00 43 01 34  83 b3 01 01 06 00 12 34   ...D.C.4 .......4
0030  55 55 00 00 00 00 00 00  00 00 00 00 00 00 00 00   UU...... ........
0040  00 00 00 00 00 00 00 01  db 00 40 da 00 00 00 00   ........ ..@.....
0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0100  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0110  00 00 00 00 00 00 63 82  53 63 34 01 03 ff 00 00   ......c. Sc4.....
0120  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0150  00 00 00 00 00 00


Code:
[2]
0000  ff ff ff ff ff ff 00 0b  5d 7e 23 dc 08 00 45 00   ........ ]~#...E.
0010  01 48 03 fd 00 00 80 11  73 fe c0 a8 01 02 ff ff   .H...... s.......
0020  ff ff 10 8f 00 44 01 34  66 60 02 01 06 00 12 34   .....D.4 f`.....4
0030  55 55 00 00 00 00 00 00  00 00 c0 a8 01 03 c0 a8   UU...... ........
0040  01 02 00 00 00 00 00 01  db 00 40 da 00 00 00 00   ........ ..@.....
0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0100  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0110  00 00 00 00 00 00 63 82  53 63 01 04 ff ff ff 00   ......c. Sc......
0120  ff 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0150  00 00 00 00 00 00


Code:
[3]
+Ethernet eth0: MAC address 00:01:db:00:40:da
IP: 192.168.1.3/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.2, DNS server IP: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROM]
Red Hat certified release, version 1.94 - built 11:47:48, Jun 10 2005

Platform: Freecom Storage  Gateway (FSG) (XScale) BE
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

RAM: 0x00000000-0x04000000, 0x0001db58-0x03fd0000 available
FLASH: 0x50000000 - 0x50400000, 32 blocks of 0x00020000 bytes each.
FREECOM ermergency button pressed!
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> load -r -v -b 0x700000 zImage-recovery
Using default protocol (TFTP)
...
Raw file loaded 0x00700000-0x00a7ebb3, assumed entry at 0x00700000


Code:
[4]
RedBoot> go
Uncompressing Linux......................................................... done, booting the kernel.
Linux version 2.4.27-uc1 (root@LAWILINUX) (gcc version 3.3.2) #1050 Mon Jan 23 15:44:47 CET 2006
CPU: XScale-IXP4xx/IXC11xx revision 1
Machine: Intel IXP425 Freecom Platform
Warning: bad configuration page, trying to continue
alloc_bootmem_low
memtable_init
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x00800000,8M mem=64M@0x00000000
Calibrating delay loop... 266.24 BogoMIPS
Memory: 64MB = 64MB total
Memory: 54736KB available (1528K code, 276K data, 60K init)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
PCI: reset bus...
PCI Autoconfig: Found Bus 0, Device 12, Function 0
PCI Autoconfig: BAR 0, I/O, size=0x10, address=0xfffffff0
PCI Autoconfig: BAR 1, I/O, size=0x10, address=0xffffffe0
PCI Autoconfig: BAR 2, I/O, size=0x10, address=0xffffffd0
PCI Autoconfig: BAR 3, I/O, size=0x10, address=0xffffffc0
PCI Autoconfig: BAR 4, I/O, size=0x20, address=0xffffffa0
PCI Autoconfig: BAR 5, I/O, size=0x100, address=0xfffffe00
PCI Autoconfig: Found Bus 0, Device 14, Function 0
PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bfff000
PCI Autoconfig: Found Bus 0, Device 14, Function 1
PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bffe000
PCI Autoconfig: Found Bus 0, Device 14, Function 2
PCI Autoconfig: BAR 0, Mem, size=0x100, address=0x4bffdf00
PCI: bus0: Fast back to back transfers disabled
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
kinoded started
VFS: Disk quotas vdquot_6.5.1
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0xff000003 (irq = 15) is a XScale UART
ttyS01 at 0xff001003 (irq = 13) is a XScale UART
ledman: Copyright (C) SnapGear, 2000-2003.
LEDMAN: registered RESET switch on IRQ26
LEDMAN: registered UNPLUG switch on IRQ27
LEDMAN: registered SYNC switch on IRQ21
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VIA_6421: IDE controller at PCI slot 00:0c.0
VIA_6421: chipset revision 80
VIA_6421: 100% native mode on irq 22
    ide0: BM-DMA at 0xffb0-0xffb7, BIOS settings: hda:pio, hdb:pio
SATA stat after reset 0
    ide1: BM-DMA at 0xffa0-0xffa7, BIOS settings: hdc:pio, hdd:pio
SATA stat after reset 0
    ide2: BM-DMA at 0xffa8-0xffaf, BIOS settings: hde:pio, hdf:pio
hda: SAMSUNG SP2514N, ATA DISK drive
blk: queue c01d59e8, no I/O memory limit
ide0 at 0xffd0-0xffd7,0xffda on irq 22
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(33)
Partition check:
hda: hda1 hda2 hda3 hda4
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
Creating 5 MTD partitions on "IXP425 Flash":
0x00000000-0x00040000 : "RedBoot"
0x00080000-0x00200000 : "kern1"
0x00200000-0x00380000 : "kern2"
0x003c0000-0x003e0000 : "RedBoot config"
0x003e0000-0x00400000 : "FIS directory"
CFI: Found no IXP425 Flash device at location zero
i2c-core.o: i2c core module version 2.9.0 (20041228)
i2c-dev.o: i2c /dev entries driver module version 2.9.0 (20041228)
IXP425 Montejade I2C support available
i2c-proc.o version 2.9.0 (20041228)
isl1208.o: version 2.9.2-Freecom (20051016) with RTC device support
eeprom.o version 2.9.0 (20041228)
w83781d.o version 2.9.2-Freecom (20051016)
i2c-algo-bit.o: IXP425 I2C Adapter sendbytes: error - bailout.
w83781d.o:  PWM-Divisor 60; must be 0-4
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double precision)
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 8192K
VFS: Mounted root (ext2 filesystem) readonly.
Freeing init memory: 60K
FSG Recovery System started
Starting network.
Using /lib/modules/2.4.27-uc1/kernel/ixp425/ixp400/ixp400.o
Module init.Using /lib/modules/2.4.27-uc1/kernel/ixp425/net/ixp425_eth.o
<6>ixp425_eth:
Initializing IXP425 NPE Ethernet driver software v. 1.1+
ixp425_eth: CPU clock speed (approx) = 0 MHz
ixp425_eth: eth0 is using the PHY at address 5
ixp425_eth: eth1 is using the PHY at address 4


FSG Recover 1.1.7


Code:
[5]
0000  ff ff ff ff ff ff 00 01  db 00 40 da 08 00 45 00   ........ ..@...E.
0010  01 48 00 00 40 00 40 11  39 a6 00 00 00 00 ff ff   .H..@.@. 9.......
0020  ff ff 04 00 00 43 01 34  06 ea 01 01 06 00 78 23   .....C.4 ......x#
0030  68 72 00 01 00 00 00 00  00 00 00 00 00 00 00 00   hr...... ........
0040  00 00 00 00 00 00 00 01  db 00 40 da 00 00 00 00   ........ ..@.....
0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0100  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0110  00 00 00 00 00 00 63 82  53 63 34 01 03 ff 00 00   ......c. Sc4.....
0120  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0150  00 00 00 00 00 00


Code:
[6]
0000  ff ff ff ff ff ff 00 0b  5d 7e 23 dc 08 00 45 00   ........ ]~#...E.
0010  01 48 1f f5 00 00 80 11  58 06 c0 a8 01 02 ff ff   .H...... X.......
0020  ff ff 10 90 00 44 01 34  ed 50 02 01 06 00 78 23   .....D.4 .P....x#
0030  68 72 00 01 00 00 00 00  00 00 c0 a8 01 04 c0 a8   hr...... ........
0040  01 02 00 00 00 00 00 01  db 00 40 da 00 00 00 00   ........ ..@.....
0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
00f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0100  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0110  00 00 00 00 00 00 63 82  53 63 01 04 ff ff ff 00   ......c. Sc......
0120  ff 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........ ........
0150  00 00 00 00 00 00   


Code:
[7]
MyIP=192.168.1.4 HostIP=192.168.1.2 BroadcastAddr=192.168.3.255 SubnetmaskIP=255.255.252.0
ifconfig eth0 192.168.1.4 broadcast=192.168.3.255 netmask=255.255.252.0 up

reiserfs: found format "3.6" with standard journal
reiserfs: using ordered data mode
reiserfs: checking transaction log (device ide0(3,4)) ...
for (ide0(3,4))
reiserfs: replayed 5 transactions in 0 seconds
ide0(3,4):Using r5 hash to sort names
mkreiserfs 3.6.19 (2003 www.namesys.com)

mkreiserfs 3.6.19 (2003 www.namesys.com)

reiserfs: found format "3.6" with standard journal
reiserfs: using ordered data mode
reiserfs: checking transaction log (device ide0(3,1)) ...
for (ide0(3,1))
ide0(3,1):Using r5 hash to sort names
reiserfs: found format "3.6" with standard journal
reiserfs: using ordered data mode
reiserfs: checking transaction log (device ide0(3,2)) ...
for (ide0(3,2))
ide0(3,2):Using r5 hash to sort names
umount: /dev/hda2: Device or resource busy
1+0 records in
1+0 records out
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will check consistency of the filesystem on /dev/hda4
and will fix what can be fixed without --rebuild-tree
Will put log info to 'stdout'
###########
reiserfsck --fix-fixable started at Thu Jan  1 00:02:20 1970
###########
Replaying journal..
Reiserfs journal '/dev/hda4' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..finished
No corruptions found
There are on the filesystem:
   Leaves 9
   Internal nodes 1
   Directories 24
   Other files 14
   Data block pointers 5557 (0 of them are zero)
   Safe links 0
###########
reiserfsck finished at Thu Jan  1 00:03:23 1970
###########
Knox: Request: 0x09.
Sun Jul  2 16:26:20 UTC 2006
Sun Jul  2 16:26:20 UTC 2006
isl1208_set_datetime(), i2c_master_send() returned 0

The system is going down NOW !!
Sending SIGTERM to all processes.
/ # Sending SIGKILL to all processes.
flushing ide devices: hda
Restarting system.


Top
 Profile  
 
PostPosted: Sun Jul 02, 2006 21:51 
Offline
Regular User
Regular User

Joined: Fri Jun 30, 2006 23:54
Posts: 30
jr wrote:
* Power-on FSG with Reset button pressed, release reset after a while
* FSG send bootp requests to LAN (timeout 30 seconds) [1]
* FSGA replies to bootp request [2]
* FSG loads "zImage-recovery" from computer running FSGA using TFTP [3]
* FSG executes "zImage-recovery" [4]

jr wrote:
Another way is setting up bootp server and tftp server to serve zImage-recovery.

Excellent. Now I'm much more interested in getting hold of one of these, as this makes Windows unnecessary for hacking around with it :-)


Top
 Profile  
 
PostPosted: Thu Aug 10, 2006 02:52 
Is it possible to upload the firmware manually from a broken FSG? BootP procedure is working on/reset -> ipaddress allocated.

But procedure hangs during tftp with FSGA.

How to do this manually with TFTP?


Top
  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron

{ ASACP_CREDITS } Powered by phpBB® Forum Software © phpBB Group