Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  1. Unfortunately, I have found that with Smooth Stream off, the intermittent playback problems are definitely there when accessing files via DB and definitely not there when accessing the same file directly.
  2. Media Streaming has been turned off all along, since I don't care for Windows Media Player and Windows Media Center. Your idea about turning off Smooth Stream is so crazy it just might work! And it does indeed cure the lag when seeking. It remains to be seen if it also eliminates the intermittent freeze-up, since that's hard to reproduce on demand. But now I'm hopeful this can be easily fixed.
  3. I should say the problems are mostly when I use Media Player Classic, which in the past had been known for its poor buffering over networks but in the last couple years it seemed to have been resolved -- evidently network performance is still not its strong suit. However, I can see problems when I run PowerDVD 11 -- if I click on a different point in the movie, it is slow to start playing if I'm using DB but instantaneous when playing it directly. I also detect small video hiccups as if frames are being dropped when it starts to resume playing -- I suspect it is having the same network problem as MPC but it is more graceful in handling the problem. Also, in running the PowerDVD tests while recording 2 HDTV shows and downloading BitTorrent, I found the DB directory suddenly quit on me altogether and Windows Explorer said it could not access the directory. Trying to access the non-DB shared folders continues to work just fine, and I'm still logged into the server via RDC -- it's only DB that has crapped out. So, it seems that DB has trouble with networking when the server's network connection is being shared with other activities.
  4. I'm not using a media-streaming feature -- I'm playing the files directly from Windows Explorer using either Media Player Classic (mostly) or PowerDVD 11 (as a backup). When I access the file from the shared DB directory, if I jump ahead a minute in the movie, there's a noticeable pause, then it starts to play for a fraction of a second, then it pauses briefly, then it plays -- this is very repeatable. Intermittently (not sure why) it will seize up completely for several seconds or more, stutter, and have other serious playback issues. When I access the same file by using the shared drive where the file is located, any seeking I do is instantaneous and once it resumes playing it plays smoothly, and without intermittent interruptions. I have noticed the DB problems are worse if the server is downloading a few hundred kb/s using BitTorrent, and also if I am recording one or more TV shows using SageTV -- but both use dedicated drives that are not pooled in DB. I ran a test, downloading at 300 kb/s and recording two HD shows all at the same time, and it made the DB file access noticeably worse, and it made the direct access not quite (still nearly) instantaneous when seeking but still smooth once playing.
  5. I have found that DB has trouble streaming video files even with the Smooth Stream option enabled for all files. This clears up a mystery that has been nagging me for months -- why my new, more powerful server with 4GB RAM running WHS2011 and DB was having playback issues, when my old 1GB server running WHS1 never had problems with the same files. The files in question are m2ts files I ripped from my blu-ray collection, so they are the highest bitrate video files in use, although the bitrates are a fraction of what the drives and ethernet can handle. To nail down whether it was a DB problem, a drive problem, an ethernet problem, a video player problem, etc. I shared the drives directly and tested a number of videos when accessed via the DB structure vs. the individual shared drive letters, and the pattern was quite clear -- the files never once skipped when accessed directly, but there were intermittent problems when accessing them via DB. I also had problems playing from DB with both Media Player Classic and PowerDVD.
  6. I've rebooted several dozen times now, attempting various ways of diagnosing the problem. I've discovered that one of the DB hard drives, at best, needs to have checkdisk run on it, and at worst may have failed. It's a 2TB drive so it will take a while for the checkdisk to run, if it completes at all. So, it appears that once a problem develops with a drive, DB freezes up the system and won't tell you why. so you just have to shoot it. The workaround seems to be to yank the offending drive so DB won't see it and freeze up, uninstall DB, reinsert the drive and diagnose/fix the problem, then reinstall DB and put the pieces back together. Some searching turned up some other posts from people having the same experience and using the same sort of workaround. Suffice it to say my opinion of DB has fallen significantly -- saying it provides any sort of data protection from failed drives could not be more wrong -- the first thing to fail is DB. What's the use of redundant drives if the whole server locks up when one drive has a problem?
  7. I've been running 1.2.x (I forget the exact version) on my WHS2011 machine for months with no problems. I ran the install for, rebooted, and couldn't access the network shares on the server. The system is nearly nonresponsive whenever DB is installed -- after uninstalling it, there are no problems -- reinstalling it, the problems return. When I access the machine locally, I can access other computers over the network, but trying to open the server itself from the network gives an error saying the server service is not running. There are no shared folders listed in Dashboard. Trying to access the pooled drive from My Computer only locks up explorer. Oh, and I tried running the DB Manager, but its "new interface" does not get along with large fonts and all I see is text overwriting text overwriting text on the screen. This is particularly frustrating given the system was running just fine with 1.2 and I can't download that version again.
  8. Interesting -- I've got a drive letter for the pool, but not the individual drives... I'll have to give that a try. I figured out from the "date created" timestamps vs the content of the TV shows that corrupted the files, that they had to have been corrupted when I was copying them onto the SageTV drive, rather than back onto DB. Also, some of them were corrupted by other video files rather than what SageTV was recording.
  9. I am transitioning from the pieces of an old WHS1 system to building a WHS2011 system running Drive Bender. Both systems had/have SageTV, which has its own dedicated drive not running DB. I was following a procedure of temporarily moving files off old WHS1 drives onto the free space on the SageTV drive, so I could format the drive, add it clean to DB, and then move the files back from the SageTV drive onto the DB pool. What I have noticed is that somewhere in the operation, the file contents were overwritten with whatever SageTV was recording. The question is whether this was during the write to the SageTV drive, or during the write to the DB pool -- I still need to investigate this but don't have time this morning. I am noticing that all the files created during a particular block of time are corrupted, so that may help me figure out what happened. An issue related to this is that I have yet to find a way to run a checkdisk on either a DB drive node or the full DB pool.
  10. When I booted up my server recently it told me my D: (drivebender drive) recycle bin was corrupted. I was in the middle of something so I figured I'd run checkdisk after a reboot. However, when I bring up Properties > Tools and click on Check Now, nothing happens. I tried looking for an equivalent feature under the DB manager, but all I see is a "repair/rebuild" function.
  11. I got it figured out -- I just had to be more patient when it was copying the files -- the zero-size files were just temporary.
  12. I've set up a DB pool and went to compress a folder, only to find it isn't an option. I don't recall if I enabled compression or not when I formatted it, and I can't find any info in windows indicating that either. I'm wondering if it simply isn't an option to use compression on a DB pool.
  13. Here's my situation: I had a WHS v1 server, and I think the power supply died. I took that as the opportunity/impetus to build a whole new server based on WHS 2011, with a new boot drive and an additional 3TB drive. The old WHS drives are intact, and I want to pull the files off the old DE drives and copy them to the new DB drive, and eventually reformat the old drives and reuse them in the new server. I've tried to do simple move/copy operations on the DE files, but it gives me errors and/or problems when I try this -- the copied files are 0-size or it gives me some sort of error...
  • Create New...