Although the Apple iPhone is coming out this Friday it seems that the overseas release might still have some hiccups. When I went to a local Swisscom vendor (Manor in Geneva) to ask about it they seemed to be thoroughly confused on all points except the release date. Read More...

Tags: iphone

If you are looking for some manual puzzles for a gift or to while away the time, and you come across puzzles from the Japanese company Hanayama, keep looking. Read More...

Tags: quality

Wow, now that's some advertisment... catchy tune, surreal landscape, cute characters, great story progression. I do not think I have ever watched a publicity 4 times just to catch new tidbits I'd missed. If you haven't seen their work check out http://www.trapcode.com/gallery/psyop_coke.mov or their main website at http://www.psyop.tv. They have done some great advertising work.

Tags: coke, trapcode, Advertisement

Although I still do not know the source of this error (essentially my exchange store stopped being able to mount) the fix was rather obvious. Searching the web did not help though. Microsoft said it was a problem in Exchange 2003 SP1 and Googling showed me many people who gave up and restored their last backup (which of course would be the best solution).

ESEUTIL by itself kept throwing the same JET_errFileIOBeyondEOF error except for eseutil /k "C:\Program Files\Exchsrvr\MDBDATA\priv.1.edb" This showed that my .edb data was fine but it stopped at the .stm file.

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating CHECKSUM mode...
Database: C:\Program Files\Exchsrvr\MDBDATA\priv1.edb
Streaming File: C:\Program Files\Exchsrvr\MDBDATA\priv1.STM
Temp. Database: TEMPCHKSUM5352.EDB


File: C:\Program Files\Exchsrvr\MDBDATA\priv1.edb

Checksum Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................


29186 pages seen
0 bad checksums
0 correctable checksums
316 uninitialized pages
0 wrong page numbers
0x42c067 highest dbtime (pgno 0xd4)

1825 reads performed
114 MB read
2 seconds taken
57 MB/second
1809651 milliseconds used
991 milliseconds per read
1516 milliseconds for the slowest read
63 milliseconds for the fastest read

File: C:\Program Files\Exchsrvr\MDBDATA\priv1.STM


So I simply deleted my .stm file and rebuilt it with C:\Program Files\Exchsrvr\bin>eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb". Voila, it worked and I could mount my Exchange Store! CAUTION: there may be user information in this file. If your users are all Outlook clients it is probably not much used but if your users are IMAP/POP3 users then they may have a lot of information there which will be lost. Q555146. Always make a backup of any file that you are recreating.

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode...
Database: C:\Program Files\Exchsrvr\MDBDATA\priv1.edb
Streaming File: C:\Program Files\Exchsrvr\MDBDATA\priv1.STM
Temp. Database: TEMPREPAIR4596.EDB

Checking database integrity.

Scanning Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................


Scanning the database.

Scanning Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................


Repairing damaged tables.

Scanning Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
.........................
Deleting unicode fixup table.
..........................


Repair completed. Database corruption has been repaired!

Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.

Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 116.391 seconds.

Below are some additional links to Microsoft support write-ups.
Q313184
Q555146

The software raid solutions of Windows 2003 is designed to only allow access to your mirrored data. For example you can install the mirrored disk into another working system to access the folders. It is not designed to be a bootable recovery solution in case the primary disk fails. Simply taking the good working drive and trying to boot from it will fail. You should be able to boot from a boot disk but not boot the mirrored drive itself.

The first most likely problem is that the mirrored drive does not have a MBR. This can be fixed using your Windows Server CD and booting to the recovery console. There you can use the FIXMBR command to write a Master Boot Record to your mirrored drive. Using the Recovery Console will also verify if the mirrored drive has a working system as it will show up as a Windows installation and you will be asked for your Windows Admin password to get access to the console.

You also might not have a proper boot.ini file. You can check this using the recovery console's bootcfg command. For me it worked but I would not rely on this in an emergency. I had simply wanted to move my Windows 2003 installation to a bigger disk so I always had a good backup to fall back on. Normally I would use Acronis workstation to clone my drive but for some reason it would just restart (when booting from the CDROM) everytime I tried to clone my Windows Server's dynamic disk partition.

NOTE: If you are tying to simply duplicate your drive, be sure to not break the mirror with both drives connected. If you do so then one of the drives will receive a new drive letter and probably not be able to boot with it. You should always break the mirror with one of the drives already removed.

Tags: windows, mirror