Unsupported SC420 does not recognise X7NC4

I have the ST2400MM0159 (2.4TB 10K SAS) in my SC420 on my SC5020s.

Some thoughts:

1. The X7NC4  is a 4K and not 512bytes per Sector Disks so you may need a rescent SCOS Version.  My 5020 was a DIP and IIRC i imaged the System with 7.3.x . So if you have something older this may the reason
2. If you buy some kind of "used" disks the Question is was the Disk erased or are old data on that disks.  Do you buy from Dell and only the SC420 is refurbished or does the Disks comes from 3rd. Party?

If you have Support left on the unti you should remove the SC420 and perform an SCOS Upgrade to 7.4.x together with Dell. After that add the 420 again and see if something changed.

Regards,
Joerg

Thank you for the quick reply!

Despite the drives being Enterprise Plus, the SC system is recognizing them as Enterprise Value, just wanted to add this to my query, if it helps.

Thank you for your response!

We've tried the OS upgrade to 7.4x still no luck with X7NC4. Guessing your 2nd point is the reason in my case.

The part no. you gave for ST2400MM0159  is RWR8F. Can you confirm if this drive is compatible with the SC420/SC5020 and if that comes with the caddy?

If it is working, I can arrange a replacement from the 3rd party I bought these drives from.

@Origin3k 

Hello Karan K,

Dell part# RWR8F is not a compellent drive.  The issue that you are having is that the drive doesn’t have compellent firmware on it.  That is the reason that you are getting the error of unsupported drive.  Compellent drives have a base firmware on them that is excepted for compellent systems.  There is not a way for a customer to force flash the base compellent firmware on a drive so that it can be read by the system.  You will need to get a true compellent drive that is read by the system.

Hello All,

We've recieved replacement drives. When Inserted it automatically created a new folder under assigned folder but unable to release or add it to the pool. When removed an re-insterted after changing the default setting to unassigned, the drives just showed up a status of "Down". Would that mean the drive had failed? It shows as SF79 on the drives firmware which seems accurate. The Part no. for the new disk is: X7NC4

Hello Karan K,

You can’t reinsert a drive in a compellent system as the serial# of the drive will be marked as bad.  The only way to resolve this is to call into support to resolve.

Hello All,
Were you able to resolve the problem? If so, how did you do it?

Hi, having the same issue with some 1.2TB drives, EnterprisePlus line, which are not recognized by the SC. 

Already tried "disk set <disk_index> 120 EnterprisePlus -systemwriteonly". The command doesn't return any errors or warnings, but the drives still remain down. Tried "disk unclobber <index>", with no effects....

Running 7.5.10.12 (I think it's the latest for SC4020). 

Has anyone managed to move forward with these errors?

Hello,

Could you post an image of the drive label for me to check validation for SC4020?

Thank you Charles. Sure, please see below. I've attached a picture with the "good" drive and with the "bad" drive. They are both the same P/N, they run the same firmware FE40. 

Also, I've attached "disk get" for both drives (I've deleted some lines so that I get within 10k characters). Setting the DriveLine with disk set didn't work. SCOS didn't update the firmware on the drives. 

So "disk get" are as follows:

HDD 1:

 2 Name 0
 3 ManagementDiscipline 1 (0) Unassigned
 82 DesiredManagementDiscipline 1 (0) Unassigned
 7 OperStatus 1 (1) Up
 6 AdminStatus 1 (1) Enable
 79 OperMode 1 (2) Normal
 29 Health 1 Healthy
 21 ParentFolder 1 1
 159 AutoManageAction 1 (1) Eligible
 160 AutoManageStatus 1 (1) Unknown
 122 LicenseStatusEvaluated 1 (1) Licensed
 123 LicenseStatusForced 1 (0) Unknown
 30 ScsiDevice 4 2326945472
 25 UniqueHWID 11 0301005000cca02d66e768
 41 VendorID 8 DELL
 42 ProductID 16 HUC101812CSS204
 43 SerialNumber 8 06HULDDB
 93 JBODIndex 1 1
 94 JBODDiskIndex 1 15
 95 JBODShelfID 1 0
 96 JBODDiskPosition 1 14
 106 JBODDrawerIndex 1 0
 107 JBODRowIndex 1 0
 105 SpinRate 2 10000
 163 SpinRateOverride 1 0
 119 SwimLane 1 0
 120 DriveLine 1 (2) EnterprisePlus
 121 DellPPID 25 TH01T8KWHGT0072M0M4QA00
 28 ClassIndex 1 2
 56 AssociationIndex 1 111
 80 HasContainedUserData 1 (0) False
 152 ConfigQualityScore 2 0x0000BEB5
 150 OverrideConfigQualityScore 1 0x00000000
 149 OutstandingRemoveRequests 1 0
 151 ForceConfigPlacement 1 TestOnlyAllow|TestOnlyDesireStrong|TestOnlyDesireWeak|TestOnlyEncourage|ProductionDefault
 166 ReadAvoidAdminStatus 1 (2) Disable
 165 ReadAvoidIndicator 1
 71 MediumErrors 1 0
 72 PossibleMediumErrors 1 0
 132 ProtectionInformati"margin: 0;">HDD 2:

 2 Name 0
 3 ManagementDiscipline 1 (0) Unassigned
 82 DesiredManagementDiscipline 1 (0) Unassigned
 7 OperStatus 1 (2) Down
 6 AdminStatus 1 (1) Enable
 79 OperMode 1 (2) Normal
 29 Health 1 Healthy
 21 ParentFolder 1 1
 159 AutoManageAction 1 (1) Eligible
 160 AutoManageStatus 1 (1) Unknown
 122 LicenseStatusEvaluated 1 (1) Licensed
 123 LicenseStatusForced 1 (0) Unknown
 30 ScsiDevice 1 0
 25 UniqueHWID 11 0301005000cca0802b94c4
 41 VendorID 8 DELL
 42 ProductID 16 HUC101812CSS204
 43 SerialNumber 8 0EGSZ0AD
 93 JBODIndex 1 1
 94 JBODDiskIndex 1 16
 95 JBODShelfID 1 0
 96 JBODDiskPosition 1 15
 106 JBODDrawerIndex 1 0
 107 JBODRowIndex 1 0
 105 SpinRate 1 0
 163 SpinRateOverride 1 0
 119 SwimLane 1 0
 120 DriveLine 1 (2) EnterprisePlus
 121 DellPPID 25 TH01T8KWHGT006BN0A5ZA00
 28 ClassIndex 1 2
 56 AssociationIndex 1 111
 80 HasContainedUserData 1 (0) False
 152 ConfigQualityScore 2 0x0000AEB5
 150 OverrideConfigQualityScore 1 0x00000000
 149 OutstandingRemoveRequests 1 0
 151 ForceConfigPlacement 1 TestOnlyAllow|TestOnlyDesireStrong|TestOnlyDesireWeak|TestOnlyEncourage|ProductionDefault
 166 ReadAvoidAdminStatus 1 (2) Disable
 165 ReadAvoidIndicator 1
 71 MediumErrors 1 0
 72 PossibleMediumErrors 1 0
 132 ProtectionInformationErrors 1 0
 74 MediumErrRecAttempted 1 0
 73 MediumErrRecAllowed 1 32
 75 RAIDScrubErrors 1 0
 89 WriteSamePreferenceUser 1 (0) NoPreference
 90 WriteSamePreferenceDell 1 (1) WriteSame
 91 WriteSamePreferenceVPD 1 (1) WriteSame
 92 WriteSamePreferenceTest 1 (0) NoPreference
 54 WriteSameEmulationEnabled 1 (0) False
 55 WriteSameEmulationTargetSize 2 4096
 35 LabelDiskIndex 1 0
 40 LabelManagementDiscipline 1 (0) Unassigned
 23 CatalogLocation 1 0
 24 CatalogSize 1 0
 4 DiskLabel 0
 5 SystemSerialNumber 4 0000af3a
 26 Notes 0
 9 NextBlockDeviceID 1 1
 78 DiskConstructionState 1 (2) Complete
 83 LastSurveyTime 1
 97 EndurancePercent 1 0
 98 EndurancePercentValid 1 (0) False
 99 EnduranceTimeStamp 1
 101 EnduranceWearDateEst 1
 100 EnduranceDaysLeadTime 1 120
 108 SEDCapabilities 1 (1) None
 109 OwnershipStatus 1 (0) Unknown
 110 LockOnReset 1 (0) Unknown
 111 BandLocked 1 (0) False
 112 BandConfiguration 1 (0) Unknown
 115 LastUnlockDuration 1 0
 114 LastCryptoEraseTime 1
 10 StatsRead 1 0
 11 StatsReadBlocks 1 0
 12 StatsWrite 1 0
 13 StatsWriteBlocks 1 0
 31 StatsWriteMultiple 1 0
 32 StatsWriteMultipleBlocks 1 0
 68 StatsWriteVerify 1 0
 69 StatsWriteVerifyBlocks 1 0
 86 StatsVerify 1 0
 87 StatsVerifyBlocks 1 0
 14 StatsReadError 1 0
 15 StatsWriteError 1 0
 33 StatsWriteMultipleError 1 0
 70 StatsWriteVerifyError 1 0
 88 StatsVerifyError 1 0
 16 TotalBlockCount 4 2344225968
 18 SystemAllocBlockCount 1 0
 153 RightsizedBlockCount 4 2344225968
 17 UnallocatedBlockCount 4 2344225968
 135 UninitializedBlockCount 1 0
 138 UninitializedPercent 1 0
 19 UserAllocBlockCount 1 0
 20 BadBlockCount 1 0
 66 ReclaimBlockCount 1 0
 139 RebuildReservedBlockCount 1 0
 140 SystemReservedBlockCount 1 0
 154 SpareBlockCount 1 0
 22 LargestFreeBlock 4 2344225968
 27 DiskSize 4 1.09 TB
 136 DiskInitializerAdminStatus 1 (2) Disable
 137 DiskInitializerStatus 1 (1) NotStarted
 141 UnmapSupport 1 (0) False
 142 UnmapSupportOverride 1 (0) UseSystemValue
 146 PIEnabled 1 (0) False
 147 PIEnabledOverride 1 (0) UseSystemValue
 143 ScrambledPI 1 (0) False
 144 ScrambledPIOverride 1 (0) UseSystemValue
 162 IsEqualLogicSnapshot 1 (0) False
 34 WarnPath 1 (1) True
 36 OperStatusAlert 24 Okay Trig: Clear: Msg: ServiceTag: Ack: 0
 37 PathAlert 24 Okay Trig: Clear: Msg: ServiceTag: Ack: 0
 38 FirmwareAlert 42 Okay Trig: 12/24/2024 03:50:20 PM Clear: 01/10/2025 05:03:07 PM Msg: Disk[1] firmware not at expected version ServiceTag: Ack: 1
 124 IncompatibleDriveLineForSystemAlert 90 Okay Trig: 12/24/2024 03:50:20 PM Clear: 01/10/2025 05:03:07 PM Msg: System is unable to accept disk 1 in enclosure position 1-15 with serial number 0EGSZ0AD and Dell part number TH01T8KWHGT006BN0A5ZA00 because disk drive line Unknown is not compatible w
 125 IncompatibleEnclosureForSystemAlert 24 Okay Trig: Clear: Msg: ServiceTag: Ack: 0
 126 IncompatibleDriveManufacturerForEnclosur 24 Okay Trig: Clear: Msg: ServiceTag: Ack: 0
 148 IncompatibleSpinRateAlert 24 Okay Trig: Clear: Msg: ServiceTag: Ack: 0
 131 RekeyAlert 24 Okay Trig: Clear: Msg: ServiceTag: Ack: 0
9006 AbnormalDesc 23 No current block device
9007 OperatingNormal 1 (0) External

Hello,

Thank you for the image.

For HDD2 is see it reports Unknown:

124 IncompatibleDriveLineForSystemAlert 90 Okay Trig: 12/24/2024 03:50:20 PM Clear: 01/10/2025 05:03:07 PM Msg: System is unable to accept disk 1 in enclosure position 1-15 with serial number 0EGSZ0AD and Dell part number TH01T8KWHGT006BN0A5ZA00 because disk drive line Unknown is not compatible w

It appears to be a drive without Compellent firmware.

There are no workarounds for this issue and the drives must be replaced with a Compellent drive.

The drives may have the same manufacture model but that doesn't mean it has the Compellent firmware.

You can contact Sales and specify Compellent drive that you need.

Article Number: 000136686

SC Series: Disks that report as Unknown drive type

https://dell.to/4239266

You may need to log in to see that article.

Thank you Charles. I was afraid this might be the case, but it's still strange that both drives report the same firmware, which is FE40. The Seagate P/N (HUC101812CSS204) runs a different firmware version on PowerEdge for instance (FJ-something?). Plus the drive came in a Compellent drive tray, which means it must have worked in a different Compellent system before. 

Could this be because the drive wasn't properly removed from the old system? Are there any CLI commands that would purge all information from those drives? I couldn't find any documentation on the "disk" commands that are available after "shellaccess developer"... 

I can't say for sure. Maybe someone did try to flash Compellent firmware on it.

I think Sam explains it best above:

"The issue that you are having is that the drive doesn’t have compellent firmware on it. That is the reason that you are getting the error of unsupported drive. Compellent drives have a base firmware on them that is excepted for compellent systems. There is not a way for a customer to force flash the base compellent firmware on a drive so that it can be read by the system. You will need to get a true compellent drive that is read by the system."