|
|
Post by drewy on Oct 20, 2009 23:30:50 GMT 7
?
|
|
tlea
New Member
Posts: 6
|
Post by tlea on Oct 21, 2009 7:35:41 GMT 7
Not yet, and I have had one RAID wipeout which took 14 hours to rebuild.
Can't get the downgrade.zip from Thecus or the factory_test.sh from peterfu to work.
At this point I have been okay for a week but am backing up daily and hoping for a stable 3.xx release soon.
For the record, I went in knowing it was beta so have no one to blame but myself. But I must say that I did expect to be able to roll back to an earlier version.
|
|
|
|
Post by drewy on Oct 23, 2009 3:09:45 GMT 7
no me niether. NOt having much luck the factory restore script doesn't work and so I've tried removing the dom and flashing a new image to that but can't get that to work either. Keep getting bad block errors while trying to mount the dom  I have a support ticket open with thecus but don't hold out too much hope. |
|
|
|
Post by drewy on Oct 24, 2009 1:43:29 GMT 7
I got a fix from Thecus support and it worked for me. Use the attached file, unzip it to a fat32 usb stick along with www.thecus.com/Downloads/N5200_N5200PRO_FW_2.00.16.bin2009/03/12 16:37 33,626,632 N5200_N5200PRO_FW_2.00.16.bin MD5(N5200_N5200PRO_FW_2.00.16.bin)= 77b3f124c8753866d3017085568df312 Plug it in the the 5200 and boot up. The Orange busy light should soon light up. This will stay lit for 1-2 mins, the unit will then bleep and the light will go out, remove the usb stick. Flashing will then continue and after another 4-5 minutes the nas should reboot. Attachments:
|
|
deej
New Member
Posts: 8
|
Post by deej on Oct 28, 2009 3:51:04 GMT 7
Will that also work with 2.01.17 beta? I need XFS support  . |
|
|
|
Post by peterfu on Oct 28, 2009 12:47:23 GMT 7
It may work, cause the script does not contain any FW file name, it just searches for a *.bin file - but if it does not work and You have already formatted to XFS, then try the FW downngrade without discs and upgrade afterwards without discs to 2.01.17.
br
Peter
|
|
|
|
Post by termlk on Oct 31, 2009 13:03:14 GMT 7
Works fine if you follow the instructions above ... only challenge I found is when to remove the USB key....it seems to continually keep installing the firmware. After about 3 times I pulled the key before all the "HHHHH..." showed up.
|
|
|
|
Post by drewy on Oct 31, 2009 23:46:06 GMT 7
Works fine if you follow the instructions above ... only challenge I found is when to remove the USB key....it seems to continually keep installing the firmware. After about 3 times I pulled the key before all the "HHHHH..." showed up. I added a little more detail to my earlier post, ref when to pull the usb stick. |
|
deej
New Member
Posts: 8
|
Post by deej on Nov 1, 2009 23:51:35 GMT 7
Well it doesn't work with the beta firmware so you'll need to downgrade to 2.00.16. For those of us who have XFS, you need to do this WITHOUT disks as peter mentionned. Afterwards upgrade to the latest beta .17, put the disks back in and voila, it works . |
|
|
|
Post by yadanac on Nov 8, 2009 1:10:02 GMT 7
Firmware 3.00.05 killed my N4100PRO transfer speed. I happened upon this topic, and tried this procedure with a downgrade back to my original firmware. It worked perfectly, and transfer speeds are back where they were. Thank You! Thank You! Thank You!
|
|
|
|
Post by steveh on Jan 29, 2010 3:03:49 GMT 7
Does anybody have a copy of the latest firmw3are that supports xfs as Thecus seemed to have pulled the 2.1 releases from both the beta and the download dirs?
Steve
|
|
|
|
Post by elroycarbon on Feb 19, 2010 2:19:10 GMT 7
man, I'd like to tip my hat to you folks. I bought my second N5200 Pro from Newegg, open box. Some joker installed 2.01.09 firmware on it. I am using it in a very limited fashion and decided to go back to the latest from their site. This thread helped me get there along with the downloads. I'm installing 5 2TB Western Digital drives, cross my fingers!
|
|
|
|
Post by spikey on Mar 22, 2010 4:50:40 GMT 7
will have to give it a go how diffrent is the lay out with it
|
|
|
|
Post by steveh on Jan 2, 2012 18:36:08 GMT 7
Just to add a little bit more info, I just went from v3 directly to 2.1.17, all I did was remove the BETA part of the filename (I didn't try with the original filename so I can't tell whether it would have worked like that).
Took about 4-5 minutes in total and I'm back where I should be on 2.1.17.
Steve
|
|
cz
New Member
Posts: 3
|
Post by cz on Feb 18, 2012 20:00:36 GMT 7
I have to add to this thread, this is one reason I'll never buy another Thecus ("new" anyways, I just bought a pair of 5200's cheap to play with alternate OS's) again. In the past, virtually every firmware that's been released the old ones "go away" within a few months, they've released some horribly buggy releases and 'poof' the old one is gone... and/or there's no rollback strategy.
And I see all the foo-foo articles about them being 'enterprise class', my experience to date (4100, 5200B, 8800) is that they are virtually unsupported within 2-3 years of coming out.
|
|
.