Author Topic: Terastation Live E04 problem  (Read 12069 times)

tjulo

  • Calf
  • *
  • Posts: 5
Terastation Live E04 problem
« on: December 19, 2008, 09:40:41 pm »
   

Hi,

 

I have a E04 error code and my Terastation Live will not boot. I tried the procedure of removing all the drives one by one and rebooting the TS but I always get the same E04 error. 

 

 

  • I then installed the TFTP found on ftp://24.153.165.234/disk1/share/nas-recovery/TFTP Boot Recovery-TS_Live-2.13.exe 
  • reconfigured the computer to IP 192.168.11.1
  • ran the TFTP Boot.exe
  • Boot the TS in Emergency mode

and NOTHING Happens. I have no firewalls on the PC and the TS and PC are connected to the same hub.
I read somewhere that the TS will take IP 192.168.11.150 when in Emergency Mode, and when I ping this IP from the PC I get no response.
 
It seems that not even the EM mode is working. What can I do to fix this I have 1TB of data in the TS, which I cannot get to...

Can I re-flash the TS from a USB pen drive? 
 
Please help
TJ 

 


tjulo

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #1 on: December 19, 2008, 10:15:35 pm »
   

Removing all the disks and booting in EM mode I was able to install the firmware on the TS and find it with the NAS Navigator.

 

Re-inserting all the disks I get the same error as before and the TS does not boot. What can I do next?


tjulo

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #2 on: December 20, 2008, 12:01:15 am »
   

Removing the first disk the TS says System Now Booting for over 2 hours now and Leds 2, 3 and 4 just blink green. What's the TS doing?

 

 

No network access, not found with Nas Navigator...

Still no access to my data.

 


Paul

  • Big Bull
  • *****
  • Posts: 1223
Re: Terastation Live E04 problem
« Reply #3 on: December 20, 2008, 12:31:35 pm »
Try flashing the firmware on each drive, then use the TFTP boot to restore the boot files.

tjulo

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #4 on: December 20, 2008, 04:18:25 pm »
   

How do I flash the firmware on the drives, without network access to the TS? Should I plug the disks into a linux box and mount the partitions?

 

THANKS! 

TJ 


Paul

  • Big Bull
  • *****
  • Posts: 1223
Re: Terastation Live E04 problem
« Reply #5 on: December 22, 2008, 09:55:14 am »
I would do it all from a direct connection to the unit.  The TFTP was designed to fix this issue.  If it is not working then I would call you local support and set up an RMA.  If data is a concern you can do an advanced replacement and put your old drives into the new unit.  This may be a result of hardware failure.

tjulo

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #6 on: December 22, 2008, 07:57:29 pm »
   

I found this post that solved my problem without data loss. Like it says in the post Buffalo should redesign the partitions on disks and stop telling customers to format their disks like so many posts in this forum.

 

<snip>

Message Edited by Colin137 on 06-23-2009 03:03 PM

Paul

  • Big Bull
  • *****
  • Posts: 1223
Re: Terastation Live E04 problem
« Reply #7 on: December 23, 2008, 08:47:07 am »

This fix replaces the boot files, as does the TFTP fix we offer, however enabling ssh and telnet on the unit voids the warranty. 

 

TFTP directions


LouJanelle

  • Calf
  • *
  • Posts: 1
Re: Terastation Live E04 problem and E06
« Reply #8 on: May 16, 2009, 08:15:54 pm »
   

TeraStation (HS-DH1.0tGL/R5) will not boot error E04

 

Procedure to correct:

·        Remove drive 1 and reboot.  Shut down.

·        Remove drive 2 and reboot.  Shut down.

·        Remove drive 3 and reboot.  Shut down.

·        Remove drive 4 and reboot.  Shut down.

·        With all drives in place, reboot.

 

TeraStation now shows an error E06

 

Procedure to correct:

·        Download and extract the most recent firmware update (VERSION=2.14-1.02) to your PC (Dell 400SC / Windows XP Pro / Service Pack 3).

·        Modify the LSupdater.ini file:

o       [Flags]

o       VersionCheck = 0

o       [SpecialFlags]

o       Debug = 1

·        Save changes and run TSUPDATER.exe

·        Right-click on the program’s task bar and check the following boxes in Debug Mode

o       Do not check version

o       Deleter user-config (admin account will be reset to admin / password)

o       Force Update

 

After the program runs and does its thing it will restart the TeraStation and “all will be well”.

 

If I down my TeraStation and reboot, I get the system error E04 and have to start the whole process all over again!  I am not sure what the two system errors are trying to tell me.

 


dirtprof

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #9 on: June 21, 2009, 08:41:55 pm »
   

I am getting E04 messages as well, and I have tried everything on this thread to no avail.  I put all four disks on my Linux box and used mdadm to reassemble the RAID5 (disk 4 was faulty), everything looked good.  But after I put the drives back in the Terastation Live, I'm still getting the same error E04, even after repeating the various firmware flash strategies.  Is there some way to use my linux box to put the firmware on the drives?


dirtprof

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #10 on: June 22, 2009, 02:08:35 am »
   

OK, I have some progress to report.  By following the directions in <snip>, I found the following:

 

1.  /dev/sdd6 (the raid5 portion on disk4) is flagged as faulty.  I used mdadm as suggested in the link to reassemble and repair the array.

2.  The file /etc/melco/diskinfo was incorrect.

array1=off (should be array1=raid5)
array2=off
disk1=normal (should be disk1=array1)
disk2=array1
disk3=array1
disk4=array1
usb_disk1=
usb_disk2=
usb_disk3=
usb_disk4=

NB: Based on the output of cat /proc/mdstat, I believe that disk1 in /etc/melco/diskinfo actually corresponds to /dev/sdd6
3.  When I reboot, all the above changes disappear, as if something during bootup wrote over them.

4.  Reflashing the firmware yields e04 yet again, and (I believe) /dev/sdd6 is corrupted again.

 

My working hypothesis is that there is a bug (feature?) that causes all changes to /etc/melco/diskinfo (and possibly elsewhere) to be overwritten during emergency bootup.  Thus the raid5 array is not created properly, and /dev/sdd6 is treated as a "normal" disk during firmware flashing, corrupting it.  So somehow I need to find a way to make these changes persist through emergency reboot (since, except for immediate post-flash, it's the only kind of boot my Terastation Live can do).

Message Edited by Colin137 on 06-23-2009 03:03 PM

dirtprof

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #11 on: June 23, 2009, 05:48:38 am »
   

SUCCESS!!!  In addition to the above, I did a couple of other things while connected via telnet (see earlier link).

 

1. # mount /dev/md0 /boot

2. # mount /dev/md1 /rootfs

3. # mount /dev/md2 /mnt/array1

4. delete all files in /boot EXCEPT initrd.buffalo and uImage.buffalo

5. update firmware

 

And all appears well.


dirtprof

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #12 on: June 23, 2009, 01:11:12 pm »
   

So, to summarize the steps that I needed to do in order to recover my Terastation Live with all data intact:

 

1.  Emergency boot

2.  Gain telnet access using ACP_Commander (voids warranty, but mine is well out of warranty and there was no other choice).

3.  Re-assemble all arrays as follows:

 # mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

 # mdadm --assemble /dev/md1 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2

 # mdadm --assemble /dev/md2 /dev/sda6 /dev/sdb6 /dev/sdc6 /dev/sdd6

4.  If any devices are bad, you'll see the message that the array was assembled with three out of four drives.  If this occurs, add that drive back in as follows

 # mdadm -a /dev/mdX /dev/sdyZ 

where X, y, and Z depend on which disk is bad in which array. It may take some time to re-add the faulty device to the array.  You can check progress using

 # cat /proc/mdstat

5.  Once all 3 arrays are re-assembled, you need to mount them as follows:

# mount /dev/md0 /boot

# mount /dev/md1 /rootfs

# mount /dev/md2 /mnt/array1

6.  Use vi to edit /etc/melco/diskinfo (see my earlier post) to ensure correct info

7.  Ensure that /boot contains only initrd.buffalo and uImage.buffalo

8.  Use a windows PC to flash firmware (I never got the tftp method to work--no files were ever pulled over, even though the PC was connected directly to the Terastation and no firewalls or antivirus software were running).

9.  Done!

 


Colin137

  • Big Bull
  • *****
  • Posts: 1125
Re: Terastation Live E04 problem
« Reply #13 on: June 23, 2009, 03:02:41 pm »

dirtprof,

 

I'm glad you were able to recover from the errors you were having. Unfortunately, I will have to remove the link from your posts per our forum guidelines. Please do not post the link again.


dirtprof

  • Calf
  • *
  • Posts: 5
Re: Terastation Live E04 problem
« Reply #14 on: June 23, 2009, 07:32:17 pm »
   

It's interesting that violating guidelines succeed where technical problems fail in eliciting official responses.  Even so, here is the only reference to posting links in the Forums' Terms of Service:

 

"You agree not to do any of the following actions while using Buffalo Technology discussion forums:
<snip>

(2) transmit via Buffalo Technology discussion forums any information, data, text, files, links, software, chat, communication or other materials ["Content"] that Buffalo Technology considers to be unlawful, harmful, threatening, abusive, harassing, defamatory, vulgar, obscene, hateful, racially or ethnically offensive, or otherwise objectionable;"

 

That was what I agreed to in order to join the forums.  The forum guidelines are almost identical to the TOS, but do have one other item tacked onto the list of forbidden actions:

 

"(9) suggest or show how to make alterations or changes to firmware or hardware of Buffalo Technology products, use of DD-WRT, Tomato, or non-Buffalo-approved firmware (violates and terminates USA warranty of wireless products.), or provide links to non-Buffalo-approved firmware or hardware how-to articles."

 

That was such an afterthought that nobody even bothered to copy it over to the Terms of Service!

 

But even that's a stretch.  I'm not suggesting alterations or changes to firmware; I'm suggesting restoration of firmware.  Gaining telnet access to the file system is absolutely required to recover the Terastation in situations like mine.  No other solutions posted on these boards worked despite following all instructions explicitly through multiple attempts.  What is truly "harmful" is telling people their only recourse is to RMA their systems or redo partitions, losing data in the process.  It is the opposite of "harmful" to document a way--so far as I know, the only way--that users can recover their systems and their data if they, too, suffer the consequences of a power outage and wind up with damaged file systems and arrays like I did.

 

If Buffalo tech support would actually provide solutions to E04 problems like mine, then guideline #9 would be defensible.  But since many E04 errors have not been addressed successfully in this forum, it is simply not defensible to block user-supplied solutions that actually do work.  Sheesh.