cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

BESR 8 - Unable to see C-Drive upon startup

Deerfield
Not applicable

‎05-07-2008 05:26 AM

Just installed BESR 8 on Win XP Pro Dell machine.  When I attempt to create first recovery point the product does not detect the "C" drive.  It is a sata drive with a second mirrored sata drive installed internally.  BESR does detect the mirrored drive "M" and the other external drives.
 
I have uninstalled and reinstalled the software with no luck. 
 
Any suggestions or ideas?
 
Thanks.
0 Kudos
10 REPLIES 10

oscubed
Level 3
Partner

‎06-05-2008 09:25 PM

I have the same issue
Intel RAID Driver on an HP Server
Mirrored "C" drive
Recognizes attached USB drive, but not "C" drive
Drive is present and accounted for in disk management etc.
BESR 8.02
Windows 2008 Server (64 bit) with Hypervisor enabled
 
 
0 Kudos

Joseph_L_
Level 5
Employee

‎12-08-2008 08:18 AM

Gather technical support information by browsing into the BESR install directory. Within the 'Utility' folder run 'partinfo.exe'. Post the results.

 

 

0 Kudos

oscubed
Level 3
Partner

‎12-08-2008 10:29 AM

- Copyright (c)2007, 2008 Symantec Corporation. All rights reserved. THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF SYMANTEC CORPORATION. USE, DISCLOSURE OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF SYMANTEC CORPORATION. The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.212 and DFARS Section 227.7202. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - %BEInstLogsDir%\* - %windir%\bkupinst.htm - %windir%\vxinst.log - %windir%\bkuptemp.log - %windir%\bkupinst.log - %SystemDir%\bepushes.log - %SystemDir%\bepush.log - %windir%\strpimon.log - %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt - %windir%\MSDE_BKUPEXEC.log - %windir%\VxSDM.log - %windir%\besernum.xml - %windir%\besernum.txt - - %windir%\MSDE_BKUPEXECDLO.log - %TEMP%\DLOAgentInstall.txt - - %windir%\JRE.log - %windir%\JRE.ISS - %windir%\evinst.log - %windir%\EISSetup.log - %SystemDir%\jupdate-1.4.2_03-b02.log - %windir%\MSDE_EXECVIEW.log - - %windir%\VREInst.log - %VreInstallPath%\Install\res.ini - - %AllUsersProfile%\Application Data\Symantec\Backup Exec CPS\Logs\cpsinst.log - %CPSInstallPath%\Install\res.ini - - %TEMP%\BESRInstall.log - - %TEMP%\*ExchangeRetrieve*.log - - %AllUsersProfile%\Application Data\Symantec\Backup Exec CPS\Logs\cpsinst.log - %BESRInstallDir%\Manager\Services\*.log - %BESRInstallDir%\Manager\Services\tomcat\conf\*.* - - - %VXGATHER_EXEDIR%\BEDIAG.EXE %VXGATHER_WORKINGDIR%\BEDIAG.EXE %BEInstDir%\BEDIAG.EXE - %VXGATHER_EXEDIR%\BEDIAG.EXE %VXGATHER_WORKINGDIR%\BEDIAG.EXE %BEInstDir%\BEDIAG.EXE - %VXGATHER_EXEDIR%\BEDIAG.EXE %VXGATHER_WORKINGDIR%\BEDIAG.EXE %BEInstDir%\BEDIAG.EXE - %VXGATHER_EXEDIR%\BEDIAG.EXE %VXGATHER_WORKINGDIR%\BEDIAG.EXE %BEInstDir%\BEDIAG.EXE - %VXGATHER_EXEDIR%\BEDIAG.EXE %VXGATHER_WORKINGDIR%\BEDIAG.EXE %BEInstDir%\BEDIAG.EXE - - %VreInstallPath%\Logs\*.* - %VreInstallPath%\Services\w32info.exe - %VreInstallPath%\Services\w32stats.exe - %VreInstallPath%\Services\w32query.exe - - %CPSInstallPath%\Logs\*.* - %CPSInstallPath%\Autonomy\Logs\*.* - %CPSInstallPath%\Services\w32info.exe - %CPSInstallPath%\Services\w32stats.exe - %CPSInstallPath%\Services\w32query.exe - - %AllUsersProfile%\Application Data\Symantec\LiveUpdate\Log.LiveUpdate - %AllUsersProfile%\Application Data\Symantec\LiveUpdate\Settings.LiveUpdate - %AllUsersProfile%\Application Data\Symantec\LiveUpdate\LUInstall.LiveUpdate - %AllUsersProfile%\Application Data\Symantec\LiveUpdate\Product.Inventory*.LiveUpdate - - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery\Logs\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery\History\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery\Schedule\*.pqj - %AllUsersProfile%\Application Data\Symantec\VProConsole\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery\CommandFiles\*.* - %BESRInstallDir%\Agent\Create Custom Symantec Recovery Disk.log - %BESRInstallDir%\Agent\LightsOut Restore Wizard.log - %AllUsersProfile%\Application Data\Symantec\VProConsole\*.xml - %SystemDrive%\VProRecovery\*.* - %BESRInstallDir%\Utility\partinfo.exe - %BESRInstallDir%\Utility\smedump.exe - %ProgramFiles%\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe - - %BESRInstallDir%\Manager\Logs\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery Manager\Management Control\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery Manager\EasyInstaller\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery Manager\Console\*.* - %BESRInstallDir%\Manager\Services\tomcat\WebApps\axis\depot\logs\server\*.log - %BESRInstallDir%\Manager\Services\tomcat\logs\*.log - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery Manager\Management Control\*.* - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery Manager\Management Control\CommandFileSubDir\*.* - %BESRInstallDir%\Manager\Services\Database\rmdb.* - %ProgramFiles%\Common Files\Symantec Shared\Logs\*.txt - %AllUsersProfile%\Application Data\Symantec\Backup Exec System Recovery Manager\Indexer Control\*.xml - %ProgramFiles%\Common Files\Symantec Shared\Indexing\SUIR\Logs\*.* - %BESRInstallDir%\Manager\Logs\trace_WRG*.txt - - %BESRInstallDir%\Exchange Retrieve\*.log %BESRInstallDir%\Exchange Retrieve\win64\*.log - %BESRInstallDir%\Exchange Retrieve\log\*.log %BESRInstallDir%\Exchange Retrieve\win64\log\*.log - %VxUpdateInstallPath%\*.xml - %BEDebugDir%\*.* - %BEServerSigLogger% - %BkupExecSigLogger% - %TEMP%\DLOClient.log - %SQLLogsDir%\*.* - %BEDataDir%\%BELogFileRoot%*.xml - %BEDataDir%\msgq*.* - - - %DrWatsonDir%\drwtsn32.log %windir%\drwtsn32.log %CommonDocumentsDir%\DrWatson\drwtsn32.log %AllUsersProfile%\Application Data\Microsoft\Dr Watson\drwtsn32.log %MyDocumentsDir%\DrWatson\drwtsn32.log %LocalAppDataDir%\Microsoft\Dr Watson\drwtsn32.log - %CrashDumpFile% %windir%\user.dmp %CommonDocumentsDir%\DrWatson\user.dmp %AllUsersProfile%\Application Data\Microsoft\Dr Watson\user.dmp %MyDocumentsDir%\DrWatson\user.dmp %LocalAppDataDir%\Microsoft\Dr Watson\user.dmp - - %PerfMonLogDir%\*.* - %SystemRoot%\setupact.log* %SystemRoot%\setupapi.log* %SystemRoot%\setuperr.log* %SystemRoot%\setuplog.txt %SystemRoot%\repair\setup.log %SystemRoot%\INF\setupapi.app.log* %SystemRoot%\INF\setupapi.dev.log* %SystemRoot%\Panther\setupact.log* %SystemRoot%\Panther\setuperr.log* %SystemRoot%\Panther\UattendGC\setupact.log* %SystemRoot%\Panther\UattendGC\setuperr.log* - - %ComSpec% - %TcpipDatabaseDir%\HOSTS - %TcpipDatabaseDir%\LMHOSTS - %TcpipDatabaseDir%\SERVICES - %windir%\DASetup.log - - - %TEMP%\DownloadManager*
0 Kudos

Joseph_L_
Level 5
Employee

‎12-09-2008 11:00 AM

This is not the correct log. Please post the log for 'partinfo.exe'.
0 Kudos

oscubed
Level 3
Partner

‎12-09-2008 01:53 PM

partinfo    PID (5368)

Base Build Number: 28254    Base Build Date: Aug  7 2008  16:03:34
OsVersion:
    Generation:               Microsoft Windows Server 2008
    Flavor:                   Enterprise Server
    OsArchitecture:           64-bit operating system
    KernelType:               Windows NT
    ProcessorArchitecture:    x64 (EM64T/AMD64)
    VersionNumber:            6.0.6001
    ServicePackVersionNumber: 1.0.0
    KernelVersionNumber:      0.0.0
    Path:                     file:///C:/Users/administrator.OS-CUBED/WINDOWS/
    ComputerName:             2008E-OS3-01
    Features:
        Execute64BitBinaries
        Execute32BitPrograms
        Hibernate
        MultipleMonitors
        NT4FTVolumes
        DynamicDisk
        NtfsLonghorn
        Fat32
        WindowsDomainMember

CPU: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz
    CPU Vendor:         GenuineIntel
    CPU Signature:      000006f7      CPU Features:       bfcbfbff
    Hyperthreads/core:         1      Cores/Package:             4
    Logical procs/pkg:         4      Number of packages:        2

    Processor cores:
    ----------------
    Processor 1: package id=0x00      core id=0x00    APIC id=0x00  affinity mask=0x00000001
    Processor 2: package id=0x00      core id=0x01    APIC id=0x01  affinity mask=0x00000002
    Processor 3: package id=0x00      core id=0x02    APIC id=0x02  affinity mask=0x00000004
    Processor 4: package id=0x00      core id=0x03    APIC id=0x03  affinity mask=0x00000008
    Processor 5: package id=0x04      core id=0x00    APIC id=0x04  affinity mask=0x00000010
    Processor 6: package id=0x04      core id=0x01    APIC id=0x05  affinity mask=0x00000020
    Processor 7: package id=0x04      core id=0x02    APIC id=0x06  affinity mask=0x00000040
    Processor 8: package id=0x04      core id=0x03    APIC id=0x07  affinity mask=0x00000080

    NX bit supported:                Yes      x64 Capable:                     Yes      Supports HW Virtualization:       No
    Virtual Addr Bits:        48      Physical Addr Bits:       36
    OS CPU Count:              8      Processor Mask:     000000ff
    Min App Addr:       00010000      Max App Addr:       7FFEFFFF
    Page Size:              4096
    Memory Usage:            92%
    Total Physical:      8190 MB
    Avail Physical:       649 MB
    Total Page:         16581 MB
    Avail Page:          8861 MB
    Total Virtual:       2047 MB
    Avail Virtual:       1995 MB
    Avail Extended:         0 MB


Registry Key: System/CurrentControlSet/Services/VDS/Alignment
Alignment Settings in Bytes
     Between4_8GB         0x00100000  (1048576)
     Between8_32GB        0x00100000  (1048576)
     GreaterThan32GB      0x00100000  (1048576)
     LessThan4GB          0x00010000  (65536)


=========================================================================================================================
Disk Geometry Information for Disk 0         Sector Count: 976,768,647   (60,801 Cylinders, 255 Heads, 63 Sectors/Track)
Signature: 694154E2
Sector Size             Physical:  512             Logical:  512
Detected Sector Size:   512
Cache Line Size:        0
Byte Alignment Factors  Sector:  0           Cache:   0
Detected Alignment:     1 MB
.........................................................................................................................
System               Part Table LBA   # Boot     BCyl Head Sect FS      ECyl Head Sect       StartSect         NumSects
=========================================================================================================================
C:\
   On Disk Values:                0   0  80         0   32  33  07      1023  254  63            2,048      976,769,024
   Calculated:                                      0   32  33         60801   47  46 

WARNING: Partition above extends beyond the end of disk.

====================================================================================================================
Partition Information for Disk   0:               466 GB
Volume Path            PartitionType  Status         Size      Part Table Lba   #     Start Sector    Total Sectors
====================================================================================================================
                       Unallocated    Pri               1 MB             None  --                0            2,048
C:\                    NTFS           Pri,Boot        466 GB                0   0            2,048      976,769,024

C:\
====================================================================================
Volume Boot Record for Disk 0:  at Sector 2,048  (0x800)
File System: NTFS    (BPB NT Version)
====================================================================================
 1. Jump:                    EB 52 90
 2. OEM Name:                NTFS   
 3. Bytes per Sector:        512
 4. Sectors per Cluster:     8
 5. Reserved Sectors:        0
 6. Number of FATs:          0
 7. Root Dir Entries:        0
 8. Total Sectors:           0
 9. Media Descriptor:        F8
10. Sectors per FAT:         0
11. Sectors per Track:       63  (0x003F)
12. Number of Heads:         255  (0x00FF)
13. Hidden Sectors:          2048  (0x00000800)
14. Total Sectors (>32 MB):  0  (0x00000000)
15. Disk Unit Number:        128 (0x80)
16. Reserved For NT:         0x00
17. Extended Boot Sig:       0x80
18. Reserved:                0x00
19. Total NTFS Sectors:      976769023
20: MFT Start Cluster:       786432
21: MFT Mirror Start Clust:  61048063
22: MFT First Cluster:       786432
23: Clusters per FRS:        246
24: Clusters per Index Blk:  1
25: Serical Number:          0x9E5C79765C794A53
26: Checksum:                0  (0x00000000)


Volumes Reported by OS
==========================================================================================================================================
Volume Path            (Volume GUID)
    Disk #              Offset in Bytes               Size in Bytes             Starting Sector               Ending Sector      Size
==========================================================================================================================================


C:\       (\\?\Volume{6c2ecf97-05b1-11dd-a0b5-806e6f6e6963}\)
    Disk #  0                 1,048,576             500,105,740,288                       2,048                 976,771,071     466 GB

0 Kudos

oscubed
Level 3
Partner

‎12-09-2008 01:54 PM


 - - - - - - - - - - Disk 0: Master Boot Record (Sector 0) - - - - - - - - - - -

     0:  33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00        3ÀŽÐ¼.|ŽÀŽØ¾.|¿.
    10:  06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00        .¹..üó¤Ph..Ëû¹..
    20:  BD BE 07 80 7E 00 00 7C 0B 0F 85 10 01 83 C5 10        ½¾.€~..|..…..ƒÅ.
    30:  E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00        âñÍ.ˆV.UÆF..ÆF..
    40:  B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09        ´A»ªUÍ.]r.ûUªu.
    50:  F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74        ÷Á..t.þF.f`€~..t
    60:  26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00        &fh....fÿv.h..h.
    70:  7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13        |h..h..´BŠV.‹ôÍ.
    80:  9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00        ŸƒÄ.žë.¸..».|ŠV.
    90:  8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1E FE        Šv.ŠN.Šn.Í.fas.þ
    A0:  4E 11 0F 85 0C 00 80 7E 00 80 0F 84 8A 00 B2 80        N..…..€~.€.„Š.²€
    B0:  EB 82 55 32 E4 8A 56 00 CD 13 5D EB 9C 81 3E FE        ë‚U2äŠV.Í.]뜁>þ
    C0:  7D 55 AA 75 6E FF 76 00 E8 8A 00 0F 85 15 00 B0        }Uªunÿv.èŠ..…..°
    D0:  D1 E6 64 E8 7F 00 B0 DF E6 60 E8 78 00 B0 FF E6        Ñædè.°ßæ`èx.°ÿæ
    E0:  64 E8 71 00 B8 00 BB CD 1A 66 23 C0 75 3B 66 81        dèq.¸.»Í.f#Àu;f
    F0:  FB 54 43 50 41 75 32 81 F9 02 01 72 2C 66 68 07        ûTCPAu2ù..r,fh.
   100:  BB 00 00 66 68 00 02 00 00 66 68 08 00 00 00 66        »..fh....fh....f
   110:  53 66 53 66 55 66 68 00 00 00 00 66 68 00 7C 00        SfSfUfh....fh.|.
   120:  00 66 61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00        .fah...Í.Z2öê.|.
   130:  00 CD 18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07        .Í. ·.ë. ¶.ë. µ.
   140:  32 E4 05 00 07 8B F0 AC 3C 00 74 FC BB 07 00 B4        2ä...‹ð¬<.tü»..´
   150:  0E CD 10 EB F2 2B C9 E4 64 EB 00 24 02 E0 F8 24        .Í.ëò+Éädë.$.àø$
   160:  02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69 74        .ÃInvalid.partit
   170:  69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72 20        ion.table.Error.
   180:  6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69 6E        loading.operatin
   190:  67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E 67        g.system.Missing
   1A0:  20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74 65        .operating.syste
   1B0:  6D 00 00 00 00 62 7A 99 E2 54 41 69 00 00 80 20        m....bz™âTAi..€.
   1C0:  21 00 07 FE FF FF 00 08 00 00 00 50 38 3A 00 00        !..þÿÿ.....P8:..
   1D0:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        ................
   1E0:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        ................
   1F0:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA        ..............Uª

 - - - Disk 0:  Volume Boot Record Hex Dump at Sector 2,048  (0x800) - - -

     0:  EB 52 90 4E 54 46 53 20 20 20 20 00 02 08 00 00        ëRNTFS.........
    10:  00 00 00 00 00 F8 00 00 3F 00 FF 00 00 08 00 00        .....ø..?.ÿ.....
    20:  00 00 00 00 80 00 80 00 FF 4F 38 3A 00 00 00 00        ....€.€.ÿO8:....
    30:  00 00 0C 00 00 00 00 00 FF 84 A3 03 00 00 00 00        ........ÿ„£.....
    40:  F6 00 00 00 01 00 00 00 53 4A 79 5C 76 79 5C 9E        ö.......SJy\vy\ž
    50:  00 00 00 00 FA 33 C0 8E D0 BC 00 7C FB 68 C0 07        ....ú3ÀŽÐ¼.|ûhÀ.
    60:  1F 1E 68 66 00 CB 88 16 0E 00 66 81 3E 03 00 4E        ..hf.ˈ...f>..N
    70:  54 46 53 75 15 B4 41 BB AA 55 CD 13 72 0C 81 FB        TFSu.´A»ªUÍ.r.û
    80:  55 AA 75 06 F7 C1 01 00 75 03 E9 D2 00 1E 83 EC        Uªu.÷Á..u.éÒ..ƒì
    90:  18 68 1A 00 B4 48 8A 16 0E 00 8B F4 16 1F CD 13        .h..´HŠ...‹ô..Í.
    A0:  9F 83 C4 18 9E 58 1F 72 E1 3B 06 0B 00 75 DB A3        ŸƒÄ.žX.rá;...uÛ£
    B0:  0F 00 C1 2E 0F 00 04 1E 5A 33 DB B9 00 20 2B C8        ..Á.....Z3Û¹..+È
    C0:  66 FF 06 11 00 03 16 0F 00 8E C2 FF 06 16 00 E8        fÿ.......ŽÂÿ...è
    D0:  40 00 2B C8 77 EF B8 00 BB CD 1A 66 23 C0 75 2D        @.+Èwï¸.»Í.f#Àu-
    E0:  66 81 FB 54 43 50 41 75 24 81 F9 02 01 72 1E 16        fûTCPAu$ù..r..
    F0:  68 07 BB 16 68 70 0E 16 68 09 00 66 53 66 53 66        h.».hp..h..fSfSf
   100:  55 16 16 16 68 B8 01 66 61 0E 07 CD 1A E9 6A 01        U...h¸.fa..Í.éj.
   110:  90 90 66 60 1E 06 66 A1 11 00 66 03 06 1C 00 1E        f`..f¡..f.....
   120:  66 68 00 00 00 00 66 50 06 53 68 01 00 68 10 00        fh....fP.Sh..h..
   130:  B4 42 8A 16 0E 00 16 1F 8B F4 CD 13 66 59 5B 5A        ´BŠ.....‹ôÍ.fY[Z
   140:  66 59 66 59 1F 0F 82 16 00 66 FF 06 11 00 03 16        fYfY..‚..fÿ.....
   150:  0F 00 8E C2 FF 0E 16 00 75 BC 07 1F 66 61 C3 A0        ..ŽÂÿ...u¼..faÃ
   160:  F8 01 E8 08 00 A0 FB 01 E8 02 00 EB FE B4 01 8B        ø.è.. û.è..ëþ´.‹
   170:  F0 AC 3C 00 74 09 B4 0E BB 07 00 CD 10 EB F2 C3        ð¬<.t.´.»..Í.ëòÃ
   180:  0D 0A 41 20 64 69 73 6B 20 72 65 61 64 20 65 72        ..A.disk.read.er
   190:  72 6F 72 20 6F 63 63 75 72 72 65 64 00 0D 0A 42        ror.occurred...B
   1A0:  4F 4F 54 4D 47 52 20 69 73 20 6D 69 73 73 69 6E        OOTMGR.is.missin
   1B0:  67 00 0D 0A 42 4F 4F 54 4D 47 52 20 69 73 20 63        g...BOOTMGR.is.c
   1C0:  6F 6D 70 72 65 73 73 65 64 00 0D 0A 50 72 65 73        ompressed...Pres
   1D0:  73 20 43 74 72 6C 2B 41 6C 74 2B 44 65 6C 20 74        s.Ctrl+Alt+Del.t
   1E0:  6F 20 72 65 73 74 61 72 74 0D 0A 00 00 00 00 00        o.restart.......
   1F0:  00 00 00 00 00 00 00 00 80 9D B2 CA 00 00 55 AA        ........€²Ê..Uª

 

0 Kudos

Joseph_L_
Level 5
Employee

‎12-09-2008 03:19 PM



System               Part Table LBA   # Boot     BCyl Head Sect FS      ECyl Head Sect       StartSect         NumSects
=========================================================================================================================
C:\
   On Disk Values:                0   0  80         0   32  33  07      1023  254  63            2,048      976,769,024
   Calculated:                                      0   32  33         60801   47  46 

WARNING: Partition above extends beyond the end of disk.

====================================================================================================================

 

 

I have bolded and underlined your error. The issue here is to do with disc partitioning. BESR fails to load if there are discrepancies in the partition table or Master Boot Record regarding the disk geometry. As BESR performs sector based backups, the disk geometry must be correct. Windows ignores discrepancies because Disk Management creates it own drive overlay.

 

If your server is configured in a RAID you can attempt the steps listed in the technote article below, otherwise BESR will not properly enumerate C:\ without correcting the drive partitioning.

 

http://support.veritas.com/docs/293297

 

For further information, you may also review the following technote document:

 

http://support.veritas.com/docs/301250

Message Edited by Joseph L. on 12-09-2008 03:27 PM
0 Kudos

oscubed
Level 3
Partner

‎12-10-2008 04:48 AM

ok the first tech note is fairly useless - I can't "detach a drive array" then boot on a system that has the OS on the array.  This system was partitioned using Windows 2008's normal installation procedure - there was nothing funky about it.  It's a simple mirror SATA drive array.

 

If my partition table is bad - how come everything runs fine in windows?  I'm not seeing any errors, system passes chkdsk, etc. 

 

I'll look into the other technote.  I am not looking forward to the thrill of editing a partition on an un-backed up system though.

 

 

0 Kudos

oscubed
Level 3
Partner

‎12-10-2008 04:52 AM

The second technote is even more useless than the first.  I didn't do a restore on this drive - it never backed up.  The disk signature didn't change - it's exactly the way Microsoft created it on install with Win 2k8.

 

I'm obviously not the only one who has this problem (see above, and similar threads elsewhere) is it possible your system is detecting an error that isn't there?  Or that there is some other fix I can apply?  Or some way to ignore the error?  Because as it stands I have an OS I cannot backup with your product, and the only solution you seem to be suggesting is "backup the os, repartition then restore the OS".  Do you see the chicken and egg problem here?

 

0 Kudos

Joseph_L_
Level 5
Employee

‎12-10-2008 08:41 AM

The second technote I posted was for information only.

 

BESR uses partition information reported from the MBR to enumerate system drives as it is a sector based data recovery utility. Windows ignores discrepancies because 'Disk Management' creates it own drive overlay. Therefore, the first partition chart (which I posted) reported in 'partinfo' is more "accurate" than the information windows is reporting. 

 

Other than a complete format and repartition of the drive, the only other option is to manually edit the disk partition table. This however, is beyond the scope of Symantecs support. Incorrectly editing the disk geometry could cause the server not to boot as well as cause data loss.

 

You could also use Windows Server Backup utility to do a system backup. Format the hard disk, Reinstall the OS/drivers and then manually restore data.

 

 Information on Windows Server Backup:

 

http://technet.microsoft.com/en-us/library/cc770266.aspx

 


Message Edited by Joseph L. on 12-10-2008 08:49 AM
0 Kudos