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 😁

  • squaresinger@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    7
    ·
    13 hours ago

    I had a problem with Fedora 42, where the performance of my games would be fine one day and abysmal another day. Couldn’t find a pattern. I googled a ton, tried to debug myself, asked on reddit, stackexchange, the fedora forum and lemmy. I only got answers like “Works fine on my machine, noob” and “I have that problem too”. It only affected games running in proton on heroic, everything else was fine.

    After about a year of on-and-off debugging and asking around, I swallowed my pride and asked ChatGPT.

    First answer from that thing was correct: I had run dnf update without doing a flatpak update right afterwards. Turns out, flatpak has its own copy of Nvidia drivers and if the system driver is updated without the flatpak copy being updated, it falls back to software rendering. So the performance was crap until I did flatpak update the next time, and broke again when I ran dnf update.

    I still haven’t found that in any documentation so far.

    AI is crap more often than not, but it does at least try to help and sometimes it actually does.

    Look in this thread here. Is there even a single answer that tries to help OP, or is every single answer here just dumb snark?

    • Brewchin@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      13 hours ago

      It’s true that people on the internet can be dicks. Even more so technical people (and that’s not limited to online: those online dicks are usually IRL dicks when taking technical stuff). But that’s a hurdle, not a barrier.

      There’s little anyone here can do to help OP, as they (if I understand it correctly) have already irreparably nuked their hardware. The current problem is significantly different and harder than the original problem. Asking randos on this community is unlikely to yield results. Hence the focus on variations of “Now… what did we learn? 🤨”

      I’m not trying to help, as I’m not familiar enough with SAS nor the current problem. The same is likely true of others here.

      • squaresinger@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        8 hours ago

        The only evidence that OP irreparably nuked their hardware is ChatGPTs word.

        The bigger issue ad hand is that everyone here is a noob when it comes to exotic hardware like SAS, and still everyone here thinks they are 1337 haxors enough to tell OP that they are a noob idiot.

        Tbh, if OP asks for help here and there’s 49 comments of people being dicks and one that actually helps it might be worthwhile. But as it stands it’s 50 to 0, with nobody here beeing educated enough to know anything about the subject.