Ubuntu
libnss-unknown package

version 18.04 crashes on loading

Asked by Peter Jordan

Closed perfectly working PC last night.
opened PC today, got first splash screen then blank.
then got following. (initramfs)
/dev/sda5 contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found.
/dev/sda5; UNEXPECTED INCONSISTENCY; Run fsck MANUALLY. (ie without -a or-p options)

Fsck exited with status code4

re tried command as follows:- (initramfs) /dev/sda5 fsck

returned sh:/dev/sda5: permission denied.
How do i sort this out as I cant get passed the above. The system was fine until last nights update. but gave no indication of problem prior to shut down.

 Run from 18.04 disc and all files still there so the problem is in the operating system itself.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu libnss-unknown Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
Best actionparsnip (andrew-woodhead666) said : 		#1

Boot to the installation media and (with the file system unmounted) run:

sudo fdisk -l

This lists all partitions. You can then use:

sudo fsck -a /dev/sfa5

If that is the file system name given in the liveCD to the partition with issues.

Once finished, run:

sudo reboot

Take the install media out at BIOS screen so the internal drive boots as normal

Revision history for this message
Peter Jordan (barule) said : 		#2

Andrew Thanks for the prompt response.

Before I try your instructions can you clarify a few points for me to
ensure I get it right.

     1. Not sure what you mean in point one (with the file system
unmounted) how do I achieve that? I have unmounted a hard drive before
via the disks proramme but not a file system. Or are you saying the file
system will automatically be unmounted as we are running from the cd
installation media.

2. To run  sudo fdisk -l  Do I have to be in a terminal. Might sound a
stupid thing to say but of course on my brocken machine I never got to a
terminal but still ran the command.

3. The message I got from my brocken system said run the manual file
system check without the  -a should I now ignore that see my original
question data.

regards

Peter

On 17/01/2019 08:38, actionparsnip wrote:
> Your question #677849 on libnss-unknown in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/libnss-unknown/+question/677849
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> Boot to the installation media and (with the file system unmounted) run:
>
> sudo fdisk -l
>
> This lists all partitions. You can then use:
>
> sudo fsck -a /dev/sfa5
>
> If that is the file system name given in the liveCD to the partition
> with issues.
>
> Once finished, run:
>
> sudo reboot
>
> Take the install media out at BIOS screen so the internal drive boots as
> normal
>

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

The file system unmounted is the default position.

Yes the fdisk command is to be ran in a terminal. You run this in the install media on the "Try" desktop and you can troubleshoot from there. This will repair the file system for you and the boot should work

If "-a" is an issue, just remove it from the command.

Revision history for this message
Peter Jordan (barule) said : 		#4

Thanks actionparsnip, that solved my question.