windowswideopen.com

Normally recommended free space should not drop below 15 percent of drive size.

Here are some common symptoms of low computer hard disk space.

1. The computer stops responding (hangs) unexpectedly, infrequently, or at random intervals.
2. The computer hangs, or automatically restarts (often without error messages in the event logs).
3. The computer repeatedly hangs or automatically restarts at predictable intervals (often without error messages being written to the event logs).
4. Loading or saving files is slow or fails.

CAUSE

These symptoms can occur if there is significant file fragmentation or not enough

available disk space. File fragmentation or a lack of sufficient disk space can cause the following conditions:

Technorati Tags: Free Disk space , Hard disk space

1. A lack of contiguous or useable file storage space.
2. The inability of the Master File Table to dynamically increase its allocated space or to use existing allocated space as file storage space, including the necessary directory pointers.
3. The inability of temporary files or folders or log files to dynamically increase at startup or during computer operation (including the paging file, temporary files, and temporary folders).
4. Improper hard disk data configuration and space usage. This issue can usually be eliminated if RAID is configured with at least 75% write back cache and where at least 25% free space is available. On a busy file system, hard disks with only 15% free space should be considered as full. If compression is enabled a bit more free space is needed.

Disks Operating SystemDisks Operating System

No Comments »
Filed under: Operating System, Disks

Here are a list of some of the potential causes of poor SAN performance:

1. HBA firmware, drivers, configuration settings
2. Fibre Channel switch configuration issues
3. Contention in the SAN between the server and storage
4. Settings on the storage unit
5. “Split I/O” on hardware RAID volumes
6. Conflicting software or drivers

Troubleshooting steps to take:

1. Update outdated HBA firmware and drivers as they may resolve the issue.
2. Contact the relevant HBA card vendor to help detect non-standard HBA drive settings.
3. Review HBA BIOS settings
4. Check queue depth settings for Qlogic and Emulex HBAs
5. Check all points between the server and the storage unit. If a fibre channel switch is involved then check port logs on the switch for CRC, encoding (ENC), timeout, loss of light, and other errors.
6. If the storage unit has a reporting facility then check all logs for errors. Also check the cache settings such as write back” vs. “write through” as cache settings can have a huge impact on performance.
7. Run a performance log that includes the physical disk, processor, and system objects. Look for high “disk queue length”. Note that the disk queue length for a given SAN volume is the total number divided by number of disk spindles per volume. A sustained reading over 2 for “disk queue length” indicates congestion.

Also see:

Troubleshoot Windows Disk Problems
Troubleshooting Windows SAN Problems

Disks Fibre Channel SAN PerformanceDisks Fibre Channel SAN Performance

No Comments »
Filed under: Disks

The following are system events that are symptoms of I/O hanging or blocking between a host
and storage device(s):

Event ID: 3
Source: LDM
Description: [computername] A Dynamic Volume
(\Device\HarddiskDmVolumes\(diskgroup)\Volume(n)) has failed.
Event ID: 9
Source: [scsi miniport driver]
Description: The device, \Device\ScsiPort1, did not respond within the
timeout period.
Event ID: 15
Source: [scsi miniport driver]
Description: The device, \Device\ScsiPort1, is not ready for access yet.
Event ID: 26
Source: Application Popup
Description: Application popup: Windows - Delayed Write Failed : Windows
was unable to save all the data for the file
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume{n}\… The data
has been lost.
Event ID: 50
Event Source: Disk
Description: {Lost Delayed-Write Data} The system was attempting to
transfer file data from buffers to \Device\Harddisk\Volume{n}. The write
operation failed, and only some of the data may have been written to the
file.
Event ID: 51
Event Source: Disk
Description: An error was detected on device \Device\Harddisk{n}\DR{n}
during a paging operation.
Event ID: 29
Event Source: dmio
Description: dmio: Harddisk2 read error at block {n}: status 0xc000009d.

Event ID: 41
Event Source: FTDISK
Description: The file system structure on the disk is corrupt and
unusable. Please run the chkdsk utility on the device
\Device\Harddisk{n}\Ft{n} with label {label}.

The following system events are symptoms of general hardware problems either with the host
or with the storage device:
Event ID: 2
Event Source: dmboot
Description: [computername] dmboot: Failed to start volume Volume7 (no
mountpoint)
Event ID: 7
Event Source: Disk
Description: The device, \Device\Harddisk{n}\DR{n}, has a bad block
Event ID: 11
Event Source: [scsi miniport driver]
Description: The driver detected a controller error on Device\ScsiPort1
Event ID: 29
Event Source: dmio
Event Type: Information Description:
dmio: Harddisk9 read error at block {########}: status 0xC000009A
Event ID: 30
Event Source: dmio
Description: dmio: Harddisk1 write error at block {########}: status
0xc000009d
Event ID: 37
Event Source: dmio
Description: dmio: Disk Harddisk1 block {########} (mountpoint D:):
Uncorrectable write error
Event ID: 55
Source: NTFS
Description: The file system structure on disk is corrupt and unusable.
Please run the chkdsk utility on the volume “Drive_letter:”
Here:
● status code 0xC000009A = STATUS_INSUFFICIENT_RESOURCES
● status code 0xC000009C = STATUS_DEVICE_DATA_ERROR
● status code 0xC000009D = STATUS_DEVICE_NOT_CONNECTED

The following event log entries are indicative of issues involving zoning or path configuration
issues:
Event ID: 1
Source: SDDMAN
Description: [computername] Device \Device\Harddisk1\DR0 path [n]
offline.
Event ID: 2
Source: SDDMAN
Description: [computername] Device \Device\Harddisk1\DR0 path [n] online.
Event ID: 31
Source: dmio
Description: [computername] dmio: Harddisk9 write error at block 6 due to
disk removal
The following event log entries indicate a change in the underlying hardware, such as a
volume expansion at the hardware level:
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 31
Description:
dmio: Harddisk0 write error at block {########} due to disk removal
Event Type: Warning
Event Source: LDM
Event Category: None
Event ID: 1000
Description:
Cannot grow LUN Harddisk{n}: Config copy write failed
Event Type: Warning
Event Source: LDM
Event Category: None
Event ID: 1000
Description:
Disk group CompernameDg{n}: Errors in some configuration copies:
Disk Harddisk0, copy 1: Block 0: Disk read failure
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 34
Description:
dmio: Harddisk0 is re-online by PnP

delayed write failed Disks event id harddisk hardware problems storage device windows delayed write faileddelayed write failed Disks event id harddisk hardware problems storage device windows delayed write failed

2 Comments »
Filed under: Disks