Score:0

Debugging root partition not unmounted on reboot in Ubuntu 20.04

sz flag

I have a problem where every time I reboot my Ubuntu 20.04, if I do a fsck on my root partition (from a Live Boot USB), I will get

Recovering journal [...] clearing orphaned inode [...]

This indicates my root partition was not unmounted successfully on reboot.

Is there a way to debug this process somehow, or maybe hook into it and try to unmount my partitions manually to see where/why it fails? Or does anyone know what component of Ubuntu handles unmounting of filesystems on reboot?

Later edit 1:

The message displayed on reboot is:

Failed to remount '/' as read-only: Device or resource busy

Later edit 2:

Is there a way to interrupt the reboot and get a command prompt inside the "ramfs root filesystem" used during reboot so I can debug things there? Like see what processes are in memory, inspect file handles etc.

Thanks

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.