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 😁

  • y0din@lemmy.worldEnglish
    1·
    3 hours ago

    That’s good news — what you’re seeing now is the expected state.

    A quick clarification first:

    Power cycle means exactly what you did: shut the machine down completely and turn it back on. There is no command involved. You did the right thing.

    Regarding the current status:

    The drive showing up in Disks but marked as unknown is normal

    At this point the disk has:

    • No partition table

    • No filesystem

    “Unknown” here does not indicate a problem, only that nothing has been created on it yet

    About sg_readcap:

    sg_readcap -l is correct

    There is no direct “comparison” mode; running it separately on sda and sdb is exactly what was intended

    The important thing is that both drives now report sane, consistent values (logical block size, capacity, no protection enabled)

    Next steps:

    Yes, the next step is normal disk setup, just like with any new drive:

    1. Create a partition table (GPT is typical)

    2. Create one or more partitions

    3. Create a filesystem (or add it back into ZFS if that’s your goal)

    At this stage the drive has transitioned from “unusable” to functionally recovered. From here on, you’re no longer fixing a problem — you’re just provisioning storage.

    If you plan to put it back into TrueNAS/ZFS, it’s usually best to let TrueNAS handle partitioning and formatting itself rather than doing it manually on Linux.

    Nice work sticking with the process and verifying things step by step.