Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

32 Good

About FreeMan

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

982 profile views
  1. I would look into that Machine Check Event. I was getting those in my log file a while back and ended up having to buy a new CPU. Bad news, I know, but on the bright side, Shiny new toy!! OTOH, it could be a memory issue.
  2. You may consider posting in the docker support formus for each of the two. You'll probably find more torrent expertise there than in the general forum. You may also try looking at dedicated forums for the two clients for some tips and tricks.
  3. Ahhh... @johnnie.black... Short, sweet, and to the point! Thanks!
  4. I've got 3 smaller, older drives (1 3TB and 2 2TB) that I've migrated all the data off of and have removed from my main server config. They're still physically in the box and connected to power & SATA. After removing them, they'll go into my backup server, the 3TB will be the new parity drive and the 2TBs will be data drives replacing 1TB drives. Before I remove them, should I run pre-clears on any of them in preparation for moving into the new box? I'm not looking to test them for infant mortality, they're well past that, but to just zero them out. As I type this, I don't think there's any need to. Doing the parity swap will overwrite everything on the 3TB drive as the new parity is written there, and doing the upgrade/swap will rebuild the 2TB drives with the existing data from the 1TB drives and zero everything beyond the data that exists on those drives. Am I thinking correctly on this now?
  5. Been using unRAID since 2012 (at least, that's when I created my forum account). I started by migrating 2 1TB drives and a couple of smaller ones out of my overstuffed WinXP machine. Very happy to be here! I have nearly no need for storage space on any of my daily machines, but it's so hard to find drives under 1TB, so mostly they just sit there with lots of empty space... A couple of memories of the early days of my setup: From when there was NO WAY a WinXP box would stay up that long and: One of my first disk config screen shots (so I could make sure I got things back in the right order). (Yes, I'm a bit of a pack rat, why do you ask? It seems this is probably about the same time I started using Evernote, which is where those were stored...) I'm now running two servers (one is a backup and is almost ready to be moved offsite). Congrats and here's to another 14+ more and more pictures of Tom in Hawaiian shirts!
  6. Thanks, @jonathanm, I'll definitely give that a shot!
  7. I'm generally the family IT guy, as I'm sure many of us here are. My in-laws took a non-functioning PC to their local IT shop who told them that it was infected with something and that their best bet was to replace the machine. Not believing that for an instant (it is an older CPU, but for solitaire, a bit of web browsing and writing a journal, it's more than sufficient), I've now got the machine and want to investigate. Here's my game plan. Please shout down anything that sounds like it has potential for screwing up my other machines at home: I've got a Win 10 VM on my server - it's currently installing all the latest updates, then I plan on installing an anti-virus and a couple of my favorite anti-malware apps. I'll shut down the VM and make a backup of the .IMG file I'll pull the infected drive from the IL's machine and plug it into my UNRAID server via USB dock. I'll mount the drive with Unassigned Devices I'll disable networking on the Win10 VM I'll map the UD drive to the VM (will this work with networking turned off?) I'll run the AV against the contents of the drive, looking to clean up and recover as many documents as possible and move them to the UNRAID server. I'll make a dedicated share that none of my other Windows machines can access. Once I've recovered as much as I can from the drive, I'll unmount it from UD and run a pre-clear on it to completely wipe it. Once it's cleared, I'll put it back in its original home, install Win10 on it and replace all the recovered documents I'll refresh the VM from the .IMG backup. I know that none of the Windows viruses that may be on the hard drive will have any impact on UNRAID, since they're not designed to run in a *nix environment. My concern is them scanning the network and finding my other Windows machines and/or the UNRAID shares while I'm doing this. A couple of thoughts on risk mitigation: Shut down all other Win machines while I'm doing this (AARGH!!! living without a computer? What am I supposed to do, talk to my wife?? ) Mount all my user shares ReadOnly to prevent the virus from writing anything to any of my other files on the server. Give the VM a different network (I use 192.168.* internally, change the VM to use 10.* or 172.16.*) so it can't talk to anything else on the network. If I do this, would it still be able to talk to UNRAID to access the UD mounted drive? I've only got one NIC in the server. If anyone has any other suggestions or sees any issues with any of the above steps, I'd be most grateful! (Plus, once I do this and get the MIL used to using Win10 instead of the Win7 that's on this box, maybe I'll be able to convince her to upgrade the WinXP box. Yes, XP. No, she's not a big fan of change...)
  8. Don't move data from /mnt/disk1/MyShare/... to /mnt/user/MyShare/... (or vice versa) That is considered mixing drive shares with user shares and it just doesn't work out well at all. You can go from /mnt/disk1/MyShare/... to /mnt/disk2/MyShare/... or /mnt/user/Share1/... to /mnt/user/Share2/... without problem, using whatever tool (Krusader/Dolphin/MC/command line/etc) you'd like.
  9. As I recall, there was a flurry of releases around 6.5.x - 6.6.x, and many of them dealt with security issues that were being discovered and patched in the Linux kernal and other core systems that Unraid relies on. I too was a bit surprised by the flurry, but I dutifully installed them because I've got a lot of data that's very important to me on my server and wanted it to be as safe as possible. Currently, I'm running 6.6.6 and my uptime is 44 days. 6.7 will be out soonish, and I'll install that with the associated reboot. I'm not getting the 130-150 days uptime that I had in the 5.x days, but, things are getting patched more quickly, so it's a trade of worth making, to me. Also, the update process is so simple, it's really not a hassle. I don't run any of the betas or RC's because I'm not interested in messing around with my one, production level, server. If I had the collection of hardware that some folks around here had, I'd probably run an RC on one or two boxen, as well. My 2 cents worth.
  10. @limetech and @bonienl - I didn't get a chance to respond in the RC3 thread. I am disappointed with the icon decision, but I understand your reasoning. I greatly appreciate that you took time to look at it and to respond with your reasons why, instead of just ignoring it and or silently changing without explanation. This is the kind of responsiveness and support that helps make this the great product it is. Life goes on - this is the last you'll hear from me about it. I promise!
  11. Thanks for the little tweak, @bonienl! I really appreciate you adding that option. I'm a little confused by the fact that you've deleted your post and crossed out all the follow ups. I hope this is still in the works, but I'll live if it isn't.
  12. No worries at all! Maybe just something to keep in mind in the future - not everyone is instantly in love with the latest design trends. I'd assume all the old, colorful icons still exist, maybe ship them (or host them somewhere) and allow for skinning options. The icons are certainly not a show stopper, even though I don't like them. I've got your attention, I'll consider this a seed planted, maybe this will have a small impact on the next GUI update. Maybe not... I've never been anything but pleased with Unraid, the upgrade process and the support. The only issues I've ever had with it have been of my own doing. (It's not your fault I deleted 11TB of data before I realized I'd screwed up )
  13. Fair enough. At least I know it was noticed! I expressed my opinion, a couple of people agreed with me, and now I'll move on with life.
  14. So I need to set it to cache-yes, run the mover, then set it to cache-no to prevent new files from being written. Got it. Mover is running now. Thanks!
  15. I got a notification from FCP that I have files on my cache drive that haven't been migrated to the array. I have the mover scheduled to run because I got this warning. Initially it wasn't scheduled because I hadn't set up any of my shares to use the cache. I turned it on briefly for one share, then turned it off. I have logging enabled on the mover. When I run the mover, nothing is logged and nothing seems to get moved. Here's the share showing files on the cache: Here's the shot showing the mover set to log: and here's the log showing the mover run: I took the screen shot of the share after the two mover runs. Any suggestions on what to do to get these files to actually migrate off the cache drive? backup-diagnostics-20190210-1615.zip