ChatNoir

@Espressomatic, @Miss_Sissy I don't think any of you will convince the other at this point. You both advanced your arguments for the community, and I am sure that it will help other user decide what's best for them. Let's agree that you disagree and move on.

Hi, from your post, it seems you are using Unraid bare metal and Ubuntu in a VM. This section is for installing Unraid as a VM in another hypervisor. If I am right, we will move this thread to a more appropriate section.

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 197 Current_Pending_Sector -O--C- 100 100 000 - 104 198 Offline_Uncorrectable ----C- 100 100 000 - 104 That does not look good. At all. Try running an extended SMART test on the drive.

I would suggest to contact support.

Please use english outside of the multilanguage subforum

26€ for a proper 16 drives controller seems either a super good bargain, or quite sketchy. Your diagnostics might provide more information on how Unraid see your HW.

Not sure what you mean. Plugins are vetted to a point. Can you clarify what you would like to improve or fix ?

If I am not mistaking, there is a log create with the backup. Have you checked the content ? It could point you in the right direction.

I just installed 1.0.1 version and I didn't any alert from ESET.

The amazon link only shows 5 ports.

I've moved it.

If I were in the US I would check https://www.ebay.com/str/theartofserver

Have you updated to the new version that is a few days old ?

I am confused, you talk about 3 Seagate 12TB drives that would be 1 year old. Your diagnostics show 3 Seagate drives but 1x 12TB and 2x 14TB. The 12TB seams to be roughly 1yo, but the 14TB seem quite new. The other 12TB drives are WD and a bit under 2yo.

Can you clarify what version of Unraid you are using ? If memory serves, the 6.8 branch stopped at 6.8.3. Maybe 6.12.8 ?

Limetech propose OEM licenses, so if things are done properly, you might not have to buy a new one. Unless the shop only provides a Trial license and you have to purchase it yourself after that ? You should probably check that with your local shop to clarify things.

Note that it is recommended now to also replace the changes.txt files. Probably only needed if you change version, but I would do it anyway, just in case you are not sure.

This uses a port multiplier and will reduce available throughput. JMB585 is a 5 ports chip and you are using it for 8.

It will depend on the motherboard and how much ports there are but you can check there :

I do not follow many threads, but I do receive notification from subforums and new users posts (moderators thing I guess). You probably already checked your spam folder on yahoo ? It still works fine with hotmail.com (barely more hyped provider )

Not available in the archive https://docs.unraid.net/unraid-os/download_list/ But why not 6.12.13 ?

Don't know about this specific model, but there are advices here :

I did change the location of my music a few months back, not really to save power but to have it more responsive when starting a new playlist. In my case I just put it on my general SSD pool that does: appdata caching transcode tempdir music now It was simpler for me and large enough (4x 500GB in RAID10). The Pool is the best solution in my opinion. Now it would depend on your specific server details to decide if it is a separate pool or something more generic.

There are BTRFS errors : Aug 19 14:06:31 Tower kernel: btrfs_validate_extent_buffer: 1850 callbacks suppressed Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 1 wanted 0xc1a226c5 found 0x6bade2d5 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 2 wanted 0xc1a226c5 found 0xee1c9cd7 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 1 wanted 0xc1a226c5 found 0x6bade2d5 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 2 wanted 0xc1a226c5 found 0xee1c9cd7 level 0 Aug 19 14:06:31 Tower kernel: I/O error, dev loop2, sector 20264160 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Aug 19 14:06:31 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 86, rd 90, flush 0, corrupt 0, gen 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 1 wanted 0xc1a226c5 found 0x6bade2d5 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 2 wanted 0xc1a226c5 found 0xee1c9cd7 level 0 Aug 19 14:06:31 Tower kernel: loop: Write error at byte offset 10375249920, length 4096. Aug 19 14:06:31 Tower kernel: I/O error, dev loop2, sector 20264160 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Aug 19 14:06:31 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 87, rd 90, flush 0, corrupt 0, gen 0 Probably to your docker image. You should delete and recreate it. If it continues, you should do a memcheck.

It would be much easier with the diagnostics. But the I/O and BTRFS errors might suggest an issue with a pool.