Cannot enumerate drives

[David_Hicks_2]

I have an issue with System Recovery 8.5 that I cannot solve.

Installation was fine, but I get the dreaded 'cannot enumerate drives, and the cannot reconcile changes' errors. I had previously followed a procesure on the forum for removing .NET 2.0, clearing entries out, and re-installing version 8. I've been buying version 8.5 for other servers so thought I'd try 8.5 on this one.

I've done a chkdsk /f, all clear

I've defragged the drive.

I've run PartInfo which looked fine, no errors.

When running SMEDump, I get a few of these errors:

* 2008-12-06T08:37:58.8670000Z Main Thread(4428) Context: TIMING : INFO

SmeCommon::Initialize (Pre-Apply)

Result: Error SMEWINDOWS_ERROR_DEVICE_OPEN_FAILED (E0020002): Device \\.\PhysicalDrive0 cannot be opened. Error 00000005: Access is denied.

For some reason, then, it cannot access the drive for authentication reasons. Anyone shed any light on how I can fix this. All my other servers run System Recovery fine.

[David_Hicks_2]

Can anyone help with SMEDump and how I can solve the access denied message?

It's getting critical that I can prove I can restore my systems to bare metal servers to satisfy our Auditors.

My other three servers on the same hardware work fine, but this one is becoming a real pain.

Thanks

[Joseph_L_]

Please run the partinfo.exe found in the same directory as smedump and post partition information results for the drive experiencing this issue.

Specifically, the chart showing your partitions. There should be one mid way in the log as well as the bottom of the log.

[David_Hicks_2]

Please find the bits from the PartInfo text file below:

=========================================================================================================================
Disk Geometry Information for Disk 0         Sector Count: 156,184,465   (9,722 Cylinders, 255 Heads, 63 Sectors/Track)
Signature: 83B083B0
Detected Sector Size:   512
Detected Alignment:     Cylinder
.........................................................................................................................
System               Part Table LBA   # Boot     BCyl Head Sect FS      ECyl Head Sect       StartSect         NumSects
=========================================================================================================================
C:\
   On Disk Values:                0   0  80         0    1   1  07      1023  254  63               63      156,167,802
   Calculated:                                      0    1   1          9720  254  63 

====================================================================================================================
Partition Information for Disk   0:               74.5 GB
Volume Path            PartitionType  Status         Size      Part Table Lba   #     Start Sector    Total Sectors
====================================================================================================================
C:\                    NTFS           Pri,Boot       74.5 GB                0   0               63      156,167,802
                       Unallocated    Pri            8.11 MB             None  --      156,167,865           16,600

C:\
====================================================================================
Volume Boot Record for Disk 0:  at Sector 63  (0x3F)
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:          63  (0x0000003F)
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:      156167801
20: MFT Start Cluster:       786432
21: MFT Mirror Start Clust:  9760487
22: MFT First Cluster:       786432
23: Clusters per FRS:        246
24: Clusters per Index Blk:  1
25: Serical Number:          0x645C46E85C46B518
26: Checksum:                0  (0x00000000)

 - - - Disk 0:  Volume Boot Record Hex Dump at Sector 63  (0x3F) - - -

     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 3F 00 00 00        .....ø..?.ÿ.?...
    20:  00 00 00 00 80 00 80 00 79 EE 4E 09 00 00 00 00        ....€.€.yîN.....
    30:  00 00 0C 00 00 00 00 00 E7 EE 94 00 00 00 00 00        ........çî”.....
    40:  F6 00 00 00 01 00 00 00 18 B5 46 5C E8 46 5C 64        ö........µF\èF\d
    50:  00 00 00 00 FA 33 C0 8E D0 BC 00 7C FB B8 C0 07        ....ú3ÀŽÐ¼.|û¸À.
    60:  8E D8 E8 16 00 B8 00 0D 8E C0 33 DB C6 06 0E 00        ŽØè..¸..ŽÀ3ÛÆ...
    70:  10 E8 53 00 68 00 0D 68 6A 02 CB 8A 16 24 00 B4        .èS.h..hj.ËŠ.$.´
    80:  08 CD 13 73 05 B9 FF FF 8A F1 66 0F B6 C6 40 66        .Í.s.¹ÿÿŠñf.¶Æ@f
    90:  0F B6 D1 80 E2 3F F7 E2 86 CD C0 ED 06 41 66 0F        .¶Ñ€â?÷â†ÍÀí.Af.
    A0:  B7 C9 66 F7 E1 66 A3 20 00 C3 B4 41 BB AA 55 8A        ·Éf÷áf£..ôA»ªUŠ
    B0:  16 24 00 CD 13 72 0F 81 FB 55 AA 75 09 F6 C1 01        .$.Í.r.ûUªu.öÁ.
    C0:  74 04 FE 06 14 00 C3 66 60 1E 06 66 A1 10 00 66        t.þ...Ãf`..f¡..f
    D0:  03 06 1C 00 66 3B 06 20 00 0F 82 3A 00 1E 66 6A        ....f;....‚:..fj
    E0:  00 66 50 06 53 66 68 10 00 01 00 80 3E 14 00 00        .fP.Sfh....€>...
    F0:  0F 85 0C 00 E8 B3 FF 80 3E 14 00 00 0F 84 61 00        .…..è³ÿ€>....„a.
   100:  B4 42 8A 16 24 00 16 1F 8B F4 CD 13 66 58 5B 07        ´BŠ.$...‹ôÍ.fX[.
   110:  66 58 66 58 1F EB 2D 66 33 D2 66 0F B7 0E 18 00        fXfX.ë-f3Òf.·...
   120:  66 F7 F1 FE C2 8A CA 66 8B D0 66 C1 EA 10 F7 36        f÷ñþŠÊf‹ÐfÁê.÷6
   130:  1A 00 86 D6 8A 16 24 00 8A E8 C0 E4 06 0A CC B8        ..†ÖŠ.$.ŠèÀä..̸
   140:  01 02 CD 13 0F 82 19 00 8C C0 05 20 00 8E C0 66        ..Í..‚..ŒÀ...ŽÀf
   150:  FF 06 10 00 FF 0E 0E 00 0F 85 6F FF 07 1F 66 61        ÿ...ÿ....…oÿ..fa
   160:  C3 A0 F8 01 E8 09 00 A0 FB 01 E8 03 00 FB EB FE        àø.è.. û.è..ûëþ
   170:  B4 01 8B F0 AC 3C 00 74 09 B4 0E BB 07 00 CD 10        ´.‹ð¬<.t.´.»..Í.
   180:  EB F2 C3 0D 0A 41 20 64 69 73 6B 20 72 65 61 64        ëòÃ..A.disk.read
   190:  20 65 72 72 6F 72 20 6F 63 63 75 72 72 65 64 00        .error.occurred.
   1A0:  0D 0A 4E 54 4C 44 52 20 69 73 20 6D 69 73 73 69        ..NTLDR.is.missi
   1B0:  6E 67 00 0D 0A 4E 54 4C 44 52 20 69 73 20 63 6F        ng...NTLDR.is.co
   1C0:  6D 70 72 65 73 73 65 64 00 0D 0A 50 72 65 73 73        mpressed...Press
   1D0:  20 43 74 72 6C 2B 41 6C 74 2B 44 65 6C 20 74 6F        .Ctrl+Alt+Del.to
   1E0:  20 72 65 73 74 61 72 74 0D 0A 00 00 00 00 00 00        .restart........
   1F0:  00 00 00 00 00 00 00 00 83 A0 B3 C9 00 00 55 AA        ........ƒ ³É..Uª

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

C:\       (\\?\Volume{5ec88ad8-d695-11d9-8f5e-806e6f6e6963}\)
    Disk #  0                    32,256              79,957,914,624                          63                 156,167,864     74.5 GB

[Joseph_L_]

Was the partinfo edited to remove other drives; is this system configured in RAID?

If the system is configured in a RAID you could attempt the following:

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

When does this error occur?

Message Edited by Joseph L. on 12-08-2008 12:25 PM

[David_Hicks_2]

There are no hidden drives in Windows.

There are two disks in a RAID 1 configuration running off of an internal on-board RAID controller.

Anything you can suggest I try?

Thanks,

David

[David_Hicks_2]

To clarify, there are only two physical drives in the system, configured as RAID 1.

Thus only a C: drive in Windows and no hidden drives.

I get the error on running BESR, 'unable to get status'.

In the event log you get the 'cannot enumerate drives error'

Error EC8F1780: Cannot successfully reconcile changes since last session. Error EC8F1771: Cannot enumerate the current drives on this system. Error E0020002: Device \\.\PhysicalDrive0 cannot be opened. Error EBAB03F1: Access is denied. Error E0020002:

[Joseph_L_]

I have seen your error when there are discrepancies in the partition table of the drive. Within partinfo, there is a slight discrepancy with the end sector reported by your BIOS and the one reported within Windows. 

Make  sure your BIOS is also up to date and then re-detect the drives within the BIOS, if this does not resolve your issue re-partitioning your drive may be the only option.

Message Edited by Joseph L. on 12-08-2008 01:35 PM

[David_Hicks_2]

I'm just running another chkdsk /r /f

Will check the BIOS version and redetect in the BIOS as suggested and will post my results in the morning.

Cheers.

[David_Hicks_2]

Hi Joseph,

I updated the BIOS but this had no effect. I think the discrepancy you see in the PARTINFO between the BIOS and the OS is not the problem as I have an indentical server running System Restore 8.5 happily and its Partinfo gives identical results.

Anything else I can try?

Thanks

[David_F]

If you have not already done so I would review the following technote documents:

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

Secondly, for your system’s safety , as well as a troubleshooting test, see if during a maintenance window you can use BESR 8.51’s SRD to take an image of the C drive. This new build touts cold imaging capabilities. If you are able to create a recovery point of the drive not only does this eliminate it has being a hardware related issue you have a backup and that you know in the event you did need to restore a recovery point back to this system the SRD does contain the correct mass storage controller driver to see your array.

[David_Hicks_2]

Read the two docos> I can't really disconnect the array and see if BESR boots as the mirrored disk with the OS are on the integrated Array itself.

I'm trying the cold image now. Will report back on the result.

Thanks David.

David

[David_F]

David,

Where you successful in your cold imaging?

Thanks

[David_Hicks_2]

The Cold Imaging didn't work as the drive could not be seen.

I've swapped the drives with replacement SATA drives but the drive still cannot be seen.

I cannot try Cold imaging a different drive other than SATA as there is no IDE or SCSI on the DL320 at all, only the embedded Adaptec SATA controller.

Not sure where I can go from here.

I doubt our Hardware Maintenance agreement will allow us to get a new motherboard ro replacement, as the system is working fine and no errors exist apart from System Restore not being able to enumerate the drives.

[Jon_R]

If you cannot see the drive within the recovery environment, the issue is likely driver related.

Run the driver validation wizard included on the Recovery Disk by following these instructions; http://support.veritas.com/docs/293208

If the driver validation fails, you can either load the drivers from within the recovery environment or create a custom Recovery Disk by following these instructions;

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