Jump to content

Wiidesire

Members
  • Posts

    26
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Wiidesire

  1. I've renamed all my drives from the default names to a custom name.

    However any notifications I receive still use the default name:

    Quote

    Unreadable Sectors Found on "PC".

    One or more disks are damaged and have data on them that is unreadable:

    • ASMT 2115 SCSI Disk Device - 512 B unreadable (1 sectors) - The rest of the disk is still being scanned

      • Model: WDC xyz

      • Serial number: xyz

    It would also be helpful if the notification would contain the location (case / drive bay) information.

     

  2. 6 hours ago, bob19 said:

    Next day, started, installed a new version (this beta) and boom, the scan starts for ALL disks again. Annoying.

    That's quite "normal" that it happened in the upgrade process to 3246, see here:

    However now that you're on 3246 it shouldn't happen anymore. I assume some drives are partially scanned now? Reboot and it shouldn't be reset to 0% anymore.

  3. The problem is that you were still on an affected version 3216. By upgrading to the newest version the Stablebit Scanner Service is forcefully shut down, thus the DiskId files can get corrupted in the upgrade process. Now that you are on version 3246 which fixed the problem it shouldn't happen anymore on your next upgrade/reboot/crash.

    I agree wholeheartedly though that we should get a way to backup the scan status of drives just in case. A scheduled automatic backup would be great. The files are extremely small and don't take a lot of space so don't see a reason not to implement it feature wise.

  4. 4 hours ago, Mick Mickle said:

    Do you think the disk id's being updated too often, as summarized above, would also be the cause of my problem? And 2.5.4.3246 could be the remedy?

    I've had it happen with normal reboots as well, just not as often as with crashes. It just depends on the timing. Imagine what happens on a reboot. Windows is forcefully shutting down services, including the Stablebit Scanner Service. So if this service gets shutdown at the timeframe where it is writing new DiskId files the files can end up corrupted, thus after a reboot the Service creates new DiskId files meaning all previous scan status is lost.

    Now the DiskId are not written literally every second anymore (which increases the risk that the service gets killed at the time of writing files significantly) but instead 20-40 minutes (don't know the exact interval now) . That's a reduction of a factor of 1200 to 2400 so the risk that you reboot at the exact time the files are written should basically be zero now.

  5. To keep everyone up-to-date:

    With the help of Alex I've identified the root cause of the issue. The LastSeen variable inside the DiskId files is changed literally every second. This means that the DiskId files are constantly being changed and in the event of a crash there is a high chance that it crashes while the new file is being written thus the DiskId files get corrupted.

    The LastSmartUpdate variable inside the SmartPersistentInfo files is updated in a more reasonable one minute interval so I'm hoping it is a quick fix to simply adjust the write interval of the LastSeen variable.

    Besides changing the interval there would have to be backup diskid files to completely eliminate the issue. So instead of creating new DiskId files when corrupt files have been detected it should copy over an older backup file of the DiskId file(s) in question. Or the LastSeen value gets completely eliminated from the DiskId file and moved somewhere else to avoid changing the DiskId files at all.

  6. On 2/18/2019 at 9:01 PM, Christopher (Drashna) said:

    Make sure that you're on the latest beta.  There are some fixes that should hopefully prevent this from happening in the future.

    http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3220_BETA.exe

    If it's still happening on that version, let us know. 

    I'm on this exact version and unfortunately this Wednesday after a reboot all my drive scan status is once again gone. So far it has happened eight times to me (over a year so on many different versions). I can tell because all the old json files are still there under C:\ProgramData\StableBit Scanner\Service\Store\Json. For whatever reason the drives get completely new ids thus losing all their status.

    Let me know what I can do to help troubleshoot this.

  7. Thanks for the fast answer.

    9 hours ago, Christopher (Drashna) said:

    Was this for the surface scan? 

    If so, even one is a critical issue.  It means that the OS failed to read from the drive, which is a SERIOUS issue.  As in "the submarine has sprung a leak" serious. It doesn't really get better on it's own.

    It was an automatic surface scan. I never said it would get better. However I'm using Scanner precisely to keep track of the health status of my drives. Not getting Email notifications of the rising unreadable sectors is a serious issue.

    9 hours ago, Christopher (Drashna) said:

    RMA the drive.

    This is why the drive is showing the unreadable (damaged) sectors.

    Drive hasn't got warranty anymore. I took the necessary precautions (backup) but the drive is still working fine. <50KB of unreadable data on a 6.000.000.000KB drive is not the biggest deal but if the unreadable count continously rises it becomes are a concern which is precisely why I need email notifications of it.

    9 hours ago, Christopher (Drashna) said:

    Writing to it *may* fix the issue, but it may not.  Also, StableBit Scanner has no way do to this currently.  

    Add it as a feature request please.

    9 hours ago, Christopher (Drashna) said:

    They shouldn't be.  Once you open the UI and "resolve" it, or click on the notification, it should "go away" until a new one is generated. 

    For SMART  warnings/errors, open the "SMART details" for the drive. From there, you can ignore them (permanently, or until it increases again). 

    So when I open the UI, go to the drive and S.M.A.R.T I can press "Ignore this warning" and the explanation says "Ignore the S.M.A.R.T attributes that are triggering the current warning". That does sound permanent to me. Can you confim that this only ignores e.g. 8 current pending sectors but once it rises I get another notification?

    For the "this harddrive is unable to read X sectors" in the UI, when I click it I can start a file scan but I don't see a way to dismiss it.

    I'm using v2.5.2.3129 btw.

  8. I've been using Scanner for a while now and I've been very satisfied with its capabilites. During the usage of the product some questions came up so I wanted to finally ask them here.

    I currently got one drive with some unreadable sectors. It were only four, so no big deal. However when I went to check today it rose to nine sectors. However I didn't get any notification which is troublesome (I only got one for the initial bad sectors but I need notifications for subsequent ones as well).

    How can I turn on notifications when unreadable sectors are rising?

     

    Another problem is that I have no way to dismiss notifications of errors. They are persistently in the taskbar. When I click on them I can only choose "Never warn me about disks with unreadable data"and "Never warn me about S.M.A.R.T warnings/failures". But that's what I don't want. What I need is a "I acknowledge this warning but keep giving me notifications if error levels rise" button.

     

    Also is there a way to force StableBit to write over the bad sectors? The S.M.A.R.T data are showing a "current pending sector count" and if I understand this one correctly when I write over this pending sector it should reallocate this sector to a good one.

     

     

     

     

  9. ​It's too late now. It wouldn't matter anyway because in the default configuration DrivePool splits your media so much across the drives that it's way too time consuming to try to replace single files manually. I'm using DrivePool for the same reason (media library) as you so I can give you two critical tips to avoid this in the future:

    ​

    ​1) Install the Ordered File Placement plugin from here. After that go to your pool options, activate the Ordered File Placement balancer and deactivate all others. Then prioritize your drives. This way when you add a TV show or a new season, it will all land on the same drive and will not be spread across the pool which is critical for a possible replacement unless you use capacity wasting duplication.

    Configurable ​Folder Split Levels would be an more ideal solution but the sole DrivePool developer "Alex" personally doesn't see the need for it -> low on priority list and will most likely never happen.

    ​2) Use the tool WinCatalog 2017 to keep track on what drive your media is. I'm very impressed with the tool so far. It not only archives the location and size of your files but also details like resolution/bitrate/audio tracks etc.

  10. But I am a customer too and I am not sure I'd want (the risks associated with) this.

    What risk? If implemented properly it will be optional. You don't need to use it.

     

    I don't need duplication and that code part alone makes DrivePool not as "simple and fast as possible". But I don't complain about it because I simply don't use it + I am not forced to use it.

  11. Oh man...  Just becacuse it's a simple idea doesn't make it simple to implement.

    Seems like you misunderstood me and took my quote out of context.

     

    The "I don't understand what's so difficult to get here" is a direct response to Alex's post "[...] but I personally, don't see a need for it. There will always be a need to split across folders even with a best-effort "grouping" algorithm".

     

    If you talk about this feature as much as you say, this is either a poor choice of words on his part or he doesn't get the Folder split level feature at all. Because in my opinion no, there is not always a need to split across folders. My use case with only the Ordered File Placement Plugin activated proofs it. And as I said he's the only developer, if he doesn't stand behind the feature or can't even grasp why it is needed, it's not high on the priority list.

     

    What I'm not saying is "this is so easy to implement, why hasn't it been done yet in all those 5 years?".

  12. I find it hard to understand using DP without duplication - kind of the point as you are looking for redundancy

     

    I'm not looking for redundancy, simply for a way to group drives together to one big volume.

    What I like about DrivePool is that even if the software is discountinued or a hard drive fails, I still have a normal folder/file structure on each drive. I don't want any RAID because of the rebuild issues and because it's not a backup.

     

     

    Oh and its easy to say you can re rip your blu-ray collection if things go south until you have to do it and spend days doing it even with a relatively small collection.

    I agree that it would take a lot of time but I also have a full backup on Amazon Cloud Drive Unlimited. With my 500 Mbit connection I can restore any lost media almost as fast as I can fill a new hard drive.

    AmazonCloudDrive.png

     

     

     

    As an alternative copy the files directly into the pool part directory on a specific drive - much more likely to stay together then and you know where they are.

    I thought about that but I don't like such micromanagement. Simply dropping data into the pool is preferable for me.

     

    For now I can live with the Ordered File Placement plugin. I've disabled all other balancers.

  13. ​​

    We hope to have a new release out soon.  As for new features, not quite yet.  I think that we want to get a stable version out, and then start working on any more new features.

     

    Thanks for the reply.

     

    Unfortunately Alex just responded today and he personally doesn't see any need for this feature. As the sole developer if he doesn't stand behind the feature, it's not high on the priority list. This is very disappointing.

     

    Here is the quote:

    "​Grouping files "together" has been requested a bunch, but I personally, don't see a need for it. There will always be a need to split across folders even with a best-effort "grouping" algorithm. The only foolproof way to protect yourself from file loss is file duplication."

    ​

    ​I don't understand what's so difficult to get here. DrivePool makes a big volume out of many hard drives. I'd wager a majority use this software (in part) for an easy to manage media library. Why else would you have multiple Terabytes of data? For text documents? How is it not logical then to get folder split levels to make replacement easy after a hard drive fails?

    ​

    It also doesn't make any sense to me to enable duplication for media that I physically own and can get back anytime by ripping the DVD/Blu-rays again. It is simply wasted hard drive space.

  14. Do this:

    http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings

    Set the "BitLocker_PoolPartUnlockDetect" setting to "False" and restart the service. 

    I can confirm this works, I'm running v 2.2.0.765.

     

    Before:

    DrivePoolSpindown1.png

    After making the changes:

    DrivePoolSpindown2.png

    Made the change...rebooted system after rebooting the service didnt do anything

     

    Still hitting drive over and over and over again

     

    KlUmsoA.png

    Just to make sure, you've done more than one change?

    ​1. Set the "BitLocker_PoolPartUnlockDetect" setting to "False"

    ​2. Rename DrivePool.Service.exe.default.config to DrivePool.Service.exe.config

    ​3. Restart DrivePool Service or Reboot

  15. ​I agree that folder level splitting is a must-have. I'd really like to use folder split level 2 for media files.

    ​Fortunately for me I can live with the Ordered File placement plug-in for now.

    ​

    The folder/file catalog should be built in, I agree. Thanks for the suggestion with WhereIsIt. I don't plan on using Duplication so I need to know which folders are on which drive in order to be able to rip the DVD/Blu-rays again when a hard drive fails.

    ​

    ​I've only been using DrivePool since yesterday and these two points jumped out to me. I also agree on most of your other points but they haven't bothered me yet.

    ​

  16. Thanks for pumping this thread, I've been using DrivePool since yesterday and my discs are being constantly accessed (my HDD enclosure has LEDs which show individual disc activity -> constant blinking with DrivePool).

    ​

    What is causing this issue?  Will try the config file change.

    ​Explanation:

    ​http://community.covecube.com/index.php?/topic/1784-drivepool-beta-constant-disk-activity/&do=findComment&comment=13602

    ​

    ​I'll try the fix tomorrow, hopefully it works.

×
×
  • Create New...