-52
ChatGPT fried my drive!? [Solved] (lemmy.zip)
submitted 9 months ago* (last edited 9 months ago) by to c/selfhosted@lemmy.world
90 comments fedilink hide all child comments
 

Did I just brick my SAS drive?

I was trying to make a pool with the other 5 drives and this one kept giving errors. As a completer beginner I turned to gpt.....

What can I do? Is that drive bricked for good?

Don't clown on me, I understand my mistake in running shell scripts from Ai...

EMPTY DRIVES NO DATA

The initial error was:

Edit: sde and SDA are the same drive, name just changed for some reason And also I know it was 100% my fault and preventable 😞

**Edit: ** from LM22, output of sudo sg_format -vv /dev/sda (broken link)

BIG EDIT:

For people that can help (btw, thx a lot), some more relevant info:

Exact drive model: SEAGATE ST4000NM0023 XMGG

HBA model and firmware: lspci | grep -i raid 00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] Its an LSI card Bought it here

Kernel version / distro: I was using Truenas when I formatted it. Now trouble shooting on other PC got (6.8.0-38-generic), Linux Mint 22

Whether the controller supports DIF/DIX (T10 PI): output of lspci -vv (broken link)

Whether other identical drives still work in the same slot/cable: yes all the other 5 drives worked when i set up a RAIDZ2 and a couple of them are exact same model of HDD

COMMANDS This is what I got for each command: (broken link)

Solved by y0din! Thank you soo much!

Thanks for all the help 😁

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 9 months ago (1 child)

How do you have the SAS drive connected to your Mint 22 box (what exact adapter/controller)? Is it going through a real SAS HBA (LSI/Broadcom-style, IT/HBA mode), or through a RAID controller / USB-SAS bridge / "virtual" adapter?

Reason I’m asking: there are basically two connection paths:

  • True HBA/passthrough: Linux gets direct SCSI access (you’ll see a /dev/sgX for the disk) and you can usually low-level reformat it back to 512-byte logical blocks (e.g., from 520/528).
  • RAID/USB/translation layer: the controller hides or emulates the SCSI commands, so tools like sg_format often can’t issue the low-level format needed to switch the sector size. That might be why the disk is visible in the disks app but not in gparted.

Given the screen shots I believe it's the later. Can someone smarter than me confirm?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 3 points 9 months ago*

    Thanks for the reply,

    It is an LSI card, the same one that was in my truenas server.

    This one bought here

    Edit: also the command that bricked the drive was me using sg_format with --size==512

    Is that the same formatting solution you were mentioning ? Is it different?

  • permalink
  • fedilink
  • source
  • parent