Gave up waiting for root device, ubuntu--vg-root doesnt exist/dev/mapper/ubuntu--vg-root does not existALERT!...
Is using an 'empty' metaphor considered bad style?
Am I a Rude Number?
How do I append a character to the end of every line in an excel cell?
New package vs new version?
"on its way" vs. "in its way"
Why is Agricola named as such?
What happens when a creature with flying blocks my non-flying attacker?
Eww, those bytes are gross
I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."
Does Skippy chunky peanut butter contain trans fat?
How does Leonard in "Memento" remember reading and writing?
Why does photorec keep finding files after I have filled the disk free space as root?
How can the probability of a fumble decrease linearly with more dice?
What is the difference between rolling more dice versus fewer dice?
Why publish a research paper when a blog post or a lecture slide can have more citation count than a journal paper?
Can I announce prefix 161.117.25.0/24 even though I don't have all of /24 IPs?
What is the wife of a henpecked husband called?
How would an AI self awareness kill switch work?
How to use Mathemaica to do a complex integrate with poles in real axis?
Constexpr if with a non-bool condition
Why did Democrats in the Senate oppose the Born-Alive Abortion Survivors Protection Act (2019 S.130)?
Early credit roll before the end of the film
What is a good reason for every spaceship to carry a weapon on board?
Has Britain negotiated with any other countries outside the EU in preparation for the exit?
Gave up waiting for root device, ubuntu--vg-root doesnt exist
/dev/mapper/ubuntu--vg-root does not existALERT! /dev/mapper/edbunto--g-root does not exist Error. Dropping to a Shell!Gave up waiting for root device on Ubuntu“Gave up waiting for root device” while bootingUpdate grub in a chroot environment with root on a luks encrypted volumeUbuntu 13.04 with LVM+FDE: “Failed to load config file /etc/lvm/lvm.conf” (doesn't boot with new kernel)New Ubuntu install, initramfsCannot boot 14.04 after upgradeUbuntu after Windows 7 disk unrecognizedHow to solve the error of “Gave up waiting for root device”Ubuntu 16.04 can't find RAIDUbuntu drops to shell on 16.04 kernelKernel Compiling - What am I doing wrong?Error during boot. encrypted source does not existGave up waiting for root file system device, in Ubuntu 18.04
today I installed Ubuntu 64-bit on a netbook. When the netbook boots this, error report appeared. I think there is a problem with the partitions.
Gave up waiting for root device. Common problems:
— Boot args (cat /proc/cmdline)
— Check rootdelay= (did the system wait long enough?)
— Check root= (did the system wait for the right device?)
— Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/ubuntu--vg-root does not exist. Dropping to a shell!
BusyBox v.1.21.1 (Ubuntu 1:1.21.1-1ubuntu1) built-in shell (ash)
Enter 'help' for list of built-in commands.
(initramfs)
Output of lsblk as requested:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 231G 0 part
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 2G 0 part [SWAP]
sr0 11:0 1 1.2G 0 rom /cdrom
loop0 7:0 0 1.1G 1 loop /rofs
boot 64-bit partitions
add a comment |
today I installed Ubuntu 64-bit on a netbook. When the netbook boots this, error report appeared. I think there is a problem with the partitions.
Gave up waiting for root device. Common problems:
— Boot args (cat /proc/cmdline)
— Check rootdelay= (did the system wait long enough?)
— Check root= (did the system wait for the right device?)
— Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/ubuntu--vg-root does not exist. Dropping to a shell!
BusyBox v.1.21.1 (Ubuntu 1:1.21.1-1ubuntu1) built-in shell (ash)
Enter 'help' for list of built-in commands.
(initramfs)
Output of lsblk as requested:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 231G 0 part
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 2G 0 part [SWAP]
sr0 11:0 1 1.2G 0 rom /cdrom
loop0 7:0 0 1.1G 1 loop /rofs
boot 64-bit partitions
1
runlsblk
and add the output to your question.
– psusi
Jan 1 '15 at 19:54
5
@psusi What iflsblk
is not available?
– sitilge
Aug 15 '15 at 20:06
add a comment |
today I installed Ubuntu 64-bit on a netbook. When the netbook boots this, error report appeared. I think there is a problem with the partitions.
Gave up waiting for root device. Common problems:
— Boot args (cat /proc/cmdline)
— Check rootdelay= (did the system wait long enough?)
— Check root= (did the system wait for the right device?)
— Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/ubuntu--vg-root does not exist. Dropping to a shell!
BusyBox v.1.21.1 (Ubuntu 1:1.21.1-1ubuntu1) built-in shell (ash)
Enter 'help' for list of built-in commands.
(initramfs)
Output of lsblk as requested:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 231G 0 part
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 2G 0 part [SWAP]
sr0 11:0 1 1.2G 0 rom /cdrom
loop0 7:0 0 1.1G 1 loop /rofs
boot 64-bit partitions
today I installed Ubuntu 64-bit on a netbook. When the netbook boots this, error report appeared. I think there is a problem with the partitions.
Gave up waiting for root device. Common problems:
— Boot args (cat /proc/cmdline)
— Check rootdelay= (did the system wait long enough?)
— Check root= (did the system wait for the right device?)
— Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/ubuntu--vg-root does not exist. Dropping to a shell!
BusyBox v.1.21.1 (Ubuntu 1:1.21.1-1ubuntu1) built-in shell (ash)
Enter 'help' for list of built-in commands.
(initramfs)
Output of lsblk as requested:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 231G 0 part
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 2G 0 part [SWAP]
sr0 11:0 1 1.2G 0 rom /cdrom
loop0 7:0 0 1.1G 1 loop /rofs
boot 64-bit partitions
boot 64-bit partitions
edited Oct 2 '16 at 11:04
knocte
689820
689820
asked Jan 1 '15 at 17:25
Jonas FranzJonas Franz
142118
142118
1
runlsblk
and add the output to your question.
– psusi
Jan 1 '15 at 19:54
5
@psusi What iflsblk
is not available?
– sitilge
Aug 15 '15 at 20:06
add a comment |
1
runlsblk
and add the output to your question.
– psusi
Jan 1 '15 at 19:54
5
@psusi What iflsblk
is not available?
– sitilge
Aug 15 '15 at 20:06
1
1
run
lsblk
and add the output to your question.– psusi
Jan 1 '15 at 19:54
run
lsblk
and add the output to your question.– psusi
Jan 1 '15 at 19:54
5
5
@psusi What if
lsblk
is not available?– sitilge
Aug 15 '15 at 20:06
@psusi What if
lsblk
is not available?– sitilge
Aug 15 '15 at 20:06
add a comment |
5 Answers
5
active
oldest
votes
Please add the outputs of lsblk -fs, fdisk /dev/sda with p flag and the report of grub repair to the question as pastebin links.
Based on searching, there seems to be similar questions on Ask Ubuntu that has no answer up to date here and Here one answer is given which explains about raid and ubuntu.
There seems to be several suggestions, some of which seem to work for some people.
From the initframs prompt try typing
ls /dev/mapper
and see if your root volume is listed. If it is not listed, try waiting 10 seconds and run ls again.
If it is now listed, type
exit
and it should now find the root device and boot (taken from here
Edit the boot config by pressing
e
when grub alert to choose OS, and replaceroot=UUID-6500...
byroot=/dev/sdx
where sdx is the boot partition. The problem here seems to be that the UUID is either wrong, or/dev/disk/by-UUID...
does not exist(1)- Adding the parameter
all_generic_ide
to the end of the boot-line likekernel /boot/vmlinuz-2.6.27-7-generic root=UUID=43206294-74ef-434d-aca2-db74b4257590 ro quiet splash all_generic_ide
seems to work for some people (2)
- The Super User question here, seems to suggest the error is due to LVM. The solution is also given in the same which is to install lvm2.
- The same Super User site also suggests booting using an older Kernel, if available. It seems to work for some people. Trying to boot using the
Recovery
option might work for some people - Post by nux_man777 here seems to suggest the error may be in the installation medium.
The error
/dev/mapper/ubuntu-vg-root
seems to be related to raid as described here.
"In the installer summary screen right before the copy process starts, click the Advanced button. Change the boot partition (this is the MSDOS-style "parent" partition not the Linux partitions) to /dev/mapper/pdc_feddabdf (or whatever dmraid lists as your fakeraid partition) Make sure the checkbox is clicked to boot from this disk. note that the installer will modify grub2 to point to the correct logical partition /dev/mapper/pdc_feddabdf1 or whatever / is on."
Detailed instructions regarding installation is given in the referred site. Please check there for more info on installation of grub.
- Booting into a live installation media and updating ubuntu by changing root using
chroot
seems to work for some people (suggested by cpttripzz here).
Instruction regarding chroot is here. You can also refer to this question at Unix & Linux. More details can be found at Arch Wiki and Gentoo Wiki. - Changing the SATA Controller to Native IDE from RAID and doing a fresh install seems to work for some people here and here
- IDE cable or the hard disk may be bad (the same ubuntu forum as above page 40)
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
|
show 10 more comments
I had this problem and nothing on any posts here or elsewhere were able to help. Specifically in my case, I could see that /dev/mapper
did not contain ubuntu--vg-root
or anything else for that matter. This means that something either went wrong when LVM tried to mount/map the volumes OR something went wrong earlier in the boot process, and this error is just a catch-all symptom for any earlier problem.
The second of these was the case for me and only because of my reading about initramfs
I was able to understand and diagnose the issue. This should be the first thing you do if you suspect something has gone wrong prior to LVM doing its thing.
In my case (which may not be the same as you but is worth documenting), I had full disk encryption (LUKS) enabled, and somehow the cryptsetup
tools had been removed from initramfs
, therefore I was not being prompted for the passphrase to unlock, and the drives were not accessible, which meant that /dev/sdaX
could not be mounted, and therefore ubuntu--vg-root
could not be mounted/mapped into /dev/mapper
. If you try to run cryptsetup
from the BusyBox prompt, youll know you have the same issue if the
cryptsetup` cannot be found.
The solution was to boot from a LiveCD, unlock the drive manually with cryptsetup
, chroot
into the root filesystem, reinstall cryptsetup
and call update-initramfs
.
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
1
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652
– dragon788
Sep 5 '18 at 19:27
add a comment |
In certain Ubuntu versions (e.g. Xubuntu 18.10) this issue might be caused by an apt autoremove
. Due to this bug apt will suggest to remove
cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2
which makes the system non-bootable (because the root partiation cannot be mounted and unencrypted using LVM).
If you are not using LVM and disk encryption this answer is probably not for you.
I was able to fix it by re-installing cryptsetup and lvm2 in a chroot environment: boot from a live USB stick, run commands below in a terminal, reboot.
# find root partition
sudo fdisk -l
# unencrypt partition
# Note: replace /dev/nvme0n1p3 with your disk
# replace "nvme0n1p3_crypt" with the correct name
# check by running this in chroot:
# $ cat /etc/crypttab | cut -f1 -d " "
# nvme0n1p3_crypt
sudo cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt
# mount root partition
sudo vgscan
sudo vgchange -ay
sudo mount /dev/mapper/xubuntu--vg-root /mnt
# prepare chroot environment
sudo mount /dev/nvme0n1p2 /mnt/boot/ # replace nvme0n1p2 with your boot partition!
sudo mount -o rbind /dev/ /mnt/dev/
sudo mount -t proc proc /mnt/proc/
sudo mount -t sysfs sys /mnt/sys/
# make dns available in chroot
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf
# enter chroot
sudo chroot /mnt /bin/bash
# re-install missing packages
apt install cryptsetup lvm2
# re-generate (this might be done also by apt in the step before, I'm not sure)
update-initramfs -u -k all
# Leave chroot environment - not sure if the following is really necessary...
exit
# Write buffers to disk
sudo sync
# Unmount file systems
sudo umount /mnt/sys
sudo umount /mnt/proc
sudo umount /mnt/boot
This Q&A helped me collecting the commands.
1
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replacednvme0n1p3
withsda5
andnvme0n1p2
withsda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)
– Oliver U
19 hours ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
add a comment |
Try the following:
(initramfs) reboot
Then, at the OS chooser prompt, try booting with an older kernel.
If you succeed, then probably this will fix the problem, as suggested in @One Face's bullets 4 and 5, and the link it refers:
sudo apt-get install lvm2
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
add a comment |
For those here suffering from encryption-related problems, as in @Zanna's answer, you'll need to follow a procedure similar to this:
Boot into your system using a live distro / USB.
Mount the encrypted partition (in Ubuntu, you should see the encrypted volume available on the desktop; double-clicking and entering the password should suffice). The partition will be mounted at
/media/ubuntu/[mount point]
. (The username will change based on distro; e.g., Xubuntu usesxubuntu
.)Open a terminal window and a bourbon.
Set appropriate bindings for mount points within the system:
sudo su -
mount -t auto /dev/sdX /media/ubuntu/[mount point]/boot
mount --bind /dev /media/ubuntu/[mount point]/dev
mount --bind /dev/pts /media/ubuntu/[mount point]/dev/pts
mount --bind /sys /media/ubuntu/[mount point]/sys
chroot
into the root directory of your encrypted disk:chroot /media/ubuntu/[mount point]
Ensure that your system has appropriate
initramfs
packages installed:sudo apt install cryptsetup-initramfs lvm2
.Critically, you'll also need to ensure that your configuration files force
initramfs
to include the cryptsetup binaries, which were removed at some point, it seems:nano /etc/cryptsetup-initramfs/conf-hook
, uncomment theCRYPTSETUP
line, and make sure it readsCRYPTSETUP=Y
.Finally, run
update-initramfs -u -k all
, shut down, pull the live media, and start back up.
Your mileage here may vary depending on what's happened with your system. If, for example, you've changed the LVM group name or the UUID, you may need to align /etc/crypttab
and /etc/fstab
to use the right identifiers. If, like me, you were migrating from one release to another, you may find that you have two encrypted volumes with the same group name—this makes mounting the disk rather difficult (you need to use the UUID explicitly).
All in all, the upgrade to Xubuntu 18.10 was awful because of this. (A stock system wouldn't reboot once the upgrades to the kernel were pulled in!) At least in the current setup I have, the system is stable through reboots.
N.b., the ACPI errors that led me all over the Internet looking for a solution were a red herring: they have no bearing on whether you can boot from an encrypted disk.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f567730%2fgave-up-waiting-for-root-device-ubuntu-vg-root-doesnt-exist%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Please add the outputs of lsblk -fs, fdisk /dev/sda with p flag and the report of grub repair to the question as pastebin links.
Based on searching, there seems to be similar questions on Ask Ubuntu that has no answer up to date here and Here one answer is given which explains about raid and ubuntu.
There seems to be several suggestions, some of which seem to work for some people.
From the initframs prompt try typing
ls /dev/mapper
and see if your root volume is listed. If it is not listed, try waiting 10 seconds and run ls again.
If it is now listed, type
exit
and it should now find the root device and boot (taken from here
Edit the boot config by pressing
e
when grub alert to choose OS, and replaceroot=UUID-6500...
byroot=/dev/sdx
where sdx is the boot partition. The problem here seems to be that the UUID is either wrong, or/dev/disk/by-UUID...
does not exist(1)- Adding the parameter
all_generic_ide
to the end of the boot-line likekernel /boot/vmlinuz-2.6.27-7-generic root=UUID=43206294-74ef-434d-aca2-db74b4257590 ro quiet splash all_generic_ide
seems to work for some people (2)
- The Super User question here, seems to suggest the error is due to LVM. The solution is also given in the same which is to install lvm2.
- The same Super User site also suggests booting using an older Kernel, if available. It seems to work for some people. Trying to boot using the
Recovery
option might work for some people - Post by nux_man777 here seems to suggest the error may be in the installation medium.
The error
/dev/mapper/ubuntu-vg-root
seems to be related to raid as described here.
"In the installer summary screen right before the copy process starts, click the Advanced button. Change the boot partition (this is the MSDOS-style "parent" partition not the Linux partitions) to /dev/mapper/pdc_feddabdf (or whatever dmraid lists as your fakeraid partition) Make sure the checkbox is clicked to boot from this disk. note that the installer will modify grub2 to point to the correct logical partition /dev/mapper/pdc_feddabdf1 or whatever / is on."
Detailed instructions regarding installation is given in the referred site. Please check there for more info on installation of grub.
- Booting into a live installation media and updating ubuntu by changing root using
chroot
seems to work for some people (suggested by cpttripzz here).
Instruction regarding chroot is here. You can also refer to this question at Unix & Linux. More details can be found at Arch Wiki and Gentoo Wiki. - Changing the SATA Controller to Native IDE from RAID and doing a fresh install seems to work for some people here and here
- IDE cable or the hard disk may be bad (the same ubuntu forum as above page 40)
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
|
show 10 more comments
Please add the outputs of lsblk -fs, fdisk /dev/sda with p flag and the report of grub repair to the question as pastebin links.
Based on searching, there seems to be similar questions on Ask Ubuntu that has no answer up to date here and Here one answer is given which explains about raid and ubuntu.
There seems to be several suggestions, some of which seem to work for some people.
From the initframs prompt try typing
ls /dev/mapper
and see if your root volume is listed. If it is not listed, try waiting 10 seconds and run ls again.
If it is now listed, type
exit
and it should now find the root device and boot (taken from here
Edit the boot config by pressing
e
when grub alert to choose OS, and replaceroot=UUID-6500...
byroot=/dev/sdx
where sdx is the boot partition. The problem here seems to be that the UUID is either wrong, or/dev/disk/by-UUID...
does not exist(1)- Adding the parameter
all_generic_ide
to the end of the boot-line likekernel /boot/vmlinuz-2.6.27-7-generic root=UUID=43206294-74ef-434d-aca2-db74b4257590 ro quiet splash all_generic_ide
seems to work for some people (2)
- The Super User question here, seems to suggest the error is due to LVM. The solution is also given in the same which is to install lvm2.
- The same Super User site also suggests booting using an older Kernel, if available. It seems to work for some people. Trying to boot using the
Recovery
option might work for some people - Post by nux_man777 here seems to suggest the error may be in the installation medium.
The error
/dev/mapper/ubuntu-vg-root
seems to be related to raid as described here.
"In the installer summary screen right before the copy process starts, click the Advanced button. Change the boot partition (this is the MSDOS-style "parent" partition not the Linux partitions) to /dev/mapper/pdc_feddabdf (or whatever dmraid lists as your fakeraid partition) Make sure the checkbox is clicked to boot from this disk. note that the installer will modify grub2 to point to the correct logical partition /dev/mapper/pdc_feddabdf1 or whatever / is on."
Detailed instructions regarding installation is given in the referred site. Please check there for more info on installation of grub.
- Booting into a live installation media and updating ubuntu by changing root using
chroot
seems to work for some people (suggested by cpttripzz here).
Instruction regarding chroot is here. You can also refer to this question at Unix & Linux. More details can be found at Arch Wiki and Gentoo Wiki. - Changing the SATA Controller to Native IDE from RAID and doing a fresh install seems to work for some people here and here
- IDE cable or the hard disk may be bad (the same ubuntu forum as above page 40)
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
|
show 10 more comments
Please add the outputs of lsblk -fs, fdisk /dev/sda with p flag and the report of grub repair to the question as pastebin links.
Based on searching, there seems to be similar questions on Ask Ubuntu that has no answer up to date here and Here one answer is given which explains about raid and ubuntu.
There seems to be several suggestions, some of which seem to work for some people.
From the initframs prompt try typing
ls /dev/mapper
and see if your root volume is listed. If it is not listed, try waiting 10 seconds and run ls again.
If it is now listed, type
exit
and it should now find the root device and boot (taken from here
Edit the boot config by pressing
e
when grub alert to choose OS, and replaceroot=UUID-6500...
byroot=/dev/sdx
where sdx is the boot partition. The problem here seems to be that the UUID is either wrong, or/dev/disk/by-UUID...
does not exist(1)- Adding the parameter
all_generic_ide
to the end of the boot-line likekernel /boot/vmlinuz-2.6.27-7-generic root=UUID=43206294-74ef-434d-aca2-db74b4257590 ro quiet splash all_generic_ide
seems to work for some people (2)
- The Super User question here, seems to suggest the error is due to LVM. The solution is also given in the same which is to install lvm2.
- The same Super User site also suggests booting using an older Kernel, if available. It seems to work for some people. Trying to boot using the
Recovery
option might work for some people - Post by nux_man777 here seems to suggest the error may be in the installation medium.
The error
/dev/mapper/ubuntu-vg-root
seems to be related to raid as described here.
"In the installer summary screen right before the copy process starts, click the Advanced button. Change the boot partition (this is the MSDOS-style "parent" partition not the Linux partitions) to /dev/mapper/pdc_feddabdf (or whatever dmraid lists as your fakeraid partition) Make sure the checkbox is clicked to boot from this disk. note that the installer will modify grub2 to point to the correct logical partition /dev/mapper/pdc_feddabdf1 or whatever / is on."
Detailed instructions regarding installation is given in the referred site. Please check there for more info on installation of grub.
- Booting into a live installation media and updating ubuntu by changing root using
chroot
seems to work for some people (suggested by cpttripzz here).
Instruction regarding chroot is here. You can also refer to this question at Unix & Linux. More details can be found at Arch Wiki and Gentoo Wiki. - Changing the SATA Controller to Native IDE from RAID and doing a fresh install seems to work for some people here and here
- IDE cable or the hard disk may be bad (the same ubuntu forum as above page 40)
Please add the outputs of lsblk -fs, fdisk /dev/sda with p flag and the report of grub repair to the question as pastebin links.
Based on searching, there seems to be similar questions on Ask Ubuntu that has no answer up to date here and Here one answer is given which explains about raid and ubuntu.
There seems to be several suggestions, some of which seem to work for some people.
From the initframs prompt try typing
ls /dev/mapper
and see if your root volume is listed. If it is not listed, try waiting 10 seconds and run ls again.
If it is now listed, type
exit
and it should now find the root device and boot (taken from here
Edit the boot config by pressing
e
when grub alert to choose OS, and replaceroot=UUID-6500...
byroot=/dev/sdx
where sdx is the boot partition. The problem here seems to be that the UUID is either wrong, or/dev/disk/by-UUID...
does not exist(1)- Adding the parameter
all_generic_ide
to the end of the boot-line likekernel /boot/vmlinuz-2.6.27-7-generic root=UUID=43206294-74ef-434d-aca2-db74b4257590 ro quiet splash all_generic_ide
seems to work for some people (2)
- The Super User question here, seems to suggest the error is due to LVM. The solution is also given in the same which is to install lvm2.
- The same Super User site also suggests booting using an older Kernel, if available. It seems to work for some people. Trying to boot using the
Recovery
option might work for some people - Post by nux_man777 here seems to suggest the error may be in the installation medium.
The error
/dev/mapper/ubuntu-vg-root
seems to be related to raid as described here.
"In the installer summary screen right before the copy process starts, click the Advanced button. Change the boot partition (this is the MSDOS-style "parent" partition not the Linux partitions) to /dev/mapper/pdc_feddabdf (or whatever dmraid lists as your fakeraid partition) Make sure the checkbox is clicked to boot from this disk. note that the installer will modify grub2 to point to the correct logical partition /dev/mapper/pdc_feddabdf1 or whatever / is on."
Detailed instructions regarding installation is given in the referred site. Please check there for more info on installation of grub.
- Booting into a live installation media and updating ubuntu by changing root using
chroot
seems to work for some people (suggested by cpttripzz here).
Instruction regarding chroot is here. You can also refer to this question at Unix & Linux. More details can be found at Arch Wiki and Gentoo Wiki. - Changing the SATA Controller to Native IDE from RAID and doing a fresh install seems to work for some people here and here
- IDE cable or the hard disk may be bad (the same ubuntu forum as above page 40)
edited Apr 13 '17 at 12:37
Community♦
1
1
answered Jan 2 '15 at 4:51
One FaceOne Face
23116
23116
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
|
show 10 more comments
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
The previous os was Win7
– Jonas Franz
Jan 2 '15 at 12:30
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
fdisk hastebin.com/wayiqowine.rib
– Jonas Franz
Jan 2 '15 at 12:46
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
lsblk --fs hastebin.com/vadapinoro.hs
– Jonas Franz
Jan 2 '15 at 12:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Boot Repair: paste.ubuntu.com/9660149
– Jonas Franz
Jan 2 '15 at 16:47
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
Error Message: postimg.org/image/tzuyske3d
– Jonas Franz
Jan 2 '15 at 16:52
|
show 10 more comments
I had this problem and nothing on any posts here or elsewhere were able to help. Specifically in my case, I could see that /dev/mapper
did not contain ubuntu--vg-root
or anything else for that matter. This means that something either went wrong when LVM tried to mount/map the volumes OR something went wrong earlier in the boot process, and this error is just a catch-all symptom for any earlier problem.
The second of these was the case for me and only because of my reading about initramfs
I was able to understand and diagnose the issue. This should be the first thing you do if you suspect something has gone wrong prior to LVM doing its thing.
In my case (which may not be the same as you but is worth documenting), I had full disk encryption (LUKS) enabled, and somehow the cryptsetup
tools had been removed from initramfs
, therefore I was not being prompted for the passphrase to unlock, and the drives were not accessible, which meant that /dev/sdaX
could not be mounted, and therefore ubuntu--vg-root
could not be mounted/mapped into /dev/mapper
. If you try to run cryptsetup
from the BusyBox prompt, youll know you have the same issue if the
cryptsetup` cannot be found.
The solution was to boot from a LiveCD, unlock the drive manually with cryptsetup
, chroot
into the root filesystem, reinstall cryptsetup
and call update-initramfs
.
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
1
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652
– dragon788
Sep 5 '18 at 19:27
add a comment |
I had this problem and nothing on any posts here or elsewhere were able to help. Specifically in my case, I could see that /dev/mapper
did not contain ubuntu--vg-root
or anything else for that matter. This means that something either went wrong when LVM tried to mount/map the volumes OR something went wrong earlier in the boot process, and this error is just a catch-all symptom for any earlier problem.
The second of these was the case for me and only because of my reading about initramfs
I was able to understand and diagnose the issue. This should be the first thing you do if you suspect something has gone wrong prior to LVM doing its thing.
In my case (which may not be the same as you but is worth documenting), I had full disk encryption (LUKS) enabled, and somehow the cryptsetup
tools had been removed from initramfs
, therefore I was not being prompted for the passphrase to unlock, and the drives were not accessible, which meant that /dev/sdaX
could not be mounted, and therefore ubuntu--vg-root
could not be mounted/mapped into /dev/mapper
. If you try to run cryptsetup
from the BusyBox prompt, youll know you have the same issue if the
cryptsetup` cannot be found.
The solution was to boot from a LiveCD, unlock the drive manually with cryptsetup
, chroot
into the root filesystem, reinstall cryptsetup
and call update-initramfs
.
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
1
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652
– dragon788
Sep 5 '18 at 19:27
add a comment |
I had this problem and nothing on any posts here or elsewhere were able to help. Specifically in my case, I could see that /dev/mapper
did not contain ubuntu--vg-root
or anything else for that matter. This means that something either went wrong when LVM tried to mount/map the volumes OR something went wrong earlier in the boot process, and this error is just a catch-all symptom for any earlier problem.
The second of these was the case for me and only because of my reading about initramfs
I was able to understand and diagnose the issue. This should be the first thing you do if you suspect something has gone wrong prior to LVM doing its thing.
In my case (which may not be the same as you but is worth documenting), I had full disk encryption (LUKS) enabled, and somehow the cryptsetup
tools had been removed from initramfs
, therefore I was not being prompted for the passphrase to unlock, and the drives were not accessible, which meant that /dev/sdaX
could not be mounted, and therefore ubuntu--vg-root
could not be mounted/mapped into /dev/mapper
. If you try to run cryptsetup
from the BusyBox prompt, youll know you have the same issue if the
cryptsetup` cannot be found.
The solution was to boot from a LiveCD, unlock the drive manually with cryptsetup
, chroot
into the root filesystem, reinstall cryptsetup
and call update-initramfs
.
I had this problem and nothing on any posts here or elsewhere were able to help. Specifically in my case, I could see that /dev/mapper
did not contain ubuntu--vg-root
or anything else for that matter. This means that something either went wrong when LVM tried to mount/map the volumes OR something went wrong earlier in the boot process, and this error is just a catch-all symptom for any earlier problem.
The second of these was the case for me and only because of my reading about initramfs
I was able to understand and diagnose the issue. This should be the first thing you do if you suspect something has gone wrong prior to LVM doing its thing.
In my case (which may not be the same as you but is worth documenting), I had full disk encryption (LUKS) enabled, and somehow the cryptsetup
tools had been removed from initramfs
, therefore I was not being prompted for the passphrase to unlock, and the drives were not accessible, which meant that /dev/sdaX
could not be mounted, and therefore ubuntu--vg-root
could not be mounted/mapped into /dev/mapper
. If you try to run cryptsetup
from the BusyBox prompt, youll know you have the same issue if the
cryptsetup` cannot be found.
The solution was to boot from a LiveCD, unlock the drive manually with cryptsetup
, chroot
into the root filesystem, reinstall cryptsetup
and call update-initramfs
.
edited Mar 23 '18 at 12:44
Zanna
50.9k13136241
50.9k13136241
answered Mar 23 '18 at 11:28
cwilkocwilko
111
111
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
1
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652
– dragon788
Sep 5 '18 at 19:27
add a comment |
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
1
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652
– dragon788
Sep 5 '18 at 19:27
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
Welcome to Ask Ubuntu! :-) Can you expand the last line into actual commands?
– Fabby
Mar 23 '18 at 12:24
1
1
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to
/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652– dragon788
Sep 5 '18 at 19:27
I wrote a script for this case (LUKS + LVM) on an NVMe drive, but may expand it to
/dev/sd*
style drives as well. unix.stackexchange.com/a/467113/103652– dragon788
Sep 5 '18 at 19:27
add a comment |
In certain Ubuntu versions (e.g. Xubuntu 18.10) this issue might be caused by an apt autoremove
. Due to this bug apt will suggest to remove
cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2
which makes the system non-bootable (because the root partiation cannot be mounted and unencrypted using LVM).
If you are not using LVM and disk encryption this answer is probably not for you.
I was able to fix it by re-installing cryptsetup and lvm2 in a chroot environment: boot from a live USB stick, run commands below in a terminal, reboot.
# find root partition
sudo fdisk -l
# unencrypt partition
# Note: replace /dev/nvme0n1p3 with your disk
# replace "nvme0n1p3_crypt" with the correct name
# check by running this in chroot:
# $ cat /etc/crypttab | cut -f1 -d " "
# nvme0n1p3_crypt
sudo cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt
# mount root partition
sudo vgscan
sudo vgchange -ay
sudo mount /dev/mapper/xubuntu--vg-root /mnt
# prepare chroot environment
sudo mount /dev/nvme0n1p2 /mnt/boot/ # replace nvme0n1p2 with your boot partition!
sudo mount -o rbind /dev/ /mnt/dev/
sudo mount -t proc proc /mnt/proc/
sudo mount -t sysfs sys /mnt/sys/
# make dns available in chroot
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf
# enter chroot
sudo chroot /mnt /bin/bash
# re-install missing packages
apt install cryptsetup lvm2
# re-generate (this might be done also by apt in the step before, I'm not sure)
update-initramfs -u -k all
# Leave chroot environment - not sure if the following is really necessary...
exit
# Write buffers to disk
sudo sync
# Unmount file systems
sudo umount /mnt/sys
sudo umount /mnt/proc
sudo umount /mnt/boot
This Q&A helped me collecting the commands.
1
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replacednvme0n1p3
withsda5
andnvme0n1p2
withsda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)
– Oliver U
19 hours ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
add a comment |
In certain Ubuntu versions (e.g. Xubuntu 18.10) this issue might be caused by an apt autoremove
. Due to this bug apt will suggest to remove
cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2
which makes the system non-bootable (because the root partiation cannot be mounted and unencrypted using LVM).
If you are not using LVM and disk encryption this answer is probably not for you.
I was able to fix it by re-installing cryptsetup and lvm2 in a chroot environment: boot from a live USB stick, run commands below in a terminal, reboot.
# find root partition
sudo fdisk -l
# unencrypt partition
# Note: replace /dev/nvme0n1p3 with your disk
# replace "nvme0n1p3_crypt" with the correct name
# check by running this in chroot:
# $ cat /etc/crypttab | cut -f1 -d " "
# nvme0n1p3_crypt
sudo cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt
# mount root partition
sudo vgscan
sudo vgchange -ay
sudo mount /dev/mapper/xubuntu--vg-root /mnt
# prepare chroot environment
sudo mount /dev/nvme0n1p2 /mnt/boot/ # replace nvme0n1p2 with your boot partition!
sudo mount -o rbind /dev/ /mnt/dev/
sudo mount -t proc proc /mnt/proc/
sudo mount -t sysfs sys /mnt/sys/
# make dns available in chroot
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf
# enter chroot
sudo chroot /mnt /bin/bash
# re-install missing packages
apt install cryptsetup lvm2
# re-generate (this might be done also by apt in the step before, I'm not sure)
update-initramfs -u -k all
# Leave chroot environment - not sure if the following is really necessary...
exit
# Write buffers to disk
sudo sync
# Unmount file systems
sudo umount /mnt/sys
sudo umount /mnt/proc
sudo umount /mnt/boot
This Q&A helped me collecting the commands.
1
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replacednvme0n1p3
withsda5
andnvme0n1p2
withsda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)
– Oliver U
19 hours ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
add a comment |
In certain Ubuntu versions (e.g. Xubuntu 18.10) this issue might be caused by an apt autoremove
. Due to this bug apt will suggest to remove
cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2
which makes the system non-bootable (because the root partiation cannot be mounted and unencrypted using LVM).
If you are not using LVM and disk encryption this answer is probably not for you.
I was able to fix it by re-installing cryptsetup and lvm2 in a chroot environment: boot from a live USB stick, run commands below in a terminal, reboot.
# find root partition
sudo fdisk -l
# unencrypt partition
# Note: replace /dev/nvme0n1p3 with your disk
# replace "nvme0n1p3_crypt" with the correct name
# check by running this in chroot:
# $ cat /etc/crypttab | cut -f1 -d " "
# nvme0n1p3_crypt
sudo cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt
# mount root partition
sudo vgscan
sudo vgchange -ay
sudo mount /dev/mapper/xubuntu--vg-root /mnt
# prepare chroot environment
sudo mount /dev/nvme0n1p2 /mnt/boot/ # replace nvme0n1p2 with your boot partition!
sudo mount -o rbind /dev/ /mnt/dev/
sudo mount -t proc proc /mnt/proc/
sudo mount -t sysfs sys /mnt/sys/
# make dns available in chroot
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf
# enter chroot
sudo chroot /mnt /bin/bash
# re-install missing packages
apt install cryptsetup lvm2
# re-generate (this might be done also by apt in the step before, I'm not sure)
update-initramfs -u -k all
# Leave chroot environment - not sure if the following is really necessary...
exit
# Write buffers to disk
sudo sync
# Unmount file systems
sudo umount /mnt/sys
sudo umount /mnt/proc
sudo umount /mnt/boot
This Q&A helped me collecting the commands.
In certain Ubuntu versions (e.g. Xubuntu 18.10) this issue might be caused by an apt autoremove
. Due to this bug apt will suggest to remove
cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2
which makes the system non-bootable (because the root partiation cannot be mounted and unencrypted using LVM).
If you are not using LVM and disk encryption this answer is probably not for you.
I was able to fix it by re-installing cryptsetup and lvm2 in a chroot environment: boot from a live USB stick, run commands below in a terminal, reboot.
# find root partition
sudo fdisk -l
# unencrypt partition
# Note: replace /dev/nvme0n1p3 with your disk
# replace "nvme0n1p3_crypt" with the correct name
# check by running this in chroot:
# $ cat /etc/crypttab | cut -f1 -d " "
# nvme0n1p3_crypt
sudo cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt
# mount root partition
sudo vgscan
sudo vgchange -ay
sudo mount /dev/mapper/xubuntu--vg-root /mnt
# prepare chroot environment
sudo mount /dev/nvme0n1p2 /mnt/boot/ # replace nvme0n1p2 with your boot partition!
sudo mount -o rbind /dev/ /mnt/dev/
sudo mount -t proc proc /mnt/proc/
sudo mount -t sysfs sys /mnt/sys/
# make dns available in chroot
sudo cp /etc/resolv.conf /mnt/etc/resolv.conf
# enter chroot
sudo chroot /mnt /bin/bash
# re-install missing packages
apt install cryptsetup lvm2
# re-generate (this might be done also by apt in the step before, I'm not sure)
update-initramfs -u -k all
# Leave chroot environment - not sure if the following is really necessary...
exit
# Write buffers to disk
sudo sync
# Unmount file systems
sudo umount /mnt/sys
sudo umount /mnt/proc
sudo umount /mnt/boot
This Q&A helped me collecting the commands.
edited 11 mins ago
answered 2 days ago
lumbriclumbric
2,84312142
2,84312142
1
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replacednvme0n1p3
withsda5
andnvme0n1p2
withsda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)
– Oliver U
19 hours ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
add a comment |
1
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replacednvme0n1p3
withsda5
andnvme0n1p2
withsda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)
– Oliver U
19 hours ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
1
1
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replaced
nvme0n1p3
with sda5
and nvme0n1p2
with sda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)– Oliver U
19 hours ago
Ohh, you just saved me about three days of work I'd put into setting up a new device. Worked perfectly! Replaced
nvme0n1p3
with sda5
and nvme0n1p2
with sda1
(linux partition inside the LVM and the small boot partition outside the LVM, respectively)– Oliver U
19 hours ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
@OliverU great that it worked! Even if you can't make it boot anymore, you should be still able to copy your home directory and maybe parts of /etc or so to a fresh install. That should be probably less work than the inital setup.
– lumbric
9 mins ago
add a comment |
Try the following:
(initramfs) reboot
Then, at the OS chooser prompt, try booting with an older kernel.
If you succeed, then probably this will fix the problem, as suggested in @One Face's bullets 4 and 5, and the link it refers:
sudo apt-get install lvm2
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
add a comment |
Try the following:
(initramfs) reboot
Then, at the OS chooser prompt, try booting with an older kernel.
If you succeed, then probably this will fix the problem, as suggested in @One Face's bullets 4 and 5, and the link it refers:
sudo apt-get install lvm2
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
add a comment |
Try the following:
(initramfs) reboot
Then, at the OS chooser prompt, try booting with an older kernel.
If you succeed, then probably this will fix the problem, as suggested in @One Face's bullets 4 and 5, and the link it refers:
sudo apt-get install lvm2
Try the following:
(initramfs) reboot
Then, at the OS chooser prompt, try booting with an older kernel.
If you succeed, then probably this will fix the problem, as suggested in @One Face's bullets 4 and 5, and the link it refers:
sudo apt-get install lvm2
answered Oct 2 '15 at 19:06
e18re18r
24968
24968
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
add a comment |
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
If lvm2 not installed older kernel will not to boot. lvm2 package and kernel is not linked things. It need to boot with Rescue System and install package through chroot.
– PRIHLOP
Sep 12 '18 at 21:00
add a comment |
For those here suffering from encryption-related problems, as in @Zanna's answer, you'll need to follow a procedure similar to this:
Boot into your system using a live distro / USB.
Mount the encrypted partition (in Ubuntu, you should see the encrypted volume available on the desktop; double-clicking and entering the password should suffice). The partition will be mounted at
/media/ubuntu/[mount point]
. (The username will change based on distro; e.g., Xubuntu usesxubuntu
.)Open a terminal window and a bourbon.
Set appropriate bindings for mount points within the system:
sudo su -
mount -t auto /dev/sdX /media/ubuntu/[mount point]/boot
mount --bind /dev /media/ubuntu/[mount point]/dev
mount --bind /dev/pts /media/ubuntu/[mount point]/dev/pts
mount --bind /sys /media/ubuntu/[mount point]/sys
chroot
into the root directory of your encrypted disk:chroot /media/ubuntu/[mount point]
Ensure that your system has appropriate
initramfs
packages installed:sudo apt install cryptsetup-initramfs lvm2
.Critically, you'll also need to ensure that your configuration files force
initramfs
to include the cryptsetup binaries, which were removed at some point, it seems:nano /etc/cryptsetup-initramfs/conf-hook
, uncomment theCRYPTSETUP
line, and make sure it readsCRYPTSETUP=Y
.Finally, run
update-initramfs -u -k all
, shut down, pull the live media, and start back up.
Your mileage here may vary depending on what's happened with your system. If, for example, you've changed the LVM group name or the UUID, you may need to align /etc/crypttab
and /etc/fstab
to use the right identifiers. If, like me, you were migrating from one release to another, you may find that you have two encrypted volumes with the same group name—this makes mounting the disk rather difficult (you need to use the UUID explicitly).
All in all, the upgrade to Xubuntu 18.10 was awful because of this. (A stock system wouldn't reboot once the upgrades to the kernel were pulled in!) At least in the current setup I have, the system is stable through reboots.
N.b., the ACPI errors that led me all over the Internet looking for a solution were a red herring: they have no bearing on whether you can boot from an encrypted disk.
add a comment |
For those here suffering from encryption-related problems, as in @Zanna's answer, you'll need to follow a procedure similar to this:
Boot into your system using a live distro / USB.
Mount the encrypted partition (in Ubuntu, you should see the encrypted volume available on the desktop; double-clicking and entering the password should suffice). The partition will be mounted at
/media/ubuntu/[mount point]
. (The username will change based on distro; e.g., Xubuntu usesxubuntu
.)Open a terminal window and a bourbon.
Set appropriate bindings for mount points within the system:
sudo su -
mount -t auto /dev/sdX /media/ubuntu/[mount point]/boot
mount --bind /dev /media/ubuntu/[mount point]/dev
mount --bind /dev/pts /media/ubuntu/[mount point]/dev/pts
mount --bind /sys /media/ubuntu/[mount point]/sys
chroot
into the root directory of your encrypted disk:chroot /media/ubuntu/[mount point]
Ensure that your system has appropriate
initramfs
packages installed:sudo apt install cryptsetup-initramfs lvm2
.Critically, you'll also need to ensure that your configuration files force
initramfs
to include the cryptsetup binaries, which were removed at some point, it seems:nano /etc/cryptsetup-initramfs/conf-hook
, uncomment theCRYPTSETUP
line, and make sure it readsCRYPTSETUP=Y
.Finally, run
update-initramfs -u -k all
, shut down, pull the live media, and start back up.
Your mileage here may vary depending on what's happened with your system. If, for example, you've changed the LVM group name or the UUID, you may need to align /etc/crypttab
and /etc/fstab
to use the right identifiers. If, like me, you were migrating from one release to another, you may find that you have two encrypted volumes with the same group name—this makes mounting the disk rather difficult (you need to use the UUID explicitly).
All in all, the upgrade to Xubuntu 18.10 was awful because of this. (A stock system wouldn't reboot once the upgrades to the kernel were pulled in!) At least in the current setup I have, the system is stable through reboots.
N.b., the ACPI errors that led me all over the Internet looking for a solution were a red herring: they have no bearing on whether you can boot from an encrypted disk.
add a comment |
For those here suffering from encryption-related problems, as in @Zanna's answer, you'll need to follow a procedure similar to this:
Boot into your system using a live distro / USB.
Mount the encrypted partition (in Ubuntu, you should see the encrypted volume available on the desktop; double-clicking and entering the password should suffice). The partition will be mounted at
/media/ubuntu/[mount point]
. (The username will change based on distro; e.g., Xubuntu usesxubuntu
.)Open a terminal window and a bourbon.
Set appropriate bindings for mount points within the system:
sudo su -
mount -t auto /dev/sdX /media/ubuntu/[mount point]/boot
mount --bind /dev /media/ubuntu/[mount point]/dev
mount --bind /dev/pts /media/ubuntu/[mount point]/dev/pts
mount --bind /sys /media/ubuntu/[mount point]/sys
chroot
into the root directory of your encrypted disk:chroot /media/ubuntu/[mount point]
Ensure that your system has appropriate
initramfs
packages installed:sudo apt install cryptsetup-initramfs lvm2
.Critically, you'll also need to ensure that your configuration files force
initramfs
to include the cryptsetup binaries, which were removed at some point, it seems:nano /etc/cryptsetup-initramfs/conf-hook
, uncomment theCRYPTSETUP
line, and make sure it readsCRYPTSETUP=Y
.Finally, run
update-initramfs -u -k all
, shut down, pull the live media, and start back up.
Your mileage here may vary depending on what's happened with your system. If, for example, you've changed the LVM group name or the UUID, you may need to align /etc/crypttab
and /etc/fstab
to use the right identifiers. If, like me, you were migrating from one release to another, you may find that you have two encrypted volumes with the same group name—this makes mounting the disk rather difficult (you need to use the UUID explicitly).
All in all, the upgrade to Xubuntu 18.10 was awful because of this. (A stock system wouldn't reboot once the upgrades to the kernel were pulled in!) At least in the current setup I have, the system is stable through reboots.
N.b., the ACPI errors that led me all over the Internet looking for a solution were a red herring: they have no bearing on whether you can boot from an encrypted disk.
For those here suffering from encryption-related problems, as in @Zanna's answer, you'll need to follow a procedure similar to this:
Boot into your system using a live distro / USB.
Mount the encrypted partition (in Ubuntu, you should see the encrypted volume available on the desktop; double-clicking and entering the password should suffice). The partition will be mounted at
/media/ubuntu/[mount point]
. (The username will change based on distro; e.g., Xubuntu usesxubuntu
.)Open a terminal window and a bourbon.
Set appropriate bindings for mount points within the system:
sudo su -
mount -t auto /dev/sdX /media/ubuntu/[mount point]/boot
mount --bind /dev /media/ubuntu/[mount point]/dev
mount --bind /dev/pts /media/ubuntu/[mount point]/dev/pts
mount --bind /sys /media/ubuntu/[mount point]/sys
chroot
into the root directory of your encrypted disk:chroot /media/ubuntu/[mount point]
Ensure that your system has appropriate
initramfs
packages installed:sudo apt install cryptsetup-initramfs lvm2
.Critically, you'll also need to ensure that your configuration files force
initramfs
to include the cryptsetup binaries, which were removed at some point, it seems:nano /etc/cryptsetup-initramfs/conf-hook
, uncomment theCRYPTSETUP
line, and make sure it readsCRYPTSETUP=Y
.Finally, run
update-initramfs -u -k all
, shut down, pull the live media, and start back up.
Your mileage here may vary depending on what's happened with your system. If, for example, you've changed the LVM group name or the UUID, you may need to align /etc/crypttab
and /etc/fstab
to use the right identifiers. If, like me, you were migrating from one release to another, you may find that you have two encrypted volumes with the same group name—this makes mounting the disk rather difficult (you need to use the UUID explicitly).
All in all, the upgrade to Xubuntu 18.10 was awful because of this. (A stock system wouldn't reboot once the upgrades to the kernel were pulled in!) At least in the current setup I have, the system is stable through reboots.
N.b., the ACPI errors that led me all over the Internet looking for a solution were a red herring: they have no bearing on whether you can boot from an encrypted disk.
edited Dec 31 '18 at 14:39
Thomas
3,79981527
3,79981527
answered Dec 31 '18 at 14:30
EthanEthan
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f567730%2fgave-up-waiting-for-root-device-ubuntu-vg-root-doesnt-exist%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
run
lsblk
and add the output to your question.– psusi
Jan 1 '15 at 19:54
5
@psusi What if
lsblk
is not available?– sitilge
Aug 15 '15 at 20:06