DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

Error while installing packages.

  • Posted January 24, 2013

cryptsetup: WARNING: failed to detect canonical device of /dev/xvda cryptsetup: WARNING: could not determine root device from /etc/fstab

I am getting those two errors, any idea?

Subscribe
Share
rbgoksoy • September 28, 2014

Same problem.

After upgrade on 12.04, my site does not work on Ubuntu 12.04.1

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Kamal Nasser • October 9, 2013

@vicparekh: You can change your droplet’s kernel here: <a href=“https://kmlnsr.me/Screenshot from 2013-10-09 17%3A41%3A43.png”>https://kmlnsr.me/Screenshot from 2013-10-09 17%3A41%3A43.png</a>

vicparekh • October 8, 2013

How exactly do I do this? “update my kernel from the Settings tab in your droplet’s page” <br> <br>I am getting the same problem as OP

Iko • September 22, 2013

Before upgrade Ubuntu 12.04 32x LTS. I test and change the /etc/fstab with this one it and working with no cryptsetup: Warning. <br> <br>sudo nano /etc/fstab <br> <br>LABEL=DOROOT / ext4 errors=remount-ro 0 1 <br>

rvangeilswyk • May 25, 2013

It did indeed - Thanks Kamal

Kamal Nasser • May 24, 2013

@rvg: Update your droplet and /then/ update your kernel from the Settings tab in your droplet’s page. It should fix the kernel modules issue.

rvangeilswyk • May 24, 2013

@raiyu - Could we get an update on the status of a resolution please? <br> <br>I ran across this issue earlier today.

Moisey Uretsky • April 13, 2013

This is an issue related to the kernel and modules being mismatched during the system upgrade and is caused by the fact that the kernel is being loaded through the hypervisor and not your local virtual machine. <br> <br>The fix to this is to allow customers to manage their own kernels in which case they would be synced to your system so running a system upgrade would not cause these errors. <br> <br>We are currently about 3-4 weeks away from releasing that so hopefully this issue will be resolved soon.

7Hz4c2 • March 15, 2013

I’ve been seeing this same issue for quite some time. I just did another apt-get upgrade and it happened. Could you please publicize the solution? Googling around doesn’t give much insight (though I actually found this thread from Google).

c0smicalninja • January 25, 2013

Okay.

Moisey Uretsky • January 25, 2013

Best to open a support ticket with the full output so we can help troubleshoot this with you.