Terastation TS-X4.OTL/R5 won't boot

So after some success with a couple of Terastations at work, I decided to dig out my own broken unit, hoping to get it up and running.

Unfortunately it is a much worse problem than the units at work. It boots up to error  E06. TFTP MODE.

I followed this guide, which explains how to set up an TFTP server, but unfortunately the machine wont fetch the files.

Pinging to the IP address given on the Terastation LCD screen returns no results.

I was able to connect up via serial to the front port (115200 bps).

Here is the report:

---------------------------------------------------------------------------------------------------------------------------------

setL2Size256K no

disL2Ecc no

disL2Prefetch yes

disL2Cache no

env finished





USB 0: host mode

USB 1: host mode

USB 2: device mode

PCI 0: PCI Express Root Complex Interface

PEX interface detected Link X4

PEX 4: interface detected no Link.

Net:   egiga0 [PRIME], egiga1

buffalo_change_power_status > Read 0x5c(swpoff_uboot_passed)

buffalo_change_power_status > Writing 0x5c(swpoff_uboot_passed)



Marvell Serial ATA Adapter

Integrated Sata device found

Found adapter at bus 0, device 1 ... Scanning channels

[1 0 0]: Enable DMA mode

  Device 2 @ 1 0:

Model: WDC WD10EZRX-00A8LB0                     Firm: 01.01A01 Ser#:      WD-WCC1U2567915

            Type: Hard Disk

            Supports 48-bit addressing

            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)



Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - ide 2:1 **

serch_boot_drv (285)>No kernel_file 2

Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - ide 2:1 **

serch_boot_drv (378)>No init_file 2

** Bad partition 1 **

serch_boot_drv (285)>No kernel_file 3

** Bad partition 1 **

serch_boot_drv (378)>No init_file 3

** Bad partition 1 **

serch_boot_drv (285)>No kernel_file 4

** Bad partition 1 **

serch_boot_drv (378)>No init_file 4

** Bad partition 1 **

serch_boot_drv (285)>No kernel_file 5

** Bad partition 1 **

serch_boot_drv (378)>No init_file 5

Lost all init_rd



Marvell Serial ATA Adapter

Integrated Sata device found

Found adapter at bus 0, device 1 ... Scanning channels

[1 0 0]: Enable DMA mode

  Device 2 @ 1 0:

Model: WDC WD10EZRX-00A8LB0                     Firm: 01.01A01 Ser#:      WD-WCC1U2567915

            Type: Hard Disk

            Supports 48-bit addressing

            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)



Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - ide 2:1 **

serch_boot_drv (285)>No kernel_file 2

Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - ide 2:1 **

serch_boot_drv (378)>No init_file 2

** Bad partition 1 **

serch_boot_drv (285)>No kernel_file 3

** Bad partition 1 **

serch_boot_drv (378)>No init_file 3

** Bad partition 1 **

serch_boot_drv (285)>No kernel_file 4

** Bad partition 1 **

serch_boot_drv (378)>No init_file 4

** Bad partition 1 **

serch_boot_drv (285)>No kernel_file 5

** Bad partition 1 **

serch_boot_drv (378)>No init_file 5

hit any key to switch tftp boot.

Hit any key to stop autoboot:  0

Using egiga0 device

TFTP from server 192.168.11.1; our IP address is 192.168.11.150

Filename 'uImage.buffalo'.

Load address: 0x2000000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

egiga1 no link

Using egiga0 device

TFTP from server 192.168.11.1; our IP address is 192.168.11.150

Filename 'uImage.buffalo'.

Load address: 0x2000000

Loading: T T T T T T T T T T

Retry count exceeded; starting again

egiga1 no link

Using egiga0 device

TFTP from server 192.168.11.1; our IP address is 192.168.11.150

Filename 'uImage.buffalo'.

Load address: 0x2000000

Loading: T T T T T T T T T T

---------------------------------------------------------------------------------------------------------------------------------

Obviously the machine is looking for the uImage.buffalo from the server. I assured I had a file there, but between no response from a ping and a lack of any activity on the TFTP server side, I think the problem is elsewhere.

I am going to try slapping this drive into the NAS at work and hope it rebuilds the partitions and installs something that will get it to boot.