semaphore timeout
Question posted by: Margie
(Guest)
on
July 20th, 2005 02:00 AM
Hi, has anyone gotten the error "semaphore timeout" when trying to do
a backup to disk? The disk is a logical partition. There are two
drives, c: and d:. Backing up to c: is fine. However, backing up to
d: produces the error below. Thanks in advance for any help.
Here is the command : backup database model to TestM2
2003-07-19 09:21:35.77 spid51 Error: 15457, Severity: 0, State: 1
2003-07-19 09:21:35.77 spid51 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to
install..
2003-07-19 09:21:35.83 spid51 Using 'xplog70.dll' version
'2000.80.194' to execute extended stored procedure 'xp_msver'.
2003-07-19 09:22:42.28 spid51 BackupMedium::ReportIoError: write
failure on backup device 'D:\Full'. Operating system error 121(The
semaphore timeout period has expired.).
2003-07-19 09:22:42.28 spid51 Internal I/O request 0x2B150AE8: Op:
Write, pBuffer: 0x2B250000, Size: 458752, Position: 72192, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0x11A00, OffsetHigh: 0x0,
m_buf: 0x2B250000, m_len: 458752, m_actualBytes: 0, m_errcode: 121,
BackupFile: D:\Full
4
Answers Posted
This most likely means your hard drive is about to fail or has corruption.
"Margie" <spy_234432@yahoo.com> wrote in message
news:8a535156.0307291239.5d859857@posting.google.c om...[color=blue]
> Hi, has anyone gotten the error "semaphore timeout" when trying to do
> a backup to disk? The disk is a logical partition. There are two
> drives, c: and d:. Backing up to c: is fine. However, backing up to
> d: produces the error below. Thanks in advance for any help.
>
> Here is the command : backup database model to TestM2
>[/color]
I've done more troubleshooting and have determined that "backup log"
works, whereas "backup database" does not. How weird!
Also, I ran chkdsk, but it does not show anything. It's an NTFS, so I
think it might be better to run upon reboot. But here are the
results.
Thanks again for any suggestions/help!
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3
Security descriptor verification completed.
14675345 KB total disk space.
8677676 KB in 191 files.
60 KB in 57 indexes.
0 KB in bad sectors.
68129 KB in use by the system.
65536 KB occupied by the log file.
5929480 KB available on disk.
4096 bytes in each allocation unit.
3668836 total allocation units on disk.
1482370 allocation units available on disk.
Anytime I've seen this error it was due to a problem with hardware in the disk subsystem. Maybe a
SCSI cable is bad, or your RAID card is getting flaky. These things might not show up in a
CHKDSK; you might need to use some of the utilities that come with your RAID card to evaluate the
disks' health.
"Margie" <spy_234432@yahoo.com> wrote in message
news:8a535156.0307300757.7be80a56@posting.google.c om...[color=blue]
> I've done more troubleshooting and have determined that "backup log"
> works, whereas "backup database" does not. How weird!
>
> Also, I ran chkdsk, but it does not show anything. It's an NTFS, so I
> think it might be better to run upon reboot. But here are the
> results.
>
> Thanks again for any suggestions/help!
>
> The type of the file system is NTFS.
>
> WARNING! F parameter not specified.
> Running CHKDSK in read-only mode.
>
> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Index verification completed.
> CHKDSK is verifying security descriptors (stage 3
> Security descriptor verification completed.
>
> 14675345 KB total disk space.
> 8677676 KB in 191 files.
> 60 KB in 57 indexes.
> 0 KB in bad sectors.
> 68129 KB in use by the system.
> 65536 KB occupied by the log file.
> 5929480 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 3668836 total allocation units on disk.
> 1482370 allocation units available on disk.[/color]
D Newton,
Thanks for your help. It did turn out to be a bad disk problem. When
we ran chkdsk /r, it discovered some bad sectors. We ran chkdsk to
fix them. After that, we de-fragged the disk. The backup worked fine
after that.
Thanks, Margie
|
|
|
What is Bytes?
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over 196,952 network members.
Top Community Contributors
|