Hi guys,

I'm having an issue with an IBM HDD (2.5" 300GB SAS 10k rpm Disk) (IBM-ESXS HUC106030CSS60 (Firmware D340)
The IBM HS21 Blade Server has a LSI 1064e SAS Controller which the Drive is connected to.
I booted into the SAS Controller Utility and went to format a disk, because i wanted to Create a RAID1 and migrate the data that was on one of the disks over to the new RAID1 using both disks, but the other disk was half synced (with a smaller RAID1 Volume, i had just upgraded to 300GB from my old 146GB Drives) so i wanted to quickly wipe the half synced disk, i went started a format from the SAS Controller Utility, but it was taking ages to finish, so i thought i'd just reboot the server thinking that i could just re-create the partition on the disk later, but it stopped the disk from being usable!!!

After trying quite a lot of things, i eventually found the HDD Low Level Format Tool 4.40,
This sees the disk and when i try and format it, it actually says it completed successfully, but it still doesn't work, it displays this information:

24/05/2014 2:59:53 a.m. HDD Low Level Format Tool 4.40; http://hddguru.com
24/05/2014 2:59:53 a.m. Low level format: [0] IBM-ESXS HUC106030CSS60 D340 [300 GB] (585937500 512-byte sectors)
24/05/2014 2:59:53 a.m. Device capacity: 585,937,500 sectors
24/05/2014 2:59:53 a.m. Locking device...
24/05/2014 2:59:53 a.m. Formatting...
24/05/2014 2:59:53 a.m. Format Error occurred at offset 0: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 65,536: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 131,072: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 196,608: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 262,144: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 327,680: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 393,216: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 458,752: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 524,288: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 589,824: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 655,360: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 720,896: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 786,432: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 851,968: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 917,504: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 983,040: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,048,576: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,114,112: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,179,648: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,245,184: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,376,256: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,507,328: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,638,400: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,769,472: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 1,900,544: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 2,031,616: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 2,162,688: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 2,293,760: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 2,424,832: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 2,555,904: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 2,818,048: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 3,080,192: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 3,342,336: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 3,604,480: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 3,866,624: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 4,128,768: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 4,390,912: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 4,653,056: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 4,915,200: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 5,177,344: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 5,701,632: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 6,225,920: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 6,750,208: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 7,274,496: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 7,798,784: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 8,323,072: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 8,847,360: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 9,371,648: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Format Error occurred at offset 9,895,936: 19 - The media is write protected
24/05/2014 2:59:53 a.m. Average speed: 43.8 MB/s
24/05/2014 2:59:53 a.m. Low-level format is complete.
24/05/2014 2:59:53 a.m.
24/05/2014 2:59:53 a.m. Remember to create new partitions.

Does anyone know how to fix this issue? Maybe the failed format job put write protections on the sectors or something and it didn't remove them because it was shutdown in the middle of the job, but how can i reverse this?
The disk is viewable in windows, but it just doesn't let you create a MBR on it. If you try and do anything to it in windows disk management it gives you this error: Data error (cyclic redundancy check)

Have you once previously enabled encryption on this drive?

_________________
Encryption is a powerful defensive weapon for free people.
It offers a technical guarantee of privacy, regardless
of who is running the government - E. Dyson

No, haven't had encryption on that drive ever.
The drive is actually brand new, it was working perfectly fine until i shut the server down in the middle of the LSI SAS Controller Utility trying to format the drive, i didn't think it would physically damage it...

You can try to use DISKPART> attributes disk clear readonly before you format it with HDD LLF.

_________________
Encryption is a powerful defensive weapon for free people.
It offers a technical guarantee of privacy, regardless
of who is running the government - E. Dyson

if i run that command it gives me this error: DiskPart failed to clear disk attributes.

Maybe the read-only flag is in the volume and not in the disk. You can try it this way:

DISKPART>list volume
select volume x
attributes volume clear readonly

_________________
Encryption is a powerful defensive weapon for free people.
It offers a technical guarantee of privacy, regardless
of who is running the government - E. Dyson

i tried that but there is no volume on the hard drive.
As i mentioned in the top post, i actually rebooted the server, when the SAS Controller was formating the disk, so there is no volume on the disk, and i can't even run the low level format tool on it, (The Low Level format tool does say it was successful, but it doesn't actually format it...)
Any other ideas guys??
i guess i'm going to have to try and get the hard drive replaced under warranty, it was brand new, i can't believe i killed it simply by rebooting in the middle of a format...

what do u get if you do diskpart> detail disk or detail volume?

_________________
Encryption is a powerful defensive weapon for free people.
It offers a technical guarantee of privacy, regardless
of who is running the government - E. Dyson

DISKPART> detail disk

Virtual Disk Service error:
The system's information about the object may not be up to date.


DiskPart has referenced an object which is not up-to-date.
Refresh the object by using the RESCAN command.
If the problem persists exit DiskPart, then restart DiskPart or restart the
computer.

If i try and do a RESCAN,
it still gives me the same error.

i've raised a support case with IBM and they have suggested i use the cfggen command line tool to do the format, but when i run the cfggen tool i get this error message:

C:\SA Utils>cfggen 0 STATUS
LSI Integrated RAID Configuration Utility v1.16.00.04
cfggen: adapter discovery failed!
cfggen: program failed; status = 0x2!


I'm slowly begining to think there is no way to fix this drive, other than get a replacement drive...

just to let you guys know, if anyone is interested,
IBM are going to replace the Hard Drive. We can't seem to fix it through any of the software tools provided by the manufactures.

Well, that seems to be the best option that you have though. Good Luck

_________________
Encryption is a powerful defensive weapon for free people.
It offers a technical guarantee of privacy, regardless
of who is running the government - E. Dyson