SATA SSD for boot

[HoneyBadger]

thank you all!, so its clear that the WD green SSD are no good for boot.
Since I already have the WD greens, are they good for slog or l2arc? or even as a data volume?

Fine for L2ARC (although your workload may not benefit from it) or as data vdevs, but not as SLOG.

 

[pro lamer]

Fine for L2ARC (although your workload may not benefit from it) or as data vdevs, but not as SLOG.

What way is it possible? Don't they have firmware bug like SanDisks utilizing the same silicon motion controller?

They seem to have a firmware bug in newer versions

Why doesn't the bug make the SSDs useless in FreeBSD at all?

Is it because we can disable TRIM support on regular pools and not on the boot pool? (I wild guess since I don't know if we can disable TRIM on boot pools or not)

Sent from my phone

 

[Ericloewe]

It should be possible, at install time.

 

[HoneyBadger]

What way is it possible? Don't they have firmware bug like SanDisks utilizing the same silicon motion controller?

Why doesn't the bug make the SSDs useless in FreeBSD at all?

Is it because we can disable TRIM support on regular pools and not on the boot pool? (I wild guess since I don't know if we can disable TRIM on boot pools or not)

Sent from my phone

According to a user comment in the bug report, the corruption doesn't seem to manifest itself when the drives are use for L2ARC:

https://redmine.ixsystems.com/issues/35065?next_issue_id=35062&prev_issue_id=35068#note-22

Though you're right, it might be an issue with them as data vdevs.

 

[kilem86]

Hi All,
What do I look for in a SATA SSD to be used as boot disk in freenas?
I recently built a freenas server using a 120 GB WD green ssd for boot. I got checksum errors and a degraded boot volume almost immediately after initial boot in freenas. I learnt from this forum that some models of ssd have a firmware conflict with freenas. So I was wondering what model/brand of SSD I can use for boot volume in freenas?

I have the same problem, with the same SSD(SSD 120GB WD Green), just install the system, and the boot pool going to degraded state... it,s any posibilities to change the firmware into the SSD?

 

[sretalla]

This is the well documented TRIM problem. Either replace with a different SSD or disable TRIM.

 

[kilem86]

thanks so much for help, and quick answer, im going to try disable trim

 

[mvcad]

Though you're right, it might be an issue with them as data vdevs.

Well I decided to replace the motherboard on my FreeNAS at home and to my surprise I found a 250GB WD Green SSD that I ahve been using as a data pool for my Jails. It has been a couple of years now with no issues at all, so maybe the problem is only when we try to use them as boot devices.

 

[sretalla]

250GB WD Green SSD that I ahve been using as a data pool for my Jails

Two possible explanations I can think of...

You don't have a periodic scrub job configured for that pool (and never ran a manual one, boot pool scrub is automatically generated).

You have somehow disabled TRIM on your system.

I would suggest that the first option is the likely one.

I'm not sure if you are getting away with it because no scrubs have been run or if you just don't see the file corruption that is there without the scrub to tell you.

 

[mvcad]

Well I wouldn’t know how to disable trim. I did remember disabling SMART on that ssd though. And also I get constat email notifications that scrub has finished. Weird but as long works I am happy.