News:

RAID is not a replacement for a backup! Here's why.

Main Menu

TeraStation Lockup

Started by NebulaSleuth, January 24, 2009, 04:33:39 PM

Previous topic - Next topic

NebulaSleuth

   

I have a TeraStation HD-H1.0TGL/R5.  I recently moved, and when I hooked up the device I got a failure on Drive 1.  I replaced drive one, and decided to delete the raid array, and start from scratch.

 

I installed a drive from a different HD-H1.0TGL/R5 which had the same make & model drive I was removing.  (That unit was dead already)

 

I also upgraded to the latest firmware (2.16).  After creating the new array, the TS starts "checking raid array".  

 

It never finishes.  It hangs up.  TeraStation Client Utility can't find it, I can't access the web page.  I have to cut power (power button doesn't work) in order to reboot it.

 

When it comes back up it starts "checking raid array" again, the lights flash, and then later "poof" its dead again.

 

I'm not accessing it at all during this, and have tried removing it from the network while it checks just to be safe, but it still locks up.

 

When it is hung, I get only green LEDs... the "link/act" light is flashing, the "status/full" lights on all four drives are on solid, and the "access" lights for driver 1 and 2 are flashing.  The "diag" light is off, and the power light is on solid.

 

Is it a door stop, or a NAS?  You help me decide....

Message Edited by NebulaSleuth on 01-24-2009 04:40 PM

Dustrega

NebulaSleuth,

   When the RAID check started how long did you let it run for?  A 4.0 TB RAID 5 setup and check could take as long as 8 hours (or more in some cases) to complete.  Regardless, if the unit is acting in the fashion that you state it would be best to boot the unit into EM and perform a firmware update (most likely the hang-up is occurring due to corrupt firmware).  Performing an EM boot and firmware flash using the following steps:

 

1. Shut down the TeraStation

 

2. Hold down the reset button on the back of the TeraStation (should be a small red recessed button) and then press the power button.

 

3. Wait for about 1 minute for the TeraStation to boot. (http://www.buffalotech.com/support/getfile/?TsClient.zip" target="_blank">NAS Navi should show results when refreshed after this amount of time.)

 

4. If the TeraStation is discovered on the network try the firmware update located http://www.buffalotech.com/support/getfile/?HDHTGL2_16.zip" target="_blank">here, save the file to your desktop and extract it when the download completes (right click on the file and choose 'Extract All').  Run the file NASupdater.exe  If NAS Navi can find the device then so should the firmware update.  If not please check your firewall/anti-virus software and disable as necessary.

 

5. A force firmware update might be necessary if all steps have failed to this point in which case follow these sub-steps:

    

     - Right-click on the NASupdater.exe and choose Send to...>Desktop (create shortcut)

 

     - Go to your desktop and right-click on the NASupdater.exe shortcut and choose Properties

 

     - In the target line (in the Shortcut tab) outside of the quotations to the right put one space and type '/force' (minus the quotes shown here)

 

     - Click on the Compatibility tab and check off the box that is next to 'Run this program in compatibility mode for:' and choose Windows 2000.

 

     - Double click on the shortcut to try again (if successful continue on to Step 6)

 

     - If the firmware update fails at this point I'm afraid your device will be the doorstop that you don't want it to be.

 

6. If the firmware update is successful then you should be able to see it within the NAS Navi and access it as usual.  If you require assistance mapping your network drive I would refer here.

 

   I hope that I didn't complicate the issue too much and I hope you find this helpful.


NebulaSleuth

   

After a firmware update it is still doing the same thing.  I've spent the last week trying different configurations, reformatting, resetting the raid config, etc...  It's not looking good.

 

:(

 

Not sure what to do next.  In about 2 dozen attempts,  1 time it finished checking, but locked up overnight.  Every other time it locked up before it finishes checking.  

 

Since it did finish once, I suspect that it isn't the check that is causing it, but that the device is simple failing and locking up for some reason.

 

Any other thoughts or ideas?

 


preps

   

Did you ever get this to work again.

I'm having similar problems with the same model!


Blackbeard

Sorry to bring back such an old thread, but it mirrors the one I started just a few hours ago. The links in this thread are invalid, so I was wondering firstly, what the current links to the firmware should be now, and secondly, was this ever resolved?

 

Just trying to do a little of my own research.


twebbjr

I have a HS-D2.0TGL/R5 Home Server I purchased a few years back brand new and it has been
sitting in the box unused all this time.

 

I just plugged it in last night and began to set it up for Raid 1 and started to transfer files from my
HD-H1.0TGL/R5 TeraStation which has been configured for Raid 1 and has been
working for over 5 years without problems, knock on wood. But it is reaching
capacity and I wanted to upgrade to the newer and larger capacity model.

 

This morning, I checked on the HS-D2.0TGL/R5 Home Server and found that my files stopped
copying over from the other server during the middle of the night. I also
noticed that the server is no-longer accessible via my network and there are 4
green status/full lights blinking simultaneously.  The Diag light is off, the Power light is on,
Link/Act light is mostly on / occasional flicker off.  The power button on the front is unresponsive.

 

I am using windows 7 with no problems for my HD-H1.0TGL/R5 TeraStation, after installing the vista patch.

I don't know the firmware version of the HS-D2.0TGL/R5, because the drive is no-longer accessible using the client utility.

 

Have you seen this problem before?

What is going on? 

Is my new server dead?

 

I've searched for the solution to this problem and I can't find one. 

 

Please help...

 

Tim

 


NinjaNAS

First, as a Mod I cannot help you upgrade the drives on this unit. Second, I would try and just unplug the unit and then restart it. It could have simply froze. The best thing to do once you get  it back on the network would be to update the firmware on the unit. If there is no updated available for it then you can just reflash the current firmware on to the unit using FAQ 2 of 5.


powerfulpowaz

I am having the same issue with all 3 of my TeraStations. If I push 1000's of files up to it for long periods of time, it completely locks up. I do NOT have modded firmware and I have experienced this issue running the latest update. I got frustrated and physicaly gained access to the Linux kernel output ( /dev/tty0 ) and watched it crash.

 

I do NOT have root access to this particular unit I am testing but can if needed. Everything is configured via the standard web gui.

 

I want to make it clear that this firmware is untouched.

 

It seems that the kernel is crashing related to the mdadm modules.

 

 

Console Output

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

array1 usage over 1%
array1 usage over 1%
array1 usage over 1%
md2_raid5: page allocation failure. order:0, mode:0x20
Mem-info:
DMA per-cpu:
cpu 0 hot: high 42, batch 7 used:6
cpu 0 cold: high 14, batch 3 used:13
DMA32 per-cpu: empty
Normal per-cpu: empty
HighMem per-cpu: empty
Free pages:         528kB (0kB HighMem)
Active:10105 inactive:16462 dirty:3203 writeback:794 unstable:0 free:132 slab:2562 mapped:9191 pagetables:266
DMA free:528kB min:1448kB low:1808kB high:2172kB active:40420kB inactive:65848kB present:131072kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 0*4kB 0*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 528kB
DMA32: empty
Normal: empty
HighMem: empty
Swap cache: add 13743, delete 13742, find 21191/23950, race 0+0
Free swap  = 130852kB
Total swap = 131064kB
Free swap:       130852kB
32768 pages of RAM
517 free pages
1259 reserved pages
2562 slab pages
30516 pages shared
1 pages swap cached
md2_raid5: page allocation failure. order:0, mode:0x20
Mem-info:
DMA per-cpu:
cpu 0 hot: high 42, batch 7 used:6
cpu 0 cold: high 14, batch 3 used:13
DMA32 per-cpu: empty
Normal per-cpu: empty
HighMem per-cpu: empty
Free pages:         528kB (0kB HighMem)
Active:10105 inactive:16462 dirty:3203 writeback:794 unstable:0 free:132 slab:2562 mapped:9191 pagetables:266
DMA free:528kB min:1448kB low:1808kB high:2172kB active:40420kB inactive:65848kB present:131072kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 0*4kB 0*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 528kB
DMA32: empty
Normal: empty
HighMem: empty
Swap cache: add 13743, delete 13742, find 21191/23950, race 0+0
Free swap  = 130852kB
Total swap = 131064kB
Free swap:       130852kB
32768 pages of RAM
517 free pages
1259 reserved pages
2562 slab pages
30516 pages shared
1 pages swap cached

 

 

EDIT

When I hold the power button down, it appears to flush the SATA disks out.

 

Console

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

Core Driver (ERROR) 0 0: Edma Error Reg 0xa8
Core Driver (ERROR) 0 0: Flush DMA, type=CALLBACK, commands 0 (on EDMA 0)
Core Driver (ERROR) 0 1: Edma Error Reg 0xa8
Core Driver (ERROR) 0 1: Flush DMA, type=CALLBACK, commands 0 (on EDMA 0)
Core Driver (ERROR) 0 2: Edma Error Reg 0xa8
Core Driver (ERROR) 0 2: Flush DMA, type=CALLBACK, commands 0 (on EDMA 0)
Core Driver (ERROR) 0 3: Edma Error Reg 0xa8
Core Driver (ERROR) 0 3: Flush DMA, type=CALLBACK, commands 0 (on EDMA 0)

 

 

Then uppon reboot, the normal boot

 


Orion2   CPU =  High

=== BUFFALO TS-HTGL R5 U-Boot. ===
 ** LOADER **
 ** BUFFALO BOARD: BUFFALO_BOARD_TS_HTGL_R5 LE (CFG_ENV_ADDR=fffff000)


U-Boot 1.1.1 (Apr 18 2007 - 18:35:44) Marvell version: 1.12.1 - TINY

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB
[256kB@fffc0000] Flash: 256 kB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done

Soc: 88F5281 D0
CPU: ARM926 (Rev 0) running @ 500Mhz
Orion 2 streaming disabled
VFP not initialized
SysClock = 250Mhz , TCl


powerfulpowaz

So it crashed agian, twice. The LCD says "ARRAY1 Resyncing"

 

array1 usage over 1%
array1 usage over 1%
kblockd/0: page allocation failure. order:0, mode:0x20
Mem-info:
DMA per-cpu:
cpu 0 hot: high 42, batch 7 used:6
cpu 0 cold: high 14, batch 3 used:11
DMA32 per-cpu: empty
Normal per-cpu: empty
HighMem per-cpu: empty
Free pages:         524kB (0kB HighMem)
Active:8836 inactive:17988 dirty:2987 writeback:534 unstable:0 free:131 slab:2336 mapped:8275 pagetables:252
DMA free:524kB min:1448kB low:1808kB high:2172kB active:35344kB inactive:71952kB present:131072kB pages_scanned:36 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 1*4kB 1*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 524kB
DMA32: empty
Normal: empty
HighMem: empty
Swap cache: add 1518, delete 1514, find 1044/1361, race 0+0
Free swap  = 130948kB
Total swap = 131064kB
Free swap:       130948kB
32768 pages of RAM
492 free pages
1259 reserved pages
2336 slab pages
30948 pages shared
4 pages swap cached
kblockd/0: page allocation failure. order:0, mode:0x20
Mem-info:
DMA per-cpu:
cpu 0 hot: high 42, batch 7 used:6
cpu 0 cold: high 14, batch 3 used:11
DMA32 per-cpu: empty
Normal per-cpu: empty
HighMem per-cpu: empty
Free pages:         524kB (0kB HighMem)
Active:8836 inactive:17988 dirty:2987 writeback:534 unstable:0 free:131 slab:2336 mapped:8275 pagetables:252
DMA free:524kB min:1448kB low:1808kB high:2172kB active:35344kB inactive:71952kB present:131072kB pages_scanned:36 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 1*4kB 1*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 524kB
DMA32: empty
Normal: empty
HighMem: empty
Swap cache: add 1518, delete 1514, find 1044/1361, race 0+0
Free swap  = 130948kB
Total swap = 131064kB
Free swap:       130948kB
32768 pages of RAM
492 free pages
1259 reserved pages
2336 slab pages
30948 pages shared
4 pages swap cached


lukell

Hi Tim, hi all,

 

want to report I have the same issue with the TeraStation (HD-HTGL5/1.0) and original firmware 2.00.

 

The station has been running fine as server for years, but I had problems back then putting all the data into the station.

Again back then, Buffalo support pointed me to firmware 2.00, which improved things. Meaning I was able to copy a couple thousand files without the hangup symptom for some time (weeks).

 

After those weeks, the symptom was back (how nice?), and support was not able to help me further.

So I copied in small chunks and that way setup the station.

 

Now that I want to migrate to a newer model, copying lots of files at once either has the TeraStation break the process at some point, reboot and check drive, or even worse, just locks up as you describe (status lights look ok, but no response on power button, no ping, no web access, basically gone from network). In the latter case pulling the power plug until now always had the TeraStation reboot just fine.

 

I have to say it is totally disappointing that Buffalo seems to never have fixed this issue, as others with the latest firmware are facing it. It seems such a common use case to copy lots of files from/to a NAS... I couldnt bring myself to buy a Buffalo model this time, trust is broken. Too many hours spent worrying.



Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 310 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1152KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]