Unexpected inconsistancy run fsck manually - at every boot. Ubuntu 16.04

[Calum_Mackenzie]

I have encountered a problem with the file system on my machine;
"Unexpected inconsistancy run fsck manually" This message appears every time I boot-up my machine.

I believe that this may possibly be a known bug in 16.04? and is caused by a problem with the clock/Date being wrong / going wrong?

I have managed to get my machine through "grub" to the Shell Command feature and Opened the "root Drop to root shell prompt" I then took the option "Press Enter for maintenance " & have entered my password in preparation for the next step..................But what is the next step?

I would be very grateful if anyone can advise on how to proceed with the recovery process?
n.b I have ubuntu 16.04 on a usb stick as an "iso file" should it be required as part of the recovery process.

[QDR06VV9]

Once you're dropped to the shell (i.e. "(Repair Filesystem) 1#"), type in

fsck /dev/sda2

assuming your root partition is on sda2. Reboot after that and tell me what happens.

[Bashing-om]

Calum_Mackenzie; runrickus

16.04 == systemd

You can also force fsck at boot time by passing fsck.mode=force, as a kernel parameter. This will check every filesystem you have on the machine.

my bit to try and help

[Calum_Mackenzie]

Hi Bashing-om,

Can you please expand & explain the procedure which you mention.

[Bashing-om]

Calum_Mackenzie; Sure !

Boot the install to the grub boot menu -> with an ubuntu kernel selected to boot -> press the 'e' key for edit mode;
Boot parameters screen, here arrow down to the line starting with linux and containing the terms "quiet splash" ;
Insert the term " fsck.mode=force " inplace of quiet splash such that now you also see the boot messages;
key combo ctl+x to continue the boot process .

All there is to it, the system will run the file system checks - and will attempt simple fixes - prior to mounting the devices. If there is a continued problem, fsck will so advise.

ain't nothing but a thing

[Calum_Mackenzie]

Hi Bashing-om,

I have done as suggested & recieved a long list of code!
To save time I have taken a picture of the screen which shows all the code responses & attaching it, so the response can be seen.

"Boot the install to the grub boot menu -> with an ubuntu kernel selected to boot -> press the 'e' key for edit mode;Boot parameters screen, here arrow down to the line starting with linux and containing the terms "quiet splash" ;
Insert the term " fsck.mode=force " inplace of quiet splash such that now you also see the boot messages;
key combo ctl+x to continue the boot process .


All there is to it, the system will run the file system checks - and will attempt simple fixes - prior to mounting the devices. If there is a continued problem, fsck will so advise."


1467916473808.jpg

[Bashing-om]

Calum_Mackenzie; Yuk ;

Not enough there to tell what is going on.
What happens now when re-booting ?

maybe, not so yes

[Calum_Mackenzie]

Response to fsck /dev/sdal

fsck from until - Linux 2.27.1
fsck 1.42.13 (17 May-2015)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdal
Could this be a zero-length partition?

[mcduck]

The last character in the partitions name is always a number. Looks like you have lower case L there, while it probably should be number 1 instead...

[Calum_Mackenzie]

UPDATE: now I have had time to copy & write the code from the screen - it is as below.

[   0.943178]   [<c102c862>]  timer_interrupt+0×12/0×20
[   0.943244]   [<c10c9f66>]   handle_irq_event_percpu+0×86/0×1c0
[   0.943309]   [<c10ca0cf>]   handle_edge_irq+0×6d/0×120
[   0.943435]   [<c10ccfe0>]   handle_level_irq+0xe0/0xe0xe0
[   0.943500]   <IRQ>     [<c17aacdc>]  _do_softirq+0×5f/0×260
[   0.934674]   [<c17aa173>]   common_interrupt+0×33/0×38
[   0.934744]   [<c10748a0>]   ? _do_softirq+0×5f/0×260
[   0.934806]   [<c10748a0>]   ? cpu_callback+0×1d0/0×1d0
[   0.934868]   [<c102c2f8>]    do_softring_own_stack+0×28/0×38
[   0.934932]   <IRQ>     [<c1074c75>]   irq_exit+0×a5/0×b0
[   0.944049]   [<c17aad98>]   smp_apic _ timer_interupt +0×34/0×3c
[   0.944110]   [<c17aa478>]   apic _ timer_interupt + 0×34/0×3c
[   0.944176]   [<c116f9ad>]    ?  panic+0×16e/0×1af
[   0.944241]   [<c1b79061>]   mount_block_root+0×199/0×20
[   0.944303]   [<c1b79210>]   mount_root+0×63/0×68
[   0.944371]   [<c1b7935a>]   prepare_namespace+0×145/0×176
[   0.944439]   [<c1b78d8a>]   kernel_init_+freeable+0×1b1/0×1d0
[   0.944513]   [<c179fcf0>]     kernel_init+0×10/0xe0
[   0.944580]   [<c1099431>]   ?  schedule_tail+0×11/0×50
[   0.944650]   [<c17a9949>]   ret_from_kernel_thread+0×21/0×38
[   0.944718]   [<c179fce0>]    ?  rest_init+0×70/0×70
[   0.944783] ---[  end trace b3d2df61bb937d79 ]---