Buffalo Forums

Products => Storage => Topic started by: sokudo on June 05, 2009, 01:02:17 PM

Title: TeraStation Live HS-DHTGL/R5 can't load Kernel
Post by: sokudo on June 05, 2009, 01:02:17 PM
   

I came back from a trip, turned on my HS-DHTGL TeraStation Live, and find that it enters EM Mode. I flashed it with the latest 2.14 firmware after following the instructions on this forum, but the TeraStation still gives System Error E04 "Can't Load Kernel".

 

I haven't tried the TFTP method because NAS Navigator finds the unit and reports it to be in EM mode.

 

Should I telnet into the unit to troubleshoot ?


Or is there a better way to restore the unit to full functionality ?
 

Title: Re: TeraStation Live HS-DHTGL/R5 can't load Kernel
Post by: joe42 on June 05, 2009, 03:47:59 PM

Likely whats happening is that the problem lies in one of the hard drives.

If flashing the firmware hasn't done the trick, try removing one drive at a time, and booting the device with only 3 of the drives in the unit at a time. If you're able to get into I12 'Degrade Mode,' flash the firmware again. If not, replace the first drive and take out the second, and so on.

Title: Re: TeraStation Live HS-DHTGL/R5 can't load Kernel
Post by: sokudo on June 06, 2009, 01:43:26 AM
   

Ok, I turned the unit off, and took out each drive, one at a time, and rebooted the unit. Each time, it came up and reported the missing drive as HDx Error E16, HDx Not found. With all of them back in, it again reports Emergency Mode, No Array Info.

I wasn't able to get into I12 'Degrade Mode'. (If one of the drives was faulty, shouldn't the TeraStation report it as having failed ? )

I'm not sure I understand the procedure you are suggesting in the last part. 

Thanks for the help !

Title: Re: TeraStation Live HS-DHTGL/R5 can't load Kernel
Post by: PCPiranha on June 06, 2009, 12:18:08 PM

The TS will report HD failure but if the kernal cant load the problem might be located on one of the disks, when you are trying to boot off of 3 drives you are trying to find the "magic" drive.

 

Now that its in EM mode try force flashing the firmware.

 

If you ever get the E04 error again try the TFTP boot procedure because the unit is sending out TFTP requests.

Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 60 (show)
Files included: 27 - 1055KB. (show)
Memory used: 734KB.
Tokens: post-login.
Queries used: 10.

[Show Queries]