<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Aclhk Aclhk wrote:</tt>
<blockquote type="cite" cite="mid:411193.10292.qm@web112516.mail.gq1.yahoo.com">
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top" style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;"><tt>after the following commands:<br>
dhcp net0<br>
set keep-san 1<br>
sanboot iscsi:192.168.1.1::::iscsi-gpxe<br>
<br>
the server will reboot or hang (booting from......)</tt></td>
</tr>
</tbody>
</table>
</blockquote>
<tt><br>
What is installed on the SAN's MBR? Which boot code or boot-loader?
There is a diagnostic MBR available at
<a href="http://etherboot.org/share/sha0/mbr-diag.bin" class="moz-txt-link-freetext">http://etherboot.org/share/sha0/mbr-diag.bin</a>. After and only after
you've backed up the current MBR, you can write these 440 bytes over
the first 440 bytes of your SAN's MBR, leaving the partition table
intact (the rest of the 512 bytes). You could then see what happens.<br>
<br>
# dd if=/path/to/san of=mbr_backup.bin count=1<br>
# dd if=mbr-diag.bin of=/path/to/san bs=1 count=440 conv=notrunc<br>
# echo Perform test<br>
# echo Restore with<br>
# dd if=mbr_backup of=/path/to/san conv=notrunc<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>