Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mvejvoda]

Ok I'm trying not to panic! I had a pair of Western Digital 1 TB drives setup as Raid 1 and all worked great. Recently took out the back drive (from the raid 1 config) to use in my sons computer while I ordered another Western digital 1 TB drive to replace in the DNS323. When i put it in, the webpage said it would format the new drive (yes I was VERY careful to write the new S/N of the new drive on paper so I knew what was going on). But the format of the new drive died 4-5 times at 94% (classic DNS323 problem). Now when I just want to get my main drive working on the dns323 it keeps asking me what config I want for my primary drive (which is the primary RAID 1 drive with all the data!). I placed this drive in another PC which runs Ubuntu 9.04 but Ubuntu doesn't seem to recognize this 900+ gig partition.. partition manager just says unknown! Is my data lost? What can I do to get a backup of the data? ANY HELP is greatly appreciated. I do beleive my data is most likely still on that drive but I have NO idea why the DNS323 doesn't just pick it up as the primary drive of my Raid 1 config as it has been doing all week!

By the way Linux shows 3 partitions on the RAID drive:

1 swap about 500MB
1 ext2 about 500MB
1 unknown about 930GB

Is there some special way (or driver or file system) to access the unknown


Thanks

[mvejvoda]

I think I'll start weeping right now

http://wiki.dns323.info/information:known_issues

I am a software engineer and I cannot believe that the dlink admin webpage told me it would format the OTHER harddrive and gave me its serial number but according to the link above it seems to go ahead and format the drive in the right hand bay! ARRRGGGG 500 gigs of data for the whole family lost! I'm not feeling so happy with Dlink anymore! If I get swindled by the software (being a programmer) how many others lose everything with this defect!

[mig]

how many others lose everything with this defect!

More than D-Link will ever admit. 

[mvejvoda]

This was the worst disaster I have had to date. Indeed all is lost (I tried all the data recovery tools and none could recover anything). I am stunned at how misleading the web ui was which lead me to this disaster! I took VERY CAREFUL note to ensure which hard-drive was being used for which action. The larger problem is that this defect seems to have been around for many firmware releases and NO MENTION from Dlink. Come on guys acknowledge it (forget about lawsuits, you're covered by the user agreements anyways) and fix the problem so that it is actually DOING WHAT IT SAYS IT WILL DO!

Now I start over from square 1 collecting data today having lost years of photos and code etc..

This was the ONLY problem I ever had with my Dlink and we use it heavily, it is an AWESOME device. Too bad we hear very little back from the team at DLink about such serious issues as basic functionality and total loss of data. I think it would serve DLink well to be open about these kinds of issues and gain the trust of the community and perhaps you'll have a golden product like the WRT54GL from LinkSys.

Anyways just my 2 cents.

P.S. the original defect (where it hangs at 94% for hours and hours) which caused this in the first place, is FIXED in 1.8 beta of the firmware, so BE SURE TO UPDATE if you are doing any hard-drive manipulation!

[ShMiCk]

This was the worst disaster I have had to date. Indeed all is lost (I tried all the data recovery tools and none could recover anything). I am stunned at how misleading the web ui was which lead me to this disaster! I took VERY CAREFUL note to ensure which hard-drive was being used for which action. The larger problem is that this defect seems to have been around for many firmware releases and NO MENTION from Dlink. Come on guys acknowledge it (forget about lawsuits, you're covered by the user agreements anyways) and fix the problem so that it is actually DOING WHAT IT SAYS IT WILL DO!

Now I start over from square 1 collecting data today having lost years of photos and code etc..

This was the ONLY problem I ever had with my Dlink and we use it heavily, it is an AWESOME device. Too bad we hear very little back from the team at DLink about such serious issues as basic functionality and total loss of data. I think it would serve DLink well to be open about these kinds of issues and gain the trust of the community and perhaps you'll have a golden product like the WRT54GL from LinkSys.

Anyways just my 2 cents.

P.S. the original defect (where it hangs at 94% for hours and hours) which caused this in the first place, is FIXED in 1.8 beta of the firmware, so BE SURE TO UPDATE if you are doing any hard-drive manipulation!

For someone that has just lost YEARS of data, you're pretty calm about the whole situation!

I want to update the firmware, but am in fear of having the same issue as you.

[fordem]

For someone that has just lost YEARS of data, you're pretty calm about the whole situation!

I want to update the firmware, but am in fear of having the same issue as you.

Nah - that's the hallmark of a true professional who has acknowleged that he was the one that screwed up - he made a concious choice to put his data at risk when he removed the first drive from the RAID array.  Sure the hardware didn't do what it should, but, even if it was 100% bug free, he could have had a disk failure and lost the data.

Yes - a firmware upgrade could cause a loss of data - it's not supposed to, but it can and does happen, so you can sit on the fence and dither or you can backup your data and then upgrade, or you can take the chance and upgrade without a backup - end of the day, it's your data, it's your responsibility.

There are two types of people - those who have lost data, and those who will