| 1 |
On Wed, 7 Sep 2016 09:22:59 +0300, gevisz wrote: |
| 2 |
|
| 3 |
> After many attempts, I finally managed to boot with the new drive |
| 4 |
> attached manually editing the above entry in /boot/grub/grub.cfg |
| 5 |
> 1) deleting the root=UUID=44*** part of its line (which probably means |
| 6 |
> that adding GRUB_CMDLINE_LINUX="root=UUID=44***" line to |
| 7 |
> the /etc/default/grub was a bad idea :), |
| 8 |
> 2) changing in the same last line sdb3 to sdc3, and |
| 9 |
|
| 10 |
Which is fine, until you next run grub-mkconfig. As Mike said, if you use |
| 11 |
an initramfs, GRUB will then use UUIDs, avoiding all this. |
| 12 |
|
| 13 |
Another possibility is that your new drive is connected to a lower |
| 14 |
numbered SATA port, which is why it jumps in front of the old drive in the |
| 15 |
device allocation. Connecting your boot drive to the lowest numbered |
| 16 |
port may avoid future queue-jumping. |
| 17 |
|
| 18 |
|
| 19 |
-- |
| 20 |
Neil Bothwick |
| 21 |
|
| 22 |
Accordion: a bagpipe with pleats. |
Archives