Linux @lemmy.ml dafunkkk @lemmy.world 1y ago

How to solve this boot error message?

I'm on debian 11, this error doesn't show up every time, but once it appear I need more that one reboot and it will fix automatically without doing nothing, don't know the reason why (just read that can be kernel dependent). What I want to avoid is that maybe it's just a warning of somethink that will cause a pc break in future (maybe hardware is starting working bad?) Do you have any sugggestion? Thanks

25 comments

In the grub menu, choose advanced options and then choose an older kernel to boot into.
If that boots fine, remove and reinstall the newest installed kernel and run sudo update-grub.
That should be the easiest way to fix the most possible causes of this error.

Edit: Now would be a very good time to back up all your data to an external drive. This might be a sign of your hard drive failing.
- I second the advice to switch to a different/previous/known good kernel. That has been the cause a most boot problems for me. I just had it happen on a VM a couple of weeks ago, so I switched to the old kernel, then removed the new kernel. I’ll wait for another kernel before upgrading.
  
  It’s probably worth scanning your disk just in case as well.
- I wouldn't be quick to assume that this means a failing disk. There would probably be more sporadic issues if this were the case.
  
  I wouldn't assume a failing disk either.
  But every time there's an error you can't pin on something you just did, a full backup should be the first thing you do as a matter of principle.
Disk sometimes being too slow to appear? Try rootwait/rootdelay kernel cmdline options.
- seems not....but I'm not used to intense task
Did you change your fstab, or have a full partition or something?
- I not on that machine but as far as I remember it's a full ntfs partition, don't think I ever changed fstab
  
  Your root filesystem is NTFS? That's likely the problem - I'm surprised it boots at all. Switching to a Linux filesystem is the likely solution. You could also try a newer kernel, too - 5.10 is quite old, current LTS is 6.1. Good luck.
Depending on if you wrote the kernel cmdline yourself I imagine this might happen using /dev/sdN style device paths? BIOS might change things up every now and then for fun, so using partition UUIDs would be a better way if so.
- so can be bios dependent?..it's possible to change from /dev/sdn to UUIDs...how? Thanks
  
  Basically just look for things like root=/dev/sda2 in the kernel command line. You can get it at runtime by running "cat /proc/cmdline" having /dev/sda etc in your fstab might also be a problem
  
  Yes if you have multiple drives some buggy BIOS may not enumerate them in the same order every time. Most modern distros do UUIDs by default but when manually setting up a bootloader it is easy to succumb to such temptations to use the much simpler device paths as the UUIDs are a pain. If you're not sure how to change the kernel parameters most likely you're good on that front actually, its in your grub config as others have mentioned. I'll leave this comment around in case some poor soul who did it manually comes across the thread.
- I hope by partition UUID you mean root=PARTUUID=, not root=UUID= because kernel can understand only PARTUUID.
  
  Yes, forgot the exact details apologies
Kernel says it can't mount root device. Maybe it is not specified or kernel just can't find it. You need to edit root= parameter for kernel. For:

GRUB: press 'e' to edit menu entry and then press 'F10' to boot

LILO: just append desired root=

EFIStub: change it in config and recompile it

If you use GRUB you can use its console and search for disk and partition where root fs is located.
You sure your hdd/ssd is fine? It complains about not being able to mount the root fs.
- how can I be sure? it just happen sometimes

25 comments