JorgeB

Did you open it already? Is the disk an ST8000DM004 ?

@gfjardimwhen possible please fix the PHP warnings generated by the plugin, I know they don't cause a problem per se but it's a pain to find them flooding various syslogs every day making it much more time consuming to go through them, thanks. Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte12h - assumed 'byte12h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant ID_MODEL - assumed 'ID_MODEL' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 470 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant SERIAL_SHORT - assumed 'SERIAL_SHORT' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 470 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte11h - assumed 'byte11h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte10h - assumed 'byte10h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte9h - assumed 'byte9h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte8h - assumed 'byte8h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte15h - assumed 'byte15h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte14h - assumed 'byte14h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte13h - assumed 'byte13h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Jul 25 21:41:08 Unraid-Plex rc.diskinfo[8419]: PHP Warning: Use of undefined constant byte12h - assumed 'byte12h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663

I also saw that but would expect to be difficult to compile it for unRAID, if you're using compression on the whole disk you can check the global compression with this, e.g.: Total (uncompressed) file size: root@Tower9:~# du -sh /mnt/disk4 1.1G /mnt/disk4 Actual used space: root@Tower9:~# df -h /mnt/disk4 Filesystem Size Used Avail Use% Mounted on/dev/md4 466G 83M 465G 1% /mnt/disk4 To get compression ratio divide the outputs, in this case it's around 13:1

Yes, I used those since I knew they would compress a lot.

I did some testing at work, and since there's not an easy way to check the compress size, I used two empty disks on my work server, both have same 512x2MB text files, these as expected are very compressible and you can see the difference: 1.09GB vs 86.3MB used

It is valid, parity is updated during the format.

No script needed, you just do it one time and it stays on, but it will only start compressing new files added to that share after +c is set, if at some point in the future you want to turn it off use chattr -c, but similarly it will only affect new/changed files.

Just set the share or folder you want to use compression with chattr, just note that since each disk is a separate filesystem it needs to be done on every disk that the share is using (if you want to use compression on all) e.g.: chattr +c /mnt/disk1/Share chattr +c /mnt/disk2/Share etc

This issue also affects the disk temps in the same way, after smart-one.cfg is created with blank temp settings they override the general temp warning, i.e., user stops getting warnings about disk temps which is more serious than the space warnings.

Turns out it was easy to find the problem. If custom disk utilization settings are used unRAID creates the file config/smart-one.cfg, e.g.: [disk1] hotTemp="" maxTemp="" warning="70" critical="90" If you then delete those values on that disk settings page, so it should start using the global settings smart-one.cfg is changed like so: [disk1] hotTemp="" maxTemp="" warning="" critical="" And this is when the global settings for that disk stop working, I'm guessing because the blank values are overriding them.

It works correctly on a new installation, so something else is causing the issue, strange that it happens on 2 different servers, I'll try to find out the cause but it might not be easy so ignore this report for now.

Strange, although you're using a different release I assume nothing was changed for notifications, I'll try to investigate this further on a clean install to try and confirm the problem.

They are, I get them if I use individual disk settings, and I don't think the problem is in my end as I tested on 2 different servers and they behave the same.

USB 3.0 port is not recommended, if you were already on USB 2.0 it can be a failing flash drive (USB 3.0 flash drives are also not recommended as they usually have a much higher failure rate)

You can enable compression different ways, for example remounting the disk with compression enable after array start, e.g. by using the user script plugin, but probably the easiest way is use chattr to set a share (or folder) to compressed, then all files inside that share/folder will inherit compression.

Try a different USB port, preferably USB 2.0

I believe this is the correct one, but never used multiple options

You can use it by adding btrfs to vfs objects on /etc/samba/smb-shares.conf for the share you want to use it then restart Samba: samba restart You'll need to redo it every time you start/stop the array, since it will default to the previous setting.

It should, SAS2008 based controllers don't support trim on most SSDs, SAS2308 and newer support.

ST8000AS002 does make a few click sounds, it's the only model I have, newer models might be different.

Not AFAIK, but you can use btrfs as the filesystem and it does support compression.

You'll need to edit config\domain.cfg on the flash drive and change SERVICE="enable" to "disable", then reboot.

It is, PCIe 3.0 is backward compatible.

Adding vfs objects = btrfs to a btrfs formatted SMB share allows copy-on-write (i.e. instant) copies to be done using windows explorer (on windows 8/server2012 or newer) using Samba's server side copy functionality, obviously as long as the copy is done on the same filesystem, e.g., from cache to cache, disk1 to disk1, etc, this would allow for example to very quickly and easily backup a vdisk before any significant change without dropping to the CLI. Alternatively allow the user to add specific vfs objects to any share using the GUI.