I am trying to get my TS back up and running after a standard shutdown process. It did shutdown successfully, but never came back up. When it finally did come back up I got an E14 followed by an E04 kernel error. I can boot it into EM mode, but I can't get to the data using EM mode. The model number is HS-DH0.0TGL/R5 it is a 1TB TS. I have been on F/W 2.14.102 since it came out. The TS is configured as a RAID 5 array. I am getting an E04 Kernel error when trying to boot the TS. So far I have tried the forced update approach about 6 times. TSupdater.exe will copy the files and the TS reboots, then starts writing the F/W and then is followed by another reboot. This always ends in an E04 error. I have removed several HDD's one at a time and tried the restructuring route based on some forum posts. Now I am trying to get it up on TFTP using the Faq on this site.
I have the correct boot recovery file and I am connected machine to machine with a static IP of 192.168.11.1. To do this I disabled all NIC's except the controller for the ethernet cable, I currently have a static IP of 192.168.11.1 and a loopback 127.0.0.1, both seem to be listening on port 69 according to the TFTP Boot.exe. The TFTP Boot.exe opens up and is accepting requests using IP 192.168.11.150, but no connectivity is observed, no blocks served... I know I can get a connection because the NAS Navigator can find the TS and I can try a forced update using the TSupdater.exe and they both connect and communicate back and forth. All to no avail. Any tricks to getting this working? I have disabled the Firewall in Windows, tried opening a range of ports, but Since I am connected directly to the TS using a cable, I know the firewall on the router is not in the way. Is there anything I can do to get the TFTP working?
I have a couple linux boxes, Ubuntu. If I want to try to get the data off this array what would be the best option. At this point I would settle for the data, even if I have to rebuild the Array.
Thanks for any insight and help,
Pat
When you say
"I have removed several HDD's one at a time and tried the restructuring route based on some forum posts."
What do you mean? What process did you use and what happened?
Did you ever get it to boot without an E04 when you had a SINGLE HDD removed? If it E04's after the force update then you have a bad HDD, you just need to figure out which one and replace it.
I originally was getting an E14 Cannot Mount Array. That was when I tried removing drives. Once it shutdown I removed the #1HDD and rebooted. Let it start all the way and shutdown and reconnect the #1HDD and attempt to restructure. I went ahead and downloaded the latest F/W version, which I was already on.. 2.14.102. I forced the update, but could not get it into debug mode like the last time I did this in '08. None the less it does update the F/W and reboots itself and further installs the F/W and then finally reboots on the updated F/W and then fails with an E04 error.
Whats the best way to find the bad HDD, since it does not seem to point itself out?
No It never has booted successfully since I shut it down to move it.
Thanks for the reply,
Pat
When you removed drive one you got the E13 error? If so thats the bad drive. If you replace it with a new one you should be able to restructure the array.
Well, I was getting the E14 error before taking any drives out. That was my original problem, the E14, can't mount array. When I take a drive out I get a Bad HDD# error. The point being I would either identify the bad HDD or it would rebuild or restore the boot sector, etc..
So I had taken each drive out while booting and rebooting to see what errors I might get. Then I forced a F/W update and that is when I started getting the E04 Kernel error. I am able ot boot into EM mode, but can't get any array info
Try to boot it up normally with out drive one. If the unit actually boots up then drive one is bad. If it does not boot up, shut the unit down and replace drive and remove drive two. See if it boots up. If it does then drive 2 is bad. If it does not boot up then repeat the process with drives 3 + 4
Ok, I once again tried booting with the drives out one at a time. Starting with drive 1 and moving through drive 4, they all gave the same E16 HD# not found error. It did not start successfully with any drive out. Once the drives are all in it will boot into EM Mode automatically with no Array Info. So I assume it is not the drives themselves. I am still thinking it is the F/W and that it is not properly installed or there is another hardware issue.
Back to the original question. Why can't I get it to connect via TFTP? I have everything configured presumably correct. The TS is plugged directly into my windows laptop and I can connect using the TSupdater and the NasNavi. I can see the TFTP Boot.exe reports it is listening on the 192.168.11.1:69 static IP-Port. The TS has an IP of 192.168.11.150 and is on the same subnet. However, the TFTP Boot.exe just sits there with the "accepting Requests" message. I know the TCP stack sees the TS becuase as it boots up and shutsdown it connects and disconnects from the static IP. I have my Windows firewall off and no anti-virus software installed.
I have a USB HDD docking station off my Ubuntu laptop. I have Ubuntu configured to automatically find and mount USB mass storage devices, but these drives do not show up and I can't find the right mount command to get them mounted. I was hoping to at least get some insight into how I might retrieve at least the data off the array.
Any one.
"Back to the original question. Why can't I get it to connect via TFTP? I have everything configured presumably correct."
Because as you stated, it automatically boots into EM mode. The TFTP is only for units that WONT boot. Yours is booting. The TFTP helps units that arent booting boot into EM mode, so theres no point in you doing it.
Just try another firmware update. If that doesn't work try the force firmware update.
Thanks for the info, makes sense. I will keep trying the forced update method. Does anyone have an info on how to attempt data recovery using a linux machine.
I have done several forced updates and went through every known procedure so far to get my TS Live to boot successfully. Still getting an E04 Unable to load Kernel message.
What else could cause this situation. I also would like to find some info on using a Linux machine ot possibly recover some data. Anything is a big help.
Then most likely you have multiple HDD failure. I will see if I can get some documentation on the linux recovery.