• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by garycase

  1. Thanks. Although I think I'll just stay with doing each disk independently, as that seems safest -- and the shares involved are all limited to only 4 disks, so it's not that hard to do. In any event, everything I wanted to "clean up" is now done -- and the stuff I couldn't do from Windows worked perfectly with MC. Thanks big time for the tip.
  2. MC worked very nicely. It apparently didn't "see" the shares; but if I went to each of the disks that were part of the share and deleted the part of the folder that was on that disk, it did everything I wanted -- the folders are now gone. i.e. the share I was working with ["OSImages to keep for friends"] is on disks 9, 10, 11, and 12. So I went to each of these disks in MC and for those that had components of the folder I wanted to delete I simply deleted them using F8 in mc. Not every folder was shown on every disk; but when I finished processing all of the disks, I went back to my PC and accessed the share and Voila!, the troublesome folders are all gone.
  3. Thanks ... I'll try this tonight. Off to the grocery store for my wife right now, so it'll be a few hours before I can get to this. I presume using mc is a "safer" approach than running New Permissions -- is that right?
  4. Is mc already built in to the system; or do I have to download/install it? [If so, do you have a link?] And can you tutor me through the specific commands that I'd need to delete one of the folders? Perhaps for the one I listed above as an example.
  5. If I type Tools - New Permissions, I get a note that outlines the mandatory need to run this when upgrading from a pre-v5 release, which indicates I should run it on all disks. I don't think I need to do this, as this system hasn't been upgraded in a long time (and it's already on a v6 release). I'm running v6.5.3 (This is an OLD server and it runs rock-solid on that release, so I never upgraded beyond it -- actually I did upgrade to the next version after it, but that caused a couple issues, so I reverted to 6.5.3 and have never changed it since). The hardware is one of Tom's original recommendations for UnRAID -- a SuperMicro C2SEA with 4GB. If I do the Tools - New Permissions should I just select the share that's having the issue [e.g. "Backups"], or so I also need to select the disks that that share is using? Is this likely to mess up anything in that share?? ... i.e. should I copy all of the contents to another system before doing it??
  6. I was cleaning out some old folders on my UnRAID server, and several of them refuse to delete ... noting they need permission from a specific user -- which happens to be the one I'm logged in as. I get a "You require permission from <username> to make changes to this file" message; but I'm logged in as the specified user. It also doesn't work if I log in as root, which I thought might give me more "superpower" privileges. Note I am NOT a "Linux guy" -- I just use UnRAID as a large protected file server for backups and archives. It's been a couple years, but I seem to recall there's a way to do this from the console using a Linux command (I think the last time somebody helped me with this they called it a "machine gun" approach 😀). I'd appreciate it if a Linux person could guide me through doing this. Note the folder names include spaces, so if I need to put things in quotes please include that detail. e.g. one of the folders is: \\media\Backups\OSImages to keep for friends\Johnson - Doug So my question is how do I navigate to this on the console, and what exact command do I type to remove it. Note there are a lot of folders under the "OSimages to keep for friends", and I only want to delete a few specific ones. Thanks in advance for the help.
  7. Yes, it works fine with 4TB drives (and larger)
  8. The old OS's I have are all VM's built with and running under VMWare Workstation on a Windows box. I also have earlier versions of them that I built when I was using Microsoft's Virtual PC many years ago (early 2000's). If you want to build these in UnRAID, you'd need the install media for the OS's.
  9. I also use it on a Windows box --> I have a scheduled task that wakes up at 4:00 in the morning; sends a WOL signal to my backup server; waits 3 minutes to be sure it's had time to boot up; and then runs a SyncBack task to back up my two always-on UnRAID servers to my backup server. After the task completes, it sends a command to the backup server to shut down. Actually, since I switched both of my servers to dual parity, I've thought about changing this task to only run once/week … but haven't got around to doing that 😊
  10. I also have a trusty old C2SEA on one of my servers -- I did the BIOS update YEARS ago with no problem. However, I doubt it really makes a difference at this point -- if a system update was to require a feature not supported by the C2SEA I very much doubt that the 2012 BIOS would resolve that => if that was to happen the only alternatives would be to retire the trusty old C2SEA or to not do any further UnRAID updates on that system.
  11. Just for grins, I used Windows Explorer to access the folder that's giving such crazy results in Windows 10 from Windows 8, Windows 7, Vista, and XP (all VM's) and they ALL show the correct results … and do so MUCH faster than Windows 10. Does anyone know if there's a setting in either Win10 or in UnRAID that will resolve this??
  12. No Plex or appdata info -- just a complete backup of all of the data on our computers … the OS is backed up separately with imaging. Also, note that Windows 7 shows the info correctly … it's only Windows 10 that fails.
  13. I noticed a significant error in the display of a folder size from Windows 10 when I did a "Properties" for one of my large backup folders -- the actual contents are fine, but I got a very incorrect size result. If I look at the folder from Windows 7 and do a "Properties" it displays the size correctly, and also MUCH faster. The correct result is 172GB with 117,583 files in 4,585 folders. Windows 7 takes 20 seconds to display this with a right-click Properties from Windows Explorer. Windows 10 takes 28 minutes and 40 seconds to finish a right-click Properties, and shows a total of 481GB with 666,853 files in 39,195 folders !!! Clearly a completely wrong result. Note that with a much smaller folder, both Windows 7 and Windows 10 show the correct results [ 47.6GB with 49,483 files in 5,578 folders ], but again Windows 7 is MUCH faster at displaying this result [15 seconds, vs. 3 min, 5 sec for Windows 10] I recall another similar issue from some time ago, which was resolved by adding a line to the Samba Extras in the Settings menu [allocation roundup size = 0], but that doesn't resolve this. Any ideas ??
  14. That should do the trick nicely. If you're going to sell your old board, I presume you've confirmed that it's working okay … this discussion started with it not working in the new case -- hopefully that was just a short (perhaps an extra standoff that wasn't removed) or a loose connection. Hopefully you've got that resolved, or will have by the time the new board arrives. … with only 9 drives I'd have probably just kept your old board and connected 3 of the drives via USB3, but the newer board will provide much better expandability. FWIW I also haven't used any USB3 connected drives on my servers, as I have plenty of SATA connections, but my understanding is that UnRAID supports v3 for array drives, and the interface speed for USB3 is well above the max transfer speed for any rotating platter drives. However, since you've already upgraded your case from a DS380 to a CS380 (I had missed that), it really doesn't matter, other than the cost of the new board.
  15. I missed that he'd switched cases. His post of 22 Nov indicated the case was a DS380. Clearly if he's got the CS380 he can switch to a mATX motherboard with no problem … although whether that's necessary or not depends on whether he needs more than 8-10 drives, which could easily be supported with the 6 onboard SATA ports and the USB v3 ports.
  16. I hope that is the case! I hope so too -- and it seems very likely since you've confirmed the PSU is good. Thank you I will investigate this Note that this motherboard will require switching to another case, since it's a mATX motherboard that won't work with your CS380. As I noted earlier, I'd simply use the onboard SATA ports plus the USB v3 ports to connect your disk drives; and the single PCIe slot for your video card -- assuming, of course, that everything is working okay when you re-mount it all in the case after carefully testing it.
  17. Note: I spent a bit of time looking and couldn't find it, but I could swear I've seen a mini-DTX motherboard (just slightly larger than a mini-ITX … and supported by your DS380 case) that has TWO PCIe slots (one x16 and an x1). If you could find one of these, you could use a 4-port SATA controller in the x1 slot and possibly have enough drive capacity, providing the motherboard had 5 or 6 onboard SATA ports. I also thought of a 3rd alternative for option (1) in my previous post … use USB v3 connections to add additional drives beyond the 6 native SATA connections. USB v3 is supported by UnRAID, and the speed of this interface compares favorably to a direct SATA connection. Your motherboard has 2 v3 ports, and you could use a powered USB3 hub if you need more than 2 extra drives. Personally, if you want to stay with the DS380, I'd either simply limit yourself to 6 drives (thus using the onboard SATA ports), or connect any additional drives via USB v3, and use the PCIe port for your video card. This lets you keep your current case and your current motherboard, and should work very nicely.
  18. Definitely sounds like a shorting issue (or a loose connector -- as I noted earlier, be sure BOTH of the motherboard power cables AND both of the PCIe connectors for the video card are firmly connected). As for a new motherboard with 2 PCIe slots -- that's not likely going to be possible if you want to stay with the DS380 case. There are a few options you can consider ... 1 -- Use the PCIe slot for your video card, and don't use the RAID controller. Instead you could do one of the following: => Use larger drives so the 6 SATA ports on your motherboard are enough 😊 => Swap to a different mini-ITX board that has at least one SATA port that supports port multipliers. The Intel chipset SATA ports on your current board do not support port multipliers. 2 - Switch to a case that will support a microATX (or ATX) motherboard … then you could use a motherboard that would provide more PCIe expansion slots and you could use both a video card and a RAID controller.
  19. Agree that the best course of action is to first set up the basics outside of the case -- be sure the motherboard's on a non-conductive surface, and just connect a memory module, the power supply, the video card, and a keyboard/mouse/monitor. If it boots to the BIOS okay at that point, then very carefully move the setup to the case. Be sure you have connected not only both of the motherboard power connectors but also the TWO PCIe connectors to the video card (one 8-pin and one 6-pin). I don't think the power supply's an issue … although its only rated at 450w rather than the 500 recommended for that video card (10% difference is very unlikely to be a problem).
  20. 😊 … agree they're not very cost effective
  21. Interesting. I don't use WMC in a VM, but I have noted that my two servers using older hardware have slower disk performance on the v6.5 versions relative to previous versions, so this may account for the stuttering. Unrelated to that, but a side note for anyone using WMC (or contemplating it) … the discussions earlier in this thread r.e. when the guide will expire are still relevant (i.e. I'd expect the most likely date will be on expiration of Windows 8.1 support, since the guide updates aren't OS-dependent) -- but since the discussions on this thread the development of an alternative guide [ ] has progressed to where it's very stable, and it uses guide data from Schedules Direct, which is not likely to go away anytime soon … so this should allow WMC's effective life to extend well beyond the support end dates for W7 and W8.
  22. You could, of course, simply drop one in your array and use it … if it fails it's no big deal assuming you have a parity protected array (even less of an issue if you're using dual parity). However, current drives easily achieve 5TB (and higher) without reverting to SMR technology, so I'd be more inclined to just get a new drive if you need the added capacity. My most recent array has a dozen 8TB HGST drives that work great.
  23. My first build was an Altair 8080 in 1975 😊. I built several 8080 and Z80 based systems in the late 70's, and a LOT of others since then. I've had a couple of systems that had similar frustrations to what you just went through, but it's been a LOT of years since those issues. In any event, glad you've got this (finally) resolved !!
  24. Hopefully the video issue is the board and not a defective 2176G !! With your luck to this point I'd keep my fingers crossed 😊
  25. Sure hope they're shipping the 2176G by March --- that's when I plan to build my next system and I REALLY want to use that in a setup very similar to what you're put together.