Raycaster

Members
  • Posts

    51
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

Raycaster's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Thank you very much for the replies, appreciated big time. Yes, I simply swapped hardware and everything worked great. OK, after the backup is done I will remove the array and cache, format drives and M.2 and copy media back on. I will do a New Config with the formatted drive, add the M.2 as the new cache and build the parity drive. As mentioned, this is just a basic media server with PLEX and hoping Unraid will enjoy the extra RAM and the i7 maybe provide some hardware encoding for PLEX.
  2. I recently was donated a i7 6700k setup with 32G ram and 256G M.2 drive. Replacing AMD A6-6400K 16G Ram. Currently I have Unraid 6.8.2 - 4T Parity + 4 @ 4T NAS Drives + Cache Drive (old 500G laptop drive - no idea why I did that...) - It has worked fine for 4 years plus... I basically just use Unraid for PLEX. The array is being backed up slowly to a 12T USB3 external so its giving me time to think of a clean REDO. I have another backup also. Some way or another 3 of my array drives are BTRFS and 1 is XFS, so I was going to preclear and format the drives to BTRFS for a fresh start. Although the M.2 is only a 256G Samsung EVO I was going to use as a cache but unsure of filesystem to use. I could go grab a 500G SSD but well... the M.2 is there free. My questions are: 1) Any advantages to starting right from scratch (Re-Install Unraid to a new USBThumbdrive and start over? 2) When removing drives from the array config is there a proper procedure to reformat? I really want to "re-load" the array to balance them and the time spent is no concern as this is purely a hobbyist machine and can be down for extended days. 3) Just stick to BTRFS across all the drives? I may use VMs later but prime use is just PLEX. 4) Is the M.2 256G cache too small or fine for my use? Thank you for your time.
  3. Thank you for the reply, unfortunately it still sees all past servers. 1) Delete Plex Docker 2) Run CaClean 3) Delete all plex related files in /boot/config/plugins/DockerMan/templates-user. Start a fresh Plex Docker and it still see's past installs that don't work.
  4. Hi Guys, simple question. Couple of days ago I got the "no soup for you" and never could figure out the reason. Gave up and deleted the Plex Docker and used CaClean to hopefully wipe and cache left over. Everytime I try to start a fresh Plex docker install I end up with my past servers included with bad paths etc. and a big mess. Just want to start from scratch and rebuild the libraries. What files need deleting that I'm missing? Possibly on boot USBkey? Thank you ahead.
  5. My Unraid has run smooth for years but I have a few used mother/cpu combos that would be alot stronger at encoding etc. for Plex. I dont have anything else running - no vms etc. I have read many threads concerning just swapping out mb/cpus with no worries but still hesitant about screwing up. I have read that Unraid will sort the drives so no need to worry about hd order. ok, sorry for the "hand holding" but is it that easy, just swap mb and replug everything in and expect no problems? Thank you for any replies.
  6. Squid, thank you very much. I have 16G of ram but it is possible I mucked the paths up and was transferring to ram instead of the USB Thumbdrive. Thank you for lending your expertise. Again I am reminded that there is a difference between "following a tutorial" and "LOOSELY following a tutorial"... damn getting old. Machine seems very happy with no errors after a reboot.
  7. I just wanted to transfer files from unraid to a USB Key and followed a Krusader tutorial with unassign devices etc. It never really worked as UnRaid always saw the USBKey as a 8G instead of 32 so I just transferred over the network. no problem. I installed the Krusader and unassigned plugin. The next day UnRaid reported "Rootfs file is getting full (currently at 100%) problem so I removed Krusader hoping (praying) this would fix the problem some how. Its a few days later and the problem remains and I'm hoping this is just a noob screw up that is fixable. Again, any help would be much appreciated.
  8. Thank you for the reply. I uninstalled CA Auto Update Applications CA Backup / Restore Appdata CA Cleanup Appdata And then re-installed. Everything is always updated asap
  9. UnRaid has been awesome for me and I went ahead and installed a UPS to eliminate some of the unexpected shutdowns in our area. With the UPS setup I turned on email notification and again everything runs smooth. Unfortunately I'm now getting the email at midnight daily: Subject: Cron for user root /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >dev/null 2>&1 Message: /bin/sh: dev/null: No such file or directory Any help would be appreciated, thank you.
  10. Turl - Moved 2nd Parity drive to Array. Operation success - perfect. John_M. - The forum page has the procedure for "How do I replace/upgrade my single cache device? (unRAID v6.2 and above only)" but at the bottom of the page also has FAQ on Can I replace my cache device with a smaller one? "The procedure I pointed you to will work as expected if the amount of data you have on your original cache disk will fit on your smaller new one." so as long as I follow: Stop all running Dockers/VMs Settings -> VM Manager: disable VMs and click apply Settings -> Docker: disable Docker and click apply Click on Shares and change to "Yes" all cache shares with "Use cache disk:" set to "Only" or "Prefer" Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page When the mover finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share) Stop array, replace cache device, assign it, start array and format new cache device (if needed), check that it's using the filesystem you want Click on Shares and change to "Prefer" all shares that you want moved back to cache On the Main page click "Move Now" When the mover finishes re-enable Docker and VMs Can't thank you guys enough for the help... (spoon feeding).
  11. Looking over the replacing cache drive guide I noticed in my haste that did not follow the guide at the bottom first as not only was I replacing the cache drive but I was replacing it with a smaller drive. 500G Momentus - 128ssd. Wondering if that contibuted to the parity problems?
  12. Again, thanks for all help. Yes I have notifications setup. I have not tried to downsize to the 128SSD after the original failure. I do realize I have to move the plex info first from the cache drive. I will try again after a more diligent search on these forums for the proper procedure. I'm also thinking of going back to a 1 drive parity instead of 2 and putting the 2nd 4T parity drive into the array as space is getting tight and the wallet seems closed to a new drive...
  13. Parity is valid Last checked on Sat 14 Jan 2017 07:40:26 AM EST (today), finding 0 errors. Duration: 10 hours, 2 minutes, 18 seconds. Average speed: 110.7 MB/sec
  14. I am sorry, no I don't believe I performed another parity check since.