Disk Error on a new SSD

[HisEvilness]

Hello,

 

I am running UnRaid Beta 6.9.0-beta30(Registered Basic) on a MSI MPG Z490 with a 10600K and 32GB of DDR4 Ram. After 24 hours my Disk 1 that is an SSD of 1Tb get's a write error but after a reboot everything is fine. This stops normal operations and the Shares disappear. I have replaced the SATA cable what is a advise from another post i saw on the matter. While this is not a big deal i get the feeling i might have configured the SMART setup not entirely correctly. I did a short and a long SMART test on the drive and it returns no errors. The mechanical hard drives( 2 x 6TB and 1 x TB) do not have any errors the entire time it is simply the SSD that has this problem. Anyone any insight on how i can prevent this?

 

I am planning to add a Parity Disk and  another SSD but i am waiting for black friday to snipe some good deals or at least i hope.

 

Cheers,

[JorgeB]

When this happens again download diagnostics (tools -> diagnostics) before rebooting and attach them here.

[HisEvilness]

1 hour ago, JorgeB said:

When this happens again download diagnostics (tools -> diagnostics) before rebooting and attach them here.

Okay i will wait for this to happen again and then follow your instructions.

[trurl]

Do you know that SSDs in the parity array can't be trimmed and can't be written any faster than HDD parity?

[HisEvilness]

On 10/23/2020 at 2:33 PM, trurl said:

Do you know that SSDs in the parity array can't be trimmed and can't be written any faster than HDD parity?

I was thinking about getting a WD Blue 6TB as parity with 256 cache, or something equivalent or with 8TB. SSD is to work from for loading server files not really intended to parity but perhaps as cache drive if that is worth it. Nothing is set in stone as i am getting used to the new OS and just finding my way around it before making things permanent.

 

Moments ago the disk write error came back as  requested the output file is attached to this post.

unraid-diagnostics-20201024-1613.zip

[trurl]

SSDs are commonly use in cache pools. SSD in an array with HDD parity has the disadvantages I already mentioned.

[HisEvilness]

42 minutes ago, trurl said:

SSDs are commonly use in cache pools. SSD in an array with HDD parity has the disadvantages I already mentioned.

My bad i was referring to the cache on the drive itself refering to this drive: https://shop.westerndigital.com/products/internal-drives/wd-blue-desktop-sata-hdd#WD60EZAZ and just using the SSD's as storage for various shares like a minecreaft server i am helping out with. Some of the ISO files for VM's etc. Using HDD's for large volume storage that does not per say needs a lot of read/write speed as well as parity drives. I got room for 5 more HDD's and 7 more SSD drives.

[trurl]

6 minutes ago, HisEvilness said:

My bad i was referring to the cache on the drive itself refering to this drive

I understood what you were referring to. That is not at all related to my post you quoted. I was just saying their are good reasons to not put SSDs in the parity array with HDDs. SSDs are better used as a cache drive, or in a cache pool, not in the parity array.

[HisEvilness]

1 minute ago, trurl said:

I understood what you were referring to. That is not at all related to my post you quoted. I was just saying their are good reasons to not put SSDs in the parity array with HDDs. SSDs are better used as a cache drive, or in a cache pool, not in the parity array.

So besides cache pools SSD do not have a real use(what is fine)So i would have to create a cache pool with the SSD's that ideally would write away the cache on down times? And then move the current allocation on the SSD to a HDD?

[trurl]

Cache can be used however you want. It can be used to speed up writes to user shares, with files being moved to the parity array later (cache-yes). Or it can be used as faster permanent storage (cache-only or prefer). Typically cache will be used for files related to dockers and VMs so they perform better and don't keep parity and other array disks spunup.

 

 

 

 

[HisEvilness]

1 hour ago, trurl said:

Cache can be used however you want. It can be used to speed up writes to user shares, with files being moved to the parity array later (cache-yes). Or it can be used as faster permanent storage (cache-only or prefer). Typically cache will be used for files related to dockers and VMs so they perform better and don't keep parity and other array disks spunup.

Okay good to know i will have to redesign my setup for it to work better, just curious i would need to get a bigger license for unraid anyway but what counts as a device, currently i am looking to have 1 Parity drive, 2 x SSD for the cache pool, and 8 normal HDD's for the Array. 

Edited October 24, 2020 by HisEvilness

[itimpi]

18 minutes ago, HisEvilness said:

Okay good to know i will have to redesign my setup for it to work better, just curious i would need to get a bigger license for unraid anyway but what counts as a device, currently i am looking to have 1 Parity drive, 2 x SSD for the cache pool, and 8 normal HDD's for the Array. 

All attached storage devices (other than the Unraid boot USB drive count) even if they are not being used by Unraid.  In your case that would be 1 + 2 + 8 = 11 devices.

[HisEvilness]

Thanks to everyone  i had to redo my Array but it is now working correctly with a cache drive.