Doubt at HP Proliant DL160 G5
-
@Lakshmana said:
When I added the new hard disk it does not join into the array and the arrayed was destroyed without doing anything.
Did you remove the failed one first?
-
If there is a hot spare it would already have started writing to it when the last drive died. You need to pull the dead drive and then insert the new. You might need to select it as a hot spare if it does not auto detect it as one.
-
@thecreativeone91 said:
If there is a hot spare it would already have started writing to it when the last drive died. You need to pull the dead drive and then insert the new. You might need to select it as a hot spare if it does not auto detect it as one.
I think you simply have to designate it for rebuild, if it does not start automatically, not as a spare of any sort.
-
@Lakshmana said:
the arrayed was destroyed without doing anything.How it was madde?
If you did something to destroy the array out side of specialize software there is very little recovery that can be done. Hopefully you have backups.
-
These threads really highlight why hardware RAID is important. Software RAID, while totally enterprise class (excluding Windows RAID and Fake RAID solutions and other obvious silly options) is confusing to people who do not specialize in the platform in question and leads to bad things happening. Even though the RAID itself is likely rock solid, that it is not a hardware SmartArray that pretty much forces you to only do the right thing, software RAID opens you up to a lot of disaster.
-
@scottalanmiller The server shows the error as SMART failure in the hard disk.I am having A and B which are old hard disk already connected in HP Proliant DL160 G5.I went to client place with the hard disk C.I went and inserted only C to the server and B in the server where the hard disk is already connected in the server.Then I booted the hard disk.Before going to array utility,it shows two hard disk C at 3.00Gb/s Data Rate and B at 1.5 Gb/s data rate.Then I went to array utility console and added the new hard disk from the Configure Disk option and went to manage array option and saw the two disk.The C hard disk is connected at 00 Port and B at 01 Port of the server.So the hard disk is not able to rebuild.So I deleted only the 00 Port that is new hard disk from the utility.And after that the user said he needs to take backup of data.So I connected A and B hard disk for taking backup.He took backup and after that I inserted C and B in their own places.But now the B hard disk shown as the hard disk to be added for building RAID1.But I didnot installed or rebuilded RAID 1 at new hard disk.So when I tried to boot the two hard disk,automatically Windows Server 2008 R2 installed in the server and after reboot of the server,there is no data present in the server?How this happened I cant understand why this happened?
-
I can't follow that exactly. But, the failed harddrive should always be remove first and the new one should be added in the same port as the failed one.
Also I would not recommend using windows raid at all. Linux is great for raids. Windows not so much.
-
@thecreativeone91 I connected the hard disk same port only but the RAID was not able to rebuild Why?
-
@Lakshmana said:
@thecreativeone91 I connected the hard disk same port only but the RAID was not able to rebuild Why?
You removed the failed drive, before doing anything? Then installed the new drive into the bay where the failed drive had been?
-
@Lakshmana said:
So when I tried to boot the two hard disk,automatically Windows Server 2008 R2 installed in the server and after reboot of the server,there is no data present in the server?How this happened I cant understand why this happened?
If you are using software RAID, it requires much expertise. Nothing will work easily. Only hardware RAID can make it really easy if you don't have an expert available.
-
I found a solution to this issue the server was without RAID and there is only one hard disk found installed with the server OS and other without Server OS which is to be installed with the server.Since this is my first server issue I found the server without RAID.
