Jump to content
Division-M Community

oj88

Members
  • Content Count

    130
  • Joined

  • Last visited

  • Days Won

    5

oj88 last won the day on June 1 2015

oj88 had the most liked content!

About oj88

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. I just opened a ticket. I was wondering why my SSD system drive was running out of space. To my surprise, the DB log files I have total to just a few bytes shy of 60GB! That's dating back to Jan or Feb this year. I asked two things.... 1. Can it be safely trimmed down or removed altogether? 2. Can it be moved to a different, non-SSD drive? And in doing so, will the performance degrade? UPDATE: After receiving a reply from Anthony, I went ahead and deleted all the files under the Logs directory. The server is still up and my SSD can breathe again.
  2. I'm also waiting for DB to fully support Server 2016.
  3. Accessing the physical DB drives directly for purposes of directory or file MADs (modifications, additions, and deletions), etc., should NOT be done. Such operations must be performed through the pool mount point and let DB manage the files. However, for purposes of error-checking or repair of the individual DB disks (a process which does not modify the file or directory structure, other than to repair it) accessing the physical DB drives directly is supported. In fact, this is documented in the FAQ; https://support.division-m.com/hc/en-us/articles/214026403-How-can-I-check-the-drives-in-a-pool- Note: Edited for brevity.
  4. I assigned letters on mine so I would be able to run Windows' native disk tools like error/surface check, defrag and disk cleanup.
  5. For something that's brand new, it already has 0xC4 (196 in decimal) Pending Sector Count. This is the number of sectors that has been identified by the drive logic to be weak/unreliable at best, or unreadable at worst. Eventually, these sectors will be marked as Bad and your Reallocated Sector Count will go up. In reading SMART parameters, just take note of the RAW entries. In other words, this typically indicates an impending issue with the drive (ie. weak magnetic media or physical damage on the disk surface). If you can have it replaced, do so now. Tip: On any new hard drive, it is best practice to run a comprehensive surface test using a hard disk utility before putting them into production. If a hard drive turns out to be a dud in the test, it's easier to have it replaced since it's not holding any of your data. I personally use Hard Disk Sentinel Pro.
  6. I'm sorry that didn't work for you. You may need to contact support. You should still be able to get a response within a day or two.
  7. Try this procedure if it fixes your problem. Uninstall DB Reboot Install DB 2.4 Reboot
  8. I ran into a similar issue several years ago. I initiated a drive removal and left it running overnight. The next morning, I got a dialogue box saying that the drive removal process was completed/successful. But then, I noticed that there is still data in the drive that was supposed to have been removed (I kept the drive letters so I will always have access to the individual disks). I clicked on Running Tasks in DB Client and to my surprise, it is indicating that the Disk Removal process is still running (Overall progress at 6%). If I have shutdown and removed the drive, that would have caused a potential data loss. This was version 1.4.5.0 mind you so it may no longer be apples to apples with the current version. I just thought I should share my experience.
  9. I've read somewhere that Handbrake would move files around after conversion. Some people have reported that even after manually setting where the file should go, Handbrake would still move the converted file to the default folder location. It's a shot in the dark but I'd try searching for the file elsewhere in the pool or on your other drives, including the OS partition.
  10. You may want to try backing up your pool (as much as you can) and rebuild it from scratch. The closest I got to hitting the panic button was when the pool wouldn't mount after an update. It was later determined that the update didn't install completely, leaving pieces of the older DB system files. Since then, I've been manually uninstalling and reinstalling DB (to update) and I've never had any issues with it. Certainly nothing about DB touching my files. To the best of my knowledge, my whole file and folder structure is fully intact. Have you tried getting in touch with them through email? (support@division-m.com) The last support instance I had with them was late Feb of this year. I requested to unlock my license because the old motherboard died. Response time was fairly quick... I got my answer in less then 2 hours.
  11. It won't lose your settings. Everything should, license and all, go back to normal. Only difference is it'll be running the newest version of DB.
  12. I've been doing the uninstall-install dance since maybe 1.9. I've had issues with DB services failing to start if I just install over the old one. This is the process I do... works 100% 1. Uninstall DB 2. Reboot 3. Install DB 4. Reboot
  13. @silkshadow, Well, there's a glimmer of hope: http://blog.division-m.com/ The force awakens...
  14. Thank you Anthony for coming up with a revolutionary product. I can't imagine how I could manage my growing media collection without DB. It's always sad to see a company close shop. But I guess that's just life. Anyway, I'm sure you'll figure out something in the future and rediscover a new 'blue ocean'. Hats off to you, sir.
  15. I agree with revengineer. To add, DE, which is an integral component of WHSv1, could interfere with the operation of DB. But I have to admit, this got me curious to know what would happen if you mix them together. Kinda like having two anti-virus programs on the same computer. We all know how bad things could become if they started fighting each other.
×
×
  • Create New...