-
This is about a HS-DHGL-R5:
Here's the deal. I've had an issue with one of the drives in my NAS going out. I replaced it, rebuilt the RAID array and I had my data back within the day. Now, within a week or two my PC wouldn't connect to it. I was thinking it was another HD, but I took them out one by one and started the NAS inbetween. Each time it recognized that hard drive X was missing, so it's not them. Now I've noticed that It doesn't say "EM MODE" it says " HS-DHTGL-EMADD" then it goes to "EMERGENCY MODE NO ARRAY INFO."
Any suggestions here? I'm lost!
BTW,
Tried updating firmware, it won't connect.
Tried the TFTP Boot recovery, and it didn't receive anything from the NAS.
Also
THE NasNavi utility can see it. It even shows it's in EMADD, but this in the only inkling of a connection I can muster. Still can't see any of the files though.
-
Does the Navigator find it?
Probably going to have to do a force update of the Firmware, make sure you have to correct version for your model (2.14 is the latest for the info you provided). Force Update
Plug TS into your comp and Make sure firewalls are off (Windows and any antivirus firewall), set manual IP on your comp to match the Range of the TS. Maybe even boot into safemode with networking.
What operating system do you have?
-
I'm running Vista on the laptop I'm trying to repair the NAS with. I will try forcing it. I have tried, but not changed the IP of the computer.
-
Can anyone tell me what EMADD stands for?
-
OK well forcing it allowed firmware to be uploaded and it tried to update but didn't complete. Upon reboot it said "System Error E04. Can't Load Krnl". What now?
-
If Nas Navi is showing an Ip Address now you should be able to log into the user interface. Put the IP add. in the address bar of a web browser. If it logs in go to maintenance>initialization>restore. And it should clear that error message out.
-
I would reboot it again and see if you still get the E04 error. If you do you can try the TFTP procedure. If that doesn't work you need to find the bad HDD by shutting down the unit, removing disk one and then power it on. If it doesn't boot replace disk one and remove disk two ect. ect. As soon as it boots without one of the drives, you have found the drive that you need to replace.
Message Edited by PCPiranha on 06-29-2009 02:44 PM
-
You said that it didnt complete. What was the error message?
-
@ Josh. It was always showing an IP. I couldn't however login.
-
@ Josh again. The error was that it never rebooted. The error code on the screen was E04 Can't Load Kernel.
-
@ PCPiranha. I've done that before as explained in the first post. I'll try it again. No harm in giving it another shot.
-
OK, it;s been solved. Simply put, I finally got the firmware updated. Once it was updated to 2.14 I removed the HD's one by one again as suggested by PCPiranha. NOW it boots fine with HD2 missing, the HD I replaced. I'm guessing they sold me a faulty HD because it lasted all of 2 weeks. Anyway, I've restructured the RAID array and it is being rebuilt as I type this. Thanks to Josh and PCPiranha!
-
OK so it hasn't been solved. After rebuilding the RAID array it says "E14 Can't Load Raid Array." Ugh, what now?
-
It appears that the problem that caused the EM mode and E04 errors (most likely power irregularities) caused some corruption on the RAID as well. If you have the data backed up, a force update with the "Rebuild Partition Table" option will most likely get the device up and running again. This will remove all data, though.
As far as the data on the RAID is concerned, E14 means that there is some problem with either the RAID or the filesystem, making it unable to mount. If the data is important, I recommend contacting a data recovery center. We suggest Drivesavers (http://www.drivesaversdatarecovery.com/) for the RAID-capable devices.
-
Oof. No I don't have the data backed up elsewhere. The NAS in a RAID 5 setup WAS my backup. Is there any way to recover it myself. I ask because my NAS is in Panama with me now.
-
"The NAS in a RAID 5 setup WAS my backup."
RAID is not backup for data, that is a common misconception. RAID is protection against single HDD failure.
The options for recovering the data yourself are somewhat limited. You can try software programs that specialize in data recovery on RAID NAS devices (like UFS Explorer, costs around 50$ for the liscense) or you can try hooking up the drives to a computer that runs linux.
Message Edited by PCPiranha on 07-01-2009 07:21 PM
-
Any experience with UFS Explorer? It seems like a good do it yourself solution. http://www.ufsexplorer.com/products.php about halfway down the page they have the NAS section. Anyone have any experience with them for those of us who can't ship their NAS back to a data recovery center? I can only imagine what would happen to it here in Panama.
-
Fair enough. I won't use it for backup anymore. Thanks for the help.
I see we posted at the same time. Looks like UFS explorer is the route I'm going to take.
-
It is OK to use for backup, as long as you have it initially stored somewhere else. A multi level backup plan will solve any possibility of future data loss.
-
I experienced the same as this user with this drive model and fw version. However removing the drives one at a time did not change anything. The common thing between us is that tftp does not work, and neither does web admin when it is in this crippled state.
-
garciara, I replied to Your Thread.
-
Sir, the TFTP and removing the drives were the instructions for the E04 error. Are you getting EM mode or the E04? If it's EM mode you just need to flash the firmware. Make sure to disable all firewalls.