Unsolved
This post is more than 5 years old
7 Posts
0
122380
August 5th, 2005 02:00
Failed drive / array won't rebuild
I have a dell poweredge 1600sc server running windows 2000 server. there are 2 seagate hard disks mirrored in RAID 1. A technician in the office restarted the server to eject the tape from its drive and discovered this beeping sound upon restarting. I suspect he powered off the server to quickly restart - no proof of that. The beeping sound led us to find the array had failed. The disk in bay 0 on controller 0 is now reading "failed". The disk in bay 1 is online.
I did a rebuild straight away but the rebuild completes and the disk still reads "failed". I powered down the server and inserted a new disk into it but the rebuild takes place and the disk still reads "failed". I read the previous failed disk on another machine and can see all contents and I feel this disk is not at all faulty.
What could be the problem now as I need to get the virtual disk out of the degraded state. The system is as PERC Subsystem 1 - CERC ATA100/4ch Controller 0
Any similar problems faced by anybody please help as I fear the second good disk that is currently working might go down again.
Thanks.
I did a rebuild straight away but the rebuild completes and the disk still reads "failed". I powered down the server and inserted a new disk into it but the rebuild takes place and the disk still reads "failed". I read the previous failed disk on another machine and can see all contents and I feel this disk is not at all faulty.
What could be the problem now as I need to get the virtual disk out of the degraded state. The system is as PERC Subsystem 1 - CERC ATA100/4ch Controller 0
Any similar problems faced by anybody please help as I fear the second good disk that is currently working might go down again.
Thanks.
0 events found
No Events found!


BGetchel
34 Posts
0
August 6th, 2005 20:00
Nasak
7 Posts
0
August 7th, 2005 20:00
BGetchel
34 Posts
0
August 8th, 2005 09:00
I don't think there's actual documentation on this, at least I've never seen it.
Yes, use the BIOS-level "CNTL-M" to do this.
However, not only has this happened to me with just about every RAID controller I've ever used, both SCSI and ATA (including my current PERC3/DC and PERC4/DC boards) that I've become very comfortable performing this function -- even though it seems very counterintuitive on the surface. Basically it's only happening at the controller level, not at the drive level. The controller THINKS you're deleting the array but the metadata written to the drive(s) remains intact, so when you define a new array (do NOT use EASY Config option -- use NEW Config) identical to the old one (select drives, Enter, F10, then be sure to choose same stripe size).. Just save the new array as you normally would only do NOT initialize the new array.
Once you do that it should work correctly. It's a fairly common solution, so it's not just me ;-)
If you're in/near Connecticut I might be able to help you out. You can email me.
pcmeiners
6 Operator
•
1.8K Posts
0
August 8th, 2005 11:00
Nasak
7 Posts
0
August 18th, 2005 02:00
After bringing up the server will the status of disk 0 be still failed until I perform a rebuild on this same disk0? I just want to be sure I understand what I will be about to do. Thanks heaps.
BGetchel
34 Posts
0
August 18th, 2005 12:00
It shouldn't rebuild at all, because you're deleting the array and creating a new one, so no "rebuild" should be involved -- it'll just think it's an entirely new array. Just make sure you don't initialize.
After you create the new array it *should* perform as it did prior to failure -- provided your hardware is functional.
Nasak
7 Posts
0
August 26th, 2005 08:00
I believe I have now created a new array.
Upon rebooting, I get this message:
" Windows 2000 could not strat because the following file is missing or corrupt
\WINNT\SYSTEM32\CONFIG\SYSTEMced
startup options for WINDOWS 2000, press F8
You can attempt to repair this file by starting Windows 2000 Setup using the original setup floppy disk or CD-ROM
Select 'r' at the first screen to start repair.
I am worried as when I insert the setup disk and choose 'r' for repair it says it cannot find a hard disk. Did I miss something on the new array creation steps to cuase this.
pcmeiners
6 Operator
•
1.8K Posts
0
August 26th, 2005 11:00
BGetchel
34 Posts
0
August 26th, 2005 11:00
Nasak
7 Posts
0
August 27th, 2005 09:00
"Setup did not find any hard disk drives installed in your computer - Make sure any hard disk drives are powered on and properly connected to your computer, and that any disk related hardware configuration is correct. This may involve running a manufacturer - supplied diagnostic or setup program. Setup cannot continue. To quit setup, press F3.
I suspect the registry hive is corrupt as per all the readings I have done - I need a solution to get to the recovery console. I'll point out that my ERD is not current.
Any help will be greatly appreciated. Thanks.
BGetchel
34 Posts
0
August 27th, 2005 14:00
When booting with the Win2k CD are you pressing "F6" to install the appropriate RAID controller driver first? If you don't it will not recognize any disks.
Nasak
7 Posts
0
August 28th, 2005 07:00
I suspect a total registry corruption.
I used Norton ghost on the 6th of August to ghost this working hard disk (disk to disk copy) of the array that was working but now cannot load windows. Will it be possible to restore registry files from the the ghosted disk?
Can I simply take this disk to another server and boot up to load windows and EXH2K or it is not as easy as it is in that with all the raid settings and all?
Suge
8 Posts
0
March 21st, 2013 17:00
Setup:
Dell PowerEdge 600sc
4GB RAM
Windows Server Ent 2K3
Drives: 2 - 80GB OS mirrored
Drives: 4 - 250GB Data RAID 5
RAID Controller: CERC ATA100/4ch RAID
I recently had one of the OS disk crash. My vender sent me a 160GB replacement. In the process of sync'ing the OS drives the RAID stated beeping
When I checked I was getting the error:
Configuration of NVRAM & drives mismatch (normal mismatch).
Checking the card documentation... it stated the problem as being:
The configuration stored on the RAID card does not match the configuration stored on the drives.
The documentation stated to do the following:
When prompted, press a key to run the BIOS Configuration Utility. Select Configure—> View/Add Configuration from the Management
Menu. Use View/Add Configuration to examine both the configuration in the non-volatile random access memory (NVRAM), and the configuration
stored on the hard drives. Resolve the problem by selecting one of the configurations.
After checking both places (NVRAM and config stored on drives)... I found the NVRAM had 1 data drive up (0) and 3 data drives failed (1, 2, & 3).
The config stored on the drive showed 2 data drives (0 & 1) up and 2 drives down (2 & 3).
I removed the RAID card and allowed the 2 OS drives to sync (reestablish the mirror)... they did so with no problems. However I still have the issue with
the RAID card... Any assistance would be helpful...
Thanks
Shug
Worked like a charm.... Thanks Brendan.... Life saver..