Disk Info issue 2015-02-16T06:41:21+00:00

Home Forums Help needed Disk Info issue

  • Author
    Posts
  • Jimmy Wilson
    Member
    Post count: 5

    So I had Tabbles set up and began tagging things. However, after I restarted the computer it can’t link the tabbles to the actual files. The disk is there and mounted to the same location. The Disk ID is the same but the Disk Size is different now. I have no way to control this since the disk is on a ZFS filesystem and changes the partition size whenever new data is added to another dataset on the same volume. Is it possible to completely disable the check for Disk serial number check? I have no use for this feature and it makes it so that the tabbles disappear anytime I add data to my data volumes.

  • Maurizio
    Keymaster
    Post count: 100

    So your disk size changes often. I’m sorry, but there is no way to have Tabbles work in this unusual setup. We have to offer an option to only use the disk serial number, but it will take time for this to be available. I’m afraid you can’t change the size of your partitions. When the size changes, you must intervene manually on the database (howtos will follow). In your case, I’m afraid you’ll have to use disks with a steady size.

  • Jimmy Wilson
    Member
    Post count: 5

    Thank you for the reply and I would appreciate a way to manually change it as a temporary fix. I’m surprised this doesn’t come up more often for home users since FreeNAS, NAS4Free and ZFS for Linux all use this same file system which is popular for home users and even some small businesses.

    I can understand using the Serial # of the disk but why is add the extra restriction of the partition size? Or since many people probably don’t need the extra verification (for me I don’t because it is always auto-mounted to the same location), a simple option to disable it would be nice.

    Thanks again for helping! And the software is awesome, this is the only major issue I’ve had so far!

  • Maurizio
    Keymaster
    Post count: 100

    why is add the extra restriction of the partition size?

    Because during initial tests we found some disks do not specify a serial number correctly, so we had to do that.

    I would appreciate a way to manually change it as a temporary fix.

    unfortunately this is not a small change, though it may look so; it is a lot of work, as it requires to update all the stored procedures and will require a database upgrade. So we won’t be able to do this soon. We have more urgent updates to make first. I will try to stick in the next bugfix release, but I can’t guarantee.

  • Jimmy Wilson
    Member
    Post count: 5

    during initial tests we found some disks do not specify a serial number correctly, so we had to do that.

    That’s interesting,

    unfortunately this is not a small change, though it may look so; it is a lot of work, as it requires to update all the stored procedures and will require a database upgrade. So we won’t be able to do this soon. We have more urgent updates to make first. I will try to stick in the next bugfix release, but I can’t guarantee.

    I understand a permanent fix can take a while, and this is obviously a minor thing so not a priority. I was referring to what you said here:

    When the size changes, you must intervene manually on the database (howtos will follow)

    About a manual intervention with the database. Since it’s not critical data I can put it on an external drive for now, so I just need a way to manually fix the database to point to the new drive if possible, thanks!

  • Jimmy Wilson
    Member
    Post count: 5

    When the size changes, you must intervene manually on the database (howtos will follow).

    Any chance I could get that how to on manually updating the database? I’m kinda stuck without that and I don’t really want to go through re-adding all of the tags.

    Thanks,
    Jimmy

  • Maurizio
    Keymaster
    Post count: 100

    Sorry for the delay.

    When the partition size changes, you need to run the following script.

    Suppose partition with volume serial number 0CED08AF has changed size from 451577638912 to 278768590848. Then, the script to run in Sql Management Studio is:

    
    use tabbles;
    
    update [file]
    set diskId = '§0CED08AF§278768590848'
    where diskId = '§0CED08AF§451577638912';

    Of course you need to find the three values (volume serial number, old size , and new size). You can discover volume serial number and new size by right clicking the disk in tabbles, then

    folder menu > advanced > “see which disk contains this file”

    you can discover the old size by right clicking a file with the “unplugged” icon, and then

    advanced > “see which disk contains this file”

    Important: Backup your tabbles.mdf file first!

  • Jimmy Wilson
    Member
    Post count: 5

    Thank you very much! I will run this later today.

  • Maurizio
    Keymaster
    Post count: 100

You must be logged in to reply to this topic.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close