Restructure Disk Array Question

[Proshooter]

   I have several 2TB Live units; HS-DH2.TGL/R5 firmware 2.14 on a small network using a gigabit router and a main workstation with Vista x64. After a complete power down to resolve an unrelated issue one of my "Buffalos" displayed an 04 error. I have reviewed the boards and understand that I may have to replace a drive as this is the second time this unit has done this. The last time I was walked through the recovery over the phone and the issue dissappeared until now, several months later. Through trial and error I was able to obtain a control screen through the IP. It indicated an array error and the next screen offered to "restructure the array" (or delete the array, which I would like to avoid as that is the whole point of the RAID5). It showed drive 2, 3 & 4 grayed out with checked boxes and drive 1 with the option to check the box before the restruture option was solid. Upon clicking the restructure command button I was warned that data may be lost and then cancelled the process. So, long lead up to short question; Is this the best way to recover the data on the array? That is will this process fix the problem, at least temorarily and allow me to move the data off the array? If so is it then Drive 1 that I should replace or is that just the drive that holds the array info? Thanks. 

Message Edited by Proshooter on 12-25-2008 12:25 PM

[Paul]

The  message means that it will format drive 1, then it will rebuild it with the other 3 drives (RAID 5).  That message is warring you that the drive your about to restructure will be wiped and built into the array.

[Proshooter]

   So even though all 4 drives have checks next to them, only the highlighted drive 1 will be formatted? Actually I have not been able to get back to that point, going around and around with the EM mode then rebooting, trying to get back there.

[Paul]

log into the IP of the device, go to disk management.  Then RAID set up, (some of the wording verys depending on what firmware your running) click on RAID array 1 then check the missing box and hit restructure.  Type in the code on the bottom of the page.

 

within 20 min (depending on how much data you have) you will be done and good to go.

 

 

[Proshooter]

   

Still not working.

While the TS unit was "loading kernel" I was able to access the drive management page via the IP. I went through the restructure process and the result indicated "successful", however the kernel never loaded, the unit went into EM mode again and appears no different. I also cannot access management through the IP after this (browser cannot find the IP -IE7), whether rebooting normally or while holding the reset button down while rebooting.

So here's my next trial; I am looking at backing up one of the other 2TB TS units to an external usb drive as described on the other thread. After that I am thinking of removing all 4 drives from that TS and inserting the 4 drives from the error prone unit. Is that likely to allow me to access the data on the problem drives? Will I still be able to swap all the drives back and not have any problems with the original set of drives in this "other" TS unit?

I am still trying to first recover the data on the problem TS unit, then secondarily find an on going solution such as replacing one or more of the drives.

Perhaps I would be better off just replacing "drive 1" with a new unformatted drive of the same model and capacity? My priority again is to recover the data over the operability of the TS unit. I have ordered a Seagate 1.5TB free agent to backup a 2TB TS unit and a couple of Samsung HD501LJ drives to replace bad drives in any of my 3 TS units as needed. Is BuffaloTech still preferring the Samsung drives as OEM or do you recommend another drive as a better replacement unit is these arrays? 

Thank you for your assistance and patience. 

 

[Matt_M]

Moving the drives over shouldn't cause any issues as long as that second TS is of the same line (IE: TS Live to TS Live and not TS Live to TS Pro or something similar). However, reading over this issue it seems to be a physical issue with that 1 disk, I would recommend simply replacing. However, if you want to be absolutely sure try the disk swap. If the problem follows the drives then it will confirm my suspicions on this and you will want to replace that problematic drive.