|
Post by phaedrus on Aug 7, 2009 19:11:48 GMT 7
That's a bit weird, 2 days ago they published v2.00.16... This version 2.00.16 is exactly the same as the 2.00.16 which had been published in March/April 2009 and was declared BETA - I do not understand Thecus anymore. So far I have almost regularly updated the FW from 1.00.3 (or was it 1.00.4?) to 2.00.10 - but I have somehow lost my trust since then. Thanks to you all for sharing your experiences! Phaedrus
|
|
|
Post by drewy on Aug 7, 2009 20:32:52 GMT 7
has anyone tried contacting Thecus for the offical line on what is happening?
|
|
|
Post by samonkey on Aug 25, 2009 10:14:03 GMT 7
Here's what happened to me with 2.01.09 over the past couple of days (we're a small outfit):
I started to get some raid drop-outs as mentioned in preceding posts, then an apparently more serious problem. Then at some point it completely removed one of the drives for no clear reason (the drive (ext3) itself checks out OK in other enclosure) .
Then it failed again... BAD. After more than 3 DAYS of trying to rebuild less than 500GB of data (previously it took about 5 hours after the (supposed) initial HD problem for the same data), I gave up and rebooted. Now the entire RAID array is completely GONE.
And to top it off, they finally got email properly working in this build, which you would think is a good thing... In hindsight it kept emailing me alternating between Em206E & Em205E about TEN TIMES / MINUTE. In short bursts, or so it seemed. BUT this morning the mailserver caught up and I had approx. 14000 (yes, fourteen thousand!!) email filling my entire Inbox...
I wouldn't touch another Thecus product with a ten-foot pole. As a matter of fact, if it wasn't for our budget, I'd be looking into something else right now.
Lessons learned: - Don't use 2.01.09 (which btw still didn't solve the Mac files issue with smb introduced after 2.00.14) - Don't turn on email notification unless you want to find your Inbox completely swamped one morning. - Don't trust RAID5. Backup everything somewhere else anyway!
|
|
sgunn
New Member
Posts: 12
|
Post by sgunn on Aug 27, 2009 20:36:53 GMT 7
Have you opened a ticket with Thecus? It may take them a few days, but they do respond. They had a beta firmware that resolved the most critical of my issues. Keep in mind that support is in Taiwan, so there is a 12 hour time difference.
As for trusting the NAS, I am in agreement with you, I no longer trust it at all, which really defeats the purpose of a raid5 NAS. And I'm sick of hearing people saying "raid is not a backup." No, it's not, but if raid doesn't provide some level of reliability, really, what's the point?
Stephen
|
|
|
Post by samonkey on Aug 28, 2009 9:26:29 GMT 7
Update: So after reading up here on the dropped drives that weren't really defective, I decided that I'd give it one last shot before building a new array. I ran complete scans on all the drives including the dropped ~supposedly~ defective one, and after one more reboot it suddenly saw the RAID array again, and started rebuilding.
Further 6 hours later it was back to being healthy and all the content seems to be there as far as I can tell... I have NO IDEA what it did doing those 3 1/2 days of "rebuilding", all drives running full-on (including the new spare)... other than send out a #*&@-load of email?!?
|
|
|
Post by rookie on Aug 30, 2009 17:08:20 GMT 7
Running with firmware 2.01.09 for some time now. Back then my old 4-disks (Samsung HD501LJ) RAID-5 array created in firmware 2.00.01 on EXT3 was running fine.
A few days ago I wanted to try the XFS filesystem in RAID-10, so deleted the array and created the new one. Still running fine, except that mounting a SMB-share on a computer takes a 'bit' longer as usual.
I also think Thecus has to do something on their NAS firmware/software stability. Probably they can learn a lot from companies like QNap i.e.
|
|
|
Post by samonkey on Sept 2, 2009 8:53:14 GMT 7
(2.01.09) When trying to do a filesystem check, I get the following message: ZFS is not need file system check! (sic) I'm using ext3...
Did other people run into that?
|
|
|
Post by wjc3usa on Sept 3, 2009 4:27:53 GMT 7
They did? I have been getting a Not Found error when I try to download. Walt
|
|
|
Post by drewy on Sept 3, 2009 5:09:01 GMT 7
they withdrew 2.01.09 due to a few problems with it
|
|
|
Post by wjc3usa on Sept 3, 2009 10:37:42 GMT 7
That's too bad.. I was looking forward to a major update, compared to my current 2.00.14.
sooo.. who's up for 2.01.12? ;D
|
|
gonz0
Junior Member
Posts: 63
|
Post by gonz0 on Sept 4, 2009 4:37:13 GMT 7
they withdrew 2.01.09 due to a few problems with it just bloody great, i have that firmware and the sammy F1 drives its not on much, just when i want to watch a film. i will leave it off until they fix the bugs.
|
|
|
Post by rookie on Sept 4, 2009 22:36:53 GMT 7
I'm running version 2.01.12 since a few days! No problems so far, but a backup-copy on an external harddisk has been made recently ;-) - (sysuser, ssh, info, ip-cam modules installed and as mentioned above a newly created RAID-10 array with XFS)
|
|
deej
New Member
Posts: 8
|
Post by deej on Sept 6, 2009 22:11:36 GMT 7
sooo.. who's up for 2.01.12? ;D I upgraded my firmware from 2.00.16 to 2.0.12 beta and installed 3 Samsung Ecogreen F2 1.5 TB HD154UI with firmware 1AG0. FW upgrade went smooth, built RAID5 XFS with 128 kb stripe size (took 11 hours), and started FTP'ing my backup data to the box. Noticed at first it didn't go over 25 MB/s write speed. Enabled Jumbo Frames (9000 bytes) and upload speed jumped to around 38MB/s. System is still uploading (I have a backup of 2.5 TB to upload) but so far it has been running nearly 48hours straight without any glitches. I'm keeping the backups of course just to see whether or not I'm going to get the same corruption issues reported here (but with other Samsung drives). For now, happy happy happy!
|
|
|
Post by rookie on Sept 9, 2009 15:45:48 GMT 7
|
|
deej
New Member
Posts: 8
|
Post by deej on Sept 12, 2009 17:30:35 GMT 7
Yes those kind of release notes are very convincing for people who wish to try that firmware *sigh* To follow up on my post higher: I added 2 extra Samsung disks and performed the RAID migration (which took more than 2 days). But now I have 5.4 TB in RAID 5, working very well. XFS is a blessing when it comes to large files (like DVD rips and HD video files).
|
|