I have recently installed deepin linux and am very impressed with it.
So much so that I have decided to make it my primary OS for a Digital Audio Workstation.
I need to run the DAW in two instances of Deepin Linux, a production instance and a development instance where all changes to the DAW and possibly the OS can be tested before committing them to the production instance.
(I realize I could use rsnapshot, but I want the mostly highly optimized performance I can get, and snapshotting can degrade system performance).
So to do this I have set up an ultra small form factor PC with 16GB RAM and an i7 processor. Partitioned the 120GB SSD into two partitions and installed Deepin Linux on the first partition.
Used Clonezilla to create a clone of the first partition and confirmed it works by cloning it back on that first partition. Cloned it to the second partition too and Clonezilla remarks the clone to have been successful.
Updated grub by booting into the instance of Deepin and running a sudo update-grub command on it. Upon reboot, only one instance of deepin linux appears in the boot menu.
Used Gparted to copy the first partition to the next. This time I can see the second partition showing up in the boot menu, but it doesn't matter which one I choose between, I keep getting logged into the instance of deepin on /dev/sda1.
Changed the UUID of the second partition via the gui tool in Gparted. Same results, can only boot into /dev/sda1 no matter what I choose.
Suspect there is some kind of issue with grub at play but have also posted to the clonezilla forum after following their advice in their topic http://drbl.org/faq/fine-print.php?p..._partition.faq
Does anyone have any ideas of how I can further troubleshoot this or know of any other resources I can tap? Has this question been asked before and my forum-fu isn't strong enough to have found it in these forums? Please let me know.
update#1: booted the PC again and randomly I have booted into /dev/sda2 this time. Great to know that I can get to it, more and more suspecting a grub issue.
update#2: found that if I run a sudo update grub, that even though I appear to boot into the same version of grub each time (I changed the background image on one of the grub files theme file so i can tell), I will then boot into the other /dev/sdax. Suspect I need to either delete the other instance of grub or will i be stuck with having to do a grub update every time i want boot into the other partition?
update#3: removed grub from sda1 with:
$ dd if=/dev/sda1 bs=512 count=1 of=sda1.bootsector.backup
$ dd if=/dev/zero of=/dev/sda1 bs=512 count=1
now 1st menu item alternately boots into sda1 or sda2 depending on if i run sudo update grub between boots or not. It also seems to be affected by if i use the cli or the gui to reboot.
Have been rebooting using cli command "sudo shutdown -r now" without updating grub, beginning to suspect some kind of race condition is operative, as it sometimes boots into /dev/sda1 and sometimes into /dev/sda2.