Cannot fix fsck errors after system crashing
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I have a dual partition with Windows 8.1 and Ubuntu 16.04. While updating and restarting Windows I forced to turn off my laptop by pressing the power button. After that Ubuntu presents a lot of problems, I tried to fix them by using the fsck command but that was not possible and in addition I could not work since the file system adopted a read-only configuration.
I decided then to change the configuration of the file /etc/fstab for the relevant partition, that is devsda9. I modified the keyword remount=ro to continue. After that I have been using the laptop for around 20 minutes without problems, however the errors are still present as the output of the following command reveals:
~$ fsck -n /dev/sda9
fsck from util-linux 2.27.1
e2fsck 1.42.12 (29-Aug-2014)
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda9 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 655158 was part of the orphaned inode list. IGNORED.
Deleted inode 655251 has zero dtime. Fix? no
Inode 655385 was part of the orphaned inode list. IGNORED.
Inode 655387 was part of the orphaned inode list. IGNORED.
Inode 655665 was part of the orphaned inode list. IGNORED.
Inode 922377 was part of the orphaned inode list. IGNORED.
Inode 939006 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1746438--1746450)-(17541643--17541655)
Fix? no
Inode bitmap differences: -655158 -655251 -655385 -655387 -655665 -922377 -939006
Fix? no
/dev/sda9: ********** WARNING: Filesystem still has errors **********
/dev/sda9: 1665447/27275136 files (0.4% non-contiguous), 76152874/109312000 blocks
Will there be a way to fix it?
16.04 dual-boot windows-8 fsck
asked Apr 12 at 6:58
dapias
1822311
add a comment |Â
up vote
0
down vote
favorite
I have a dual partition with Windows 8.1 and Ubuntu 16.04. While updating and restarting Windows I forced to turn off my laptop by pressing the power button. After that Ubuntu presents a lot of problems, I tried to fix them by using the fsck command but that was not possible and in addition I could not work since the file system adopted a read-only configuration.
I decided then to change the configuration of the file /etc/fstab for the relevant partition, that is devsda9. I modified the keyword remount=ro to continue. After that I have been using the laptop for around 20 minutes without problems, however the errors are still present as the output of the following command reveals:
~$ fsck -n /dev/sda9
fsck from util-linux 2.27.1
e2fsck 1.42.12 (29-Aug-2014)
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda9 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 655158 was part of the orphaned inode list. IGNORED.
Deleted inode 655251 has zero dtime. Fix? no
Inode 655385 was part of the orphaned inode list. IGNORED.
Inode 655387 was part of the orphaned inode list. IGNORED.
Inode 655665 was part of the orphaned inode list. IGNORED.
Inode 922377 was part of the orphaned inode list. IGNORED.
Inode 939006 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1746438--1746450)-(17541643--17541655)
Fix? no
Inode bitmap differences: -655158 -655251 -655385 -655387 -655665 -922377 -939006
Fix? no
/dev/sda9: ********** WARNING: Filesystem still has errors **********
/dev/sda9: 1665447/27275136 files (0.4% non-contiguous), 76152874/109312000 blocks
Will there be a way to fix it?
16.04 dual-boot windows-8 fsck
asked Apr 12 at 6:58
dapias
1822311
Let it do an fsck on the next boot by runningsudo touch /forcefsck. Then restart.
– Byte Commander
Apr 12 at 7:45
The ouput offsckpersists
– dapias
Apr 12 at 14:00
Then please try booting from an Ubuntu live USB or DVD and run the fsck from there, while your installation partition is unmounted, and without the-noption.
– Byte Commander
Apr 12 at 14:20
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a dual partition with Windows 8.1 and Ubuntu 16.04. While updating and restarting Windows I forced to turn off my laptop by pressing the power button. After that Ubuntu presents a lot of problems, I tried to fix them by using the fsck command but that was not possible and in addition I could not work since the file system adopted a read-only configuration.
I decided then to change the configuration of the file /etc/fstab for the relevant partition, that is devsda9. I modified the keyword remount=ro to continue. After that I have been using the laptop for around 20 minutes without problems, however the errors are still present as the output of the following command reveals:
~$ fsck -n /dev/sda9
fsck from util-linux 2.27.1
e2fsck 1.42.12 (29-Aug-2014)
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda9 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 655158 was part of the orphaned inode list. IGNORED.
Deleted inode 655251 has zero dtime. Fix? no
Inode 655385 was part of the orphaned inode list. IGNORED.
Inode 655387 was part of the orphaned inode list. IGNORED.
Inode 655665 was part of the orphaned inode list. IGNORED.
Inode 922377 was part of the orphaned inode list. IGNORED.
Inode 939006 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1746438--1746450)-(17541643--17541655)
Fix? no
Inode bitmap differences: -655158 -655251 -655385 -655387 -655665 -922377 -939006
Fix? no
/dev/sda9: ********** WARNING: Filesystem still has errors **********
/dev/sda9: 1665447/27275136 files (0.4% non-contiguous), 76152874/109312000 blocks
Will there be a way to fix it?
16.04 dual-boot windows-8 fsck
asked Apr 12 at 6:58
dapias
1822311
I have a dual partition with Windows 8.1 and Ubuntu 16.04. While updating and restarting Windows I forced to turn off my laptop by pressing the power button. After that Ubuntu presents a lot of problems, I tried to fix them by using the fsck command but that was not possible and in addition I could not work since the file system adopted a read-only configuration.
I decided then to change the configuration of the file /etc/fstab for the relevant partition, that is devsda9. I modified the keyword remount=ro to continue. After that I have been using the laptop for around 20 minutes without problems, however the errors are still present as the output of the following command reveals:
~$ fsck -n /dev/sda9
fsck from util-linux 2.27.1
e2fsck 1.42.12 (29-Aug-2014)
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda9 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 655158 was part of the orphaned inode list. IGNORED.
Deleted inode 655251 has zero dtime. Fix? no
Inode 655385 was part of the orphaned inode list. IGNORED.
Inode 655387 was part of the orphaned inode list. IGNORED.
Inode 655665 was part of the orphaned inode list. IGNORED.
Inode 922377 was part of the orphaned inode list. IGNORED.
Inode 939006 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1746438--1746450)-(17541643--17541655)
Fix? no
Inode bitmap differences: -655158 -655251 -655385 -655387 -655665 -922377 -939006
Fix? no
/dev/sda9: ********** WARNING: Filesystem still has errors **********
/dev/sda9: 1665447/27275136 files (0.4% non-contiguous), 76152874/109312000 blocks
Will there be a way to fix it?
16.04 dual-boot windows-8 fsck
16.04 dual-boot windows-8 fsck
asked Apr 12 at 6:58
dapias
1822311
asked Apr 12 at 6:58
dapias
1822311
asked Apr 12 at 6:58
dapias
1822311
asked Apr 12 at 6:58
dapias
1822311
asked Apr 12 at 6:58
dapias
1822311
1822311
Let it do an fsck on the next boot by runningsudo touch /forcefsck. Then restart.
– Byte Commander
Apr 12 at 7:45
The ouput offsckpersists
– dapias
Apr 12 at 14:00
Then please try booting from an Ubuntu live USB or DVD and run the fsck from there, while your installation partition is unmounted, and without the-noption.
– Byte Commander
Apr 12 at 14:20
add a comment |Â
Let it do an fsck on the next boot by runningsudo touch /forcefsck. Then restart.
– Byte Commander
Apr 12 at 7:45
The ouput offsckpersists
– dapias
Apr 12 at 14:00
Then please try booting from an Ubuntu live USB or DVD and run the fsck from there, while your installation partition is unmounted, and without the-noption.
– Byte Commander
Apr 12 at 14:20
Let it do an fsck on the next boot by running
sudo touch /forcefsck. Then restart.– Byte Commander
Apr 12 at 7:45
Let it do an fsck on the next boot by running
sudo touch /forcefsck. Then restart.– Byte Commander
Apr 12 at 7:45
The ouput of
fsck persists– dapias
Apr 12 at 14:00
The ouput of
fsck persists– dapias
Apr 12 at 14:00
Then please try booting from an Ubuntu live USB or DVD and run the fsck from there, while your installation partition is unmounted, and without the
-n option.– Byte Commander
Apr 12 at 14:20
Then please try booting from an Ubuntu live USB or DVD and run the fsck from there, while your installation partition is unmounted, and without the
-n option.– Byte Commander
Apr 12 at 14:20
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024257%2fcannot-fix-fsck-errors-after-system-crashing%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Let it do an fsck on the next boot by running
sudo touch /forcefsck. Then restart.– Byte Commander
Apr 12 at 7:45
The ouput of
fsckpersists– dapias
Apr 12 at 14:00
Then please try booting from an Ubuntu live USB or DVD and run the fsck from there, while your installation partition is unmounted, and without the
-noption.– Byte Commander
Apr 12 at 14:20