<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Intel Modular Server / Compute module boots with drive assigned to another in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Intel-Modular-Server-Compute-module-boots-with-drive-assigned-to/m-p/1181174#M79672</link>
    <description>&lt;P&gt;We have 2 MFSYS25 Chassis. One populated with MFS500SI and one populated with MFS5520VI. They are working fine since many years.&lt;/P&gt;

&lt;P&gt;After IMS end of life we purchased 2 additional chassis and some MFS5000SI compute module (second hand from two different sellers on ebay),&lt;/P&gt;

&lt;P&gt;We are trying to duplicate the running setup as a backup.&lt;/P&gt;

&lt;P&gt;We fired up compute Module 1 and installed an OS using virtual drive 'Linux1'. That worked fine. But then we ran into problems for the second install. If compute module 2 is booted with compute module 1 turned off, it boots correctly. If however, compute module 1 is already booted with 'Linux1' assigned to it, and then we try to boot compute Module 2 to which is assigned virtual drive 'Linux2'; then, instead of booting as 'Linux2', it comes up as 'Linux1' and the file system on&amp;nbsp;compute module 1 (to which virtual drive Linux1 is assigned) &amp;nbsp;becomes read only.&lt;/P&gt;

&lt;P&gt;The console of&amp;nbsp;compute module 1&amp;nbsp;shows messages like:&lt;/P&gt;

&lt;P&gt;sd 1:0:0:0: rejecting I/O to offline device&lt;/P&gt;

&lt;P&gt;We then concluded that perhaps the second hand chassis we purchased was bad.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;So we&amp;nbsp;tried using the chassis purchased from another seller and the issue was the same.&lt;/P&gt;

&lt;P&gt;Also because we had 5 compute modules, we swapped the first 2 with 2 others and the problem was reproduced.&lt;/P&gt;

&lt;P&gt;[All 5 compute modules have manufacture dates in Oct 2007].&lt;/P&gt;

&lt;P&gt;If someone has any insight on what is going on here, it will be much appreciated.&lt;/P&gt;

&lt;P&gt;(Please note that there is only 1 SCM installed so there is multipath complication)&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 05 Sep 2018 23:35:50 GMT</pubDate>
    <dc:creator>Dave__Rakhal</dc:creator>
    <dc:date>2018-09-05T23:35:50Z</dc:date>
    <item>
      <title>Intel Modular Server / Compute module boots with drive assigned to another</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-Modular-Server-Compute-module-boots-with-drive-assigned-to/m-p/1181174#M79672</link>
      <description>&lt;P&gt;We have 2 MFSYS25 Chassis. One populated with MFS500SI and one populated with MFS5520VI. They are working fine since many years.&lt;/P&gt;

&lt;P&gt;After IMS end of life we purchased 2 additional chassis and some MFS5000SI compute module (second hand from two different sellers on ebay),&lt;/P&gt;

&lt;P&gt;We are trying to duplicate the running setup as a backup.&lt;/P&gt;

&lt;P&gt;We fired up compute Module 1 and installed an OS using virtual drive 'Linux1'. That worked fine. But then we ran into problems for the second install. If compute module 2 is booted with compute module 1 turned off, it boots correctly. If however, compute module 1 is already booted with 'Linux1' assigned to it, and then we try to boot compute Module 2 to which is assigned virtual drive 'Linux2'; then, instead of booting as 'Linux2', it comes up as 'Linux1' and the file system on&amp;nbsp;compute module 1 (to which virtual drive Linux1 is assigned) &amp;nbsp;becomes read only.&lt;/P&gt;

&lt;P&gt;The console of&amp;nbsp;compute module 1&amp;nbsp;shows messages like:&lt;/P&gt;

&lt;P&gt;sd 1:0:0:0: rejecting I/O to offline device&lt;/P&gt;

&lt;P&gt;We then concluded that perhaps the second hand chassis we purchased was bad.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;So we&amp;nbsp;tried using the chassis purchased from another seller and the issue was the same.&lt;/P&gt;

&lt;P&gt;Also because we had 5 compute modules, we swapped the first 2 with 2 others and the problem was reproduced.&lt;/P&gt;

&lt;P&gt;[All 5 compute modules have manufacture dates in Oct 2007].&lt;/P&gt;

&lt;P&gt;If someone has any insight on what is going on here, it will be much appreciated.&lt;/P&gt;

&lt;P&gt;(Please note that there is only 1 SCM installed so there is multipath complication)&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 05 Sep 2018 23:35:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-Modular-Server-Compute-module-boots-with-drive-assigned-to/m-p/1181174#M79672</guid>
      <dc:creator>Dave__Rakhal</dc:creator>
      <dc:date>2018-09-05T23:35:50Z</dc:date>
    </item>
  </channel>
</rss>

