title: OCS_Prerun arguments fail on new SSD setup
body: <p>Working on a Clonezilla Live bootable USB 3.0 Portable SSD.  We previously had a setup using OCS_Prerun arguments on an old 2TB HDD which routinely saw <code>dev/sdc2</code> as the 2nd Image Storage partition of this HDD.</p>
  <p>We have upgraded to a new USB 3.0 SSD and can <em>sometimes</em> get this thing to work w/ the same OCS_Prerun arguments when using a USB 2.0 cable, or a USB 3.0 cable in a USB 2.0 slot, but the moment we plug it in with a USB 3.0 Cable in the USB 3.0 slot, it no longer sees <code>dev/sdc2</code> properly!</p>
  <p>Is there a different process used when working w/ USB 2.0 vs USB 3.0 devices in Linux, and/or is there a different process used when working w/ HDD's vs SSD's when assigning the <code>dev/sdX</code> labels?</p>
  <p>Any clues?</p>
  <p>OCS Prerun tasks are as follows:</p>
  <pre><code>&quot;OCS_Prerun&quot;: sudo mkdir /images
  &quot;OCS_Prerun1&quot;: sudo mount /dev/sdc2 /images
  &quot;OCS_Prerun2&quot;: sudo mount --bind /images /home/partimag/
  </code></pre>