Thread resurrection! This actually happened to a member of our IT department again, today.
Has anyone else ever run in to this problem? Some possibilities of causes:
Computer had the original OS hard drive and the secondary drive in the computer before, while FOG imaged it The original OS drive was removed, and replaced with a new SSD The hard drive mode was switched from RAID to AHCI in the bios After all those changes were made, FOG imaged the secondary drive, instead of the SSD Post installation, the SSD is listed as /dev/sda and the secondary drive is listed as /dev/sdbStill pretty stumped. Anyone think any of those options would have temporarily caused the secondary drive to be read as /dev/sda?