DISCLAIMER: This is obviously unsupported activity, so you're probably wandering outside of warranty territory. I don't work for JRiver, I'm just a user who likes linux, so take this with a grain of salt.
Here is a general guide to doing a recovery chroot:
http://superuser.com/questions/111152/whats-the-proper-way-to-prepare-chroot-to-recover-a-broken-linux-installationOnce you're chrooted in you'll need to find out what the UUID of the drives are, and then fix your /etc/fstab
1) To find out what the UUIDs of your drives are, you'll need to run the command blkid probably using sudo. blkid will just provide a list of partitions and UUIDs. If you're not sure which partitions of which, run lsblk; it will show you which partitions are mounted where (if any) and what label the system is currently using for which drive (i.e. you should be able to identify from the output of lsblk whether your ssd is currently sda or sdb, etc.).
2) Then you'll need to edit your /etc/fstab. I have no idea what the default partition scheme of an Id looks like, so I can't offer specific advice, but generally each line is an entry, and each entry includes multiple arguments like this:
/dev/sda2 / ext4 rw,relatime,discard,data=ordered
That's just an example, yours may have different parameters. The important parts for your purposes are the first and second entries ("/dev/sda2" and "/" respectively).
The first entry is the partition identifier and will need to be replaced with "UUID=" followed by the appropriate UUID that you found in step one. It's important that there is no space between the equals sign and the UUID, and no spaces within the UUID.
The second entry is where the partition will be mounted, in my example "/" which is the "root" of the file system. This is where it might get complicated as I don't know what the partition scheme for the Id looks like. It's likely though that if you fix the first entry on each line so that it refers to the appropriate UUID, you may not need to mess with the mount locations.
Once you've fixed it, finish the chroot guide above and take a stab at rebooting.
Again, this is unsupported, so you'll be "on your own" with this. That said, if you run into issues, open a new thread and I'll try my best to help (time permitting, I've got a one-year old
)