this post was submitted on 26 Dec 2025
-48 points (35.5% liked)

Selfhosted

53934 readers
857 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
-48
ChatGPT fried my drive!? (lemmy.zip)
submitted 1 day ago* (last edited 17 hours ago) by rook@lemmy.zip to c/selfhosted@lemmy.world
86 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

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

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: verbatim output from

Thanks for all the help 😁

you are viewing a single comment's thread
view the rest of the comments
[–] rook@lemmy.zip 4 points 18 hours ago (1 children)

Thanks for the uplifting words

I've connected to drive to another PC running Linux Mint 22, and the disks app can see the drive but no actions can be done on it. And Gparted can't even read it lol.

Any ideas?

[–] Greg@lemmy.ca 3 points 13 hours ago (1 children)

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?

[–] rook@lemmy.zip 3 points 5 hours ago* (last edited 5 hours 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?