Hello, David & Bob. In the Message; Subject : Corrupted root Message-ID : <25788.43553.278475.807670@orion.rgrjr.com> Date & Time: Sat, 22 Jul 2023 21:18:41 -0700 [BR] == Bob Rogers <rogers@rgrjr.com> has written: BR> From: Carl Spitzer {L Juno} <lynux@juno.com> BR> Date: Sat, 22 Jul 2023 20:14:11 -0700 [...] BR> I'm with David here; I don't see how you can umount / after booting -- BR> or even remount it read-only. You also don't say much about the present BR> state of your system (rebooted? just the session crashed? something BR> else?), so it's hard to be clear on what your options are. But if you BR> have no more user sessions, then it may not matter: You may be able to BR> get a clean backup of /home from where you are now, and then just reboot BR> into a rescue system (or anything that doesn't require mounting /) so BR> you can fix /. I agree the problem with Carl's question is, as you say, that it leaves out the important question of under what circumstances. But, is it necessary to run fsck on / that Carl is trying to adopt? In the Message; Subject : Corrupted root Message-ID : <1690082052.15872.3.camel@linux-7k5b.site> Date & Time: Sat, 22 Jul 2023 20:14:11 -0700 [CS] == Carl Spitzer {L Juno} <lynux@juno.com> has written: [...] CS> The system crashed and shut off during a Firefox secession I think CS> I had too many tabs open. This is a typical phenomenon caused by lack of memory, but does this phenomenon cause system corruption? I can't figure this out..... Regards.