• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2994
  • Last Modified:

Adaptec Raid 1 Rebuild - 1210SA

Client has an Adaptec Raid 1 array with 2 x 80gb SATA Drive.  I believe the card is a 1210SA.

Drive 0 of the array failed and I shut the server down and rebooted back into windows hoping that the drive would automatically start rebuilding.  No such luck it seems.  in the Adatec Storage Manager the drive just says Ready, when I right click the only option is to Create Hot Spare.

From what I read now... the correct way is to initialize the drive through the raid bios then rebuild through the storage manager.  Since I installed the drive I left the premisis and am connected by remote access.  

Is there anything I can do to "initialize" the drive through windows to start the rebuild without going back up there and rebooting to the raid bios?

Thanks
0
Fluid_Imagery
Asked:
Fluid_Imagery
  • 8
  • 7
1 Solution
 
lnkevinCommented:
in the Adatec Storage Manager the drive just says Ready, when I right click the only option is to Create Hot Spare....

You are in the right track of rebuilding raid. With adaptec, you just get in Adaptec Storage Manager and right click on the drive and Create Hot Spare. Right after you create Hot Spare (or Hot Fix other name), your raid start rebuilding.

K
0
 
Fluid_ImageryAuthor Commented:
Is there somewhere it would say "rebuilding"  right now all it has is Port 0 - Hot spare   Port 1 - Optimal

Under Logical Devices - Data1 - Degraded

Don't see anything in the event log
0
 
lnkevinCommented:
Reboot your server and try it again. It should show you the status of rebuild.

K
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
lnkevinCommented:
There are three ways to replace a drive and rebuild RAID in adaptec. You can keep this guide for the future usage:

Manual rebuild using Array Configuration Utility
Shut down the system and replace the failed drive with a new one (of equal or greater capacity). Boot the system, press Ctrl + A to access the BIOS / Configuration Utility of the HostRAID controller. Select "Array Configuration Utility". From the Array Configuration Utility (ACU) menu select "Manage Arrays". From the List of Arrays, select the array you want to rebuild. Press Ctrl + R to rebuild. Wait for the rebuild to be finished.
Note: This procedure is not available with the Adaptec SATA RAID 1210SA.

Manual rebuild using Command Line Utility
Shut down the system and replace the failed drive with a new one (of equal or greater capacity). Boot into the operating system and start the Command Line Utility HRCONF. Use the HRCONF command "setstate" to rebuild the array.
See the Command Line Utility User's Guide or the HRCONF online help for further information.

Rebuild using Adaptec Storage Manager
Shut down the system and replace the failed drive with a new one (of equal or greater capacity). Boot into the operating system and start the Adaptec Storage Manager. Right click on the new drive and make it a Hot Spare. The rebuild process should start automatically shortly.

K
0
 
Fluid_ImageryAuthor Commented:
I'm at witts end with this raid controller.

I did what you sait to create the hot spare with the storage manager.  I tried rebooting once everyone left and it said No Operating System found... lovely message.  So I pull ed the cable on Drive 0 and it booted back into windows.  I shut the server back down and went into the Raid Bios and initialized the new drive I put in.  Still no option to "rebuild" the array in storage manager... only create hot spare.

I noticed a bunch of error messages in the event viewer for the windows services of the Storage Manager so I uninstalled it and put a new version on.  Previously the drives showed the same capacities.  But now with the new software it shows... New Drive  74.505gb  and System drive (Channel 1) 74.535gb.  The drivers are both 80gb drives, both WD but different model numbers.  

Would that be the reason why its not giving me the option to rebuild?   Can I use a 160gb that I have for the drive since I have those in stock and can try again tomorrow or should I order the same drive as what's in there?
0
 
Fluid_ImageryAuthor Commented:
I still can't get over how big of a piece of junk this controller is.

So I went up again today after picking up a larger hard drive at the office.  Put the drive in, initialized it through the raid bios and booted into windows.  There is no rebuild optoin through the controller bios which is also odd.

This time I right clicked the "Ready" drive and created the global hot spare which now says it's protecting the logical disk... yesterday with the 20mb smaller drive it said created hot spare but not protecting the logical disk.

Still nothing about the rebuilding anywhere... still can't right click and force the rebuild.  The command line you sent me above doesn't get recognized although I definately installed the CLI module.  So I left it as the hotspare and am calling the client back later to see if there is any update.  One thing I didn't try is to close the Storage Manger down and reopen it to see if any status got updated...

I don't know what else to try if this doesn't work  outside of pulling the server, taking an image of the drive... destroying the array completely and rebuilding it from scratch and reimage the box,  seems ridiculous to do that.

Any other ideas?
0
 
Fluid_ImageryAuthor Commented:
One thing I didn't mention is that I tried rebooting the server again with the hot spare enabled and the larger drive and it still didn't boot... said operating system not found.  Rebooted and reinitialized the drive and I got back into windows.  Maybe it's a bad controller?
0
 
lnkevinCommented:
I tried rebooting the server again with the hot spare enabled and ....

Why don't we try to stick with the procedure? We may just have to follow the steps to stick the disk in while the server is off and then create hot spare.... Read the following and try it again:

Shut down the system and replace the failed drive with a new one (of equal or greater capacity). Boot into the operating system and start the Adaptec Storage Manager. Right click on the new drive and make it a Hot Spare. The rebuild process should start automatically shortly.

K
0
 
Fluid_ImageryAuthor Commented:
That's what I did when I went there.  Should it say "rebuilding" or something of the sort.  It's been 2 hours and it's just sitting on  - Port 0 - Hot Spare


Screen shot attached.
0
 
Fluid_ImageryAuthor Commented:
didn't attach for some reason

http://scott.fluidimagery.com/1210sa.jpg
0
 
lnkevinCommented:
Here is another procedure from Adaptec. I noticed that we are missing a few last steps. Give it a try starting from step 5:

Please follow the steps below to rebuild your degraded RAID 1:

1. Determine the cause of the failure, i.e. loose cable, faulty drive, inadequate power

2. If necessary, replace the failed drive with another drive of the same or larger size

3. Initialize the replacement drive in the controller BIOS

4. Allow the system to boot the operating system and run Storage Manager Browser Edition (SMBE)
Note: Storage Manager Browser Edition is no longer the most current storage management software. Please visit our Support site to download the current release of Adaptec Storage Manager (ASM) management software for your controller.

5. Click on spare button and select the initialized drive as a spare to put a check mark on it. Select the degraded RAID 1 to put a check mark on it, then select done.

6. RAID 1 should begin rebuilding automatically at this point. If you don't see the rebuild process start, close storage management software and re-open it to refresh the view. It should then indicate the array is rebuilding.

Please make sure that the latest BIOS and driver for the controller is installed otherwise the rebuild process might not start automatically.

K
0
 
lnkevinCommented:
These are the keys we missing:

To assign a dedicated spare in SMBE,
click on the Spare button on the screen
click on the drive to be set as a spare
click on the array it will be dedicated to
click on the finish button to create the spare.
The array should start rebuilding to the new spare drive.

K

0
 
Fluid_ImageryAuthor Commented:
Those buttons are no longer in ASM, or maybe I'm missing something?

"Note: Storage Manager Browser Edition is no longer the most current storage management software. Please visit our Support site to download the current release of Adaptec Storage Manager (ASM) management software for your controller."
0
 
lnkevinCommented:
Can you run HW diag?

K
0
 
tdeliaCommented:
I have the exact same problem.
The system was reporting a degraded array, so I rebuilt the "bad" drive using ASM. After a reboot I get the 'No Operating System Found' error. When I boot with a Windows server CD and try to do a recovery console repair, I get an error. I also can't do a "dir" at the C prompt to see any files. For kicks I started the Windows install from CD (yes -- loaded F6 drivers), just to see if the installer would see the OS, but it's not seeing any partitions/installed OS. "Unpartitioned Space." Is it possible that the Adaptec controller rebuilt the array based on the bad drive instead of the good drive? Is there a way to restore/re-discover the MBR/partitions on the disk without wiping? I can't imagine that the data just disappeared -- nothing was "formatted." I've also tried disconnecting the bad drive and changing to non-raid mode in BIOS to get a good boot from one drive, but I get the same error. After re-enabling SATA RAID in BIOS, the controller sees the raid as if nothing is wrong, but still no OS.
0
 
Fluid_ImageryAuthor Commented:
Problem was with the Adaptec Card.  We've since upgraded them to a new RAID Card.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now