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 😁

  • biggerbogboy@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    20 hours ago

    I actually had an AI assist me in flashing the firmware, as well as flashing a custom ROM later on, of a phone I was just testing on for fun, and I was only confident since I had a chunk of prior knowledge of ADB as well as other tools and the differences between mobile and desktop system structures, and for the stuff I didn’t understand or know, I just researched externally and figured it out.

    Blindly trusting it though is a fools errand, just like myself a few years back messing with my laptop’s Linux install, copy pasting everything and then complaining when shit broke.