5 minutes ago, ConnerVT said:

 

I have to say this is unusual.  Do you use this drive for anything else other than booting your server?  Backup appdata, or have something writing logs to it?  It should be a mostly unused device (since I rebooted 6 days and 6 hours ago, I have 24k reads and 5k writes).

I have two servers and they have both been up approximately 32 Days.   

 

                  Writes      Reads

Server1        6172          949

Server2        4574          662

 

I suspect most of the write activity is the result of Plugin upgrades which have been fast and furious with the required updates for version 6.12.   

I have been doing some network re-configuration this week, and reinstalled some Dockers I broke.  That would account for some of it.

6 hours ago, orlando500 said:

I buy the "best" usb sticks but they tend to last about a year for some reason. So a better solution is on my wish list.

 

What is your definition of "best"?

In the context of Unraid, best typically means USB 2.0, physically large, all metal, low idle power draw, brand name sticks.

 

Very few drives that meet that criteria are still for sale unfortunately.

On 3/21/2023 at 2:43 AM, JonathanM said:

What is your definition of "best"?

In the context of Unraid, best typically means USB 2.0, physically large, all metal, low idle power draw, brand name sticks.

 

Very few drives that meet that criteria are still for sale unfortunately.

I try to buy sticks that are close to your description and also like "best in test" from like spaceinvader etc

I have been sitting out updating my Unraid since 6.9.2 mainly out of laziness and everything working fine for me, but I'm planning to get into its guts to remove my GPU as I do not need it running in there anymore and drawing power for no reason so I was thinking I might as well see about updating unraid itself while I am at it.
Nothing special, one cache SSD, 3 HDDs in the array, a bunch of dockers, most notable probably being Plex and Nextcloud.
Is there anything I should be watching out for when updating to 6.11.5?

5 minutes ago, Crovaxon said:

Is there anything I should be watching out for when updating to 6.11.5?

Should be pretty straight forward, but good idea to read the release notes for v6.10.0 and v6.11.0

I may have overlooked the instructions in the forums but where do I submit my diag zip? I encounted issues running VMs on latest RC so I had to roll back to stable. Here's a snapshot of the error I was experiencing:

 

2023-05-10T19:39:07.746549Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument

 

Rolld back to stable and all is well in the world now. 

 

Edit. 

Disregard. I'm a fool. Got a local issue that may not be related to the RC. I have no shame though. I lost my self respect years ago in the meme wars.

 

Edited May 10, 20233 yr by darthkielbasa

13 hours ago, darthkielbasa said:

I may have overlooked the instructions in the forums but where do I submit my diag zip?

For future reference, simply drag and drop the zip file in the text box or use the link at the bottom of the text box.

Hi all it's been awhile! My server has been running steady for years on 6.5.3. Updated the hardware cpu/motherboard/ram/psu last week and let it run for a week to test all good. Today I updated to 6.11.5 by replacing the bz files on the flash drive. No VM no docker. The server will only boot on safe mode gui. When I try reg boot I get the following error when I try and access from browser. 

 

Warning: readlink(): No such file or directory in /usr/local/emhttp/plugins/dynamix/include/local_prepend.php on line 18

 

Warning: parse_ini_file(state/sec_afp.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/template.php on line 40

 

Please point me in the direction to get this back working thanks!

6.11.5 is a very old Unraid release.   Any reason you did not go the current stable release (7.0,0).   You are likely to get better support if using a current release.

Found this post 

 

deleted dynamic.plg and I can now login! no more errors!