Jump to content

thepregnantgod

Members
  • Posts

    180
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by thepregnantgod

  1. In my transition from Drivebender to Drivepool/Scanner combo I'm noticing that a number of my 20 3-4 TB drives have bad sectors. In fact, my brand new WD Red 4TB drive had an unreadable sector out of box! That being said, a few questions: 1. At what point should I look to RMA (if under warranty) a drive? How many unreadable sectors? I know that once one is identified the drive uses a different/replacement sector and some such... 2. After Stablebit scanner identifies the bad sector does it (on a firmware level) have the drive mark it as bad and thus it will be skipped if data is written to the drive? Or...is this dependent on Stablebit scanner being installed? 3. How often is too often to scan the drives? The default is 30 days but finding these bad sectors is frustrating and I'd rather identify them before I write data across them. 4. If I reinstall the OS - will all the drives need rescanning? Or will Stablebit somehow know that the drive has been recently scanned and marked healthy? (I'm assuming no) Thanks.
  2. Thanks. I'm migrating now and though it's tedious with 60TB of data, I enjoy your product. The interface is much cleaner and simpler. I do have some questions regarding standy on disks, but I posted that question to a more relevant thread.
  3. Sorry, if I'm necro'ing an old post, but I'm switching to Drivepool/Stablebit Scanner combo from DriveBender. and I'd like some advice on how to best maintain the health of my disks regarding standby/disk control, query, etc. options now available. My setup: 20 Green disks (3TB and 4TB) attached to two Supermicro SAS/SATA 8 port cards and the remaining to onboard Intel/Marvel controllers. I will have one large duplicated pool containing all 20 disks. Electricity is not a concern, performance is secondary concern, but health of disks is primary concern. That being said, what are your recommendations on things like spin down, standby, don't wake up for SMART, etc. Thanks.
  4. When both products were in beta, I picked Drive Bender and have been using it since. However, recently, I'm getting a lot of dropped drives which is greatly frustrating. The idea of running Stablebit Scanner along side Drive Pool has me considering the switch. However, I have 20 drives totaling 60TB in storage with everything duplicated (a hidden duplicate on various drives) so manually recombining stuff is going to be a pain. That being said, can someone familiar with both programs answer these questions for me: 1. If a drive drops, is there a manual/automatic tool that will identify which primary files were located on the dropped drive and then find the duplicates remaining in the pool and mark them primary then duplicate them? 2. Is there a caching mechanism? What type of read/write should I expect if a file is being copied twice in parallel? All my drives are green 5400rpm drives yet on tests, I'm still getting around 60megs read/100megs write in my current config. 3. If Stablebit scanner finds errors on a drive - what does it do? Some of my reading says it pulls the drive automatically - but then would it initiate (the answer the question 1?) 4. In the same vein, is there a tool to check the integrity of the duplication? Can I scan for every file in a duplicated directory to confirm that it has a duplicate somewhere else in the pool? Thanks. Edit: Larsp has posted an "unofficial" guide on how to migrate the Drive Bender pool to StableBit DrivePool, include a script to handle reorganizing the duplication into a format that StableBit DrivePool will properly handle. http://community.covecube.com/index.php?/topic/511-migrate-from-drive-bender-to-drive-pool/?p=4554 -Christopher, aka Drashna
×
×
  • Create New...