Print

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

[Absynthe]

I had a power failure yesterday morning.  I didn't think anything of it, just powered the drive up and let it run.  Today, I noticed there were files missing from some directories.  Not all the files, just some.

After I reboot the drive, some files ( not all ) showed up. After another reboot, they disappeared again.

I'm running RAID 1 using 2 Seagate 750GIG drives.
I've reset the box to factory defaults ( in part because I couldn't remember my password ).
I've changed the IP to be hardcoded so that in case of future power failures it always comes up the same so that devices mapped to it can still find it.
I have set no special permissions for users or groups, I'm just running this as one big drive and anyone on my home network can access everything.
I'm not running an FTP server, or iTunes or anything else. Just using this as a file server.

I don't see any disk management tools in the admin utility and my local disk management doesn't see the drive since it's mapped as a network drive.

Help?

[jamieburchell]

I don't know the answer but you could try upgrading to the latest firmware, which includes a "Scan disk" option in the tools?

[Absynthe]

Thank you for the suggestion.  Last night I upgraded to 1.07.  But I don't see a scandisk.  Where is that? Is it on the menu in the web interface options?

All I have under Tools is...
Admin Password
Time
System
Firmware
Email Alerts
Power Management
Raid
DDNS
Logout

[gunrunnerjohn]

I believe he's talking about the latest beta, links at the bottom of this page: http://forums.dlink.com/index.php?topic=5486.0

Release notes for 1.08b8: http://forums.dlink.com/index.php?topic=5485.0

[Absynthe]

Thank you.  I got the new firmware and applied it.  Ran scandisk and got a big old "FAILED".

It's a raid1.  How do I repair a raid 1 or figure out which drive is failing?

[gunrunnerjohn]

This may be a case where removing the drives and using a Linux system to read them is going to be the best option.

[Absynthe]

Oooh, hmm. That could be a problem.  I have no machines running Linux.

Since it's RAID1, which means the drives are mirrored, could I pull a drive out and stick it into a regular desktop and be able to read the drive? I've never repaired RAID1, but set up RAID1 exactly because I didn't want to lose data.

[fordem]

Oooh, hmm. That could be a problem.  I have no machines running Linux.

Since it's RAID1, which means the drives are mirrored, could I pull a drive out and stick it into a regular desktop and be able to read the drive? I've never repaired RAID1, but set up RAID1 exactly because I didn't want to lose data.

I guess you learned a valuable lesson then, too bad you had to learn it the hard way - RAID1 does not prevent a loss of data, what you really needed was to back the data up somewhere else.  RAID arrays are subject to data corruption, in pretty much the same fashion as any other storage would be, if the power fails during a write.  They also will not protect against data loss due to deletion (whether accidental or deliberate) or a virus attack, etc.

Putting a drive in a 'regular desktop' probably won't help, but, it's worth a try.  Assuming your 'regular desktop' is running Windows, it will not read these disks because they are formatted with the linux ext2 file system, you could try installing the ext2ifs file system driver which I have used sucessfully to "read data", but it has no repair utilities, so I have my doubts about it being able to read data that the DNS-323 itself won't read.

[Absynthe]

Well crap... kinda sucks to be me then I think.  Is there anything else I can do?  The disk isn't completely dead ( yet ). Is there a way I can pull the data down still?

[Georgio]

Stick the drive into your regular desktop PC and boot into linux using a live CD, such as Ubuntu. Then use e2fsck command to repair the file system.