Jump to content

mentalinc

Members
  • Posts

    14
  • Joined

  • Days Won

    1

Posts posted by mentalinc

  1. Hey

     

    I'm considering using Drivepool to present a large pool to databases (SQL Server & Oracle) are there any issues with this?

    Is this supported in a production environment?

     

    The databases are used for data analysis not running a system, so mainly just queries and a a few transformation queries after the data is initially loaded.

     

    thanks

  2. Not tried it but I think if you move the drive you want to empty to the bottom of the "ordered file placement" plugin and selected "control new file placement and move existing..." if should do what you want and empty the drive assuming there is enough space.

  3. Could they look to add a checksum verification on Amazon end, this would save everyone a pile of bandwidth, but add a pile of compute time on Amazon end I guess.

     

    1. Compute chunk checksum 

    2. Upload chunk

    3. Run Amazon checksum API

    4. Receive Amazon generate checksum (will be only a few bytes depending on MD5 or SHA1 etc)

    5 compare checksums from step 1 & 4. If same move to next file, if cehcksum is  different, error restart at step 1 for current file

  4. Hey

     

    It looks like the OS drive can be added to the Drivepool based on the GUI...

    I'm thinking of installing windows on an SSD and then adding the OS drive into the Drivepool and using the balancer plugin to use the SSD cache...

    Is this a supported method or will it cause me some issues?

     

    Thanks

  5. Latest beta fixes this issue thanks.

     

    Shame the upgrade lost all the scan status, so all drives need to be rescanned again. Hopefully that will be fixed before it goes into a production release.

     

    thanks again for the speedy response

  6. Hi

     

    I've noticed that when I have the scanner open and then switch user on Windows 10 and log back in again the scanner window goes blank. The only way to get the application to work again is to close and then reopen the scanner.

     

    2MUAOTd.png

     

    I'm using version 2.5.1.3062

     

    thanks

  7. Yeah would be cool if you could click a button and have the scanner agree the file system check is now fine instead of me having to manually override it.

     

    Love the support on the fourms by you Chris. I have purchased to licence my NAS and PC with the scanner and drivepool.

  8. Hi

     

    I received a notification that the file system is damaged on one of my drives which is not part of the Drivepool.

    I then click the GUI to have it auto repair. Went through the force mount etc before it said it couldn't fix the issue.

    I run chkdsk at the command line and it found an issue. told me to run with /scan then came back with no errors which is great.

    I then ran it again and eventually running with /f solved the problem.

     

    Now I'm not sure if this is a path the app tried to take itself and failed. It would be great if the scanner could run the chkdsk command again and see there is no issue and clear the alert (So I don't have to manually override it).

     

    Not sure where to raise potential bugs so using the forums.

     

    output from my command line is below:

     

     

    C:\WINDOWS\system32>chkdsk i
    The drive, the path, or the file name is not valid.

    C:\WINDOWS\system32>chkdsk i:
    The type of the file system is NTFS.
    Volume label is non Drivepool.

    WARNING! /F parameter not specified.
    Running CHKDSK in read-only mode.

    Stage 1: Examining basic file system structure ...
    187904 file records processed.
    File verification completed.
    0 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    206436 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    9267 data files processed.
    CHKDSK is verifying Usn Journal...
    608 USN bytes processed.
    Usn Journal verification completed.
    Detected errors in the Master File Table (MFT) mirror.
    The Volume Bitmap is incorrect.
    Windows has checked the file system and found problems.
    Please run chkdsk /scan to find the problems and queue them for repair.

    1953382399 KB total disk space.
    1669068616 KB in 136554 files.
    66424 KB in 9268 indexes.
    0 KB in bad sectors.
    314035 KB in use by the system.
    65536 KB occupied by the log file.
    283933324 KB available on disk.

    4096 bytes in each allocation unit.
    488345599 total allocation units on disk.
    70983331 allocation units available on disk.

    C:\WINDOWS\system32>chkdsk i: /scan
    The type of the file system is NTFS.
    Volume label is non Drivepool.

    Stage 1: Examining basic file system structure ...
    187904 file records processed.
    File verification completed.
    0 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    206436 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    9267 data files processed.
    CHKDSK is verifying Usn Journal...
    1184 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1953382399 KB total disk space.
    1669068616 KB in 136554 files.
    66424 KB in 9268 indexes.
    0 KB in bad sectors.
    314035 KB in use by the system.
    65536 KB occupied by the log file.
    283933324 KB available on disk.

    4096 bytes in each allocation unit.
    488345599 total allocation units on disk.
    70983331 allocation units available on disk.

    C:\WINDOWS\system32>chkdsk i:
    The type of the file system is NTFS.
    Volume label is non Drivepool.

    WARNING! /F parameter not specified.
    Running CHKDSK in read-only mode.

    Stage 1: Examining basic file system structure ...
    187904 file records processed.
    File verification completed.
    0 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    206436 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    9267 data files processed.
    CHKDSK is verifying Usn Journal...
    2640 USN bytes processed.
    Usn Journal verification completed.
    Detected errors in the Master File Table (MFT) mirror.
    The Volume Bitmap is incorrect.
    Windows has checked the file system and found problems.
    Please run chkdsk /scan to find the problems and queue them for repair.

    1953382399 KB total disk space.
    1669068616 KB in 136554 files.
    66424 KB in 9268 indexes.
    0 KB in bad sectors.
    314035 KB in use by the system.
    65536 KB occupied by the log file.
    283933324 KB available on disk.

    4096 bytes in each allocation unit.
    488345599 total allocation units on disk.
    70983331 allocation units available on disk.

    C:\WINDOWS\system32>chkdsk i: /scan
    The type of the file system is NTFS.
    Volume label is non Drivepool.

    Stage 1: Examining basic file system structure ...
    187904 file records processed.
    File verification completed.
    0 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    206436 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    9267 data files processed.
    CHKDSK is verifying Usn Journal...
    3216 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1953382399 KB total disk space.
    1669068616 KB in 136554 files.
    66424 KB in 9268 indexes.
    0 KB in bad sectors.
    314035 KB in use by the system.
    65536 KB occupied by the log file.
    283933324 KB available on disk.

    4096 bytes in each allocation unit.
    488345599 total allocation units on disk.
    70983331 allocation units available on disk.

    C:\WINDOWS\system32>chkdsk i: /f
    The type of the file system is NTFS.

    Chkdsk cannot run because the volume is in use by another
    process. Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted. All opened handles to this volume are now invalid.
    Volume label is non Drivepool.

    Stage 1: Examining basic file system structure ...
    187904 file records processed.
    File verification completed.
    0 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    206436 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    9267 data files processed.
    CHKDSK is verifying Usn Journal...
    3800 USN bytes processed.
    Usn Journal verification completed.
    Correcting errors in the Master File Table (MFT) mirror.
    CHKDSK discovered free space marked as allocated in the volume bitmap.

    Windows has made corrections to the file system.
    No further action is required.

    1953382399 KB total disk space.
    1665996616 KB in 136553 files.
    66424 KB in 9268 indexes.
    0 KB in bad sectors.
    314035 KB in use by the system.
    65536 KB occupied by the log file.
    287005324 KB available on disk.

    4096 bytes in each allocation unit.
    488345599 total allocation units on disk.
    71751331 allocation units available on disk.

    C:\WINDOWS\system32>chkdsk i:
    The type of the file system is NTFS.
    Volume label is non Drivepool.

    WARNING! /F parameter not specified.
    Running CHKDSK in read-only mode.

    Stage 1: Examining basic file system structure ...
    187904 file records processed.
    File verification completed.
    0 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    206436 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    9267 data files processed.
    CHKDSK is verifying Usn Journal...
    4240 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1953382399 KB total disk space.
    1669068624 KB in 136555 files.
    66424 KB in 9268 indexes.
    0 KB in bad sectors.
    314035 KB in use by the system.
    65536 KB occupied by the log file.
    283933316 KB available on disk.

    4096 bytes in each allocation unit.
    488345599 total allocation units on disk.
    70983329 allocation units available on disk.

     

     

     

    Version 2.5.1.3062

  9. Hi

     

    Having just had a drive die (basically ended up being a DOA started to fail after 8 days up time).

    Is it possible to have scanner send me a weekly "status" email?

    Basically I'd like scanner to "let me know everything is ok" that way if I don't get this email I can start to investigate.

     

    I also had issues where the drive failing would stop the network from working (no idea why this happened) which meant the scanner failure emails weren't getting sent.

    I'd notice the server network failure (ping still worked but nothing else), reboot the box and the failure notifications would then hit my inbox, which would be way to late if it went unnoticed for too long.

     

    Second Q:

    Does Scanner have remote management similar to drive pool?

    Would be great to be able to open that up instead of having to RDP in to check health...

     

    Thanks

     

  10. Hi

     

    I have my "NAS" (server 2012R2) running on a 192.168.1.x subnet while my main PC runs on a 192.168.2.x subnet.

     

    I don't seem to be able to detect Drivepool running on the NAS.

     

    Does drivepool only scan the current subnet? is it possible to pass a command line to point it to eh correct IP address of the NAS as a manual workaround?

     

    Looking forward to usig the product.

     

    Thanks

     

×
×
  • Create New...