“The format did not complete successfully”


A few days ago a colleague of mine was to add a few more disks in a Windows cluster 2003 Enterprise, and create a new Failover Cluster Instances, and one of the disks, an gave an error “The format did not complete successfully.”

Format

The cause off this issue, is validated by the presentation of the discs through the Storage, and presented a new LUN and still give the same error. Attempted to make the format in various ways, but without success.

After some research we came across an article that references the activation of automount

This problem may occur if AutoMount is not turned on on a computer that is running Windows Server 2003, Enterprise Edition. When AutoMount is turned on, and a new hard disk is detected, AutoMount automatically tries to assign a drive letter and mount the disk”

To resolve this problem, follow these steps:

  1. At a command prompt, type mountvol /e to turn on the Automount option for new disks.
  2. Run the New Partition wizard. Format a new volume that does not have a drive leter.

At a command prompt, type mountvol /n to turn off the Automount option.

VERY IMPORTANT Do not leave the Automout option turned on on systems that have complex storage configurations, such as Storage Area Networks (SANs). On systems where drives are exposed to more than one system, the drives could be exposed to unexpected systems. This exposure could cause these systems to lose data access or could cause data corruption.

Source: Microsoft Kb.

How to check allocation unit size


The best way, and the right tool for the job is fsutil. In command line just type;

fsutil fsinfo ntfsinfo <drive>:

Examplae: fsutil fsinfo ntfsinfo c:

Output:

C:\>fsutil fsinfo ntfsinfo e:
NTFS Volume Serial Number : 0x0e6640c86640b1ef
Version : 3.1
Number Sectors : 0x0000000018ffe2fb
Total Clusters : 0x000000000031ffc5
Free Clusters : 0x0000000000059043
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
Bytes Per Cluster : 65536
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000280000
Mft Start Lcn : 0x000000000000c000
Mft2 Start Lcn : 0x000000000018ffe2
Mft Zone Start : 0x00000000002e88c0
Mft Zone End : 0x0000000000307ea0

🙂

Static Routing in Windows Server 2008


Static Routing
in Windows Server 2008

We have been using the route command for years. You can configure
static routing in Windows 2008 Server using either the route command or using
the GUI. However, if you use the Windows GUI interface, those routes will not
be listed in the CLI interface, when you type route print. Thus, I
highly recommend that if you are going to use static routing in Windows 2008,
you just use the route command at the windows command prompt.

So let’s look at some examples of how you configure static routing using
the route command:

Show the static routing table

Showing the static routing table is easy, just use the route print
command, as you see in Figure 1 below.

Figure 1: Showing the IP Routing table in Windows Server 2008

In the route print output, the first important thing that you see is the
interface list. Windows Server IP interfaces are labeled with an interface
number. The interface numbers in Figure 1 are 16, 14, 1, 15, 20, and 12. These
interface numbers are used whenever you add or delete routes to the routing
table.

The second important thing in the route print output is the IPv4
Routing Table. This shows us the network destination, network mask, the default
gateway, interface, and metric. This table tells the Windows Server where to
route the traffic.

Add a static route

So how do you add a static route at the command line? The answer is easy-
use the route add command, like this:

route add 1.1.1.0 mask 255.255.255.0 10.0.1.1 if 1


As you see in Figure 2, the results of our route add was an affirmative
“OK!”

Figure 2: Using the route add command in Windows 2008

What was important in the route add command was the network we want to add,
its subnet, the destination/gateway, and the interface for that route.

This writes the persistent route to the following Windows Registry key as a
string value (REG_SZ):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\

Parameters\PersistentRoutes

Delete a static route
Deleting a route is even easier than adding a route. All you have to do is
to tell route delete the network that you want to remove, as you see in
Figure 3.

Figure 3: Using the route
delete command in Windows 2008

So those are the basics of configuring static routes at the command line.

Change disks in SQL Cluster.


Here are the general steps recommended for the migration of SQL Storage volumes, for instance:Ensure that there are Full backups of all databases in the system, when just prior to migration.

Stop all SQL Server services (Cluster Manager – Take Offline Services SQL only).

Assigning the new storage volumes and Drive Letter’s temporary copies.

Full copy of all existing data, keeping the ACLs of existing volumes to new ones.

Removal of dependencies on the SQL Service of old records.

Removing the Drive Letter’s of old records and assignment of these new discs to Drive Letters (attention has to be guaranteed that all drive Letters are kept for each volume replaced)

We recommend that prevented access by the operating system on both nodes to the old disk (disable the making of the Path, or another method which ensures that the OS does not access the old disk), but keeping the data intact in case you need to RollBack.

Allocation of new volumes in the SQL Cluster Group.

Making even the services of SQL “Offline” Move SQL group for each of the physical nodes in the cluster, must raise all funds, with the exception of SQL Services. With this step we ensure that the new volumes are correctly recognized by the OS of each physical node.

Assign dependencies removed in section 5 to the SQL Service, should be exactly the same as previously existing.

Making again the SQL Failover Group, even with the SQL services “Offline”, among all physical nodes in the cluster.

Making the Bring Online Services and SQL Move Group from all physical nodes in the cluster to ensure that the SQL service is started successfully on all physical nodes in the cluster.

You can follow the following article concerning optimization of the discs to SQL Server 2008: