NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Shardstrat
Mar 19, 2014Aspirant
I/O errors, unspecified disk
Two questions: 1) I've been getting error messages that say "Access to the disk on channel (??) is producing I/O errors. Although the array is still redundant, please replace this drive as soon as p...
Shardstrat
Mar 27, 2014Aspirant
Update: Tech Support responded and said that Disks 3 and 4 had bad sectors. They told me to clone at least one of the disks and then boot up up using three disks. I cloned Disk 3 and replaced it with the cloned drive, and when I booted up I received a message saying "C:\ 0/0 GB available", then "Volume C:\ is dead", then "C:\ 1/1 GB available". Frontview shows disks 2 and 3 as containing data, but Disk 1 as containing no data. I'm currently waiting for Tech Support to call back.
____________________________
Update: Tech Support told me to boot into Debug mode and wait for instructions. Two days later, Level 3 Tech Support sent me an e-mail telling me to do what I've already done - clone a disk, replace the defective drive with the cloned one, and try to boot. They also told me to open Port 23 on the NAS. However, since I've been in Debug Mode all this time, they already have access to the NAS via telnet. A call to Level 2 support confirmed this. Now I am waiting for another response from Level 3 support, who seem unaware of the history of the case or of the fact that the NAS is available to them via telnet and has been for the past three days.
Meanwhile I have cloned Disk 4, which was obviously the most defective one. In fact Disk 3 showed a total of only four errors during the cloning process (I can post the output). I was able to clone Disk 4 up to 66% using dd_rescue before reaching a point at which no more data was being copied, and then in the reverse direction up to the 36% level. So theoretically most of the data have been cloned.
My questions are:
- Could booting the NAS while holding in the reset button, as I was told to do, have been responsible for making the data on Drive 1 inaccessible?
- If not, why is Disk 1 showing no data?
- Can the data be recovered from Disk 2 and the clones of Disks 3 and 4?
____________________________
Update: Tech Support told me to boot into Debug mode and wait for instructions. Two days later, Level 3 Tech Support sent me an e-mail telling me to do what I've already done - clone a disk, replace the defective drive with the cloned one, and try to boot. They also told me to open Port 23 on the NAS. However, since I've been in Debug Mode all this time, they already have access to the NAS via telnet. A call to Level 2 support confirmed this. Now I am waiting for another response from Level 3 support, who seem unaware of the history of the case or of the fact that the NAS is available to them via telnet and has been for the past three days.
Meanwhile I have cloned Disk 4, which was obviously the most defective one. In fact Disk 3 showed a total of only four errors during the cloning process (I can post the output). I was able to clone Disk 4 up to 66% using dd_rescue before reaching a point at which no more data was being copied, and then in the reverse direction up to the 36% level. So theoretically most of the data have been cloned.
My questions are:
- Could booting the NAS while holding in the reset button, as I was told to do, have been responsible for making the data on Drive 1 inaccessible?
- If not, why is Disk 1 showing no data?
- Can the data be recovered from Disk 2 and the clones of Disks 3 and 4?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!