SAS drive not showing up after sg_format command was interrupted

Hello,

I have 4 HGST 4TB 7200RPM SAS that I’ve tried to add to a new pool.
I got one of them that gave the following error message: “disk: ‘sdb’ is incorrectly formatted with data integrity feature (dif).” so I went googling and saw the sg_format command was what to use in cases like that.
I went ahead from the web interface console and ran the command but got kicked out a few minutes after and realize I couldn’t follow the process progression.
Long story short I restarted the server to redo the command from the terminal and realized the drive was not detected.

So can this be reversed or did I screw up the drive completely?

I already unplugged the drive from the server for a minute or 2 and replugged it but same thing. It’s not being seen by the dell controller.

Actually the controller sees the drive as a 0kb drive with the status “failed”.

These are “Sun Oracle” branded BTW.

My experience is that the format continues in the background, you just miss the progression. I believe my disks(8tb) used around 15 hours to reformat.

Unfortunately the drive does not appear at all in “disk” in truenas so I doubt that will be happening in my case. The Dell controller sees the disk plugged but report a failed state and a 0kb capacity.

I’ve tried from a different server, I’ve tried to let the drive seat unplugged for a while, but still no cigar.

What does sg_format do to a drive that it can brick it? Please explain.

If you use the --ffmt option it turns it into minutes not hours for info.

sg_format --format --ffmt=1 --size=4096 /dev/da0
1 Like

Thanks!
By using a different HBA adapter with IT mode, I was able to pass the drive in a failed state and relaunch the command which brought back the drive.

Problem solved.