Jump to content

Spinman

Members
  • Posts

    9
  • Joined

  • Last visited

Spinman's Achievements

Newbie

Newbie (1/3)

0

Reputation

  1. Ah... Finally noticed the pool options button below the graphic - thought it was a title... All is now well!
  2. Just completed a rebuild of my WHS2011 platform - and installed Drive Pool v2.2.0.651BETA, instead of returning the the version 1 module. For the life of me, I don't see any tabs to access and configure the balancing settings. Can someone point me in the right direction?
  3. Currently, I have to open up the drive details to see that oldest scan date for a particular drive. It would be nice to have it be a display option on the high level display (perhaps next to drive status). Just a thought for a future build...
  4. Hate to resurrect an old thread - but seems relevant... I have been trying to install scanner version 2.5.1.3062 on my win7 box since it was released - and keeps getting flagged by Avast!. I have submitted the info to Avast on several ocassions, but apparently has never been added to their exception listing. The install always fails every time I retry... 1) Is anyone else having problems? 2) Perhaps someone else would have been luck getting this resolved with Avast. Christopher?
  5. Spinman

    Stale Drive Info?

    Ah Yes, I always forget to manually delete the notification in dashboard. Instead, I expect the system to automatically remove it once the problem has been resolved. I did delete it, and it has not come back. So all is well for the moment. I checked the SMART for the drive in question, as well as all drives - and the statistics show no bad sectors and no reallocated sectors. That would explain why the drive showed no errors when loaded in another system. So I guess I'm confused as to why stablebit scanner set the drive as having a bad sector in dash board in the first place. No harm, no foul. Thanks
  6. Spinman

    Stale Drive Info?

    Running Scanner on my WHS2011 platform. One day the scanner identified a drive as having a bad sector. Scanner would never seem to be able to pass the sector in trouble (constantly trying to read?). The drive would then begin to drop and reattach every 30 seconds or so. I pulled the drive in question and tested it in a win7 box that also has scanner installed and did not encountered any problems. The drive reported clean. Ran the MFG diagnostic programs and the drive reported clean. WHS still reported a drive had a critical error - even though the drive was no longer installed in the box. Reinstalled back into the WHS 2011 machine, and the drive dropping problem soon began again. Upgraded Scanner to latest beta {v2.5.0.341 } to see if that would handle the drive any differently - it did not, drive was constantly dropping. Thought I would need to replace the drive. As a last resort, I installed a drive cage to facilitate hot swaps and utilized new cables to the controller for all drives. While I tried to match the drives to the previously used controller ports - apparently I didn't. When I rebooted all drives were recognized and functioning, but scanner reported that they had never been scanned - I lost my history. I still had an WHS critical error message that one drive had a bad sector. (How could it know if the drives had never been scanned). Strange that the scanner program did not match the prior drive history with the current drive installation, instead thinking them to be drives it had never seen before. Scanner finally finished scanning all drives and reported that all were at 100% (3 green check marks on each drive). So perhaps my bad sector and drive dropping was the result of a bad cable or controller port. But even after the scan has completed, WHS is still reporting a drive has a bad sector. I have rerun the analysis and it still shows a drive has a bad sector. I note the add-in "Home Server Smart 2013" has an option to delete stale drive information for drives that are no longer mounted in the system. Wondering if there should be such an opion on Drive Scanner. Is there something in the registry I should manually delete to see if that will eliminate my bad sector error warning message?
  7. Yes, I can also confirm problems. Also running Avast! [v2014.9.0.2021] Had to disable AV to install program. It installed and worked perfectly while Avast was disabled. Once Avast was restarted, the scanner program was flagged and disabled. StableBit.Scanner_2.5.0.3041_BETA on Win 7 Pro 64 bit
  8. I'm experiencing the same problem. Is there an email address I can send my dump of the service to (instead of using the web form)?
  9. Running 2.5.0.2968 beta on WHS2011 Just thinking outloud... [i know it has been said before that the scanner program is designed not to write to the hard disk] I just had a disk develop problems - currently 4,390 bad sectors on a 3TB advanced format drive per Stablebit Scanner. [Why does HD Sentinel v4.50 only report 592 weak sectors?] The drive is marked "Damaged", and the drive pool balancer started to move files off of the drive (until I turned it off). I ran a file scan, and only one file was reported as being damaged. My only automoated option appears to be to try to recover the file. 1) Why not add an option to permit me to delete the file from the results screen? Instead, I had to manually track down the file to delete it via Windows Explorer. After I deleted the file, I ran another file scan and it reported no damaged files. I copied over the file from my backup offline storage. Almost immediately, HD Sentinel reported another bad sector on the drive. I started another Stablebit Scanner file scan, and the same file was reported as damaged. So apparently, the location where that file is being stored is still unstable. 2) Why not add an option to permit me to deep scan all of the sectors of a damaged file to see if additional damaged surface area can be found and marked inactive? I don't want to scan the entire 3TB drive again, if only a small area is damaged. To prevent the problem from replicating again when I replaced the damaged file with my backup copy, I left it on the disk, rename it to "Damaged File.xxx", and reloated it to the root directory outside the pool. I then copied the backup file to the drive - this time to a different location, as the damaged area is still occupied by the "Damaged File.xxx". 3) Why not add an option to permit me to rename the file from the results screen? Instead, I had to manually track down the file to rename it via Windows Explorer. I am now paranoid about the stability of this drive, and am concerned about further deteriation over time. Waiting to see if I should RMA it... 4) Why not add an option to rescan "damaged drives" on a different time schedule vs. the default 30 day cycle. I might like to scan this drive every 14 days to ensure that there is no additional performance deteriation. 5) I noticed that were were good sectors mixed in with bad sectors. Why not add an option to block off and mark all sectors as bad beginning with xxxxx and ending with xxxxx - that way you are not trying to store data in a questionable area. Just some thoughts...
×
×
  • Create New...