- #Hp smart array controller software software
- #Hp smart array controller software license
- #Hp smart array controller software windows
what I learned tells me the level of "interference" on the part of the Smart Array is minimal. The Smart Array will only play nice if you let it administer the raw disks. Leaving disks "Unconfigured" or otherwise not a member of an array prevented them from being shown to the O/S. One other thing, I found no way to enable a true "Pass-Through" on this Smart Array. So, some more evidence that the HP Raid cards store all the array info on the drives themselves, not the card. No going into the configuration menu or other intervention needed, the P410 recognized the Raid 5 array and immediately made it available, upon boot-up! I though that was quite nice. Note: I have also had good success running a Raid 5 on the P410, Originally, I created it on a P400, then decided to swap it out for a P410. However, if you're careful and you don't initialize or erase, you can often get your drive back to working well by using a nice little tool such as "TestDisk". So, there seems to be a way to get the job done here, you just have to be aware that the Smart Array (and many other controllers from what I've read) will over-write a bit of data on any disk you decide to set up as a RAID array of any sort. Then you tell TestDisk to "Write" the info back to the disk, reboot the computer, and voila! Back to happy-land. You can use the "P: List Files" to se ethat those files are indeed there. Use the excellent "TestDisk" utility, you can select the physical disk, tell it you had an Intel partition, and after a quick search, it should find your missing information.
#Hp smart array controller software windows
if you try to take this drive out of the Smart Array and go back into a regular motherboard port, Windows Disk Management shows it as "Unallocated". The Smart Array controller overwrites some data at the beginning of the disk and. Seems the P410 knows we want JBOD but refuses to give it to us! That's rather frustrating. You will notice, if you check the "Physical Device" info in Smart Storage Administrator there is an item in the list which reads: "Exposed To OS: No". Lo and behold, my data is all there, nice! So, after doing this, Windows immediately pops up the new drive. I then configured it with the HP "Smart Storage Administrator" (A Windows Utility) as a "Single Disk Raid 0" as others have commented. I took a working 320GB SATA disk which I had loaded files onto, and plugged it into a port on the HP P410 controller. please chime in, anybody, if you have some additional info. Right now, I am not sure if this "Feature" is what get enabled when you add the RAM and Battery/SuperCapacitor to the card - I am thinking it is.
#Hp smart array controller software license
This "Advanced Pack" license enables Raid 6 and 60, and other "Advanced Settings". I also found it came loaded with a "Feature License", which is called "Advanced Pack 01". It came with 512MB of RAM, "Flash" backed, with "SuperCapacitor". I have a P410 controller bought off ebay. Here is my personal experience with a HP Smart Array P410 RAID Controller: The P400 auto-config may have killed anything on the disks anyway, by creating a RAID-5 without asking permission.Saving the RAID-0 config (or any other P400 config) will empty the disk(s).You need to create RAID-0 configs to get the disks through to the OS.The P400 does not pass unassigned disks to the OS.I had to create 6 RAID-0 disks, and they appeared - all empty, however. Back at the P400 equipped machine, I deleted the unwanted RAID-5, the disks didn't appear at the OS level. I brought the disks back to the original machine, but the RAID had already been corrupted, the OS saw 6 empty disks now.ĭamage already done, I played with the disks a little bit. In my case, however, the P400 did recognize the disks as new and - without seeking my confirmation - it did auto-create a RAID-5 array at the controller level as soon as I powered up the computer.
#Hp smart array controller software software
The target machine didn't have enough SATA ports, so I thought, well, no problem, it is a SOFTWARE RAID anyway, why not attach the disks to a P400, the disks would - if the controller behaved like stated - appear as JBOD, and the OS would - like it had done many times before when I moved software RAIDs from one machine to another - recognize the RAID. They had always been part of a software RAID, the RAID functionality of the ICH9 "Fake" RAID controller had never been used anyway. I learned this the hard way today when trying to bring over a 6 disc software RAID-5 from a machine with a faulty 6 channel SATA RAID controller. There may be other controllers behaving like LapTop006 said, the P400 does not, at least not with the original firmware (V2.75). It should also be noted, just because I just killed 7TB of data by following LapTop006's, well, lets call it "personal opinion", that a P400 Controller would expose unassigned disks as JBOD, that this is nothing but a guess, and it is false, at least for my P400.
0 kommentar(er)
