Print

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

[albert]

My NAS is running the latest firmware, ie. 2.05b10

Recently I replaced drive 1 (right slot) with a brand new drive as the old one is running out of space. Everything run fine and I managed to transfer over 150GB of files from drive 2 over using the "My Files" apps.

Thing went bad when I decided to perform a scan disk on the new drive to verify if there is any bad sector. The process went through normally and fairly quickly which is kind of weird. I decided to do the same for the second drive since it was quite sometime I last did a scan. The scan process stuck at initializing phase and I abort it but when I check on the volume status, drive 1 seem to be initialize and all the files previously copied are gone! Restart NAS and got the same result. WTH went wrong!!

Anyone came across the this issue using this firmware version? I recall performing scan on version 2.05b08 without problem. My trust in this NAS is completely lost, I am currently waiting for a HDD docking unit to arrive so that I can perform recovery on the lost data. Damn sad. 

[FurryNutz]

I presume that if you install a new drive that checking for drive errors is not needed.

However, if one would want do this, the scan disk feature should be done before putting any data on the drive.

However it also odd that after you started it and seem to hang up that the data was erased during initialization. 

This seems to be something new you have experienced. Nobody else has reported this seems like.

[albert]

I disagreed with you. Newly purchase drive doesn't meant it is free of bad sector(s), doing a surface scan should be the first thing to do.

As for the scan disk feature, it should be able to done anytime, much like the chkdsk command in Windows, without fear of data lost. As mentioned earlier, I have done this many time in the past on older firmware without issue.

The hanging part is on the second drive, the first scan went through without problem but seem to complete rather quickly.

I presume that if you install a new drive that checking for drive errors is not needed.

However, if one would want do this, the scan disk feature should be done before putting any data on the drive.

However it also odd that after you started it and seem to hang up that the data was erased during initialization. 

This seems to be something new you have experienced. Nobody else has reported this seems like.

[FurryNutz]

Any status on this?

I disagreed with you. Newly purchase drive doesn't meant it is free of bad sector(s), doing a surface scan should be the first thing to do.

As for the scan disk feature, it should be able to done anytime, much like the chkdsk command in Windows, without fear of data lost. As mentioned earlier, I have done this many time in the past on older firmware without issue.

The hanging part is on the second drive, the first scan went through without problem but seem to complete rather quickly.

I presume that if you install a new drive that checking for drive errors is not needed.

However, if one would want do this, the scan disk feature should be done before putting any data on the drive.

However it also odd that after you started it and seem to hang up that the data was erased during initialization. 

This seems to be something new you have experienced. Nobody else has reported this seems like.

[albert]

What status are you referring to? If referring to data recovery, I managed to get back some but not with the right filename I was hoping for. I did not perform any more scan disk for fear of losing data, I took out the new drive and intend to use it on another NAS.

Anyway, I have already purchase a non D-Link NAS and slowing moving data over when I have the meant to purchase bigger capacity drive. As for the existing DNS-320, it will serve as spare storage device until it fail completely.

Any status on this?

[FurryNutz]

Good Luck.