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 😁

  • lambalicious@lemmy.sdf.orgEnglish
    1·
    17 days ago

    The manuals are written by experts for experts and in most cases entirely useless for complete beginners who likely won’t be able to even find the right manual page (or even the right manual to begin with).

    Asking for help online just gets you a “lol, RTFM, noob!”

    This is a thing that honestly still makes me seethe sometimes, because as much as the manuals are there and people should be told to read the manual before anything else, there is a vast difference between a user’s manual and a technical manual. People who answer basic questions by telling the user to RTFManpage instead of leading them to the bropage or the tl;drpage or a simple use case tutorial (or even better, providing the example themselves) ironically builds bad cred for a movement for well-documented software.

    The User’s Manual for a car covers, at best, how to turn the ignition on, how to drive, how to brake in difficult conditions and how to change the tires. Maybe it covers where exactly the friggin’ cupholder is. A Technical Manual for a car is for when there’s a real exceptional emergency that’s not simply covered by user service. The computer does not work and someone (not you, but the technician!) needs to know how to pin the RS232 connectors for the emergency interface of the onboard chip. The refrigeration liquid tube has broken off and you need to know what model or measurements the replacement needs to be and what heat can it withstand before it starts melting and likely obstructing the valve. You need to know if (or for how long) the car’s engine can withstand frontal semiautomatic fire and up to what reverse speed can the vehicle perform a safe J-turn maneuver in case you face an ambush.

    ~95% of manpages I’ve ever seen are Technical Manuals. ~70% of “help” for non-browser systems, as well.

    What beginners need to be directed at before anything else is the User’s Manual.

    And if that one is not available, go get writing it.

    </rant>

    All that said, none of that excuses turning to AI. AI is explicitly and specifically for when you don’t want things to work, or for when you are specifically looking for someone to bullshit you. They are for evading responsibility, not for finding solutions.