Ran into a similar problem though caused by something else, verified that the drive marked as offline was actually valid by removing it and plugging it into a different machine via a External SATA dock. Then plugged it back into my machine, downloaded AMD RAIDXpert and was able to rebuild the array fine:D – RobV Apr 20 '13 at 19:50. I have a H710 array controller in a T320 server. Boot is set up as Raid 1 with 2 drives mirrored. Proper way to replace a failed drive on a H710 array controller I have a H710 array controller in a T320 server. Boot is set up as Raid 1 with 2 drives mirrored. If the drive is in and offline/failed state then you just need to pull it out.
Hi all, I have an Intel D975XBX2 with the Marvell 88SE61xx Raid controller installed.I have been using 4 Seagate ST3250410AS drives in a Raid10 array for over 3 years with no problems. These drive were all in a single VD (Virtual Disk) that was my 'D' drive. This all worked great under Windows XP Pro. It was finally time to upgrade to Windows 7 64bit Enterprise.
I got an new SATA Drive for C: and did a clean install expecting that I would not see my Raid10 Array until I installed new drivers after Windows 7 was up.At this point the Bios still showed that I had 1 VD defined with members 1,5,9,13 during the POST. I then downloaded the new Marvell drivers from the Intel website (STORAllOSMRUSetup1.2.0.7103PVMarvell). The install went fine and I was instructed to reboot. This time the Marvell message at post showed that I had 'NO Virutal Disks Defined'The Physical drives are still there but now called 0,4,8,12. In windows disk manager I can see all 4 drives 1 is Basic/Offline the other 3 are Unknown/Offline.I tried going back to my Windows XP system and have the same result.I made the bad assumption that since the Raid10 configuration was on the Motherboard that it would be preserved so I have parts of it backed up nut not all.
I has over 40000 pictures and MyDocuments on it so I really don't want to loose the data.I have looked at the BIOS utility, the MarvellMRU and the MarvellCLi read the manual and find no help. I tried to call Intel but the board is out of support as of Dec 2009 but they said to contact Marvell but they won't talk to an end user.What I really need to know is if the Marvell utilities are smart enough to see the defunct array on the Physical drives if I just create a new Virtual Disk? I have seen other Raid controllers do this. My next step is to try hooking up 4 different drives to the Marvell controller, define a VD and add the PD's and test access from window 7.
I will then delete the VD and them build again to see if it finds the old format. One other option is to use a bit-copy program to copy each of the drives from the failed array and try the recover on the copies.I would love to hear from others that have had a similar problem.Take CareK0IBM. Hi all, I have an Intel D975XBX2 with the Marvell 88SE61xx Raid controller installed.I have been using 4 Seagate ST3250410AS drives in a Raid10 array for over 3 years with no problems. These drive were all in a single VD (Virtual Disk) that was my 'D' drive. This all worked great under Windows XP Pro.
It was finally time to upgrade to Windows 7 64bit Enterprise. I got an new SATA Drive for C: and did a clean install expecting that I would not see my Raid10 Array until I installed new drivers after Windows 7 was up.At this point the Bios still showed that I had 1 VD defined with members 1,5,9,13 during the POST. I then downloaded the new Marvell drivers from the Intel website (STORAllOSMRUSetup1.2.0.7103PVMarvell). The install went fine and I was instructed to reboot. This time the Marvell message at post showed that I had 'NO Virutal Disks Defined'The Physical drives are still there but now called 0,4,8,12.
In windows disk manager I can see all 4 drives 1 is Basic/Offline the other 3 are Unknown/Offline.I tried going back to my Windows XP system and have the same result.I made the bad assumption that since the Raid10 configuration was on the Motherboard that it would be preserved so I have parts of it backed up nut not all. I has over 40000 pictures and MyDocuments on it so I really don't want to loose the data.I have looked at the BIOS utility, the MarvellMRU and the MarvellCLi read the manual and find no help.
I tried to call Intel but the board is out of support as of Dec 2009 but they said to contact Marvell but they won't talk to an end user.What I really need to know is if the Marvell utilities are smart enough to see the defunct array on the Physical drives if I just create a new Virtual Disk? I have seen other Raid controllers do this. My next step is to try hooking up 4 different drives to the Marvell controller, define a VD and add the PD's and test access from window 7. I will then delete the VD and them build again to see if it finds the old format.
Hello,I believe I am in that same small boat, (rubber liferaft?)Anyway it looks like the Marvel raid controller is runnning my CD/DVD drives and the Intel controller is now running the HD's. I am pretty sure that was not the case before.I cant seem to do anything with the Marvel MRU. CLI is just for Linux i know.Maybe inside BIOS If I delete the controller and reinstall will I still be able to load?
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun.
As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.or read our to learn how to use this site. I've had this PC for 10 weeks or so.
I ordered a new custom machine with 4 Disks (2 Pairs in RAID 1) for reliability and to avoid losing my system and data should one of my disks fail. The 1st array is for the OS and installed programs and the second array is for my data.Yesterday when I switched on my machine I got the message that the 1st array status was critical and it suggested that 1 disk was not responding or had failed. The screen went black and the machine would not boot.I had a look in the BIOS at the boot settings and found listed under boot devices the following:RAID array 2RAID array 3Single Disk 1So I selected Single Disk 1 as the boot device and the machine started up and I was able to get into Windows. Under Computer I could see the operational data array as D: but I could also see both disks from the failed array as C: and H. This suggests to me that neither of the disks has actually failed but that the RAID array has somehow become corrupted and needs to be rebuilt.In the BIOS/RAID setup options there is no option to rebuild an array and my motherboard manual also does not give information on rebuilding an array - only creating one in the first place.I called the company who I ordered the machine from as I got a free 3 year warrantee with the machine. They were very unhelpful and told me to search the internet for a fix! And I dont really want to have to ship my machine back to them as firstly it will take a long time and secondly I am sure they will wipe my OS and restore the machine to base which is exactly what I was trying to avoid in getting a machine with RAID 1 setup in the first place.
So I've been searching the internet without alot of success. What I did find was a program called AMD RAIDXpert. This has showed me that Drive on Port 1 is assigned to 'JBOD' which I believe means that is the disk I am booting to as 'Single Disk 1'. Drive on Port 3 is assigned to Raid 1 LD 1. Whilst both disks show up as having 150.03GB capacity, the disk on Raid 1 LD 1 has only assigned 149.97GB. The disk on JBOD has assigned the full 150.03GB. OK nobody has replied to me yet but I feel I am making some progress.
I found this posted on another problem regarding a very similar (exact same) problem to my own:STARTIssue: AMD RaidXpert Service gives an Raid 1 (or 5, as reported in other forum) array 'error' stating a single disk failure. One of the two drives (or may be more in your case, but if that's the case you are beyond screwed) in the Raid 1 array becomes a JBOD standalone drive, basically detached from the array for whatever reason. The drive is still listed as healthy and SMART scan does not show any issue either. It is simply 'assigned as JBOD' under 'Logical Drive View' in RaidXpert.OR, you really have a dead drive, and you have inserted a new drive. But even after you have initialized it, the Rebuild tab is still greyed out.The 'reasonable' procedure, by intuition, since there is no manual, is to start RaidXpert in the browser (username and password by default are both 'admin'), go to the 'Logical Drive View' and do a 'Rebuild'. The problem is, the 'Rebuild' tab is greyed out and unusable. You can only see the failed array listed as 'Critical', one of the two drives (in my case) is still mounted as part of the Raid 1 array, but the other drive is now JBOD.
This can also happen if the drive is new. It is simply 'assigned' as a JBOD. And the 'Rebuild' tab is still greyed out.You basically cannot rebuild.This problem has been reported on many forums and no one has provided a step-by-step solution. The AMD Help with the software is inaccurate and unhelpful.Solution: Make sure that you have boot into the remaining Raid 1 drive and NOT the JBOD drive if the array was your system drive. This can be double-checked by going into the BIOS during POST and you should make sure that in the Boot sequence you are booting through the Raid array. If the array is not your system drive, this precaution is not necessary.Start RaidXpert in Windows. After you have logged into RaidXpert, click 'Logical Drive View' under 'AMD RAIDXpert' - 'Logical Drive View'.
You can check the serial number of the working drive and the 'JBOD' drive under Physical Drive View, you will see which drive has been assigned to the array and which one is assigned as JBOD. If you are using the new drive, you should see that its serial number is associated with the JBOD assignment. Make a note of that, and make sure you are not replacing the wrong drive.Under 'Logical Drive View', and to the right of the screen you will see 'Delete' as a usable tab. Do not worry, nothing will happen yet.Under the 'Delete' tab, you will find check boxes next to each one of your array and JBOD drive.
Check the JBOD drive and click 'Submit'. You will see two warning messages telling you that the data in the JBOD disk will be erased. If this is your new drive, no problem, just hit 'Ok'. And the drive would disappear from the 'Logical Drive View'. If this was one of the two system drives, this is your last chance to make sure that this is not the drive you have booted into. If you are sure, hit 'Ok', and the drive would disappear from the 'Logical Drive View'.Once that's done, the Rebuild tab would appear.
You can also see under 'Physical Drive View' that this drive is no longer assigned, and is therefore 'Spare and free' and can be used for Rebuilding.Now hit 'Rebuild' and the process will begin. And you are set.END.Now that all makes sense to me but the bit I am having trouble with I have highlighted in bold. My PC will not boot if I select 'RAID array 2' as the boot drive and will only boot if I select 'Single Disk 1'.
So I am not sure if the disk I am booting into is the JBOD assigned disk or not. I think it is.
And that is a problem as that means if I delete the JBOD disk using RAIDXpert as instructed then I may very well wipe out my OS and no longer be able to boot up.I could prove this one way or the other if there is some way in windows to find the serial number of the disk I have booted into. Can anyone tell me how to find a Hard Drive serial number in Windows Vista for Drive C? Is it possible?.
I managed to fix my problem and rebuild my Raid array using the solution described above. The biggest problem I had was that I could not work out if I was booting into the Disk assigned to the Raid 1 array or assigned to JBOD. In the end I unplugged each drive individually and tried to boot into each. Only 1 would boot at all and that drive was assigned to Raid 1 in RaidXpert (but was listed as 'Single Disk 1' in BIOS) so I was pretty sure I was booting into the disk needed.
So I deleted the JBOD drive in RaidXpert as instructed and sure enough I was able to select rebuild and it was fixed in less than an hour.Hopefully this thread will help someone else with the same problem. Hi Folks - New to this BB so I am saying hi!However, I have a fix for the AMD RaidXpert issue which does not require you to delete your Raid setup.1) As posted, verify which drive is your data drive.
It should be pretty easy because it will be the only drive in your raid view. I fixed my problem using combination of Stephen W and Doubleram.both steps are correct.
I had to use combination of their steps to get around the drawback of ATI RaidXpert.ASUS M4A88T:1. I had 2 RAID1 drives that on a previous system had worked fine.2. I connected them together to a new system and the RAID Bios only showed RAID1 array as critical.3. Inside the RAID1 details page, it only listed one of the previous RAID drives, and the other as??????-Missing, although the other was connected.4. From the main RAID page, it did correctly detect the other drive, but did not show it as part of any JBOD or RAID.Now copying the steps from Doubleram:1) As posted, verify which drive is your data drive.
It should be pretty easy because it will be the only drive in your raid view. Or follow the instructions above to find the drive you have your data on.2) Reboot and go into your raid bios (-F) for my board but your's may differ.3) Now I'm going from memory - should have written it down.4) Go to Raid view I believe this is Number 1.5) you should see your raid drive and your single drive6) Define a new raid (don't remember which control sequence it is but, it's at the bottom of your screen)7) Your single drive should appear as the only drive available. Hello gals & guys, - I’m new here as well and I’d like to add some remarks to “DoubleRam’s” and “Stephen W’s” comments on how to rebuild a RAID array based on AMD’s SouthBridge chip sets: series 700, 800, 900.Firstly two comments on RAIDXpert in general:.
If the slightest data inconsistency occurs the RAID array will go instantly out of service (dis-arrays). This can happen any time and is the more likely the bigger the HDD is! It doesn’t necessarily mean that tone of the two HDDs went bad. It might be just a very seldom read/write error on one of the disks. So, before you discard the dropped HDD check it for errors (checkdisk) and first try to rebuild the array with the same disk!. The RAIDXpert manual provides no instruction at all on how to re-array a broken logical drive (LD). My very fast & system alive solution (AMD RaidXpert -web admin- should be installed):Confirmation part: We need to confirm the disk that will be deleted.
At web admin panel : Find the serial numbers of disks under Physical Drive View then find their port numbers. Match the pyscical disks and RAID/JBOD disks using port numbers. At PC case: Find the target disk from serial number.
Usually JBOD is the dropped RAID disk. Unplug the SATA cable. Test the files, OS, system stability.
If everything is OK re-plug the disk.Rebuild part:. Click Logical Drive View Delete and select JBOD at exact port. Confirm & Delete.That's it.
Now RAID is being rebuilt. Check the progress status at the Events.Edited by Nime, 23 January 2013 - 10:40 AM.