Ok now I've fixed it. I found a slightly newer version of the Perc firmware (2.8-1 (Bld 7692) and updated it. I then restarted with the faulty drive inserted and a dedicated spare (the 33.6Gb drive).
The re-build failed after 20 minutes or so and it immediately started re-building onto the spare.
To rebuild a raid volume the replacement disk must be the same size of bigger. So your new disk should have at least 34.18gb. As it is smaller it won't rebuild, even if there is free space. You may have to use a 73gb if you can't get the exact size.
Thanks for the advice but I thought that might be the case so this afternoon I tried a 73GB disk as well but it does exactly the same thing.
I have configured the 73GB drive as a hot spare but it won't seem to use it - the virtual disk shows 2 x disks on-line and the spare Ready but not in use.
I have a second identical server (same updates, drivers, etc) and when I run OMSA on that I get an option to re-configure virtual disks but that option is not available on the server with the faulty disk. Both servers are using OMSA 4.5.
remove it as a hot spare so that it's just 'ready' in OMSA right click on the drive and see what options you get. There may be an option to rebuild. If not pull the disk, wait a minute or so and re-insert it. Might force a rebuild. Also try the drive in a different slot.
Thanks for the advice - I have tried your suggestions but without success. OMSA now says that the array is degraded and has two 34G drives on line and one 73G drive 'ready'.
On all three drives the power leds flash every half second or so but there is no activity on the replacement drive. Any other suggestions to save a complete re-build.
TimR13
8 Posts
1
June 16th, 2009 02:00
Ok now I've fixed it. I found a slightly newer version of the Perc firmware (2.8-1 (Bld 7692) and updated it. I then restarted with the faulty drive inserted and a dedicated spare (the 33.6Gb drive).
The re-build failed after 20 minutes or so and it immediately started re-building onto the spare.
tommo666
3 Apprentice
•
1.2K Posts
0
June 12th, 2009 08:00
To rebuild a raid volume the replacement disk must be the same size of bigger. So your new disk should have at least 34.18gb. As it is smaller it won't rebuild, even if there is free space. You may have to use a 73gb if you can't get the exact size.
TimR13
8 Posts
0
June 12th, 2009 09:00
Thanks for the advice but I thought that might be the case so this afternoon I tried a 73GB disk as well but it does exactly the same thing.
I have configured the 73GB drive as a hot spare but it won't seem to use it - the virtual disk shows 2 x disks on-line and the spare Ready but not in use.
I have a second identical server (same updates, drivers, etc) and when I run OMSA on that I get an option to re-configure virtual disks but that option is not available on the server with the faulty disk. Both servers are using OMSA 4.5.
Any other ideas?
tommo666
3 Apprentice
•
1.2K Posts
0
June 13th, 2009 08:00
remove it as a hot spare so that it's just 'ready' in OMSA right click on the drive and see what options you get. There may be an option to rebuild. If not pull the disk, wait a minute or so and re-insert it. Might force a rebuild. Also try the drive in a different slot.
TimR13
8 Posts
0
June 15th, 2009 03:00
Thanks for the advice - I have tried your suggestions but without success. OMSA now says that the array is degraded and has two 34G drives on line and one 73G drive 'ready'.
On all three drives the power leds flash every half second or so but there is no activity on the replacement drive. Any other suggestions to save a complete re-build.
Thanks in advance