the_larizzo

There was a feature request to allow the changing of the starting block but there hasn't been any traction. allow-different-starting-block-for-cache

I like the smaller font hah... Like you said they can't win for stuff like that.

How do you validate the starting block?

Is there a reason they can't be trimmed with the LSI? It's some sort of limitation?

I just bought an LSI SAS 9211-8i and was wondering how I should wire my drives. My drives: 4x 2tb and 1x 2tb parity 2x 250g SSD Should I connect everything to the LSI SAS 9211-8i or should I connect some to the on board SATA controler? It's also a sata 3 6Gb/s. If I do connect some to to the onboard what should I connect? Or am I over thinking all this?

Thank you for the quick response!

I was looking at buying a sas9201-8i off ebay but the cheapest ones all have low-profile brackets. Are all PCI card brackets the same screw placement? Can I just take one off a card I have at home and put it on?

Did you reboot before taking the diagnostics? It's a fresh syslog for a few minutes ago. You'll have to see if you get an alert again then do a diagnostics. Is your server open to the internet (ssh or web)? If it is this isn't a great idea. EDIT: Saw you said you rebooted above, so you'll have to wait and see if you get failed logins again.

Is it only me or the containers don't show any disk activity is this something I can enable somehow? Or does anyone know of another way to monitor individual container IO?

Has anyone tested since moving to 6.4.0_rc15e (Kernel: Linux 4.14.4-unRAID x86_64)? Wondering if the issue is resolved.

I ended up having to fallback to 6.2.4. Server would lock up every 2 days, XFS only.

This is happening to me also but all my filesystems are XFS. My server with run for about 2 days then the load goes through the roof and I can no longer run any commands or shut off. I have to hold the power button to restart.

I'm using AMD cpu and I'm seeing 4 cores. Check the bios to make sure there's not some sort of power feature that disables cores enabled. EDIT: Someone seems to be having a similar issue on 4.4 kernel with proxmox so maybe it is a 4.4 kernel issue. https://forum.proxmox.com/threads/missing-cpu-cores.27219/

While LT states that hardlinks do now work on user shares it is still a new feature with not a lot of evidence as of yet as to the stability or usability of that feature. For the immediate future you'll be safest putting docker appdata directly onto a disk share. Sent from my LG-D852 using Tapatalk Although if it's not used then any remaining issues won't get found. I like to live dangerously so I'll try it out... I do have daily backups anyway. So I would just do a move from my disk appdata to the /mnt/user/appdata and point my containers correct?

Can someone clarify for me what I should be doing for Docker and VMs in reference to the shares? It was my understanding that I should map docker .img and appdata to a disk directly and not use user share as it can cause issues, is this correct? Or should I use user share and create hard links? I'm confused now ha. I'm not using a cache drive btw.