4 replies to this topic

[rheinze]

Hello,

I have two Dell PowerEdge M610 running in a Blade Chassis. The Chassis is connected via FC with a Dell/EMC SAN. Each M610 has local drives that are configured to a RAID1 virtual drive. The Windows Server installation was not done using a Dell OEM Kit. There is only one system drive and no other partitions, for example the Dell partitions.

I want to create a image from the M610 and restore it on the other M610. I restore the image without errors. When booting the just restored M610 the boot sequence stops right after the initialization of the iDRAC6 card. I only see a blinking curser.

The strange thing is:

1. When i insert a USB stick with GRUB4DOS and tell GRUB to start from the first HDD partition, the Windows Server 2003 R2 x64 starts just fine.
2. I can restore the image to vmware workstation and have been able to startup the restored system inside the VM. Therefore there are no issues with the image.

Any Ideas regarding how to convince the server to boot my restored image?


Thanks!

Best, René

[Sha0]

Yes. Use GRUB4DOS to chain-load the Recovery Console, then use FIXMBR and FIXBOOT.

Also, what did you use to transfer the image?

[steve6375]

Is the boot partition marked as Active? Can you examine the MBR?

[rheinze]

@steve6375
The partition is marked as Active. I included the MBR at the end of the post.

@Sha0
I used Acronis Backup & Recovery Workstation 10 build 13544. Unfortunately I don´t have the Recovery Console installed on my system drive.
I followed this guide to create a bootable USB Stick with a Recovery Console.

The creator from the guide includes the "DriverPack MassStorage wnt5" with his release. But still the "CERC 6i Integrated" does not seem to be integrated. There is a Dell Dell PERC 5i/6i integrated, but still I´m not able to access the system installation when booting to the Recovery Console located on the USB Stick. I could start the recovery console from the installation cd, but i don´t have a usb floppy disk drive for the driver available.


MBR of the harddisk:

3ÀŽÐ¼ |ûPPü¾?|¿PW¹å
ó¤Ë½¾±8n | uƒÅâôÍ‹õƒÆIt8,tö µ´‹ð¬< tü» ´ÍëòˆNèF s*þF€~t€~t ¶uÒ€FƒFƒV
è! s ¶뼁>þ}Uªt€~ tÈ ·ë©‹üW‹õË¿ ŠV ´Ír#ŠÁ$?˜ŠÞŠüC÷ã‹Ñ†Ö±ÒîB÷â9V
w#r9Fs¸
» |‹N‹V ÍsQOtN2äŠV ÍëäŠV `»ªU´AÍr6ûUªu0öÁ
t+a`j j ÿv
ÿvj h |j
j´B‹ôÍaasOt2äŠV ÍëÖaùÃInvalid partition table Error loading operating system Missing operating system ,Dcç:C €

ÿÿ? a
E Uª



MBR of the system partition:

ëRNTFS 
ø ?  ? € € hE ·[L   bì5P6P ú3ÀŽÐ¼ |û¸ÀŽØè ¸
ŽÀ3ÛÆ èS h
hjËŠ$ ´Ís¹ÿÿŠñf¶Æ@f¶Ñ€â?÷â†ÍÀíAf·Éf÷áf£ ôA»ªUŠ$ ÍrûUªu öÁ
tþ Ãf`f¡ f f; ‚: fj fPSfh
€> … è³ÿ€> „a ´BŠ$ ‹ôÍfX[fXfXë-f3Òf· f÷ñþŠÊf‹ÐfÁê÷6 †ÖŠ$ ŠèÀä
̸
Í‚ ŒÀ ŽÀfÿ ÿ …oÿfaàø
è  û
è ûëþ´
‹ð¬< t ´» ÍëòÃ
A disk read error occurred
NTLDR is missing
NTLDR is compressed
Press Ctrl+Alt+Del to restart
ƒ ³É Uª

[Sha0]

MBR of the harddisk...

Uh, your paste doesn't really look nice. If you can get TinyHexer, you could use File -> Disk -> Open drive... and then take a screen-shot of the window (maximize it).

Or you could save the MBR as a file and upload the file somewhere so people can download it and look at it.

Or possibly the best would be to use hexdump (under Linux, for example) as in:

$ dd if=/dev/sdaX of=my_mbr.bin count=1

$ hexdump -C my_mbr.bin

00000000  fa 31 c0 8e d8 8e c0 8e  d0 bc 00 7c fb fc 89 e6  |.1.........|....|

00000010  bf 00 06 b9 00 01 f3 a5  ea 1d 06 00 00 88 16 00  |................|

00000020  08 b4 08 cd 13 31 c0 88  f0 40 a3 f0 06 80 e1 3f  |.....1...@.....?|

00000030  88 0e f2 06 be be 07 31  c0 b9 04 00 f6 04 80 74  |.......1.......t|

00000040  03 40 89 f7 83 c6 10 e2  f3 83 f8 01 75 73 8a 16  |.@..........us..|

00000050  00 08 b8 00 41 bb aa 55  31 c9 30 f6 f9 cd 13 72  |....A..U1.0....r|

00000060  23 81 fb 55 aa 75 1d f6  c1 01 74 18 57 be e0 06  |#..U.u....t.W...|

00000070  8b 5d 08 89 5c 08 8b 5d  0a 89 5c 0a 8a 16 00 08  |.]..\..]..\.....|

00000080  b4 42 eb 2a 57 8b 45 08  8b 55 0a f7 36 f2 06 42  |.B.*W.E..U..6..B|

00000090  89 d1 31 d2 f7 36 f0 06  88 c5 d1 e8 d1 e8 24 c0  |..1..6........$.|

000000a0  08 c1 88 d6 8a 16 00 08  bb 00 7c b8 01 02 cd 13  |..........|.....|

000000b0  72 16 5e 81 3e fe 7d 55  aa 75 08 fa ea 00 7c 00  |r.^.>.}U.u....|.|

000000c0  00 77 05 be f4 06 eb 03  be 0f 07 ac 20 c0 74 0c  |.w.......... .t.|

000000d0  b4 0e 8a 3e 62 04 b3 07  cd 10 eb ef eb fe 00 00  |...>b...........|

000000e0  10 00 01 00 00 7c 00 00  00 00 00 00 00 00 00 00  |.....|..........|

000000f0  00 00 00 00 4d 69 73 73  69 6e 67 20 6f 70 65 72  |....Missing oper|

00000100  61 74 69 6e 67 20 73 79  73 74 65 6d 0d 0a 00 4f  |ating system...O|

00000110  70 65 72 61 74 69 6e 67  20 73 79 73 74 65 6d 20  |perating system |

00000120  6c 6f 61 64 69 6e 67 20  65 72 72 6f 72 0d 0a 00  |loading error...|

00000130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

*

000001b0  00 00 00 00 00 00 00 00  ff ee dd cc 00 00 00 00  |................|

000001c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

*

000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|

00000200

MBR of the system partition...

There is only one MBR on a disk: Sector 0, the first sector. The boot sector of a partition is not called an MBR. Some people call such a boot sector the Partition Boot Record or the Volume Boot Record. Please don't confuse these types of boot sector. If you are following a tutorial and it talks about the MBR, it really shouldn't mean a partition's boot sector and you might end up in trouble.

Unfortunately, I cannot read your boot sectors to see if they have any problems.