Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

About tscales

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. I have 30 years in IT and it isn't 'bit rot'. Something happened. Either you have a program that opened/closed the file, zeroing it or you're in the early stages of a drive failure. I'd lean towards the latter. Are all the files on one physical drive? What does SMART say?
  2. I don't understand this. If you're backing up the drive mount, it will only backup one copy. The only way you'd be backing up the dupes is if you're backing up the individual drives. Why would you?
  3. I would love this two. I'd make it configurable that I can specify the tier of a drive. My machine supports SSD, SAS and Sata. Within each there are different performance characteristics. I'd also like to be able to do it two ways: 1) Lock a folder to a tier. 2) Have files migrate from best tier to oldest tier based on last access. Haven't used it, it goes to the lowest tier.
  4. My goal is a truly redundant environment. If any component fails, the transition is transparent to any user. I'm so new to Server 2012 and Hyper-V. There are iSCSI targets, SMB shares, etc. etc. etc. So many options and so little understanding
  5. Almost exactly what I ended up with. I have 12 Drives passed through to DB running on Windows 7. Using a Windows 2012 Hyper-V. My only issue now is that I'd like to move the drives to iScsi and you're limited to 2TB per VHD when their CSVs. Another thread
  6. Everything you describe will work just fine, assuming there are not duplicate directories/files between X and Y (since you'll be merging them). Personally it would make me nervous to have two drive letters to the same pool, but pretty sure it works. I don't use XMBC, but I do use BeyondTV. I stream 720P AVI files to as many as 7 concurrent TVs. Works just fine. More a factor of network bandwidth than DB. Go for it. Just do each step and test it.
  7. This isn't directly applicable, but with VMWare and HyperV, I pass the drives through to the virtual host and then run drivebender there. Works fine.
  8. I would rescan my media library, but it doesn't completely surprise me. DB loads after the OS, so if the OS expects the files to be there doing boot, it isn't going to find them. I have to delay my media program by two minutes just to be safe.
  9. Just open up Disk Management and relabel them. DB doesn't care what they're called. You can even move them port to port and DB doesn't care. It is very forgiving.
  10. Well, $Recycle bin is your recycle bin. Don't delete that. System volume info is just that and required by the OS. Has nothing to do with DB. The Backup files are generated by DB. Not sure why, but seriously, would you really want to mess with that. In other words, it is working, so leave it all alone.
  11. I added to another post on ESXi, but since I am using Hyper-V, I thought I would ask my question in a new thread. Right now, I have Windows 2012 Server, with Hyper-V, running on a Dell Precision T7400. It's reasonably powerful: Dual Xeon X5460 Quad Core processors 16GB memory Silicon Image 3124 driving two external eSata boxes (16 drives) Silcon Image 3132 driving a smaller external eSata box (5 drives) Mostly 2TB and 3TB drives, but a smattering of smaller drives for different VMs. So far so good. My implementation was to use passthru on the drives to the VM (W
  12. I'm going to start another thread as I have some questions, but I have DB running on a Windows 7 Pro VM inside Microsoft Hyper-V 2012. I couldn't get ESXi to be stable on my machine -- it just hated my external eSata enclosures. I also had issues with passing the drives through. The only solution I could find was passing the whole eSata card and that was wildly unreliable with inexpensive eSata cards. So, I switched to Microsoft Windows 2012 with Hyper-V 2012. It lets me pass through individual drives. I then pool them with DB in the VM. Works like a champ. I don't feel lik
  13. Check and see if you have two mount points for D:. I did and what Explorer was seeing was the empty one. I deleted one and it cleared things up.
  14. If I recall correctly, your mistake may have been to "Keep the data". I believe this let's DB use the empty space on the drive, but keeps the existing data out of the pool. Assign the drive a drive letter and look for the data outside the <GUID> of the pool. If it is there, move it into the pool with Explorer. You need to Merge, not Keep.
  15. My only observation is that it won't be particularly speedy with three smaller external drives. An investment in a larger drive would be so much simpler. That said, I have a huge DB pool that is rock solid reliable. Just no USB drives.
  • Create New...