tucansam

Members
  • Posts

    953
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

tucansam's Achievements

Collaborator

Collaborator (7/14)

14

Reputation

  1. 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.
  2. 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.
  3. 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.
  4. 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.....
  5. You want the full log? Because its huge.....
  6. So I set up the syslog server for no reason? Was hoping the logs would show something. Diags attached. ffs2-diagnostics-20220203-2245.zip
  7. Yes. Right at 0900 is when I noticed the array was stopped. Everything up to the point of the server time error looked normal. The log covers more than a week and I didn't want to post it all, but I can.
  8. This has now happened again. Array stopped on its own at some point during the night. The GUI worked, however restarting the array had no effect (it tried, the web interface allowed me to click the button to start the array, but after several minutes of waiting, it never happened). Rebooting from the GUI had no effect. I had to 'sudo reboot' from the shell, and now its doing a parity check. This is probably the fourth or fifth time now that this has occured. At the suggestion of you good folks, I have unraid logging to a syslog server, so now I have logs after a reboot. Here's a section that looks pertinent: Feb 1 17:47:14 ffs2 emhttpd: read SMART /dev/sdl Feb 1 17:47:33 ffs2 emhttpd: read SMART /dev/sdp Feb 1 17:47:42 ffs2 emhttpd: read SMART /dev/sdv Feb 1 17:47:49 ffs2 emhttpd: read SMART /dev/sdt Feb 1 17:47:56 ffs2 emhttpd: read SMART /dev/sdx Feb 1 17:48:03 ffs2 emhttpd: read SMART /dev/sdu Feb 1 17:48:15 ffs2 emhttpd: read SMART /dev/sdj Feb 1 17:48:24 ffs2 emhttpd: read SMART /dev/sdb Feb 1 17:48:37 ffs2 emhttpd: read SMART /dev/sdc Feb 1 17:49:48 ffs2 emhttpd: read SMART /dev/sdw Feb 1 18:37:55 ffs2 ntpd[1686]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Feb 1 18:37:55 ffs2 rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] Feb 1 20:33:05 ffs2 emhttpd: spinning down /dev/sdr Feb 1 20:33:05 ffs2 emhttpd: spinning down /dev/sdq Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdm Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdh Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdj Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdg Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdw Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdd Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdt Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sde Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdu Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdb Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdx Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdf Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdv Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdc Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sds Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdn Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdl Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdi Feb 1 20:33:12 ffs2 emhttpd: spinning down /dev/sdp Feb 2 03:00:01 ffs2 CA Backup/Restore: It doesn't appear that the array is running. Exiting CA Backup Feb 2 07:00:01 ffs2 crond[1707]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null Feb 2 09:04:10 ffs2 webGUI: Successful login user root from 192.168.0.105 Feb 2 09:04:28 ffs2 emhttpd: shcmd (874446): /usr/local/sbin/set_ncq sdq 1 Feb 2 09:04:28 ffs2 kernel: mdcmd (37): set md_num_stripes 768 Feb 2 09:04:28 ffs2 kernel: mdcmd (38): set md_queue_limit 80 Feb 2 09:04:28 ffs2 kernel: mdcmd (39): set md_sync_limit 5 Feb 2 09:04:28 ffs2 kernel: mdcmd (40): set md_write_method Feb 2 09:04:28 ffs2 emhttpd: shcmd (874447): echo 128 > /sys/block/sdq/queue/nr_requests Feb 2 09:04:28 ffs2 emhttpd: shcmd (874448): /usr/local/sbin/set_ncq sdp 1 Feb 2 09:04:28 ffs2 emhttpd: shcmd (874449): echo 128 > /sys/block/sdp/queue/nr_requests Feb 2 09:04:28 ffs2 emhttpd: shcmd (874450): /usr/local/sbin/set_ncq sde 1 Feb 2 09:04:28 ffs2 emhttpd: shcmd (874451): echo 128 > /sys/block/sde/queue/nr_requests Feb 2 09:04:28 ffs2 emhttpd: shcmd (874452): /usr/local/sbin/set_ncq sdf 1 Feb 2 09:04:28 ffs2 emhttpd: shcmd (874453): echo 128 > /sys/block/sdf/queue/nr_requests Any ideas?
  9. Not sure what is happening. Don't think its a power issue (as in, not a loss of power). Came home to no shares, array stopped. Uptime for server is 1 day. Looks like /var/log/syslog starts just after 1PM yesterday. Second time this has happened in a few weeks or so. Nothing has changed; I'm working on other projects and unraid has been left to its own devices for months now, aside from docker and plugin updates. Shutdown was unclean, as soon as I entered my key and started the array, it started a parity check. I posted about this before but can't find the thread... Someone posted a way to persist log info after a reboot so I can post it the next time it happens. If that person would be kind enough to explain it again, I'd like to see if this happens a third time..... Thanks.
  10. Yesterday's parity check was running fine when I went to bed. Woke up this morning to a server that was running, but whose array had been shut down. Parity check bubble in the upper right corner of the browser window said it completed with errors, but couldn't give me specifics. I entered my passphrase and started the array, which took a really long time to come online. Now another (automated, I assume due to an unclean shutdown?) parity check has begun. Diags attached. sat_ffs2-diagnostics-20211218-0827.zip
  11. Errors were found but SMART says "passed." I remain confused. SMART report after extended test attached. ffs2-smart-20211019-1731.zip
  12. Up to 454 rear errors now. Running extended test as we speak.
  13. Just finished a parity check over the weekend and now this. Diags attached. ffs2-diagnostics-20211018-1829.zip
  14. OK I'm just doing them in the order that the GUI is popping up the options........