New hard drive test

[Robti]

Sorry newbie with truenas and had a search but couldn’t find anything up to date, what is recommended to test new hard drives before setting pool up ?
Thanks

 

[awasb]

GitHub - Spearfoot/disk-burnin-and-testing: Shell script for burn-in and testing of new or re-purposed drives

Shell script for burn-in and testing of new or re-purposed drives - Spearfoot/disk-burnin-and-testing

github.com

 

[jgreco]

couldn’t find anything up to date,

What does "up to date" mean? Hard drives are decades-old technology. Building Intel-architecture servers isn't new either.

The main question is if you're using FreeNAS, TrueNAS Core (both based on FreeBSD) or Scale (based on Linux).

For all three, the general burn-in guidelines suggested in

Building, Burn-In, and Testing your FreeNAS system

I've been meaning to post some guidance here for a while now. We frequently see people come to the forums with hardware problems that should have washed out in the system build process, but since many of the users here are DIY'ers without...

www.truenas.com

are a grand idea. This also points to a FreeBSD-specific disk testing tool --

solnet-array-test

Back in the late '90's, I was managing a bunch of large whitebox storage servers. For the largest of these, I had the pleasure of building and deploying a massive storage server, 8 shelves of 9 drives each, Seagate ST173404LW 73GB drives, a...

www.truenas.com

which is a bit more than two decades old but is as relevant today as when I wrote it. Just because it's old doesn't make it out of date.

There are some other scripts out there to do other kinds of testing that may be destructive to an installed pool. If you don't have anything on your disks, they're fine too. Note that this isn't an either/or proposition. My tool is looking for performance indicators that could reveal underlying issues with the disks or controllers, and does a basic disk check as a bonus, but is nondestructive to your data. Other tools may do read/write testing that kill any data on the disks. Both strategies have upsides and downsides.

 

[Robti]

What does "up to date" mean? Hard drives are decades-old technology. Building Intel-architecture servers isn't new either.

The main question is if you're using FreeNAS, TrueNAS Core (both based on FreeBSD) or Scale (based on Linux).

For all three, the general burn-in guidelines suggested in

Building, Burn-In, and Testing your FreeNAS system

I've been meaning to post some guidance here for a while now. We frequently see people come to the forums with hardware problems that should have washed out in the system build process, but since many of the users here are DIY'ers without...

www.truenas.com

are a grand idea. This also points to a FreeBSD-specific disk testing tool --

solnet-array-test

Back in the late '90's, I was managing a bunch of large whitebox storage servers. For the largest of these, I had the pleasure of building and deploying a massive storage server, 8 shelves of 9 drives each, Seagate ST173404LW 73GB drives, a...

www.truenas.com

which is a bit more than two decades old but is as relevant today as when I wrote it. Just because it's old doesn't make it out of date.

There are some other scripts out there to do other kinds of testing that may be destructive to an installed pool. If you don't have anything on your disks, they're fine too. Note that this isn't an either/or proposition. My tool is looking for performance indicators that could reveal underlying issues with the disks or controllers, and does a basic disk check as a bonus, but is nondestructive to your data. Other tools may do read/write testing that kill any data on the disks. Both strategies have upsides and downsides.

Thanks what I meant by up to date was looking at the community posts and couldn’t find any recent ones, will have a read on what you posted
Thanks