Sonicmojo

I am getting this as well on assorted folders but VERY infrequently. Like I will go to a location that has not been accessed a very long time - say 6 months - go to create a folder and Windows complains that the folder cannot be created - then I check the parent folder properties and get various messages about permissions being in the wrong order etc etc. But this is happening on Windows 10 as well. I did run Windows 7 on this machine about a year ago and pool was created well before that. Would a "reset permissions" session be in order here? And would I apply it to the entire pool? My concern is that I am running my pool using drive points - so on my Windows 2012R2 server - it's one giant 14.5TB D drive. I am sensing this could take a long time to reset? Appreciate any comments or tips before I attempt this. Sonic.

So something like this? Deactivate the StableBit DrivePool license on existing server build Shut down the system Disconnect data drives (but leave them in the box) Power up Install Server 2016 (wiping C during install) Do basic config of new server install and shut down Reconnect existing data drives Power up and ensure data drives show in Disk Manager Create new mountpoints for data drives Install/Activate the StableBit DrivePool (And Scanner) software for new build Let it to "automagically" (automatically) recreate the pool on this new build Continue with rest of server config. Anything else I should be aware of? Sonic.

Drashna, I found this older thread where I asked you for some specifics on migrating disks from one server to another. I am back for more confirmation on what to do with existing disk sets (16TB in Server A and 6TB in Server B) if I plan to install a new OS. Within Q1 2018 - I want to upgrade both of these servers from Windows Server 2012 R2 to Server 2016. I have read a bit about "in-place" server upgrades - but I think I will start from scratch and install the OS clean on each - meaning I will need to power down the storage disks - disconnect them and then power them back up when Server 2016 is installed and ready to go. On both of my systems - I am using drive mountpoints to ensure each Pool - is displayed via a single Drive letter (D:\ in this case). Using your suggested procedure: Deactivate the StableBit DrivePool license, if needed. Shut down the system physically remove the drives Put the disks into the new system power on the new system install and activate the StableBit DrivePool software on the new system Wait for it to "automagically" (automatically) recreate the pool on this new system What other steps do I need to do (and when) within this list with regards to mountpoints etc on the drives without upsetting any data on them - and hopefully being able to recreate the pool and get them back on the network with minimal downtime? Appreciate your insight as always. Cheers! Sonic.

Getting the drive out of the pool was the only way to get DP to reorganize and to remove the "read only" state it placed on the pool as soon as my drive went "missing" My assumption all day yesterday was that the drive was suspect and I was going to remove it anyway, copy the files somewhere safe and either replace the drive or leave the pool usuable but smaller. If you read all about Drivepool here: https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Removing a Drive from the Pool It apparently does a bunch of nice things for the user - if the drive is healthy: When a drive is removed from the pool, StableBit DrivePool will move all of the unprotected pooled files stored on it onto a different drive that's part of the pool. StableBit DrivePool will also regenerate every protected file part that is on the disk being removed (unless Duplicate files later was selected). Then, the virtual pool drive shrinks in capacity by the size of the drive that was removed. But if a drive is unhealthy (or supposedly missing like mine was) - DP does a lock down on the pool. So the only way to get the pool usable (Read/write) again was to remove the drive. Regarding Windows Server Backup - there is so much bad press on this - it's not worth my time. As soon as I turned this thing on a few weeks back - the event log started filling with bizarre errors. I do not trust anything that is that difficult to get working. A clue prior to yesterday's problem was the sudden appearance of Event ID 157 ("Disk 1 has been surprise removed.") one minute before Scanner notified about a missing disk. If I cross-reference that message ID - with messages like this from various forums - starts to form an interesting picture on where the problem most likely lies... "On a recently deployed 2012 R2 system it looks like these warnings were generated during (or immediately after) a "Windows Server Backup". "Ever since my upgrade to Server 2012 R2 I too am logging this error. It is always in the 04:30AM time frame daily since the upgrade" "My server throws these messages every day while finishing its backup job (using Windows Server Backup)" Another thread is here: https://community.spiceworks.com/topic/463141-windows-server-backup-causing-eventid-157-disk-n-has-been-surprised-removed Could it be a bad cable - remotely possible - but this server is racked and cannot be opened - so it's not loose. I will continue to monitor and act if necessary. Cheers! Sonic.

Update Yesterday prior to heading out for the day - I shut the server down to ensure the drive in question would not be subject to any further data loss etc. I spent some of the day researching Scanner, Drivepool and some of the other event log messages I was seeing on the server early yesterday morning when this disk went missing. When I returned home from work - I read that my first move here should be to get this drive out of the Pool - as DP invoked it's "read only" mode to the entire pool due to the missing disk. So I fired up the server expecting to see the missing disk in DP. Much to my surprise - the server came up normally. All disks were online and acting normal. No messages in Event log. No messages in DP. No messages from CrystalDiskMark and no message from Intel Rapid Storage manager. Basically no messages from anything about anything. I immediately moved into analysis mode and started Scanner to have a good look at this disk. It scanned the entire disk and found nothing. All SMART readings are normal. As far as I can see - there is nothing wrong with this disk given all the angles I probed it from. A more interesting viewpoint is what I saw from other research regarding Windows Server backup (on 2012R2). I found a few articles and forums posts going into details about VSS, hot swap, filter manager and other oddball scenarios - where basically the Intel Rapid Storage Manager somehow thought that Disk 2 on this server was a hot swap disk and Windows (if just for a short minute or two @ 3:00 am yesterday (the time server backup runs) - decided this disk was pulled or disconnected and marked it as "missing". Even a reboot did not bring it back online. But after a complete shutdown? Success. I have had similar situations when using hard disks in hot swap trays on my workstation and the odd time Windows cannot "eject" a disk properly during hot swap and suddenly decides to make it invisible in Explorer etc - even tho the disk is clearly in the tray and running. Only a complete shutdown makes resets the disk subsystem and the disk does appear normally in Explorer after a restart. While I remain a tad skeptical on this - and have since stopped the clunky Windows Server Backup (I was only backing up the C: drive anyway) I cannot find anything in the slightest that makes me think this disk is suspect. I have backed up all data on it to be safe - but as of right now - it seems 100% solid. Good news is that Stablebit stuff was rock solid and I am glad I had it on board to give me peace of mind. Cheers! Sonic.

I do have duplication in the pool - but only on one specific folder in the pool (Videos). Will this make a difference? But i agreed with you on the process. If I can get this drive to behave (new cable, different port etc) - I would most certainly try to put in back in the server - add the new drive and then try the removal. But let's say the worst happens - like for example - I can only spin this disk up long enough on another machine just to get the data off of it? Is there another more manual guideline out there to move the data back into place AFTER a new disk has been added to the pool? Without actually having the old disk in the server? My fear is that if this suspect disk is getting actually close to a major failure - I really do not want to chance trying to spin in up in the server - and possibly compromising it completely. Thoughts? Sonic.

Thanks! Yes - I shut down the server before leaving for work today. As soon as I get back home - I will pull the drive and bring it over to my personal workstation and see what I can see. If I can spin it up on another machine - I will move to data copy immediately. I have never seen a drive simply die without any warning whatsoever - especially a NAS specific drive that should be a bit more resilient. The most ironic part about this is that I did not have Scanner set up correctly on this server for months and months and now - after just two days of having it correctly auditing the environment - I sudden have a drive fail? Karma or what? Now - assuming I can spin this drive up - and I can get at the data - what is the best way to get the data over to a replacement (which I am going to move forward with anyway) and rebuild the pool? Sonic

Hello, After months and months of solid service - I suddenly received an email from Scanner this morning saying a disk was "missing". I am using both Scanner and Drivepool on a Windows 2012R2 server. I have 5 drives in the system - one SSD for system and 4 4TB Seagate NAS drives to form the pool. ALL NAS drives are setup with mount points (No drive letters). All I know so far is that the disk is not visible in Disk Management or in CrystalDIskMark when run each within Windows when booted. I have done nothing else so far. Changes to the system within the last few days has only been to update to a beta edition of Scanner 2.5.2.3129. While I am realistic and drives do fail - this is most odd. The only other issue that may be a contributing factor is that Windows Backup was set to run at 3:00am on alternating days and I do see a series of "disk" type messages in Event viewer around these times for the last 2 weeks or so - but this is the first instance of an actual problem,. What should be my next move so as not to make things worse - AND to avoid data loss? Should I run Stable bit troubleshooter? Power down the box? Appreciate an update ASAP. Cheers, Sonic.

Chris, Have checked and now have the Start/Stop Automatically set right. I also have the "Unless disk scans are past due by X days" option enabled - and I assume since these disks have not been scanned for over 18 months - that is why Scanner is doing them now - outside my set "work" window (12:00am - 5:00am)? Scanner is grinding away since I posted this morning - and it looks good. With regards to this beta - is there anything special I need to do to install it? Do I need to shut down the existing Scanner - and if so - how? Appreciate an update on this. Sonic.

I have Scanner running on a Windows 2012R2 Server and installed this instance back in April 2016. I believe I had configured everything correctly - but today after months of what I thought was solid service - I see this when examining the drives: (see attachment). Under Settings - I have the scanning "work" set to happen between midnight and 5:00am but it seems that I have not had the actual Start/Stop Automatically button set. Is this how I need to have Start/Stop Setting configured (see StartStopSettings) If this is not correct - What do I need to have set to ensure that scanning happens ONLY between 12:00am and 5:00am? Also - I saw this error appear in the error logs today for the first time - ever. Ideas? Exception: System.NullReferenceException: Object reference not set to an instance of an object. at ScannerServiceLib.Info.SmartDiskInfo.#pt() at ScannerServiceLib.Info.SmartDiskInfo.#MS() at CoveUtil.ReportingAction.Run(Action TheDangerousAction, Func`2 ErrorReportExceptionFilter) Cheers, Sonic

Chris, I too am considering a server rebuild soon - and would like to do the same as the folks above. However - I am using drivepoints for my drives - which has worked perfectly. What is the correct order of business here: 1. Reinstall Windows Server 2. Connect my drives and redo the drivepoints 3. Then install DrivePool and Scanner ? Sonic

Thanks! Probably won't want to risk my server data with a bleeding edge build at this time. Will be patient for the next "public". Cheers! Sonic.

Not coming at this from a trouble/complaint angle but I noticed today that Drivepool remains at the same version level as when I started this past spring. Does this app ever get any updates. Or am I missing a notification or something? Cheers, Sonic

Wow. Awesome overview. Just what I needed. Now - some comments on SLAT - I did some digging and the only thing I could find is - looks like the CPU (on server) only needs SLAT if : "SLAT is required on the server if the RemoteFX role service is enabled" Since I am planning to create two stock SERVER VMs (one for a DC and one for WSUS - both running Server 2012 R2) I do not think I need SLAT for that. Will test this fact tomorrow during the build I wanted to thank you so much for the "ordered" list of what to do should I find out that this Q9550 is not up to the task of hosting a couple of basic VMs. One more Q: I did not use any drive letters on the current (SERVER A) build - all drives use mount paths. I would of course - use the same pathing logic on the new server - with the exact same drives mounted to the exact same paths. Will this make the transition a bit more seamless - if I really have to move DrivePool over to this secondary server? Will report back once I have gotten my hand dirty Cheers! Sonic

Finally have my new home server (SERVER A) stable and Drivepool is working very well. But - as a restless spirit - I cannot leave well enough alone - so here's what's cooking in the next week or so. In an effort to purge a huge pile of old parts from my stash (circa 2009-2012) I have now cherry picked the best couple of motherboards, CPU etc etc to build a secondary file server (lets call it SERVER B ) The intent of this second box is as a backup zone to our primary home server AND I also wanted to create a couple of VMs (Using Windows Server 2012R2 with the Hyper-V role enabled). But as I read more about the CPU I intend to use (Q9550) on the motherboard I intend to save (GigaByte EP45-UD3R) with the RAM I have available (8GB DDR2) - I am getting a sense that certain virtualization extensions for Hyper-V 2012 may not be fully supported given the age of these parts. I am also wary of the available RAM if I want to create several more VMS later. SERVER A has 16GB while SERVER B will only ever have 8GB. (DDR2 RAM is non existent now) So - I got to thinking - it may be much better to use my brand new Xeon based Server A for my Hyper-V experiments (as it has all modern Virtual extensions ready to roll) and instead transition the NAS drives from the new server over to this secondary build and make it the "primary file server". But what exactly would need to happen if I did decide to take the drives out of Server A and stick them in Server B? What exactly do I need to do on SERVER A to make a transition? Do I go into Disk Manager and simply "delete/remove" all the drives? Do I simply shut down the box and pull the drives out? Do I need to deactivate my DrivePool and Scanner licenses on Server A first - before removing drives? I am very keen on knowing the correct "order" of operations before I attempt anything as I cannot have the server drives compromised in any way. Just want to make sure I do it by the book - the right way - the first time. Any info on how to accomplish the following would be most appreciated. Cheers! Sonic.