tucansam

I've been running the same two USB sticks for my Pro licenses for a long, long, long time. I remember 5RC2 as a version from that time period, and probably was messing with it earlier than that. I am about to do the first major server upgrade (MB + CPU) of one my server's lifetime's, and I might as well move to brand new USB sticks so I don't have any unfortunate failures, given their age. What is the easist/least risky way to move to new USB sticks?

Thank you. Yes, I have an old pcie-1x NVS200 to use as a video card in that server, unless the 1050ti would be the better option. Was just trying to figure out if the 9700 would be better served by giving it a higher-end video card.

Gang, I am going to be upgrading from an i7-2600 to an i7-9700F. I'm upgrading a couple of other systems too, and will have a GTX 1050ti laying around unused. From the standpoint of Plex transcoding, 1080p and possibly 4k, will the 1050ti have an appreciable impact in helping, or is the 9700F sufficient enough on its own? I have several family members who stream 1080p content and often share my 10mbps upstream connection, so I have streams limited to 3-4mbps. As such, as soon as I get three or more transcoding, my i7-2600 pegs. I know the 9700F is a huge upgrade, I'm just wondering if the 1050ti is worth hanging onto and putting in my unraid server for Plex. If so, I'm not sure how to enable its use in the docker container. Thanks.

Thank you. This explains why my console, which I have probably used ten time in 12 years, went from regular old text like we've had since the 80s to some high-resolution colorful screen config with fancy fonts. I still didn't get a GUI, but rather just the typical shell, but it looked nice, I'll give ya that. I'll wait til my new hardware gets here and plan an upgrade once its in place. The little i7-2600 has served me well, but adding family members to Plex for remote streaming is showing the system's age a bit. I am running a 16-port SATA controller and an expander to an external storage system. I hope those drivers aren't the problem.

Do I use the integrated GPU, like for Plex? No, not that I know of. I'm not sure how to black list it. I'm on an i7-2600 and have an i5-9400 + 300 series MB on the way. Will upgrade the system to more modern hardware and then try the unraid update again.

Going on two days of uptime. So, incompatible hardware with the new kernel, then???

6.9.2 is back and now has going on 24 hours of uptime. Which is sad because I may never be able to upgrade the unraid version again.

I just downloaded it as well. Gonna just go with defaults?

That's the only stuff in the syslog. I'm going to look into downgrading back to 6.9.2.

Came home to a crashed server. -- pi@pihole:/var/log $ more ffs2.log May 31 04:32:29 ffs2 rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="15169" x-info="https://www.rsyslog.com"] start May 31 04:36:00 ffs2 root: Fix Common Problems Version 2022.04.14 May 31 04:43:48 ffs2 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update fix.common.problems.plg May 31 04:43:48 ffs2 root: plugin: creating: /boot/config/plugins/fix.common.problems/fix.common.problems-2022.05.30-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/Sq uidly271/fix.common.problems/master/archive/fix.common.problems-2022.05.30-x86_64-1.txz May 31 04:43:48 ffs2 root: plugin: checking: /boot/config/plugins/fix.common.problems/fix.common.problems-2022.05.30-x86_64-1.txz - MD5 May 31 04:43:48 ffs2 root: plugin: running: /boot/config/plugins/fix.common.problems/fix.common.problems-2022.05.30-x86_64-1.txz May 31 04:43:49 ffs2 root: plugin: running: anonymous May 31 07:00:11 ffs2 crond[1022]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null May 31 07:07:46 ffs2 emhttpd: spinning down /dev/sdc May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdg May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdw May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sde May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdu May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdb May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdx May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdv May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdo May 31 07:07:50 ffs2 emhttpd: spinning down /dev/sdi May 31 07:07:54 ffs2 emhttpd: spinning down /dev/sdm May 31 07:07:54 ffs2 emhttpd: spinning down /dev/sdj May 31 07:07:54 ffs2 emhttpd: spinning down /dev/sdd May 31 07:07:54 ffs2 emhttpd: spinning down /dev/sdf May 31 07:07:54 ffs2 emhttpd: spinning down /dev/sds May 31 07:07:58 ffs2 emhttpd: spinning down /dev/sdk May 31 07:07:58 ffs2 emhttpd: spinning down /dev/sdh May 31 07:07:58 ffs2 emhttpd: spinning down /dev/sdl May 31 07:34:06 ffs2 emhttpd: read SMART /dev/sdh May 31 10:14:01 ffs2 emhttpd: spinning down /dev/sdt May 31 10:14:01 ffs2 emhttpd: spinning down /dev/sdr May 31 10:14:01 ffs2 emhttpd: spinning down /dev/sdq May 31 10:26:25 ffs2 emhttpd: read SMART /dev/sdt May 31 10:26:25 ffs2 emhttpd: read SMART /dev/sdr May 31 10:26:25 ffs2 emhttpd: read SMART /dev/sdq May 31 10:52:49 ffs2 emhttpd: spinning down /dev/sdh May 31 12:04:09 ffs2 emhttpd: read SMART /dev/sds May 31 12:19:30 ffs2 emhttpd: read SMART /dev/sde pi@pihole:/var/log $

Windows. Browsing directories with massive amounts of files, or massive nested directories, or both, has always been an issue.

Froze again overnight. I set up the syslog server, but the last time that was suggested, for another problem, it generated zero useful info. I've re-started a file copy from a local host to unraid that died during the freeze. 355KB/s.

Well its been up for a while, knock on wood. But copying 80MB of files to a share took 22 minutes......

Up 18 mins this time, then hung. Can I roll back to the previous version of unraid without destroying everything? Hopefully its better than a Windows rollback..... ffs2-diagnostics-20220530-1830.zip

Since Day 1, more than ten years ago, unraid has never handled huge amounts of files well. I have massive collections of music, tv show episodes, and family pictures spanning a century. Unraid has performed slowly when accessing them since the very beginning.

Here's a photo of what the screen looked like before I had to power off/on. Totally frozen, no movement, KB dead, and showed an uptime of 17min when it froze.

Has now hung a second time, as of this moment, 22 minutes after I posted my last message. ffs2-diagnostics-20220530-1741.zip

Upgraded to Version: 6.10.2 yesterday. Less than 24 hours later the server hung. I couldn't even get Num Lock to work on an attached KB, or a an attached monitor to wake up. Totally brain dead, power only lighting lights and fans. Power cycle, stopped the parity check. Now totally unable to ssh in ("Couldn't agree on a host key algorithm" was the error from Putty) and copying files to the server is going between 256Kb/s (not a typo) and 1.74Mb/s. Any suggestions?

Not sure what all of that means. I just have a ton of files from old dvds and blurays that I ripped, and would like to be able to take some load off my CPU when three or four folks jump on to stream remotely.

Guys, I have a GTX750ti that is about to be replaced. Thrown into an i7-2600 unraid/plex server, would it help with plex transcoding, particularly taking 1080 streams and transcoding to 720 for remote users at 2-4mbps? Thanks.

My server seems to be rebooting on its own, has happened four times now. Set up a syslog server to try to track it and it provided zero useful information. Not sure what to make of it. When will the next unraid version be available? There hasn't been a new version in quite a while. Thanks.

Any more ideas guys?

Yeah, for sure cooling it fine. The main server's PS is a bit old, been running for years. But its a bulletproof Corsair model and i've got no indications of power issues. Tons of drives and even during parity checks everything just hums along, have never had issues before. The last major change was the addition of six disks on an SAS expander. But now that I've added those disks to the array, I can't exactly undo it if it broke the system somehow.....

You want the full log? Because its huge.....

So I set up the syslog server for no reason? Was hoping the logs would show something. Diags attached. ffs2-diagnostics-20220203-2245.zip