Originally Posted by tea for one I've just noticed that I had an incorrect instruction in post 2. I typed nvme0n1p1 twice by mistake - schoolboy error........ Can you boot into a live session again and run fsck on both partitions. Code: sudo fsck /dev/nvme0n1p1 Code: sudo fsck /dev/nvme0n1p2 No problem. Tried the new instructions. The second partition turned out to be clean. No new errors on the first. Rebooted, still no luck.
sudo fsck /dev/nvme0n1p1
sudo fsck /dev/nvme0n1p2
Ah, that's a pity - I was very hopeful. Boot into live session again, download the boot-repair utility and try the recommended repair. All digits crossed for successful outcome
Originally Posted by tea for one Ah, that's a pity - I was very hopeful. Boot into live session again, download the boot-repair utility and try the recommended repair. All digits crossed for successful outcome I did exactly that. After boot repair, tha computer experienced kernel panic. Apparently, initramfs for the default kernel was missing. Luckily an older kernel booted. I generated initramfs for the latest kernel as described in this post. Then the computer booted as usual. Thanks for the help anyway. The dirty bit could have caused further trouble down the road.
Try running fsck.vfat or dosfsck on the first partition as it is a vfat filesystem and not a Linux filesystem. fsck may detect the filesystem and run either but no harm in trying the commands. The link below is to the manual pages for this software which gives an explanation and various options. Unmount the partition before running fsck. https://man7.org/linux/man-pages/man8/fsck.vfat.8.html
Originally Posted by sdayanik I did exactly that. After boot repair, tha computer experienced kernel panic. Apparently, initramfs for the default kernel was missing. Luckily an older kernel booted. I generated initramfs for the latest kernel as described in this post. Then the computer booted as usual. Thanks for the help anyway. The dirty bit could have caused further trouble down the road. Splendid, well done. I think that the "dirty bit" would need to have been repaired before the missing initramfs was spotted. Anyway, all's well that ends well. Worth marking the thread as solved?
Any time you have a sudden power loss it is likely to damage the filesystem so if you have problems in the future in that situation and booting fails, run a filesystem check on the unmounted partition.
View Tag Cloud
Ubuntu Forums Code of Conduct