JorgeB

Please post the diagnostics: Tools -> Diagnostics (after booting with v6.7)

Like @Squidmentioned FCP only started testing for this now, write cache was already disable, you just didn't know.

Sorry, didn't notice, that's one of the problems with posting in an existing thread. Not that I know of. So you're saying write cache was enable on those disks before v6.7? Or that yo never got a warning from FCP before?

See first post on this thread, assuming it's a SATA disk.

Yes, AFAIK this is a disk setting, not kernel related

You're not the first where hdparm fails to enable it, but IIRC just second one, the other user tried different controllers and didn't make a difference, but it won't hurt to try.

No, some drives come with it disabled, mostly enterprise drives, though it appears to be happening with more and more drives recently.

Yes: https://forums.unraid.net/topic/61996-cron-jobs-notify/?do=findComment&comment=607842

The SMART test aren't failing, the ones complete did so without error, maybe an issue on how Unraid retrieves the info: # 1 Background short Self test in progress ... - NOW - [- - -] # 2 Background short Completed - 174 - [- - -] # 3 Background short Completed - 155 - [- - -] # 4 Background short Completed - 51 - [- - -] # 5 Background long Completed - 29 - [- - -] # 6 Background short Completed - 22 - [- - -] # 7 Background short Completed - 0 - [- - -] # 8 Background short Completed - 0 - [- - -] # 9 Background short Completed - 0 - [- - -]

Looks fine to me, likely some Unraid bug relating to SAS drives, and without the type 2 protection they should be usable now.

Marvell/VT-D issues are nothing new, see for example this thread, some users are more affected than others, it might get better or worse with any newer kernel, nothing that LT can fix directly, anyone than can afford to get them replaced with for example an LSI HBA should.

It's because of the Marvell/VT-d issue, see here:

Don't see any issues with SMART health, but this could be a problem: Formatted with type 2 protection More info here: http://talesinit.blogspot.com/2015/11/formatted-with-type-2-protection-huh.html

It will have more bandwidth, the question is if it's needed, depends on how many disks you have on the expander and if using single or dual link, some benchmarks here.

No, they all work.

No idea then, try it on a different controller if available, I don't remember seeing anyone else with the same issue.

What's the board/server? Is it an HP microserver?

sdparm is for SAS devices only, hdparm for SATA, so hdparm for that one, what error are you getting after running the command?

You can use an Intel SAS expander.

It does, but you need to change the cache slots to 1 first, with multiple cache slots btrfs is the only option. Alternatively you can wipe the ssd with blkdiscard and will have the option to format it after array start.

Difficult to say what caused the corruption but check --repair should only be used if told to do so by a btrfs maintainer, or risk making things worse. Also even if it's now working after a fix you're much more likely to run into corruption again, I would recommend backing up cache, re-format and restore the data, or at least make sure backups are current.

Is the server connect to some sort of power saving plug? It might be set to high and detect the lower power as off and cut off power.

👍

No problem, do you mind confirming if the controller you were using looks like this one: https://www.amazon.de/dp/B07MVYN6X9/ref=cm_sw_em_r_mt_dp_U_5kzZCbKDS7ZGC So I know for the future, as in the syslog it appears the same as this 10 port one: https://www.amazon.de/Informatique-Controller-Professionelle-Komponenten-vorinstallierten/dp/B01ENKHLS6/ref=sr_1_fkmrnull_3?__mk_de_DE=ÅMÅŽÕÑ&keywords=asmedia+10+port&qid=1557240379&s=computers&sr=1-3-fkmrnull

Yep.