Jump to content
Division-M Community

oj88

Members
  • Posts

    152
  • Joined

  • Last visited

  • Days Won

    10

oj88 last won the day on January 7

oj88 had the most liked content!

Profile Information

  • Gender
    Not Telling
  1. ^ Thanks for the reply. Yes, removing a drive from the pool would initiate a file move, which then the remaining drives in the pool would pick up. There were quite a few weirdness going on with the removed disk. I can't account for the 650GB. To be specific, if I select all the folders on the root directory and click properties, it says that all they're occupying were a few MBs. But if I look at the drive's properties, there's a hefty 650GB of space being utilized. Anyway, after doing spot checks, I was confident that the file move went well. The disk now has been repurposed so I can no longer work on resolving those issues.
  2. Took almost 24 hours but I woke up today and DB reported that the disk removal has completed. It's now running a File Duplication task. All indications seems to point that the pool is healthy, so far. But here's the rub... The removed 3TB disk now shows up with a drive letter, which is expected, BUT it still has around 650GB worth of data on it. I would've thought it should be empty, with only the folder structure intact. My new question now is, how do I know if the 650GB worth of files have truly been copied to the pool? I mean, I don't want to manually check this. In other words, should I take DB's word that the disk removal was 100% successful and that I can safely repurpose the 3TB drive without worry of data loss?
  3. Long story short, I need to add 2x 8TB drives but my system only has one empty SATA port available. I have added the first 8TB drive into the pool and have initiated the removal of the oldest disk from the pool, a 3TB drive. The 2nd 8TB drive will take its spot. I understand that the disk removal process can take a long time so there's always a risk of something happening mid-stream... from power outages to Windows deciding to go rogue, etc. What happens if this process is interrupted? Is it something that can be resumed after a reboot?
  4. I think the "Ping" volume only works on systems with LEDs on individual HDD slot or enclosure. Otherwise, looking up serial numbers would be the only way to go.
  5. Yeah, Same here. Irreplaceable files were duplicated so the only items lost were Plex media. I can recreate them from scratch but it doesn't make it any more pleasant.
  6. Thank you. The drive no longer show up in BIOS... no chance I'll be able to check SMART, much less recover any files using Windows.
  7. Well, 2021 for me has come up to a rocky start. I'm still shaken a bit from this ordeal so please bear with me. I would appreciate help and sanity checks with the following: 1. How do I generate/enumerate a list of files along with their path names that are now missing from the pool? 2. Do I just "Force remove" the drive in DB to regain Read/Write access to the pool? 3. After #2, will the duplicated folders be re-duplicated automatically to the surviving drives? The 4TB drive was around 85% full so that is a LOT. It would really help to know what exactly was in it. Thanks! As for the drive, this is what it sounds like (audio only).
  8. Touché I probably shouldn't have given this parameter too much emphasis. Consider it just an example. What I'm trying to do is to inspire abstract thought, however absurd, but should still be plausible. Funny enough, all WD Purple drives are CMR, whereas WD Red in the 2-6TB range are SMR. That will probably account for the presumed better write performance, but without stipulating that that was probably made in comparison to their SMR NAS drives...maybe.... But I digress. Beyond physical and accidental damage, what other parameters can dictate the lifespan of a WD Purple (or Seagate Skyhawk, for that matter) when used as a traditional drive?
  9. In my test runs on Windows 10, it will only recognize physical drives. It won't let you backup shared folders or mapped drives pointing to a NAS or in my case, another Windows machine where the pool resides. My best guess is that, if I ever managed to get it running on the actual server where DB is, it will only backup the individual physical drives, NOT the pool drive. But that wasn't the show-stopper. My main issue with them is that, ONLY they get to choose which files to backup! This is in spite of their "no strings attached" slogan. Just take a few moments to read the aforementioned "strings": https://help.backblaze.com/hc/en-us/articles/217665388-What-does-Backblaze-Backup-. Particularly, take a look at the section on Network Drives and Excluded Files.
  10. I can live with a marginally slower performance across the board. What I am worried about is what sort of voodoo magic did the engineers do to make these drives optimized for surveillance use. To be precise, they have this feature called "AllFrame AI", which, suffice to say, makes the drive better at its job in an NVR environment. What's the possibility of this "AllFrame AI" interfering when used in a non-NVR specific equipment? Another thing... these drives are designed to have a load/unload cycle max of 300,000. I would imagine that in a NVR with continuous recording, the drives would be actively writing non-stop, which should prevent the heads from parking. However, when you use it as an ordinary drive, which translates to less active read/write usage, will these drives self-park their heads after being idle for a while? If yes, that would really eat up the load/unload cycle, doesn't it? I believe this was an issue associated with WD Green drives' having high load cycle counts, as they park their heads after just 8 seconds of inactivity. Of course, all this is conjecture and that should give you an idea how much thought (and over-thinking) I'm giving this.
  11. I didn't go that far. My DB pool is running on Windows Server 2019, which is unsupported. I asked the question seeking to get a go or no-go before I move the DB pool to a Windows 10 OS, which is supported. But since I never got any reply, I just dropped the idea and kept DB in Windows Server.
  12. Is anyone running mixed WD Red (NAS) and WD Purple (Surveillance) HDDs in the same pool? Please share your experience. WD Purple drives are way cheaper now than WD Red drives. I currently have 7 WD Red drives now in a 24TB pool and I'm wondering if I can use a WD Purple drive as the 8th drive. Follow-up question... how about using WD Purple with Synology SHR? This is used as an iSCSI target for backup purposes.
  13. Everything I've done is default or out-of-the-box settings. In case you don't already know, that particular Backblaze plan doesn't support Windows Server OS. The Backblaze app will also not allow you to backup mapped networked drives/NAS. It's likely it won't let you backup the pool drive as well. Though it might backup individual drives in the pool, how it would work with Drive Bender's folder structure, I don't know. That unlimited plan is full of caveats. Better try it out first before committing to it, long term.
  14. Been using Plex with Drive Bender for years. I have had NO interoperability issues, whatsoever. As for duplication, you enable it per folder. So if you have 100 files in that folder with duplication turned on, you'll have a copy of each 100 files elsewhere on a different physical disk in the pool. That also means that that folder will be using up twice as much storage from the pool.
  15. Once you've copied all your relevant files from "K:\" to another drive or PC, you can uninstall DB and just reformat the individual drives in the DB pool like any normal drive.
×
×
  • Create New...