diff options
| author | yar | 2017-04-03 22:08:41 -0700 |
|---|---|---|
| committer | yar | 2017-04-03 22:41:19 -0700 |
| commit | dd9dbe43a35f665b10ab779a5df0bcc43b5ecd65 (patch) | |
| tree | 3b37ae6c977b0269c62dd149f21cd0c56407a9dd | |
| parent | a50d1d41ea347a52adc9a3e945dc3f1b2ce83e74 (diff) | |
| download | aur-dd9dbe43a35f665b10ab779a5df0bcc43b5ecd65.tar.gz | |
warn about device names
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md index d3e247422177..1327b2e4228a 100644 --- a/README.md +++ b/README.md @@ -30,6 +30,8 @@ Configs are a compromise between vanilla Linode and Arch. Most drivers are disab You may also need to install grub files to /boot: `grub-install --no-bootsector --boot-directory=/boot /dev/null` + Take extra care to make sure you're booting from the correct device name. Xen devices are called /dev/xvda while KVM devices are called /dev/sda. If you're running grub inside your old Xen linode, it will automatically add "root=/dev/xvda" to your kernel line in /boot/grub/grub.cfg. Once you migrate to KVM, this will no longer work. You'll have to either edit this file by hand before shutting down to migrate, or edit it using the interactive grub command line afterwards. Once you've migrated, running grub-mkconfig again should fix it. Also be sure to check /etc/fstab or /etc/crypttab for any other device names that might give you boot problems. + # STEPS TO USE 1. pacman -Syu |