ucliker

I need help deciphering what these attributes mean in scrutiny. I purchased two Seagate EXOS 8TB hard drives and one (my parity drive) shows failed Read Error Rate. Is this a comparison of data between my drive and Backblaze or is this actually failing? My smart reports all say PASSED. Given that this is my parity drive I would like to know before something really bad happens.

Is this error because I ran mprime?

I woke up this morning to this error "Out Of Memory errors detected on your server". I am running 64GB of ram and don't really have anything crazy running not even VM's. Here is my diagnostic report if anyone could help that would be appreciated. tower-diagnostics-20210319-1313.zip

Squid replied in my other thread. You can use docker-xfs now in unRAID 6.9 rc2. You can change it I the the settings. I plan on upgrading my cache drive anyways tomorrow so I will realign and format it.

tower-diagnostics-20210203-1923.zip Here is my diagnostics

How do I go about changing my docker image from Btrfs to xfs in unRAID 6.9 rc2?

How do I go about changing my docker image from Btrfs to xfs in unRAID 6.9 rc2?

I’m getting constant writes to my cache drive (500GB SSD) and after upgrading to 6.9 rc2 I hoped it would fix it. I have narrowed down the issues to btrfs and loop2 in iotop. My question is why is btrfs showing up when my drive is xfs? Is the docker image or something else formatted as btrfs and if so can it be changed to docker-xfs? Also I have really know idea what loop2 means but I guess its the cache drive configuring and how unraid utilizes it?

I'm not sure if this has anything to do with UD and UD+, I received a notification from Fix Common Problems to install UD+ so I did and now my unassigned SSD will not show up in shares anymore. It's mounted and the share button is on. Any input? The drive is NTFS if that helps.

I love the fact that I can add different drive types without adding pools etc. It would be great if the SSD caching was so hard on the devices and the writes were better controlled.

Thanks, Yes I got it working but I just assumed the "nag" reminder would go away. Thanks for the input though, it was driving me nuts.

I have been trying for days to get the port forwarding message to go away. I have a Frontier router and I have port forwarded many times and this is the only time I can't get it to work. It's driving me crazy!

My unraid system runs flawlessly even with the 6.8.0 update. I wanted to add an NVME PCIE SSD so I can transfer the files from it and format it. Every time I add it to the system my cache SSD (Sata) throws xfs errors and I need to repair it. I'm mounting the NVME as an unassigned device so I'm not really sure whats going on here. The NVME is my old windows 10 ntfs partition which shouldn't conflict with anything.

Every 10Gbit NIC card I've used run pretty hot under load. I just try to add as much airflow to them as possible.

I think adding the correct metrics worked. Since my 10gbe card is directly connected to another card in my workstation unRAID sees that and assumes it needs its own default route. I just set that to metric 2 and my default gateway (192.168.1.1) to metric 1 and it seemed to fix everything. Thanks @bonienl for comment regarding the router setup, that helped. Also thanks @ken-ji for the help with the metrics, the policy-based routing definitely made more sense once I read about it on the Cisco website. I may have had metrics setup prior to upgrading at some point and never changed it back after swapping nic cards or something.