Hi there, Digital Ocean Community, I have a digital ocean droplet that was on $56 per month with premium intel CPU & 8 Gigs of Ram. We had purchased this server two years ago. Now due to some reasons, we had to upgrade the ram of server.
After initial research, we upgraded the RAM & CPU (Only) option and didn’t go with anything besides this.
For this, I booted in my droplet and wrote the command:
shutdown -h now
After turning off droplet safely, I upgraded the ram & cpu of server which took only 1 minute.
After that I rebooted into server and from that time I am getting
“end Kernel panic — not syncing : VFS :Unable to mount root fs on unknown—block(0,0)”
I tried talking with support team, and they sent me some commands + Urls to websites to follow to resolve the issue.
But nothing has been helping me so far. What’s more troublesome is that I cannot create another droplet, because there’s a lot of data on existing droplet.
Here’s what I have followed so far:
mount /dev/vda1 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt/
grub-install /dev/vda1
grub-install --recheck /dev/vda1
update-grub
Can anyone please help me out on this issue?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Heya,
When I’ve had similar problems, I’ve tried some of the following:
-
Check Boot Loader Configuration:
- After
chroot /mnt/, ensure the GRUB configuration is correct. Sometimes, the GRUB config might not correctly identify the root file system. - You can edit the GRUB configuration file (
/etc/default/grub) and then runupdate-grubagain.
- After
-
Reinstall the Kernel:
- While in the chroot environment, you might want to try reinstalling the kernel. This can sometimes resolve issues with kernel panic. Use
apt-get install --reinstall linux-image-$(uname -r)to reinstall the current kernel.
- While in the chroot environment, you might want to try reinstalling the kernel. This can sometimes resolve issues with kernel panic. Use
-
Check File System Consistency:
- Before mounting the filesystems and chrooting, run a file system check on your root partition (
/dev/vda1). Usefsck /dev/vda1to check and repair the file system.
- Before mounting the filesystems and chrooting, run a file system check on your root partition (
-
Review fstab File:
- In the chroot environment, check the
/etc/fstabfile to ensure that the entries there correctly match your disk partitions and file systems.
- In the chroot environment, check the
-
Recheck GRUB Installation:
- The command
grub-install /dev/vda1is typically not recommended as it installs GRUB on the partition rather than the MBR (Master Boot Record). You should usegrub-install /dev/vdainstead. This installs GRUB in the MBR of your disk, which is usually required to boot properly.
- The command
If it doesn’t help, please provide me with your Ticket Reference so that I can try and get more support from DigitalOcean for you.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.