<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">For what it’s worth I’ve seen the same error message on a Dell server that happened to have 10TB-drives (not the boot disks!) that was formatted using 4104-bytes sectors in order to support the T10-PI/DIF & T10-DIF standards. The errors started to occur when we replaced the RAID controller with an HBA. Non 512/4096-bytes sectors apparently confused the boot loader when scanning the drives for the boot zpool. This was on a FreeBSD system though. The solution was to perform a low level reformatting of the drives in to standard 4096 byte sectors.<div class=""><br class=""></div><div class=""><br class=""></div><div class=""><a href="https://en.wikipedia.org/wiki/Data_Integrity_Field" class="">https://en.wikipedia.org/wiki/Data_Integrity_Field</a></div><div class=""><br class=""></div><div class=""><a href="https://access.redhat.com/solutions/41548" class="">https://access.redhat.com/solutions/41548</a></div><div class=""><br class=""></div><div class=""><a href="http://www.enterprisestorageforum.com/storage-technology/sas-vs.-sata-4.html" class="">http://www.enterprisestorageforum.com/storage-technology/sas-vs.-sata-4.html</a></div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">—</div><div class="">[L<span style="font-family: sans-serif; font-size: 13px; background-color: rgb(249, 249, 249);" class="">ı</span>.U] System Administrator ITI-NET IT.LiU.SE +46-13-28 2786</div></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 18 May 2017, at 21:55, Geoff Nordli <<a href="mailto:geoffn@gnaa.net" class="">geoffn@gnaa.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi.<br class=""><br class="">I upgraded to the latest r151022 version. The upgrade went fine, rebooted the machine, then upgraded to the new loader.<br class=""><br class="">When i rebooted after the loader upgrade, I got an error message:<br class=""><br class="">panic: bd_strategy: 512 bytes I/O not multiple of block size.<br class=""><br class="">press a key on the console to reboot....<br class=""><br class="">Rebooting...<br class=""><br class="">panic free: guard1 fail @ 0x2e2e2e67 from ../../common/devopen.c:64<br class=""><br class="">The boot disk is an 80GB intel ssd.<br class=""><br class="">Any thoughts?<br class=""><br class="">thanks,<br class=""><br class="">Geoff<br class=""><br class="">_______________________________________________<br class="">OmniOS-discuss mailing list<br class=""><a href="mailto:OmniOS-discuss@lists.omniti.com" class="">OmniOS-discuss@lists.omniti.com</a><br class="">http://lists.omniti.com/mailman/listinfo/omnios-discuss<br class=""></div></div></blockquote></div><br class=""></div></body></html>