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 π
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?
sg_formatcan restore your disk.You need to figure out the block layout of the drive and restore a sector map that aligns with the disk.
Start here:
https://forum.level1techs.com/t/how-to-reformat-520-byte-drives-to-512-bytes-usually/133021
And it bears repeating: LLMs do not think, they generate text from statistical output. If the the topic is advanced or uncommon, errors in output are far more likely.
So don't be tempted to ask chat gpt for further help on this, if that isn't clear yet.
From what I understand, I formatted it with 512, but i needed to do it with 520 and then 512?
sg_format -v --format --size=520 /dev/sda
then
sg_format -v --format --size=512 /dev/sda
Well, no... You need to find the geometry of your disk.
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.
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.