Thanks for the prompt reply. When I drill down into the Perc device and show the drive details in server Setup and Lifecycle Controller it shows type and size of the drives but not model & make information. But then it does this on all the drives I have even working ones. However I have found the issues - and you were partly right about the issue being the disks.
It turns out that these disks had previously been used in a Hitachi Vantara System and have had the firmware flashed/replaced. This causes weird problems as the controller will recognise the disks and can "use" them but will fail when it tries to write to them. I am being sent replacements for these drives.
In case anyone else has similar issues you can test this as follows, using the SeaChest utilities that can be downloaded from the Seagate website.
Run the following command to get details of the drive:
openSeaChest_Info -d /dev/sdc -i
This should return the correct model number, something like ST4000NM0023, and a firmware version, something like 0007 (you can check the expected firmware version on the Seagate website by entering the drive serial number here https://apps1.seagate.com/downloads/request.html).
If instead it returns a model number starting with DK and a firmware revision that does not start with a 0 then the firmware has been replaced - and the disk will not work in RAID (although may work standalone or as a single RAID0 disk).
Depending on what the disk is and what it has been flashed with it may be possible to download the disk firmware from the Seagate website and re-flash the drive back to the Seagate firmware (again use the link above to download the firmware and a flashing utility - make sure you are comfortable doing this and you understand the process or you risk bricking your disk).
Hi, this looks more like a non-certified drives issue. The drives are all the same and it seems they cannot communicate properly on the basis of fimrware. This causes strange behavior. When you look at the details of the drives via iDRAC or OMSA, how do they look, do details such as firmware versions and part numbers come out? Do the drives have a Dell P/N number on label them? non-Dell disks can cause problems. It may appear as a foreign disk due to a different virtual disk configuration when there was another RAID configuration before on the same drives. If this is happen after reseating drives, foreign import can also be tried.
Geoff Bland
3 Posts
0
May 24th, 2022 03:00
Erman,
Thanks for the prompt reply. When I drill down into the Perc device and show the drive details in server Setup and Lifecycle Controller it shows type and size of the drives but not model & make information. But then it does this on all the drives I have even working ones. However I have found the issues - and you were partly right about the issue being the disks.
It turns out that these disks had previously been used in a Hitachi Vantara System and have had the firmware flashed/replaced. This causes weird problems as the controller will recognise the disks and can "use" them but will fail when it tries to write to them. I am being sent replacements for these drives.
In case anyone else has similar issues you can test this as follows, using the SeaChest utilities that can be downloaded from the Seagate website.
Run the following command to get details of the drive:
This should return the correct model number, something like ST4000NM0023, and a firmware version, something like 0007 (you can check the expected firmware version on the Seagate website by entering the drive serial number here https://apps1.seagate.com/downloads/request.html).
If instead it returns a model number starting with DK and a firmware revision that does not start with a 0 then the firmware has been replaced - and the disk will not work in RAID (although may work standalone or as a single RAID0 disk).
Depending on what the disk is and what it has been flashed with it may be possible to download the disk firmware from the Seagate website and re-flash the drive back to the Seagate firmware (again use the link above to download the firmware and a flashing utility - make sure you are comfortable doing this and you understand the process or you risk bricking your disk).
Cheers
Geoff
DELL-Erman O
Moderator
•
3K Posts
1
May 23rd, 2022 06:00
Hi, this looks more like a non-certified drives issue. The drives are all the same and it seems they cannot communicate properly on the basis of fimrware. This causes strange behavior. When you look at the details of the drives via iDRAC or OMSA, how do they look, do details such as firmware versions and part numbers come out? Do the drives have a Dell P/N number on label them? non-Dell disks can cause problems. It may appear as a foreign disk due to a different virtual disk configuration when there was another RAID configuration before on the same drives. If this is happen after reseating drives, foreign import can also be tried.
Hope that helps!
DELL-Erman O
Moderator
•
3K Posts
0
May 24th, 2022 04:00
Hi Geoff, thanks for your detailed feedback. It'll be helpful for the rest of community.
Cheers,