mamat
New Member
Posts: 12
|
Post by mamat on Feb 17, 2007 18:45:15 GMT 7
Yes sure, I will check if this is the same file ... as soon as I can connect to my device, because just for now it don't even respond to a ping ... After I need SSHD to do that, am I right ?
|
|
|
Post by omega on Feb 17, 2007 19:42:26 GMT 7
Yes, one way is to use ssh, login and check it. The easiest way might be that you send me the file Thecus sent you per PM and I check it myself... Andreas
|
|
mamat
New Member
Posts: 12
|
Post by mamat on Feb 17, 2007 21:12:53 GMT 7
Andreas, Yes PM me your email and I will send you the files
|
|
|
Post by kevincy on Feb 18, 2007 7:30:33 GMT 7
Andreas, Yes PM me your email and I will send you the files Hello Matthieu, Some question , What version display on LCM (click esc on LCM key pad) ? What network info in LCM ? Do you have try the reset button to reset network default?
|
|
mamat
New Member
Posts: 12
|
Post by mamat on Feb 19, 2007 23:23:49 GMT 7
Hi Kevincy,
when I press the 'esc' button it says "No HBT Log !! 01.02.c6" and I reset it, but I still can't connect to it ... the IP are WAN : 192.168.1.100 and LAN : 192.168.2.254
Everything is properly plugged, my network is working, there is no error message displayed on the thecus but it's not reachable from my browser at this IP ..
|
|
|
Post by omega on Feb 20, 2007 0:24:38 GMT 7
What IP address are you using on your computer and did you try both network ports?
How do you check if you can reach the computer? Using the ping command?
Andreas
|
|
tay
New Member
Posts: 4
|
Post by tay on Feb 20, 2007 7:42:09 GMT 7
Hi Kevincy, when I press the 'esc' button it says "No HBT Log !! 01.02.c6" and I reset it, but I still can't connect to it ... the IP are WAN : 192.168.1.100 and LAN : 192.168.2.254 Everything is properly plugged, my network is working, there is no error message displayed on the thecus but it's not reachable from my browser at this IP .. I had a similar problem on my 5200 whne I got it recently . What IP address are you using on your PC(s)? After the flash update it will reset all the network settings. Also using the wizard off the CD might allow you to get to the unit on a differant subnet and change the IP address assuming thats an issue. Just my 2 cents worth
|
|
mamat
New Member
Posts: 12
|
Post by mamat on Feb 20, 2007 17:11:56 GMT 7
Hi Andreas, Tay
I'm using the address 192.168.1.100 in my browser to connect to the thecus, I also tried to ping it with no result
But yes, all my other devices connected on my network have an IP like 192.168.0.X, so that could be the problem .. but I need to connect first to the thecus to change its IP ... and I tried the wizard CD but it cannot discover any device .. this is very strange
I will try to change my network subnet to match 192.168.1.X and see if it works
thanks, MAtthieu
|
|
|
Post by phylobates on Feb 20, 2007 18:03:52 GMT 7
Hi Mamat, Omega et Al
Last night I upgraded ( attempted ) our N5200 box firmware from 1.000.4 to 1.00.07 and oh woe is me! Descovering Thecus was enjoying a 2 week chinese new year holiday , I resorted to looking up my problem in google and it's will great relief I've found this forum.
To get to the point, I've got exactly the same issue as Mamat . With the logs reporting a upgrade C[3] fail after 5%, further upgrades failing. I was then unable to do anything useful via the web interface, and with the file sharing system automatically disabled for the firmware upgrade I was nowhere.
I tried a soft , then hard reset.. but the box stops at the self test phase of its startup.
I see Mamat has had success with the "factory_test.sh" sent from thecus. Do I take if I put the upgrade binary on a usb stick togeather with this file, insert into the box and reboot it will preform the firmware upgrade and make all my ( Nas related ) problems go away , without loosing my Raid data? That would be bliss...
Any help ( and a copy of the "factory_test.sh" ) file would be so much appreciated !
Many thanks.
|
|
mamat
New Member
Posts: 12
|
Post by mamat on Feb 20, 2007 18:26:27 GMT 7
IT WORKED !! I was not able to connect because of a different subnet .. thanks a lot to all of you for your great help phylobates : if you PM me your email address I will forward you the thecus support mail I received with the files that worked for me as it seems that we are having the same problem, so I hope it will work for you too !
|
|
tay
New Member
Posts: 4
|
Post by tay on Feb 21, 2007 0:17:12 GMT 7
IT WORKED !! I was not able to connect because of a different subnet .. thanks a lot to all of you for your great help phylobates : if you PM me your email address I will forward you the thecus support mail I received with the files that worked for me as it seems that we are having the same problem, so I hope it will work for you too ! Glad you got it going...although the wizard should have found it, but hey ho
|
|
tay
New Member
Posts: 4
|
Post by tay on Feb 21, 2007 0:23:01 GMT 7
Do I take if I put the upgrade binary on a usb stick together with this file, insert into the box and reboot it will preform the firmware upgrade and make all my ( Nas related ) problems go away , without loosing my Raid data? That would be bliss... Any help ( and a copy of the "factory_test.sh" ) file would be so much appreciated ! Basically the reason I had to use the factory script was that I had no web services running on my new 5200, the usb key with the script and firmware was all that was required to get my box seen on the network and the web services running, not to mention the firmware upgrade I likewise can forward you the details/script if you wish. Its simply this script file and the firmware on a USB stick and thats it. If your system is a live system then you take your life in your own hands as I had nothing to lose
|
|
|
Post by phylobates on Feb 21, 2007 17:34:45 GMT 7
Thanks to mamat and tay for the files, but unfortunately I did'nt get anywhere.
I followed the thecus instructions , set up a usb disk, copied the files inserted the usb and started the box.. the usb showed power, but did'nt flash to indicate file transfer and the box proceeded throuigh it's usual "booting".. then "Self Testing" where it stops. I did try different USB ports, different USB sticks, different USB formatting (FAT 16 / Fat 32 ).
I did read at the top of the PDF instructions that ver 1.00.04 onwards of the firmwhere implements a factory reset, by holding in the reset button on front panel. This I also tried , during booting , after booting, still no joy.
Have decided to give the thecus another chance ( I do like the little box ) , and have another N5200 on order for delivery tommorow. I will then attempt to swap out the disks from one to the other. I'm hoping the raid information is stored on the disk rather than the firmware. If that fails, I'll simply format and restore from a back-up. Resulting in a day or so's loss of data, but at least I'll be up and running again ! That is unless anyone has any other ideas...
|
|
|
Post by zaphoddt on Feb 21, 2007 19:44:54 GMT 7
Hi - I have just experienced almost the exact same problem.
My upgrade (1.03 -> 7) got to about 5%, then failed. I foolishly rebooted my N5200, only to find it appears to work perfectly, no errors on the LCD, all lights normal, but no shares available and cannot access through the browser. I can ping it though on the address I had it set to.
The setup wizard can find it and allows login and confirmation of IP address, but nothing more.
Any advice welcome...
|
|
|
Post by phylobates on Feb 23, 2007 17:17:56 GMT 7
Thought post an update to my situation...
I'd given up up on restoring the firmware and had ordered a replacment box, which turned up this morning.
I dutify reconfigured the network, DHCP, set the box to use active directory from our domain controller for the access control lists. I then shutdown , reinserted the drives removed from the previous box back (in the same order), held my breath, switched on and.........
... it booted up smoother than a cashmere codpiece. It recognised the raid array complete with hot spare, reasembled, all the folders complete with descriptions and ACL's set-up! As I had called it the same network name, our server picked it up as part of the distributed file share and it was instantly availible form the network as if nothing had happend.
There just is'nt a big enough smiley but I'll settle for this one ;D
|
|