Start a Conversation

Unsolved

This post is more than 5 years old

2865

August 22nd, 2017 07:00

Error code 2000-0151

Good Day.

Can anybody help me with an error I am getting on a Dell R520 server. It puts one of the drives in a BLOCKED state and after doing a drive diagnostic I am given the following error for this specific drive:

S/N Unknown, incorrect status = 8000000000000018
EFI Protocol Error

BIOS 2.4.2

Error Code: 2000-0151

Validation : 83680

It should not be blocking this drive as it is a Dell drive (ST3300657SS).


Moderator

 • 

6.2K Posts

August 23rd, 2017 14:00

Hello

The information provided indicates that the drive is blocked due to a communication issue. Either the drive is faulty or incompatible. Almost anything in the RAID chain could also affect communication. You will need known good hardware to test with in order to rule out a hardware issue.

It should not be blocking this drive as it is a Dell drive (ST3300657SS)

Our drives use the same model number of their Seagate equivalent. A model number does not mean the drive is Dell certified. Our version of the drive has our firmware. Check the drive for a Dell label. If it is one of our drives it will have a Dell label with either/both a 5 digit part number and a 25 digit PPID.

Thanks

2 Posts

August 24th, 2017 01:00

Good Day.

Thank you for your response. It is a certified Dell drive with the Dell label on it with part number. It has been used in production before;we are just trying to rebuild it but gave this problem which it has not done before.

Regards,

Adam

Moderator

 • 

6.2K Posts

August 24th, 2017 10:00

It is a certified Dell drive

Then you will need to move or swap hardware to find out which part is faulty. Try the drive in another slot if available, and move parts around as much as you can to try to isolate the problem. The controller puts a drive into blocked status if it is able to detect the presence of a drive, but it is unable to fully communicate with it.

Almost anything in the RAID chain could also affect communication. You will need known good hardware to test with in order to rule out a hardware issue.

Thanks

No Events found!

Top