Oh my what a ride! I got everything up and running in a RAIDZ2 with the 6 x 4TB drives! (soon i will add another 4 x 1tb in an icy dock as a separate vdev)

Everything works now with no errors! 🥳

I could not have fixed this without your help. You are a lifesaver and probably saved this drive from the landfill lol. I honestly can’t thank you enough for your continuous support throughout many days!

You are the light that shows that there are still good people on the internet that want to help, and not just lurkers that laugh and move on and treat everything as content instead of a person on the other side sharing something that is important to them.

In my case I was in need of help, and like one comment put it: Out of the 50 messages of ridicule, one person will actually go out of their way and help.

I learned soo much and a good lesson too!

Thanks again for your help, and I will remember this interaction for the rest of my self-hosting journey! I’m serious.

Keep helping others and sharing your knowledge. I will pay this kind gesture forward in the new year, and help others more with the things that I know. 🫡

(Please don’t delete this convo, might help someone in the future)

Thanks again and Happy Holidays!

I wish you all the best in the New Year! 🤗 🎉

Great News!

Format completed and now the drive is viewable in “Disks” (however it is still unknown compared to the other one, it might just need a normal format.

The code for the comparison returns invalid option, I assumed you need just -l comparison:

sudo sg_readcap -l /dev/sdb and sudo sg_readcap -l /dev/sda

One question I have is: what do you mean by powercycle? Is that another command to run on the problematic drive? If you mean turn off the pc and turn it back on, I will do that right now, just after the drive has completed formatting.

After PowerCycle (turned pc off and on)

sudo sg_readcap -l /dev/sdb and sudo sg_readcap -l /dev/sda

Would the next step be formatting of some kind?

Thanks for the continued support! ❤

I’ve attached an identical Segate SAS drive from the server.

To confirm, it is the same LSI card that was in the TrueNAS server. I pulled it out of the server and put it into the trouble shooting machine, where I run the commands.

It is this one: 01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 05)

I did not see your other reply lol, I will also try this command that you recommended:

sudo sg_format –format –size=512 –fmtpinfo=0 –pfu=0 /dev/sdb

Also, the sg_format ran for less than 5 minutes, very quick. However, if I can recall, it did say it was completed.

**Note: ** “Bricked Drive” turned to sdb

Identical working drive installed as sda

Here is the dmesg -T > dmesg-full.txt with the identical drive

Here is the code from: (with the output for each drive, separately)

sudo lspci -nnkvv

sudo lsblk -o NAME,MODEL,SIZE,PHY-SeC,LOG-SeC,ROTA

sudo fdisk -l /dev/sdX

sudo sg_inq -vv /dev/sdX

sudo sg_readcap -ll /dev/sdX

sudo sg_modes -a /dev/sdX

sudo sg_vpd -a /dev/sdX

Thanks again for all the help, I await your reply. :)

I will let you know the results of (sudo sg_format –format –size=512 –fmtpinfo=0 –pfu=0 /dev/sdb), as soon as it’s done.

Thanks for the reply,

It is an LSI card, the same one that was in my truenas server.

This one bought here

Edit: also the command that bricked the drive was me using sg_format with --size==512

Is that the same formatting solution you were mentioning ? Is it different?

Thanks for the uplifting words

I’ve connected to drive to another PC running Linux Mint 22, and the disks app can see the drive but no actions can be done on it. And Gparted can’t even read it lol.

Any ideas?

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

Thank you for helping! Like I said I’m a complete beginner with little knowledge of all this, means a lot 🤗

just so you know I connected the drive to my dell pc, so its just the one broken drive not all 6.

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

Edit: from LM22, output of sudo sg_format -vv /dev/sda

I really appreciate your knowledge and help 🙂
Let me know if anything else is needed

Mb, I meant I wiped the drive…

I am using Truenas CE

The drive got whipped and apparently you’re not supposed to wipe a SAS drive like a normal SATA one …

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?

there is this app that I found on fdroid that makes it pretty easy to log notes and photos on a daily calendar.

It certainly does not replace ANY of the other methods of documentation like videos and quality photos, and long detailed journal entries.

I just use it because it reminds me of the Snapchat Memories feature but FOSS.

It is a good starting spot, and makes it easy to document with photos.

It has been pretty good to me so far, I recommend that you give it a shot:

Can be found here: https://f-droid.org/packages/com.demizo.daily_you/

Github: https://github.com/Demizo/Daily_You

Looks like this

So are you saying these plugs will work on SATA drives?

Thanks for you help, I will try this. I will wait until my first SAS dies on noraidSAS card and then get a sata pcie and one by one move to sas

Interesting, so first my best bet would be to her a non raid SAS card and the do what you said ?

So you mean use it until I have all drives and a data card then copy my NAS to a DAS and then back to my NAS?

And also the cards as far as I know have 2 mini SAS ends so I can’t switch to data one by one, they go in fours?

That’s what I was thinking but my wires are mini SAS to SAS and they are in a 1:4 ratio.

Like this

Wouldn’t that mean that it would be impossible to make a drive data it they are connected in 4s

The SAS cables go in pairs of 4…

If one dies I have to replace 4… And the raid HDD builder won’t be able to build more that 1 at a time probably?

Unless you were suggesting something else

Do you recommend SAS over SATA? What would I do of I wanted to move to SATA drives and already having data on the hardware raid? How would I transfer all that?

What I’m worried about is that once one drive fails, then I won’t want to replace it because I want to go full SATA. But then that would mean my NAS storage would shrink and loose data.

That means that I have to replace all drives to data at the same time, and if I have lots of data on the hardware said SAS drives. How do I transfer all that data to the new drives ?

Any ideas? The best I can think of is to have 2 pcie cards one with the raid and another data. But how would they share the data if the SATA is not in the hardware raid pool.

It shows up in try has as one big 18TB drive (I have 24tb, so raid is working).

How do I configure that? Just put it in one pool? In truenas terms what do I do with the 18tb?