You could choose the live option. Then edit things to the mounted HD install. Your /boot/grub/grub.cfg is probably off a bit, or your /etc/fstab, or you need an initrd image of the kernel to include the drivers needed to load the drivers that you need. I would assume that the initramfs error has something to do with that initrd image. It's either not there, or it's looking in the wrong place for it. The /dev/ names are unreliable and should probably be swapped from root=/dev/ to root=UUID= or root=LABEL= along with the equivalent changes in /etc/fstab. Or the non-existance of /etc/fstab is sometimes better. Although without /etc/fstab the / filesystem gets mounted read-only when you boot. Easily compensated for, but annoying.
# mount -o remount,rw /
$ cat /proc/partitions
$ lsblk
$ blkid /dev/sda1
And various other ways to identify things. On my system it looks something like.
from grub.cfg
Code:
linux /boot/vmlinuz-4.0.1 root=UUID=20150720-2222-2222-2222-222222222222 ro quiet
initrd /boot/initrd.img-4.0.1
from /etc/fstab
Code:
UUID="20150720-2222-2222-2222-222222222222" / xfs defaults 0 1
Sometimes the initrd line in grub points at /initrd.img which is a symlink to the real one. But if you install another kernel, it could point at the wrong one. Using the full filename helps avoid the confusion.
$ ls -l /
Code:
lrwxrwxrwx 1 root root 31 May 3 16:37 initrd.img -> /boot/initrd.img-3.16.0-4-amd64
lrwxrwxrwx 1 root root 27 May 3 16:37 vmlinuz -> boot/vmlinuz-3.16.0-4-amd64
As you can see from my system, loading a 4.0.1 kernel with the initrd image pointed at a 3.16 kernel (the distros kernel) is a point of failure I recently had. Changing "initrd /initrd.img" to "initrd /boot/initrd.img-4.0.1" in the grub.cfg overcame that issue. Triggered in my case by an update to the 3.16 distro kernel after I had installed my 4.0.1 custom kernel. As all kernel updates from the distro reruns update-grub.