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…

Edit: 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 😞

  • rook@lemmy.zipOP
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    3
    ·
    9 hours ago

    Thanks for the input

    I thought the SAS worked like a data, just wipe and go… I’m not sure how to get this SAS connected to another computer as it is connected to my server through a SAS card…

    Any ideas?

    • frongt@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 hours ago

      Yeah, generally it does. Maybe just see if there’s a command to turn DIF off? I’ve never had an issue using a SAS drive just like any other. It’s certainly not anything permanent.

    • nutbutter@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 hours ago

      I have never worked with SAS drives. Another way to do what I suggested is to connect the server to a display output and boot a linux ISO with a libe environment.