News:

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

Main Menu

Terastation TS4200D-EU - recovery image

Started by similije, December 27, 2021, 05:50:48 AM

Previous topic - Next topic

similije

Hi everyone,

At my office we have an old Terastation TS4200D-EU with faulty drives. We wanted to put it to some use, so we filled it with a couple of spare WD purple drives.
The unit is old and we don't have the USB recovery that came with it. Since there is nothing on the EU site, i downloaded the TS5k_recovery_260
from US site. I booted the device in EM mode and performed the FW installation (v4.18). Everything went well, except the device in now identified as TS5200D.

Everything seems to be working fine, and I don't know whats the real difference between TS4200D-EU and TS5200D-EU. Should I leave it as it is, or try the recovery process again?
If I should do the recovery again, does anyone, please, have a recovery image for T4000 EU series?

Thanks in advance

1000001101000

I have no idea what's different about the TS4000 series vs TS5000 other than they never seem to have marketed a US version of the TS4000.

I did work with someone who had one once and I believe they were able to make this process work for them:
https://buffalonas.miraheze.org/wiki/Create_Recovery_Disk_for_Intel-based_Terastation

You can also usually get an official recovery image from support for a fee.

You could also try installing Debian on it, I'd actually appreciate getting someone to try it out and see if it needs any customization for the TS4000:
https://github.com/1000001101000/Debian_on_Intel_Terastations

similije

Thanks for the quick reply. I've tested the device today and it seems to be working fine even with TS5000 Firmware.
I've compared the specs and the only difference seems to be that TS5000 is advertised as network DVR/Video surveillance solution
and TS4000 as NAS solution. Hardware seems to be exactly the same.
I'll try the custom boot first, and report the results.
Afer that, whan I have time, I'll try the Debian...

Thanks again...

similije

I tried both things, but it' doesn't work.
In both cases it either it won't try to boot at all, or it gets stuck at "Booting from USB...."
Tried different tools, simple variations, but nothing....
After unpacking the TS5000V2.6bootUSB.ddi, i tried to edit grub file and repack it again, but this
also didn't work. I've noticed that the grub location in original firmware is not /boot/grub/grub.cfg
but only /grub/grub.cfg.  So instead of grub-mkrescue i tried genisoimage, xorisso, but nothing....

At the end I did a very simple thing, I mounted TS5000V2.6bootUSB.ddi image (used WSL), and while mounted
I edited the original grub.cfg (only changed ts4000=no to ts4000=yes in 4 places) and unmounted the image.
This way, everything except grub.cfg remained the same as in original image...
Tried to boot and..... it works!!! The device is recognized as TS4200D, as it should be....
After that i did an update to v4.18 and it works fine. The only thing I noticed compared to TS5200 is
that the remote management option is missing in 4200. Everything else seems to be the same...

1000001101000

I'm glad to hear you figured something out.

I haven't made one of these in ages, it could be the instructions are obsolete somehow. I'd be curious to know what the terminal output in the VGA port looked like when booting the failed custom image so we could try to troubleshoot/fix the process.

Fortunately, the Debian installer images work differently and shouldn't suffer the same issue if you still want to try that.


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

[Show Queries]