Recovery mode not working

[sparxz]

Could not reboot PC.

Tried to use [Shift] [Advanced mode]

First tried removing problem packages (dpkg)
Did not work
So tried File system check(fsck):

After prompt to "Remount".

I get -
/lib/recovery-mode/recovery-menu: line 75 /etc/default/rcS: no such file or directory
fsck from util-linux 2.31.1
/dev/sde2 is mounted.
e2fck: Cannot continue, aborting.
Finished, please press ENTER.

No suggestions are given. So any idea what I can do ?

Thanks.Image already addedImage already addedImage already addedImage already added

[claydoh]

So... what specific thing or problem are you trying to recover from?

[GreyGeek]

Could not reboot PC.

Tried to use [Shift] [Advanced mode]

First tried removing problem packages (dpkg)
Did not work
So tried File system check(fsck):

After prompt to "Remount".

I get -
/lib/recovery-mode/recovery-menu: line 75 /etc/default/rcS: no such file or directory
fsck from util-linux 2.31.1
/dev/sde2 is mounted.
e2fck: Cannot continue, aborting.
Finished, please press ENTER.

No suggestions are given. So any idea what I can do ?

Thanks.Image already addedImage already addedImage already addedImage already added

Is the "addedImage" message repeated several times the result of trying to upload an image to this forum?

As far as your primary problem, did you checksum your downloaded ISO before you burned it or made a LiveUSB? It not, then perhaps your ISO download was corrupt. If the ISO checks did you check the LiveCD or LiveUSB.

Suggestion: download a fresh copy of the ISO and do the checksum to verify it. Then checksum the install medium after you make it.

If it turns out that you did do your checksums before you made your installation medium, then use the Partition Manager and use its "SMART" test to see if the drive has run out of reserve sectors or is showing some other problem

[sparxz]

Hi
I belive "Recovery mode" is an option from a non booting system.

Recovery mode is an option from the install DVD ISO, but also from a post installed system, holding down [Shift]

I had the system installed for about a week, and it ran fine, got updates etc.
So I doubt an original ISO DVD from over a week ago, could hide a fault in a much latter fully updated sytem.

I will use a Partition magic, to see if it is just down to a file sytem fault.
If that does not work, it looks like I will have to remove/format the installed sytem
and almost start from scratch, leaving the Home directory intact.

I thought Ubuntu/Kubuntu would have passed-out Micro$oft's methods by now ?!
Now I wish I could also roll back, like TrueOS/BSD.

Thanks

PS There is kind of wierd fault that adds below into my forum posts:
Image already addedImage already addedImage already added
Image already added
Image already added

[oshunluvr]

Rollback functionality is possible and easily done, but not with an ancient file system like EXT. Do some research on BTRFS.

The error message you posted is also searchable and may have various causes including not actually being a problem, but rather a red herring.

I don't have any other suggestions because general comments aren't really helpful for remote troubleshooting. A broken package installation would not cause file system corruption so I fail to see how fsck would help if that is your primary complaint. If a package update was interrupted, the normal response is to continue the installation via "sudo dpkg -a --configure" rather than removing the partially installed packages. Often, installations include removals so you can inadvertently break your install by just randomly uninstalling packages without cause. Not really an "Ubuntu vs. Windows" thing, more of a "user vs. OS thing".

Frankly, if your install is only a week old, you'll probably spend less time re-installing (from a fully verified ISO burn) than running done what happened or what you did.