output of “fsck -n devicename” is “filesystem still has an error”
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
root@USER:~# fsck -n /dev/nandb
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
Warning! /dev/nandb is mounted.
/dev/nandb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 389 has zero dtime. Fix? no
Deleted inode 261798 has zero dtime. Fix? no
Deleted inode 262015 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(34036--34059) -(1097199--1097472)
-(1119106--1119161) -(1608640--1608649) -(1616520--1616569)
-(1644614--1644615) -(1644726--1644727) -(1644784--1644785)
-(1645185--1645186) -(1646267--1646268) -(1646403--1646412)
-(1655093--1655094) -(1655655--1655664) -(1655805--1655806)
Fix? no
Free blocks count wrong for group #49 (802, counted=809).
Fix? no
Free blocks count wrong for group #50 (20011, counted=20010).
Fix? no
Free blocks count wrong (1498568, counted=1498574).
Fix? no
Inode bitmap differences: -389 -261798 -262015 -(390789--390790) -390793
-(390795--390800) -390841 -390843 -390848 -390850 -(390852--390853)
Fix? no
/dev/nandb: ********** WARNING: Filesystem still has errors **********
/dev/nandb: 62693/486720 files (0.2% non-contiguous), 444968/1943536 blocks
I want to Know
1) why these errors occur?
2) How to Fix These errors?
Thanks,
memory fsck inode
asked Nov 29 at 5:39
niranjan pawar
94
|
show 2 more comments
up vote
-1
down vote
favorite
root@USER:~# fsck -n /dev/nandb
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
Warning! /dev/nandb is mounted.
/dev/nandb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 389 has zero dtime. Fix? no
Deleted inode 261798 has zero dtime. Fix? no
Deleted inode 262015 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(34036--34059) -(1097199--1097472)
-(1119106--1119161) -(1608640--1608649) -(1616520--1616569)
-(1644614--1644615) -(1644726--1644727) -(1644784--1644785)
-(1645185--1645186) -(1646267--1646268) -(1646403--1646412)
-(1655093--1655094) -(1655655--1655664) -(1655805--1655806)
Fix? no
Free blocks count wrong for group #49 (802, counted=809).
Fix? no
Free blocks count wrong for group #50 (20011, counted=20010).
Fix? no
Free blocks count wrong (1498568, counted=1498574).
Fix? no
Inode bitmap differences: -389 -261798 -262015 -(390789--390790) -390793
-(390795--390800) -390841 -390843 -390848 -390850 -(390852--390853)
Fix? no
/dev/nandb: ********** WARNING: Filesystem still has errors **********
/dev/nandb: 62693/486720 files (0.2% non-contiguous), 444968/1943536 blocks
I want to Know
1) why these errors occur?
2) How to Fix These errors?
Thanks,
memory fsck inode
asked Nov 29 at 5:39
niranjan pawar
94
1
Who knows why they happened could be anything from power failure to failing hardware. Unmount the file system and try to fix it ( cant fix when mounted)
– Panther
Nov 29 at 6:10
not able to unmount filesystem it's showing like the device is busy can't unmount.@Panther
– niranjan pawar
Nov 29 at 6:50
Then fix it from a live usb
– Panther
Nov 29 at 6:52
You can work through adminschoice.com/repairing-unix-file-system-fsck , click the additional sections at the bottom for additional details/ pages
– Panther
Nov 29 at 7:36
i use "umount -l busy_device_path" it works but when i unmount filesystem fsck command is not working its showing no such device mounted @Panther
– niranjan pawar
Nov 29 at 7:57
|
show 2 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
root@USER:~# fsck -n /dev/nandb
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
Warning! /dev/nandb is mounted.
/dev/nandb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 389 has zero dtime. Fix? no
Deleted inode 261798 has zero dtime. Fix? no
Deleted inode 262015 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(34036--34059) -(1097199--1097472)
-(1119106--1119161) -(1608640--1608649) -(1616520--1616569)
-(1644614--1644615) -(1644726--1644727) -(1644784--1644785)
-(1645185--1645186) -(1646267--1646268) -(1646403--1646412)
-(1655093--1655094) -(1655655--1655664) -(1655805--1655806)
Fix? no
Free blocks count wrong for group #49 (802, counted=809).
Fix? no
Free blocks count wrong for group #50 (20011, counted=20010).
Fix? no
Free blocks count wrong (1498568, counted=1498574).
Fix? no
Inode bitmap differences: -389 -261798 -262015 -(390789--390790) -390793
-(390795--390800) -390841 -390843 -390848 -390850 -(390852--390853)
Fix? no
/dev/nandb: ********** WARNING: Filesystem still has errors **********
/dev/nandb: 62693/486720 files (0.2% non-contiguous), 444968/1943536 blocks
I want to Know
1) why these errors occur?
2) How to Fix These errors?
Thanks,
memory fsck inode
asked Nov 29 at 5:39
niranjan pawar
94
root@USER:~# fsck -n /dev/nandb
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
Warning! /dev/nandb is mounted.
/dev/nandb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 389 has zero dtime. Fix? no
Deleted inode 261798 has zero dtime. Fix? no
Deleted inode 262015 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(34036--34059) -(1097199--1097472)
-(1119106--1119161) -(1608640--1608649) -(1616520--1616569)
-(1644614--1644615) -(1644726--1644727) -(1644784--1644785)
-(1645185--1645186) -(1646267--1646268) -(1646403--1646412)
-(1655093--1655094) -(1655655--1655664) -(1655805--1655806)
Fix? no
Free blocks count wrong for group #49 (802, counted=809).
Fix? no
Free blocks count wrong for group #50 (20011, counted=20010).
Fix? no
Free blocks count wrong (1498568, counted=1498574).
Fix? no
Inode bitmap differences: -389 -261798 -262015 -(390789--390790) -390793
-(390795--390800) -390841 -390843 -390848 -390850 -(390852--390853)
Fix? no
/dev/nandb: ********** WARNING: Filesystem still has errors **********
/dev/nandb: 62693/486720 files (0.2% non-contiguous), 444968/1943536 blocks
I want to Know
1) why these errors occur?
2) How to Fix These errors?
Thanks,
memory fsck inode
memory fsck inode
asked Nov 29 at 5:39
niranjan pawar
94
asked Nov 29 at 5:39
niranjan pawar
94
edited Nov 29 at 5:50
asked Nov 29 at 5:39
niranjan pawar
94
asked Nov 29 at 5:39
niranjan pawar
94
asked Nov 29 at 5:39
niranjan pawar
94
94
1
Who knows why they happened could be anything from power failure to failing hardware. Unmount the file system and try to fix it ( cant fix when mounted)
– Panther
Nov 29 at 6:10
not able to unmount filesystem it's showing like the device is busy can't unmount.@Panther
– niranjan pawar
Nov 29 at 6:50
Then fix it from a live usb
– Panther
Nov 29 at 6:52
You can work through adminschoice.com/repairing-unix-file-system-fsck , click the additional sections at the bottom for additional details/ pages
– Panther
Nov 29 at 7:36
i use "umount -l busy_device_path" it works but when i unmount filesystem fsck command is not working its showing no such device mounted @Panther
– niranjan pawar
Nov 29 at 7:57
|
show 2 more comments
1
Who knows why they happened could be anything from power failure to failing hardware. Unmount the file system and try to fix it ( cant fix when mounted)
– Panther
Nov 29 at 6:10
not able to unmount filesystem it's showing like the device is busy can't unmount.@Panther
– niranjan pawar
Nov 29 at 6:50
Then fix it from a live usb
– Panther
Nov 29 at 6:52
You can work through adminschoice.com/repairing-unix-file-system-fsck , click the additional sections at the bottom for additional details/ pages
– Panther
Nov 29 at 7:36
i use "umount -l busy_device_path" it works but when i unmount filesystem fsck command is not working its showing no such device mounted @Panther
– niranjan pawar
Nov 29 at 7:57
1
1
Who knows why they happened could be anything from power failure to failing hardware. Unmount the file system and try to fix it ( cant fix when mounted)
– Panther
Nov 29 at 6:10
Who knows why they happened could be anything from power failure to failing hardware. Unmount the file system and try to fix it ( cant fix when mounted)
– Panther
Nov 29 at 6:10
not able to unmount filesystem it's showing like the device is busy can't unmount.@Panther
– niranjan pawar
Nov 29 at 6:50
not able to unmount filesystem it's showing like the device is busy can't unmount.@Panther
– niranjan pawar
Nov 29 at 6:50
Then fix it from a live usb
– Panther
Nov 29 at 6:52
Then fix it from a live usb
– Panther
Nov 29 at 6:52
You can work through adminschoice.com/repairing-unix-file-system-fsck , click the additional sections at the bottom for additional details/ pages
– Panther
Nov 29 at 7:36
You can work through adminschoice.com/repairing-unix-file-system-fsck , click the additional sections at the bottom for additional details/ pages
– Panther
Nov 29 at 7:36
i use "umount -l busy_device_path" it works but when i unmount filesystem fsck command is not working its showing no such device mounted @Panther
– niranjan pawar
Nov 29 at 7:57
i use "umount -l busy_device_path" it works but when i unmount filesystem fsck command is not working its showing no such device mounted @Panther
– niranjan pawar
Nov 29 at 7:57
|
show 2 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484822%2foutput-of-fsck-n-devicename-is-filesystem-still-has-an-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Who knows why they happened could be anything from power failure to failing hardware. Unmount the file system and try to fix it ( cant fix when mounted)
– Panther
Nov 29 at 6:10
not able to unmount filesystem it's showing like the device is busy can't unmount.@Panther
– niranjan pawar
Nov 29 at 6:50
Then fix it from a live usb
– Panther
Nov 29 at 6:52
You can work through adminschoice.com/repairing-unix-file-system-fsck , click the additional sections at the bottom for additional details/ pages
– Panther
Nov 29 at 7:36
i use "umount -l busy_device_path" it works but when i unmount filesystem fsck command is not working its showing no such device mounted @Panther
– niranjan pawar
Nov 29 at 7:57