So I don't really know how to explain what happened. I put new drives in, had all those issues. I decided i'm going to update the SAS RAID drivers and Firmware, then the BIOS. After that i went in to fix the degraded RAID, when i got it, there was no issues, it said the drives were already part of the RAID, so that was freakin weird. I got out since there didn't seem to be anything left to do in there. I tried to get into OMSA, that seemed broken now, so then to make sure the RAID wasn't degraded anymore for real, I ran the firmware update on the two drives in the RAID array i couldn't upgrade because it was degraded and it worked fine. So problem fixed, not sure how, but it was a best case scenario.
I don't think that's possible, as the system will detect the drive as foreign container with backplane global ID, it will detect it as previous known RAID array. You may not be able to clear foreign, as it may cause data lost to the exist RAID10 array that you wanted to rebuild.
What I can think of is, to clear the foreign configuration and init the drive from another server if you do have one.
RAID 10 DB VD 4 drives(two drives died initially, but one came back to life and i upgraded f/w)
RAID 10 Temp VD 4 drives
RAID 10 Log VD 4 drives
Single non-RAID drive
All drives in RAID 10 were 300GB SSD SAS 12Gbps Sandisk LT0200MO Dell PN 2XR0K 12 drives total
RAID 1 is Seagate ST300MP0005
Tried multiple types of new drives, replacement drives I have are Toshiba HGST SSD 12Gbps SAS 800GB HUSMM3280ASS204 drives are showing in a ready state. I can still go through with adding them as a global hot spare(if i go to virtual drive and select assign hot spare the drives do not show up), however they never get rebuilt into the degraded RAID 10 DB virtual disk.
Basically, I just need to know, will this work if i do it in the Ctrl+R RAID config, screen(what to do there would be good to know for the H730P as it's my first time working with this model) and how long it will take as i'd like to keep downtime to a minimum.
So I tried using drives from another server and cleared the foreign config, however no matter what drive i use even new ones it doesn't allow me to use the drives as a hot spare. The virtual disk is only showing two drives in it now. If i go to add a hot spare the new drives don't show up. I get this message when assigning as global hot spare.
"This Physical disk is not suitable to protect all current or potential virtual disks on this controller. Possible reasons include: Insufficient physical disk space, unsupported mix of SAS and SATA type physical disks, unsupported mix of SSD and HDD type physical disks, unsupported mix of 512Bytes and 4KBytes sector size physical disks, unsupported mix of PI capable and incapable type disks and non-SED drive assigned as a GHS when encryption virtual disk is present. Continue with assigning as a global hot spare?"
One of the disks I'm trying to use is the exact same type of drive. I actually got a failed drive to come back up and upgraded the firmware, so now that one is good. However, that one doesn't show up as an option either. I should technically be able to do this without restarting and doing ctrl+r. Is that my only option now? I was wanting to avoid downtime.
I doubt this will be any different from the CTRL-R menu.
You assign a Global Hot Spare from the Physical Disks menu. Your SSD's are NOT compatible as a hot-spare for an array made up of HDD, so you will ALWAYS get that message when assigning a Global Hot Spare.
You can assign a Dedicated Hot Spare from the Virtual Disks menu. It probably will not let you assign it to a VD that contains disks incompatible with the one you are assigning (for example, you cannot mix SSD and HDD, SAS and SATA, or 4kn and 512x formatted drives). HGST specifications are hard to come by these days, but you might check to see if the drives have the same sector size (512 vs 4k). Since the controller can't mix the two formats, if the Sandisk and HGST drives are different, then they would not meet the compatibility requirements of a Hot Spare. Otherwise, they seem to meet the requirements (both are SSD and both are SAS and the new ones are the same size or larger). The other possibility is if one or the other is not a Dell-certified drive - it's possible that the programming just doesn't match for the controller to integrate them.
Everything is the same all drives SSD, all drives 512 and SAS. However, oddly enough, one of the drives in the RAID 10 array that is degraded is saying it's an HDD even though it is clearly not. It's the same exact drive as the other drive in the array yet it's showing it as an HDD. I'm going to upgrade the PERC H730P firmware before i reboot and see if I can do it from the Ctrl+R screen. If that doesn't work, then I guess my only option would be to create a new RAID 10, move all the DB files from the degraded array to the new RAID 10 array. It's still kicking which was my main concern as this is the 40,000 hour of operation bug.
Thanks for letting me know that the problem that you had was fixed. The reboot did the work where the drives did not kick in as a hot spare to rebuild the RAID array. There are certain time where a reboot is all it needed for the rebuild to occur.
narfman14
5 Posts
0
October 19th, 2020 17:00
So I don't really know how to explain what happened. I put new drives in, had all those issues. I decided i'm going to update the SAS RAID drivers and Firmware, then the BIOS. After that i went in to fix the degraded RAID, when i got it, there was no issues, it said the drives were already part of the RAID, so that was freakin weird. I got out since there didn't seem to be anything left to do in there. I tried to get into OMSA, that seemed broken now, so then to make sure the RAID wasn't degraded anymore for real, I ran the firmware update on the two drives in the RAID array i couldn't upgrade because it was degraded and it worked fine. So problem fixed, not sure how, but it was a best case scenario.
DELL-Joey C
Moderator
•
4.1K Posts
0
October 15th, 2020 21:00
Hi,
I don't think that's possible, as the system will detect the drive as foreign container with backplane global ID, it will detect it as previous known RAID array. You may not be able to clear foreign, as it may cause data lost to the exist RAID10 array that you wanted to rebuild.
What I can think of is, to clear the foreign configuration and init the drive from another server if you do have one.
Let me know your thoughts.
narfman14
5 Posts
0
October 19th, 2020 09:00
4 virtual disks,
Raid 1 OS VD
RAID 10 DB VD 4 drives(two drives died initially, but one came back to life and i upgraded f/w)
RAID 10 Temp VD 4 drives
RAID 10 Log VD 4 drives
Single non-RAID drive
All drives in RAID 10 were 300GB SSD SAS 12Gbps Sandisk LT0200MO Dell PN 2XR0K 12 drives total
RAID 1 is Seagate ST300MP0005
Tried multiple types of new drives, replacement drives I have are Toshiba HGST SSD 12Gbps SAS 800GB HUSMM3280ASS204 drives are showing in a ready state. I can still go through with adding them as a global hot spare(if i go to virtual drive and select assign hot spare the drives do not show up), however they never get rebuilt into the degraded RAID 10 DB virtual disk.
Basically, I just need to know, will this work if i do it in the Ctrl+R RAID config, screen(what to do there would be good to know for the H730P as it's my first time working with this model) and how long it will take as i'd like to keep downtime to a minimum.
theflash1932
9 Legend
•
16.3K Posts
0
October 19th, 2020 09:00
How many drives are in the system?
How many Virtual Disks are configured on the server?
What make and model are ALL the drives in the server?
Despite the message, does it allow you to assign the hot-spare anyway?
narfman14
5 Posts
0
October 19th, 2020 09:00
So I tried using drives from another server and cleared the foreign config, however no matter what drive i use even new ones it doesn't allow me to use the drives as a hot spare. The virtual disk is only showing two drives in it now. If i go to add a hot spare the new drives don't show up. I get this message when assigning as global hot spare.
"This Physical disk is not suitable to protect all current or potential virtual disks on this controller. Possible reasons include: Insufficient physical disk space, unsupported mix of SAS and SATA type physical disks, unsupported mix of SSD and HDD type physical disks, unsupported mix of 512Bytes and 4KBytes sector size physical disks, unsupported mix of PI capable and incapable type disks and non-SED drive assigned as a GHS when encryption virtual disk is present. Continue with assigning as a global hot spare?"
One of the disks I'm trying to use is the exact same type of drive. I actually got a failed drive to come back up and upgraded the firmware, so now that one is good. However, that one doesn't show up as an option either. I should technically be able to do this without restarting and doing ctrl+r. Is that my only option now? I was wanting to avoid downtime.
theflash1932
9 Legend
•
16.3K Posts
0
October 19th, 2020 13:00
I doubt this will be any different from the CTRL-R menu.
You assign a Global Hot Spare from the Physical Disks menu. Your SSD's are NOT compatible as a hot-spare for an array made up of HDD, so you will ALWAYS get that message when assigning a Global Hot Spare.
You can assign a Dedicated Hot Spare from the Virtual Disks menu. It probably will not let you assign it to a VD that contains disks incompatible with the one you are assigning (for example, you cannot mix SSD and HDD, SAS and SATA, or 4kn and 512x formatted drives). HGST specifications are hard to come by these days, but you might check to see if the drives have the same sector size (512 vs 4k). Since the controller can't mix the two formats, if the Sandisk and HGST drives are different, then they would not meet the compatibility requirements of a Hot Spare. Otherwise, they seem to meet the requirements (both are SSD and both are SAS and the new ones are the same size or larger). The other possibility is if one or the other is not a Dell-certified drive - it's possible that the programming just doesn't match for the controller to integrate them.
narfman14
5 Posts
0
October 19th, 2020 14:00
Everything is the same all drives SSD, all drives 512 and SAS. However, oddly enough, one of the drives in the RAID 10 array that is degraded is saying it's an HDD even though it is clearly not. It's the same exact drive as the other drive in the array yet it's showing it as an HDD. I'm going to upgrade the PERC H730P firmware before i reboot and see if I can do it from the Ctrl+R screen. If that doesn't work, then I guess my only option would be to create a new RAID 10, move all the DB files from the degraded array to the new RAID 10 array. It's still kicking which was my main concern as this is the 40,000 hour of operation bug.
DELL-Joey C
Moderator
•
4.1K Posts
1
October 20th, 2020 02:00
Hi,
Thanks for letting me know that the problem that you had was fixed. The reboot did the work where the drives did not kick in as a hot spare to rebuild the RAID array. There are certain time where a reboot is all it needed for the rebuild to occur.
Let me know if you have any other issues.
JoelPichette
1 Message
0
April 4th, 2021 18:00
Is it because the drives have added 1 hour to their clock to 40,001 hours while you were messing in the bios?