|
|
Post by turtlesoup on Nov 9, 2006 15:52:05 GMT 7
Hi,
I'm glad to have found this forum.
I bought a n5200 a few weeks ago and immediately upgraded to the 1.00.3 firmware. I was experiencing random reboots every few days. I emailed thecus and they sent me the 1.00.4.9 firmware the next day. I just upgraded it today so I'll see how it goes, but has anyone else experienced these reboots?
Oh and my lcd display freezes on the new firmware.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Nov 9, 2006 19:09:25 GMT 7
I experienced reboots and crashes with 1.00.03 firmware due to snapshots. The beta firmware you installed has disabled snapshots.
My LCD is also non-functional with the beta firmware. Hopefully the next version will fix that.
|
|
|
|
Post by turtlesoup on Nov 10, 2006 1:51:46 GMT 7
Hi, thanks for the reply. I had seen issues with snapshot on this forum. I used all my space (i.e. 100%) on the "Data Percentage" so I assume no space should be left for snapshot and it would have been disabled? Maybe not.
The reason I got the n5200 was because I've owned a n2100 for the past 10 months and had 0 problems with it (other than transfers are kind of slow). I needed more space plus I wanted some redundancy support. I'll be selling the n2100 to a friend.
Thecus has had a LOT of firmware updates for the n2100 so I'm hopeful the n5200 updates will be equally abundant.
|
|
mango
New Member
Posts: 7
|
Post by mango on Nov 10, 2006 20:10:48 GMT 7
I also have problems with random reboots every 1-2 days. My LCD display usually freezes after 16-24 hours... and after another 16-24 hours the N5200 reboots. If it gets rebooted while you are copying files to it the RAID can be destroyed and you loose all your data. Happened to my the first week while I was testing the unit.
I have updated to the latest beta 1.00.04.9 and I still experience random reboots. I dont use the snapshots feature.
I have sent severals emails to TheCus support about this and I have yet to receive a reply.
I while wait a few more days for a new firmware update... if they don't fix the problem I'm going to return the N5200 to the reseller.
|
|
|
|
Post by turtlesoup on Nov 11, 2006 1:03:08 GMT 7
Hey mango,
sounds exactly like the problem I am having. One time it rebooted while I was writing to it but luckily I didn't lose any data. However it did have to rebuild the array (I could access it while it was rebuilding) and that took all day.
I wrote Thecus about the problem but they just told me to upgrade to the 4.9 firmware. I still had the problem though. Nice to know I'm not the only one experiencing this but as you said, my main concern is it rebooting during a read/write and wiping out my data.
Are you using the 4 port gigabit switch on the back? I didn't notice any reboots the 1st week I owned the unit and I believe they only started once I began using the gigabit switch. I've unplugged everything from the switch and crossing my fingers that it might have been causing the problem.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Nov 11, 2006 2:08:15 GMT 7
Like I've said, since snapshots were disabled I havent had a crash/reboot issue.. Though I also don't have the router (I have the 5200B version).
|
|
mango
New Member
Posts: 7
|
Post by mango on Nov 11, 2006 5:51:25 GMT 7
turtlesoup: Yes. I have the gigabit router version but I'm only using the WAN port atm.
|
|
|
|
Post by turtlesoup on Nov 11, 2006 14:21:38 GMT 7
 Hmm, I was hoping the use of the switch was causing the problem. Let's see what else we have setup the same since we seem to have the same reboot problem. I'm using 5 WD5000YS-01MPB0 disks in a raid 5 config. I used 100% of the space for data (none for USB target). The only service I have running is SMB/CIFS.
|
|
mawe
New Member
Posts: 14 
|
Post by mawe on Nov 11, 2006 16:50:43 GMT 7
I'm using 5 WD5000YS-01MPB0 disks in a raid 5 config. I´ve got the same 5 WD5000YS-01MPB0 and experienced bad quality of the hard disks. I had 2 out of 5 hard disks with failure just after I bought them. |
|
|
|
Post by turtlesoup on Nov 12, 2006 1:20:41 GMT 7
Hi Mawe,
did you get those HDs replaced? And have you had problems since then? Mine seem to be working ok (unless they are the cause of the reboots).
Anyway, my n5200 rebooted again last night, so I don't think the gigabit switch is the cause.
I emailed Thecus again so I'll post their response when/if I get one. I still think the N5200 is a great machine but I really hope Thecus will show interest in finding and solving the reboot problem.
|
|
|
|
Post by kevincheng on Nov 15, 2006 23:20:48 GMT 7
Hi Mawe, did you get those HDs replaced? And have you had problems since then? Mine seem to be working ok (unless they are the cause of the reboots). Anyway, my n5200 rebooted again last night, so I don't think the gigabit switch is the cause. I emailed Thecus again so I'll post their response when/if I get one. I still think the N5200 is a great machine but I really hope Thecus will show interest in finding and solving the reboot problem. I have talk to thecus guy. They say that problem have be fixed in next firmware release. |
|
jamis
Full Member
Posts: 109
|
Post by jamis on Nov 16, 2006 5:07:07 GMT 7
I have talk to thecus guy. They say that problem have be fixed in next firmware release. Did they happen to say when the next firmware (beta or otherwise) will be available? |
|
|
|
Post by turtlesoup on Nov 16, 2006 7:22:54 GMT 7
I have talk to thecus guy. They say that problem have be fixed in next firmware release. Wow! That would be excellent! That is my only real complaint about the N5200 is the random reboots. Thanks! |
|
|
|
Post by kevincheng on Nov 16, 2006 12:35:26 GMT 7
I have talk to thecus guy. They say that problem have be fixed in next firmware release. Did they happen to say when the next firmware (beta or otherwise) will be available? Maybe those two day!! ;D |
|
|
|
Post by quick on Nov 18, 2006 4:27:55 GMT 7
Hi...
Discovered just now that I am also having these random reboots.
I am running 1.00.04.9 and would be very happy to get feedback on how the 1.00.04 works.
|
|
Hmm, I was hoping the use of the switch was causing the problem. Let's see what else we have setup the same since we seem to have the same reboot problem.