News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

Terastation ts5800 problem booting BIOS

Started by sgit, March 02, 2022, 06:28:49 AM

Previous topic - Next topic

sgit

Hello

I got a problem with my ts5800. I start it ok, check the hdds and ram ok but when BIOS start just show 2 lines and freeze.
In the terastation lcd it show "Starting up"

I took a screenshot

I changed RAM and battery and tried remove disc 1 and disc 8 to start but got the same problem

Any ideas?

PD: Íf I change the 8 disk in the same order to another ts5800,could It work and recover the data?

Thanks


1000001101000

Does it say anything on the rest of the screen?

sgit

Nop, just that you see in the pic, two lines and the Bios stop
I had checked another ts5800 and in the next step the bios should show the keys to access bios setup

sgit

#3
Ok I tried to change the 8 disk to a similar NAS and... It`s work!

I assume the firmware of my original NAS is damaged. It don´t work without discs, fail at the same point, two lines in BIOS start

Could I install a new firmware or flash de BIOS without discs by anyway?

Thanks

UPDATE: I tried start with USB but I can`t because the bios stop before check the USB ports   

1000001101000

The two things I would try:
Clear the CMOS, possibly unplug the battery and leave overnight etc.
Dump the bios with an spi programmer and compare to a dump from a working unit. Attempt to reflash it if that seems workable.

sgit

I think it like you.

I´ll leave today without battery but i think It wont work

Anyone dump the bios anytime or could help me dumping it? I get a working motherboard but need any help to extract bios or a motherboard diagram?
Do you think to dump bios I would need unsolder and extract the correct chip? or maybe the motherboard have a port to extract it?

Thanks

1000001101000

I haven't done it with this series of device, but hopefully the BIOS/etc is stored on one of the 8-pin chips marked with a red dot:
https://static.miraheze.org/buffalonaswiki/9/9c/Ts5800dn_board4.jpg

Typically those can be dumped/flashed without soldering using one of these (assuming the chips aren't damaged):
https://www.amazon.com/Organizer-Socket-Adpter-Programmer-CH341A/dp/B07R5LPTYM/


1000001101000

I took a look to see if I could dump mine without needing to open up the case, I ended up with something that looks promising:


# flashrom --programmer internal -c "MX25L3273E" -r test.img
flashrom v1.2 on Linux 5.15.0-0.bpo.2-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found chipset "Intel ICH10R".
Enabling flash write... The Flash Descriptor Override Strap-Pin is set. Restrictions implied by
the Master Section of the flash descriptor are NOT in effect. Please note
that Protected Range (PR) restrictions still apply.
OK.
Found Macronix flash chip "MX25L3273E" (4096 kB, SPI) mapped at physical address 0x00000000ffc00000.
Reading flash... done.



# binwalk test.img

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
4096          0x1000          UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
135168        0x21000         UEFI PI Firmware Volume, volume size: 1638400, header size: 0, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
136736        0x21620         Intel x86 or x64 microcode, sig 0x00030661, pf_mask 0x04, 2011-12-22, rev 0x010d, size 5120
142880        0x22E20         Intel x86 or x64 microcode, sig 0x00030660, pf_mask 0x04, 2010-11-03, rev 0x0003, size 5120
149024        0x24620         Intel x86 or x64 microcode, sig 0x00020661, pf_mask 0x01, 2009-10-23, rev 0x0104, size 5120
155168        0x25E20         Intel x86 or x64 microcode, sig 0x00030661, pf_mask 0x08, 2011-12-22, rev 0x010d, size 5120
161312        0x27620         Intel x86 or x64 microcode, sig 0x00030660, pf_mask 0x08, 2010-11-03, rev 0x0003, size 5120
167456        0x28E20         Intel x86 or x64 microcode, sig 0x000106ca, pf_mask 0x20, 2009-08-25, rev 0x0106, size 5120
580972        0x8DD6C         Microsoft executable, portable (PE)
735810        0xB3A42         Copyright string: "Copyright (C) 2011 American Megatrends, Inc."
1839104       0x1C1000        UEFI PI Firmware Volume, volume size: 262144, header size: 0, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1839212       0x1C106C        Microsoft executable, portable (PE)
1841828       0x1C1AA4        Microsoft executable, portable (PE)
1843088       0x1C1F90        Microsoft executable, portable (PE)
1852796       0x1C457C        Microsoft executable, portable (PE)
1904908       0x1D110C        Microsoft executable, portable (PE)
1906572       0x1D178C        Microsoft executable, portable (PE)
1920348       0x1D4D5C        Microsoft executable, portable (PE)
1925064       0x1D5FC8        Microsoft executable, portable (PE)
1965724       0x1DFE9C        Microsoft executable, portable (PE)
1969296       0x1E0C90        Microsoft executable, portable (PE)
1977112       0x1E2B18        Microsoft executable, portable (PE)

sgit

Hi

First time, thanks for your help, It could safe me life

I bought last day the thats clamps in Ali to try dump it without soldering. My motherboard is similar, but as you can see there are 3 chips with red dots, could be any of them? I had dump its one by one and compare with the chips of my good motherboard? (I assume that possibly the clamps work just with one chip, the farest from ram because the others are more small o big and can´t fix with dumper )

In your other post you saw me a dump, Did you got with the clamps in one of thats chips or you connect to NAS by ssh or similar?

Thanks

1000001101000

Mine is running Debian Linux, I was able to create that dump by connecting over ssh and using a utility called flashrom.

The large chip with many pins is the microcontroller which drives the LCD and some other functions. I don't know of a way to dump/flash it but it also shouldn't be the problem.

I would suggest looking at the model numbers on those 8-pin chips and looking up what they are online. One will probably be a 4kb spi flash chip which should have the bios image on it (the same as what I was able to dump from the OS). If the other one is also spi flash it might be worth dumping it to compare to your other board. I know arm devices usually have a separate bootrom chip, i don't know what it is for this device.

sgit

Hi

Ok then I`ll wait for the clamp and I ´ll dump both chips on the good motherboard and compare with the failed mobo. I will tell you any differences between them

Thanks for the help

sgit

#11
Hello again

Ok, finally I could dump firmware bin from fail and ok Bios Chipset

The failed mobo dumping was different from the ok mobo. Then I wrote the correct firmware in the failed bios chipset. When finished I checked It two times and It was fine and the firmware is identical to correct dump.

Next step I start the failed NAS and...failed again in the same step

Again I dump the BIOS firmware and...It corrupted again

I did the same process two times and It always corrupted the firmware

Any ideas?

PD: I add a bios firmware screenshot
My chip is different, is a 25L3206E but as you say (1000001101000) it can´t be other chip in the mobo


JoeAsheville

Hopefully you've corrected this problem 120 days on, but if not...I would suspect a physically bad chip. This is a rare occurrence, but it can happen. If you can obtain a new chip, replace, re-write as described in the immediately prior post, and reboot. Then go from there.

Otherwise it's a parts unit.

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: 356 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1160KB.
Tokens: post-login.
Queries used: 20.

[Show Queries]