What's the best SSD to use?

Status
Not open for further replies.

Rickinfl

Contributor
Joined
Aug 7, 2017
Messages
165
I have tried 2 brand new Sandisk 240 gig SSD drives and both after a day or two FreeNAS says my boot pool has unrecoverable errors.

So what brand works because Sandisk seems not to be.


Thanks,
Rick
 
Last edited by a moderator:

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Hardware specs? You're the first I've seen to have issues with Sandisk SSD's as a boot device.

More information on your setup would be helpful.
 

Rickinfl

Contributor
Joined
Aug 7, 2017
Messages
165
Running Tyan S7012 Motherboard 2 - 6 core X5650 Xeon. 24 Gig of Ram. 8 - 3 TB drives.

I have 2 of these setups both get SSD errors. Other server is same motherboard, but 2 - 4 core X5620 Xeon.



This is error in GUI
Code:
CRITICAL: Feb. 17, 2018, 3:46 a.m. - The boot volume state is DEGRADED: One or more devices has experienced an error resulting in data corruption. Applications may be affected.

This is error in console.
Code:
pool: freenas-boot
state: DEGRADED
status: One or more devices has experienced an error resulting in data
		corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
		entire pool from backup.
  see: http://illumos.org/msg/ZFS-8000-8A
 scan: scrub repaired 3.50K in 0 days 00:00:04 with 25 errors on Sat Feb 17 03:45:04 2018
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  DEGRADED	 0	 0	25
		  ada0p2	DEGRADED	 0	 0	53  too many errors

errors: Permanent errors have been detected in the following files:

		<metadata>:<0x3e>
		<metadata>:<0x40>
		freenas-boot/ROOT/default:<0x0>
		//usr/local/lib/python3.6/site-packages/django/db/migrations/__pycache__
		freenas-boot/ROOT/default@2018-02-10-00:05:11:<0x0>
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/django/contrib/admin/templates/registration
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/django/contrib/admin/templatetags
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/cryptography/hazmat/primitives/asymmetric
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/Crypto/SelfTest/__pycache__
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/migrate93/django/contrib/sites/locale
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/www/dojo/dojox/dtl/render
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/www/dojo/dojo/nls/sr
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/botocore/docs/__pycache__/shape.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/migrate93/django/conf/locale/os
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/migrate93/django/conf/locale/os/LC_MESSAGES
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/migrate93/django/conf/locale/pa
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/migrate93/django/conf/locale/pa/LC_MESSAGES
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/migrate93/django/conf/locale/pl
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/xml/etree/__pycache__/cElementTree.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/chardet/__pycache__/codingstatemachine.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/lib/python3.6/site-packages/requests/__pycache__/status_codes.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-02-10-00:05:11:/usr/local/www/dojo/dojox/dtl/ext-dojo
 
Last edited by a moderator:

ethereal

Guru
Joined
Sep 10, 2012
Messages
762
cksum are usually cable issue - change cable and try a different sata connector
 

Rickinfl

Contributor
Joined
Aug 7, 2017
Messages
165
I've tried many cables. I'm trying a 1tb Hard drive right now to see if it's an issue with SSD
 

Rickinfl

Contributor
Joined
Aug 7, 2017
Messages
165
Here is what's strange and makes me think it's not the SSD. Same system hardware I loaded pfSense on that SSD and it runs fine no errors. I'm thinking FreeNAS doesn't like that SSD for some reason.
 
Last edited by a moderator:

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
I'd run memtest on your server to rule that out.

Also what are you running for a power supply?
 
Last edited:

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Same system hardware I loaded pfSense on that SSD and it runs fine no errors. I'm thinking FreeNAS doesn't like that SSD for some reason.
Or it could be that pfSense does not use ZFS and so just does not detect problems with data errors on the SSD.

This could be due to a semi-working SATA controller on the motherboard, one that is not well supported by FreeBSD.
 

scrappy

Patron
Joined
Mar 16, 2017
Messages
347
Or it could be that pfSense does not use ZFS
The latest release supports ZFS if the user specifies it during installation.
 
Status
Not open for further replies.
Top