Jump to content

RJGNOW

Members
  • Posts

    123
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by RJGNOW

  1. SNIP

     

    Has anyone ever had two drives go on them like this..? It seems incredibly unlikely, I'm thinking it's either:

    • Something in my server is faulty & fried the 2 Seagates in quick succession. Is that possible? What could do that?
    • or...
    • Both Seagates were Friday-afternoon lemons from the moment they were made. I bought them at the same time from Amazon - for all I know they were manufactured within minutes of each other. Is that a stupid theory?

    Opinions / advice would be welcome, as always!

     

    I have had 3 drives fail in a 2 week span, 2 of those three were ~4 days apart. All drives by the same manufacture.  Now my set up consists of 48TB so I have many drives so my failure % may not be all that "unlucky". 

     

    I alway duplicate important info at least 4x's...

  2. The "never" allow placement means that it won't allow placement on other drives... unless that drive is completely full and there are no other suitable drives (such as in the case of duplication and selecting only one drive for the rules). 

     

     

    The three settings I mentioned (sorry, they are in the main balancing tab), they control how the files are placed, in regards to the other balancers.  Unchecking the first, means that the file placement rules ignore the real time placement of the balancers. 

    The Third means that it ignores the balancers if it tells them to empty a drive (such as what the SSD optimizer may do, and what the ordered file placement and drive usage limiter balancers do).

     

     

    Ok, so this doesn't sound like I have any protection with this setup.  Not too mention, that even when implementing all your suggestions it's still gives me those warnings.. I can force a re-balance, which clears the blue folder warning (not the warning in yellow), but it doesn't last very long, and I'm back to the blue folder warnings...

     

    Is there any way I can achieve my goal?  ie: Use the SSD as the drive for reading and writing but also balance those files to the other drives for safety?

     

    b12218424670894.jpg

  3. The blue icon indicates that it's calculating and attempt to apply the file placement rules.  However, depending on the exact config, it may not be able to do so properly.

     

    On thing that may help here is to set the options on the rules to "never" allow placement on other drives, and see if that helps.

     

    If that doesn't help, try doing this:

    * UNCHECK "File placement rules respect real-time file placement limits set by the balancing plug-ins."

    * CHECK "Balancing plug-ins respect file placement rules."

    * UNCHECK "Unless the drive is being emptied."

     

    Does this mean that the data on the SSD will not be duplicated / Protected?

  4. I trying to understand what I'm looking at here....  Iv'e setup the SSD for Folder Placement rules, and I want to make sure they are being duplicated for protection...

     

    1) I'm always seeing a little blue folder to the right of every drive that says something like "File placement rules need to be applied"... What does that mean?

     

    2) When I open the balancing plug-in, under file placement,  I'm seeing what looks like a warning... 13.3 Gigs could not be moved because a suitable destination could not be found......"

     

     

    b949c1424489909.jpg

     

     

    8f7461424489913.jpg

  5. To clarify, the WSS Troubleshooter didn't properly create the shared folders in the dashboard?

     

    If that's the case, could you run "fsmgmt.msc", open the "Shares" section, find the shares in question, right click on them and select "Stop Sharing". Don't do this for the "NETLOGON", "REMINST", "SYSVOL", "Folder Redirection", or "File History Backups" shares.

    Then use the dashboard to create new shares with the existing locations. This should let you create them and set the permissions for them.

     

    That is correct..

     

    When you say "shares" are you referring to the folders??? There are quite a few folders (inside the ServerFolders folder) I would have to manual create here, 

  6. Brand new machine, fresh OS install.

     

    Problem:

    None of DrivePool folders are showing up in the Dashboard.   I can access them via \\SERVER though

     

    What I've Done:

    Took HDD from older server, installed in new server,  copied all folders over to new SSD, Removed Old SSD from New Server.

    Added all the drives to DP

    Shutdown DP Service

    Moved all folders from root of SSD to n:\PoolPart.xxxx\ServerFolders\

    Cleaned out C:\ProgramData\StableBit DrivePool. and "%AppData%\StableBit DrivePool" folders

    Rebooted server...

    Forced a Rebalance in DP

    Ran the Wss.Troubleshoot_2.0.0.1.exe to fix up permission

    Rebooted server

     

    Still folders are not showing up in the Dashboard.

     

    I've done this twice now, and still nothing..

     

     

     

     

     

  7.  

    1. Glad to hear that, and that should be good.
    2. Okay, though if they have existing data, you'll probably want to seed the pool (move the files in to the hidden PoolPart folder and remeasure the pool). 
    3. As for IO intenstive, I mean stuff like massive databases, hyperv, etc.  However, it sounds like it''s not going to be very data intensive at all, (otherwise, you'd be using SQL, I'd think, but I could be wrong).  And that should work great with StableBit DrivePool.

    As for the SSD stuff, you mean like the SSD Optimizer?

    https://stablebit.com/DrivePool/Plugins

    It places new files on the SSD, and then moves them off to the "archive" drives. 

     

    And you can use the File Placement rules to "lock" frequently accessed files to specific drives, as well.

     

     

     

    I'm looking for file safety and speed, will the File Placement rules to that?

  8.  

    Well, I'd recommend using Windows Server 2012R2 Essentials, specifically. There are some slight differences, but they're worth having.

     

    If you already have the software, then that's fine.

     

     

    As for migration, move the pooled drives over. They'll be recognized in the new machine as a pool (as long as you have StableBit DrivePool installed). But you may want to run the WSS troubleshooter on the system, to reshare the pooled files for you:

     
     
    As for StableBit DrivePool, it depends on the work load here.  If you're doing very IO intensive tasks, then a good RAID card may be much more worthwhile here, as you'll get MUCH faster reads and writes (depending on the array type).  

    However, for backups and other tasks that are not IO intensive, then I think it's a great fit for the small business environment. (especially with StableBit Scanner).  

    Just remember to backup the data, and make sure it ends up offsite at some point, just in case.  And yes, StableBit CloudDrive may be great for that purpose, actually.

     

    1) It's R2 so that's good.

    2) There is no DrivePool installed or setup on the existing WHS 2011 Machine, I want to use it due to my own personal experience with it. (and I really don't want to mess with a RAID configuration)

    3) How do I define "Very IO Intensive Tasks"?  I think the most IO action will be related to accessing a MS Access database. Would that be considered IO intensive?

     

    The current File Server is made up of both SSD's (used to house all the working data and one for the OS) and Standard 7200 RPM drives used for backups.  Is there a way to configure DrivePool to use an SSD as a type of landing drive for faster IO to the network, and duplicate across the slow 7200 RPM drives?

     

    Thanks again for your help!

  9. Long time DP and Scanner user for my home, but I've just been tasked with converting my employers file and remote servers into one machine running 2012 Essentials.

     

    Existing Systems:

     

    The "Remote" server (2008 R2) sole purpose was to allow 3 users access to some, on server, software programs, via RDS. (7 year old machine)

     

    The "File" server is a WHS 2011 machine and it's sole purpose is to house shared folders and backup all the desk top machines (All Windows 7 Pro). (8 year old machine)

     

    New System:

     

    New server is a i7 16Gigs of RAM and will serve both roles ( I understand the 3 users will have to use Anywhere Access to connect to their physical machines instead of RDP)

     

    Questions:

     

    What do you guys think about Drivepool in a small business (7 users) environment?  I'm now thinking about adding the CloudDrive solution also..?

     

    I would really appreciate any migration advice you can extend also, which includes the equipment, OS, etc...?

     

    TIA

  10. Thanks Christopher,

      1) If it is dangerous to move any file on the effected HDD, then why does DrivePool continue to use the drive (reads and writes)?  I would think that scanner should notify DrivePool of the error and at the very least cause DrivePool to stop utilizing the disk or start duplicating to another drive if at all possible.??

     

    OK: That solved it, so I guess when scanner does a surface scan it doesn't check the file system? As I ran 2 scans after I did a windows repair?

     

    2) On my WHS 2011 Box:

         a: When you attempt to repair the disk through Scanners UI, it crashes WHS connector window and pretty much locks the interface up it you try to reconnect. I send the files after this took place.

  11. Title says it all.... Damaged File System Error Will Not Clear.

     

    1) Removed drive from pool,

    2) Reformatted HDD

    3) Re-added drive to pool.

    4) Forced Scanner to rescan drive

     

    Error persists in scanner.

     

    5) double checked with the windows disk check and it return OK.

     

    Now what? (I just started a 2nd scan)

     

    I also noticed that even with a corrupted file system, DrivePool was still reading and writing data to that drive. I know that the drive will evacuate on a SMART error but it doesn't look like that happens with any other error???

     

    Scanner Version : 2.5.2.3074 BETA

     

  12. The build number may not be the latest, but the complete version including build number is higher.  Which is what led to the confusion.

     

    PS: The file is still listed as a download..

  13. If you look at the Beta download page I see this entry at the very bottom:

     StableBit.Scanner_2.6.0.3055_BETA.wssx                       23-Sep-2014 21:17   11M

    Is this dated incorrectly or is the version # incorrect?

     

     

  14. That's the problem.

     

    When you boot without StableBit DrivePool not installed the pool drive is not there and NFS can't find its shares.

     

    We do support upgrading by simply installing over an existing version (except when upgrading from 1.X to 2.X). Can you elaborate as to why you can't upgrade by simply running the new installer? Is there an error that comes up? What do you see?

     

    Thanks,

     

    I get this error when trying to install over.

     

    02fe36324455355.jpg

  15. This only happens on upgrade?

    And this is with the built in NFS Server for WHS2011?

     

    If so, then it's possible because the pooled disk is disappearing temporarily during the upgrade process.

     

    What version of DrivePool are you using again?

     

    And we'll look into this. (https://stablebit.com/Admin/IssueAnalysis/2186)

     

    1) Yes

    2) Yes

    3) Build .513

     

    Oh and I should add that every update requires me to first uninstall SB, Reboot, and Re-install the new version.  I have been unable to simply install over top an existing version, nor have I been able to uninstall and avoid a reboot.

  16. SUCCESS!!

    After several hours I finally discovered the source of the problem. The offending program was a program called Asus Remote Go.  It appears it was installed with the MB Drivers and only effects the stablebit pooled drive.  It does not effect any of the other drives (Mapped or local) on the machines.

     

    Posted for those who might end up with the same problem.

×
×
  • Create New...