Print

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

[Tullaian]

I had a drive failure in my DNS-323 this week setup in RAID1. Removed the old faulty HDD, put in a new one , it was recognised, formatted the new drive then commenced rebuilding the array. It started with an estimate of 11,000 minutes or 183 hours which is 7.6 days.

The array was 750GB of which only at the time ~ 200GB was used. Is it really possible for a resync of 200GB to require 8 days? Or is this a sign that something else is funamentally wrong here ?

In the meantime I can't map the degraded array anymore when I was able to when the drive originally failed. The system reconises both drives, recognises the array is being rebuilt so it all appears fine other than the fact it will need more than a week to be ready to use again.

Erk ?

[fordem]

The RAID rebuild time is an estimate that takes into consideration "current usage" of the NAS - if you reduce that usage, by disabling unneccesary services (itunes, etc.) and not accessing the storage, the rebuild time should decrease.

[Tullaian]

You were correct, it was done in the moning so some amount of time less than  8 hours. Quite alarming to see that message pop up for 8 days.

The array has rebuilt itself and all appears to be fine except for the fact that I cannot map the drive at all now. I'm running W7/64 and I can see the device and connect to it via the web, I can ping it but none of the existing network maps reconnected when it fired up. When I deleted them and remapped either via Windows Explorer or via Easy Share they all fail to map as well.

I was finally able to map it via IP address after some messing around but it seems very slow now using for instance the printer sharing. There is obviously something wrong with connectivity to the device but can't for the life of me work out what it might be. Is there some setting I need to reset somewhere after a rebuild of an array that has anything to do with connectivity? Or is there a setting on the desktop machines that needs to be flushed? Doesn't seem to make sense that I can see the device in explorer but can't map it, but can map it with an IP address. I didn't change anything on the network at all other than taking one drive out, putting a new drive in.

Ideas?

[fordem]

Mapping by hostname is not particularly reliable in a mixed linux/windows environment (the DNS-323 uses linux as it's OS), unless you have a name server installed to handle the name resolution that is required.

Your options are to ...

a - install a name server.
b - edit the hosts file on each windows system so windows will handle name resolution.
c - map the drive using the ip address.

Option c is the easiest approach.