SAN Windows XP Boot - bluescreen

Brought to you by: steven_shiau

SAN Windows XP Boot - bluescreen

Forum: Help

Creator: Timothy Shelley

Created: 2011-10-04

Updated: 2012-12-12

Timothy Shelley - 2011-10-04

Hi,

We've started to play with the SAN Booting on DRBL. I've got so far as booting the machine but it only gets so far into the boot before a blue screen flashes very quickly on the screen and it reboots. We are using drbl-1.10.31

I know in Windows XP bluescreens can be caused by major hardware changes. Since the instructions tell us to remove the HDD could this be causing the problem?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Timothy Shelley - 2011-10-04

Hi,

Also to add - is there anything I should have done to the installation of Windows before following instructions at
http://drbl.sourceforge.net/one4all/drbl-sanboot.php?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2011-10-05

"is there anything I should have done to the installation of Windows before following instructions at http://drbl.sourceforge.net/one4all/drbl-sanboot.php? " -> No, everything required is shown in the step:
"4. How to make SAN Booting on DRBL? Take MS Windows as an example:"

Are you sure the SAN/AoE client you boot is the same model with the source machine? For MS Windows it has to be the same.

Steven.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Timothy Shelley - 2011-10-05

Hi Steven,

Ok, I missed the hyperlink in the word 'this' in the san boot instructions. Light blue on my monitor really does not show well so the first time I read it I missed them.

Now that I have carried out all the steps I still get the blue screen of death but this time it stops on it - althought he message is mostly off the screen the error seems to say Parity Check/Memory Parity error.

Yes, this is the same machine that is booting as the one we created the image from.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Timothy Shelley - 2011-10-06

Hi,

As a further note when i run 'fdisk -l' on the img file I get:

Disk test.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5a137f31

   Device Boot      Start         End      Blocks   Id System
test.img1   *           1        1305    10482381    7 HPFS/NTFS
Partition 1 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(1304, 254, 63)

Could the problem with the different endings be the cause of the BSOD?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Timothy Shelley - 2011-10-06

Hi,

The img file in my previous post is called test.img because I wanted to test if dd produced a different image so I ran it. Then realised that your script does the same thing… so running the 'fdisk -l' on the img generated by /opt/drbl/sbin/drbl-aoe-img-dump -x still gives the different endings.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2011-10-13

MS Windows is very difficult to debug… and I have very limited experience about it.
Anyone on this forum has any idea about this?

Steven.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.