Jetracer

I recently bought a new sas drive, a Seagate ST8000NM0065. It is plugged into an Adaptec 7805 in hba mode. The drive formatted fine and it spun down fine. However it would not spin back up and Unraid disabled the drive. I'm not sure if this is possibly a drive/hba mismatch, I did order another hba to test with. Any help or insight is appreciated. tower-diagnostics-20230730-1935.zip

After disabling the sas spindown plugin and a reboot and rebuild the drive seems to be fine now. Are there any downsides to leaving this drive (and my other sas drive) spun up or should I try another hba card and see if the issue persists.

The drive was purchased knowingly used from a fairly reputable source on another forum. The power on time is high at over 4 years but SMART still shows good, which I know dosen't mean the drive is fine.

I recently purchased a new 8tb drive from a known good seller as well as an Adaptex ASR-7805 card and proper sas cables. The drive in logs is device sdc and is currently disabled and will not spin up. EDC feature is disabled on this drive and low power spinup is not a feature. Attached are the server logs. The 7805 is in hba mode. tower-diagnostics-20230730-1935.zip

Currently on 6.9.2, sata controller passed through to a windows 10 vm. Every 15 minutes or so the vm pauses itself. I originally had this as a vdisk on an unassigned drive. That paused so I thought maybe letting it run on cache, paused. So my last idea was pass through a sata controller that only had 2 ports with the ssd i had dedicated for this vm. It is pausing as well. I have tried the command, btrfs balance start -dusage=75 /mnt/cache during each of these stages. I have the dynamix trim plugin installed seems to be working (cache drive is an u.2 nvme drive). Any help is appreciated. unraid-diagnostics-20200222-0914.zip

I have a windows 10 vm running on an ssd that is passd through by pointing the vdisk location to /dev/disk/by-id/ata/disknamehere. It's up and running fine my only issue is windows sees this as a regular HDD and not an SSD. I tried searching but havent seen any topics regarding this issue. Hoping im just missing something.

So to upgrade our containers should we switch to linuxserver/sonarr:release or just linuxserver/sonarr Current I'm still on linuxserver/sonarr:preview Edit just noticed the line lsio dosent have a stable release yet.

I love Unraid because in a world of overly complicated software, Unraid makes my home server a dream to deal with and maintain on a daily basis. Now if only our cto would get on board at work! One thing I would love to see added, well with the addition of wireguard... and the new login prompt.... well nothing. Unraid has become one of the best pieces of software I have ever used. Maybe a download more storage button 🤣

If we are still using the beta how would we go abouts updating? Backup the config and scripts and uninstall the beta plugin and install the regular?

Thank you, got that setup. Is there a way to backup dockers before deleting the docker.img so one dosent have to completely set up each docker? I've had to set up sabznd, ombi, and the like far too many times to want to do it again.

Appdata was set to prefer, and download. Would it be wise to turn cache off for download, and data where the majority of my data lives? This is primarily a plex server with a few vms for testing/learning. Looking at the link you sent only system and appdata should be set to prefer correct? downloads to cache yes and data to no. My thinking is only during heavy downloads should the cache fill up (roughly 256gb). Normally its a episode of a show or a single movie being downloaded at any time normally nothing at all. yeah im going to set up email notifications now as well.

Logged into my server today as i normal do a few times a week to check on things and fix common problems had a red error saying cannot write to docker image. Clicked on the log and its full of btrfs errors. My docker image is set to /cache and im running two ssd's as cache. I also use cache for downloads and plex transcoding. Not really sure what happened looking for help. I have attached diagnostics. tower-diagnostics-20190623-1836.zip