I have had this problem several times.
I have several volume groups, each with its own logical volumes. But if one (or more) of those logical volumes gets corrupted, and I try to reboot, I can't, since the booter sees a bad file system and can't continue. If I log into maintenance mode, I can't do anything useful. Typically, I would just want to disable the logical volume from being mounted, which would allow the boot to continue, and I could fix the problem once the system is up. But the system is read-only, so I can't edit fstab. (BTW, I have had a disk fail on me on boot up, so I couldn't edit fstab before shutting down :-). )
The only way I have found to get around this is to boot up in rescue mode, and comment out the offending mounts from fstab.
I realize that if the primary volume group/logical volume(s) are corrupt, then continuing would be useless. But In my case, it wasn't.
I was just wondering if there is a way to have the booter prompt me to continue or not, rather than just drop to a (somewhat) useless maintenance mode.
Okay, this is a bit of a gripe, but I have been burned by this many times, and am a little frustrated :-(.