fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
I dual boot Ubuntu and Windows 7.
I was browsing on FireFox in Ubuntu and all of a sudden I get some error message, so I rebooted.
Now when I try to boot into Ubuntu I get this message:
fsck from util-linux 2.26.2
/dev/sda6 contains a file system with errors, check forced.
/dev/sda6: Inodes that were part of a corrupted orphan linked list found.
/dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda6 requires a manual fsck
Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
How can I fix this?
boot filesystem fsck
edited May 26 '17 at 7:06
Zanna
50.9k13136241
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
add a comment |
I dual boot Ubuntu and Windows 7.
I was browsing on FireFox in Ubuntu and all of a sudden I get some error message, so I rebooted.
Now when I try to boot into Ubuntu I get this message:
fsck from util-linux 2.26.2
/dev/sda6 contains a file system with errors, check forced.
/dev/sda6: Inodes that were part of a corrupted orphan linked list found.
/dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda6 requires a manual fsck
Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
How can I fix this?
boot filesystem fsck
edited May 26 '17 at 7:06
Zanna
50.9k13136241
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
1
Have you been able to find out the root cause? I experienced exactly the same issue two times within two days using Kubuntu 16.04. Is this some software problem or an indication for defective hardware?
– Silicomancer
Aug 14 '16 at 10:19
1
@Silicomancer, I had this, and other related issues, and it seems quite likely to be related to a failing hard drive. I know my hard drive failed some of the S.M.A.R.T diagnostics right around when this problem occurred. Sometimes a manual 'fsck /dev/sdaX' would fix it, but other times the problem wouldn't be resolved and I'd get a kernel panic on the next boot. I've got a new HD in the mail.
– gammapoint
Apr 14 '17 at 21:05
add a comment |
I dual boot Ubuntu and Windows 7.
I was browsing on FireFox in Ubuntu and all of a sudden I get some error message, so I rebooted.
Now when I try to boot into Ubuntu I get this message:
fsck from util-linux 2.26.2
/dev/sda6 contains a file system with errors, check forced.
/dev/sda6: Inodes that were part of a corrupted orphan linked list found.
/dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda6 requires a manual fsck
Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
How can I fix this?
boot filesystem fsck
edited May 26 '17 at 7:06
Zanna
50.9k13136241
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
I dual boot Ubuntu and Windows 7.
I was browsing on FireFox in Ubuntu and all of a sudden I get some error message, so I rebooted.
Now when I try to boot into Ubuntu I get this message:
fsck from util-linux 2.26.2
/dev/sda6 contains a file system with errors, check forced.
/dev/sda6: Inodes that were part of a corrupted orphan linked list found.
/dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda6 requires a manual fsck
Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
How can I fix this?
boot filesystem fsck
boot filesystem fsck
edited May 26 '17 at 7:06
Zanna
50.9k13136241
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
edited May 26 '17 at 7:06
Zanna
50.9k13136241
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
edited May 26 '17 at 7:06
Zanna
50.9k13136241
edited May 26 '17 at 7:06
Zanna
50.9k13136241
edited May 26 '17 at 7:06
Zanna
50.9k13136241
50.9k13136241
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
asked Nov 12 '15 at 13:53
JordyJordy
1,036284
1,036284
1
Have you been able to find out the root cause? I experienced exactly the same issue two times within two days using Kubuntu 16.04. Is this some software problem or an indication for defective hardware?
– Silicomancer
Aug 14 '16 at 10:19
1
@Silicomancer, I had this, and other related issues, and it seems quite likely to be related to a failing hard drive. I know my hard drive failed some of the S.M.A.R.T diagnostics right around when this problem occurred. Sometimes a manual 'fsck /dev/sdaX' would fix it, but other times the problem wouldn't be resolved and I'd get a kernel panic on the next boot. I've got a new HD in the mail.
– gammapoint
Apr 14 '17 at 21:05
add a comment |
1
Have you been able to find out the root cause? I experienced exactly the same issue two times within two days using Kubuntu 16.04. Is this some software problem or an indication for defective hardware?
– Silicomancer
Aug 14 '16 at 10:19
1
@Silicomancer, I had this, and other related issues, and it seems quite likely to be related to a failing hard drive. I know my hard drive failed some of the S.M.A.R.T diagnostics right around when this problem occurred. Sometimes a manual 'fsck /dev/sdaX' would fix it, but other times the problem wouldn't be resolved and I'd get a kernel panic on the next boot. I've got a new HD in the mail.
– gammapoint
Apr 14 '17 at 21:05
1
1
Have you been able to find out the root cause? I experienced exactly the same issue two times within two days using Kubuntu 16.04. Is this some software problem or an indication for defective hardware?
– Silicomancer
Aug 14 '16 at 10:19
Have you been able to find out the root cause? I experienced exactly the same issue two times within two days using Kubuntu 16.04. Is this some software problem or an indication for defective hardware?
– Silicomancer
Aug 14 '16 at 10:19
1
1
@Silicomancer, I had this, and other related issues, and it seems quite likely to be related to a failing hard drive. I know my hard drive failed some of the S.M.A.R.T diagnostics right around when this problem occurred. Sometimes a manual 'fsck /dev/sdaX' would fix it, but other times the problem wouldn't be resolved and I'd get a kernel panic on the next boot. I've got a new HD in the mail.
– gammapoint
Apr 14 '17 at 21:05
@Silicomancer, I had this, and other related issues, and it seems quite likely to be related to a failing hard drive. I know my hard drive failed some of the S.M.A.R.T diagnostics right around when this problem occurred. Sometimes a manual 'fsck /dev/sdaX' would fix it, but other times the problem wouldn't be resolved and I'd get a kernel panic on the next boot. I've got a new HD in the mail.
– gammapoint
Apr 14 '17 at 21:05
add a comment |
3 Answers
3
active
oldest
votes
Try this:
fsck /dev/sda6
(where /dev/sda6 is the partition mentioned)
And enter Yes (y) to for each error. Or press a one time for always-yes.
Then reboot and it should be fine.
edited Jan 16 at 18:10
Zanna
50.9k13136241
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
7
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
3
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, runfsck -a /dev/sda6and repair the errors.
– Nikolay Nikolov
Nov 12 '15 at 14:21
10
do not forget to add-yat the end, or else glue your finger pressed to y
– aditya
May 21 '17 at 12:00
3
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
2
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
|
show 12 more comments
I have noticed that even if you do a fsck on the disk the problem may occur again in a few days.
I have found that the problem is worse on SSD disks than the regular HDD disks. I have found some steps that may fix the problem temporarily.
fsck -fy /dev/sda1
if sda1 is the right partition - the prompt will tell you exactly which one requires fsck.
After that if the systems boots up you may have another problem with the package management system, so if you open a terminal and type sudo apt-get update you may get an error. Do not worry. Run these commands:
sudo apt-get update
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade
My opinion is that there is serious problem in Ubuntu with regard to SSD disks. The community should fix it.
I have found a possible cause of this problem: Probably the system did not shutdown normally.
edited May 26 '17 at 7:11
Zanna
50.9k13136241
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
4
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
add a comment |
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY means there is some file system error in the disk. Run the fsck command manually. After that it will ask some more questions - just answer y and press enter and finally reboot the server.
answered Dec 8 '16 at 14:13
GNKGNK
9161713
add a comment |
protected by Community♦ Apr 13 '16 at 9:40
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try this:
fsck /dev/sda6
(where /dev/sda6 is the partition mentioned)
And enter Yes (y) to for each error. Or press a one time for always-yes.
Then reboot and it should be fine.
edited Jan 16 at 18:10
Zanna
50.9k13136241
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
7
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
3
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, runfsck -a /dev/sda6and repair the errors.
– Nikolay Nikolov
Nov 12 '15 at 14:21
10
do not forget to add-yat the end, or else glue your finger pressed to y
– aditya
May 21 '17 at 12:00
3
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
2
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
|
show 12 more comments
Try this:
fsck /dev/sda6
(where /dev/sda6 is the partition mentioned)
And enter Yes (y) to for each error. Or press a one time for always-yes.
Then reboot and it should be fine.
edited Jan 16 at 18:10
Zanna
50.9k13136241
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
7
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
3
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, runfsck -a /dev/sda6and repair the errors.
– Nikolay Nikolov
Nov 12 '15 at 14:21
10
do not forget to add-yat the end, or else glue your finger pressed to y
– aditya
May 21 '17 at 12:00
3
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
2
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
|
show 12 more comments
Try this:
fsck /dev/sda6
(where /dev/sda6 is the partition mentioned)
And enter Yes (y) to for each error. Or press a one time for always-yes.
Then reboot and it should be fine.
edited Jan 16 at 18:10
Zanna
50.9k13136241
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
Try this:
fsck /dev/sda6
(where /dev/sda6 is the partition mentioned)
And enter Yes (y) to for each error. Or press a one time for always-yes.
Then reboot and it should be fine.
edited Jan 16 at 18:10
Zanna
50.9k13136241
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
edited Jan 16 at 18:10
Zanna
50.9k13136241
edited Jan 16 at 18:10
Zanna
50.9k13136241
edited Jan 16 at 18:10
Zanna
50.9k13136241
50.9k13136241
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
answered Nov 12 '15 at 14:01
Nikolay NikolovNikolay Nikolov
2,9811613
2,9811613
7
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
3
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, runfsck -a /dev/sda6and repair the errors.
– Nikolay Nikolov
Nov 12 '15 at 14:21
10
do not forget to add-yat the end, or else glue your finger pressed to y
– aditya
May 21 '17 at 12:00
3
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
2
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
|
show 12 more comments
7
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
3
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, runfsck -a /dev/sda6and repair the errors.
– Nikolay Nikolov
Nov 12 '15 at 14:21
10
do not forget to add-yat the end, or else glue your finger pressed to y
– aditya
May 21 '17 at 12:00
3
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
2
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
7
7
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
Ok, so run fsck -a /dev/sda6 and enter Yes to all errors.
– Nikolay Nikolov
Nov 12 '15 at 14:13
3
3
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, run
fsck -a /dev/sda6 and repair the errors.– Nikolay Nikolov
Nov 12 '15 at 14:21
Reboot linux, and if all looks good from the booting, then you should go to the apt-get again. If puts you again to busybox terminal, run
fsck -a /dev/sda6 and repair the errors.– Nikolay Nikolov
Nov 12 '15 at 14:21
10
10
do not forget to add
-y at the end, or else glue your finger pressed to y– aditya
May 21 '17 at 12:00
do not forget to add
-y at the end, or else glue your finger pressed to y– aditya
May 21 '17 at 12:00
3
3
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
@aditya: You could also press 'a' for always instead of 'y' without using -y
– Arigion
Aug 12 '17 at 10:17
2
2
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
@Rishabh Agrahari, I think maybe the disk. You should test it with smartd tools.
– Nikolay Nikolov
Sep 11 '18 at 6:31
|
show 12 more comments
I have noticed that even if you do a fsck on the disk the problem may occur again in a few days.
I have found that the problem is worse on SSD disks than the regular HDD disks. I have found some steps that may fix the problem temporarily.
fsck -fy /dev/sda1
if sda1 is the right partition - the prompt will tell you exactly which one requires fsck.
After that if the systems boots up you may have another problem with the package management system, so if you open a terminal and type sudo apt-get update you may get an error. Do not worry. Run these commands:
sudo apt-get update
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade
My opinion is that there is serious problem in Ubuntu with regard to SSD disks. The community should fix it.
I have found a possible cause of this problem: Probably the system did not shutdown normally.
edited May 26 '17 at 7:11
Zanna
50.9k13136241
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
4
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
add a comment |
I have noticed that even if you do a fsck on the disk the problem may occur again in a few days.
I have found that the problem is worse on SSD disks than the regular HDD disks. I have found some steps that may fix the problem temporarily.
fsck -fy /dev/sda1
if sda1 is the right partition - the prompt will tell you exactly which one requires fsck.
After that if the systems boots up you may have another problem with the package management system, so if you open a terminal and type sudo apt-get update you may get an error. Do not worry. Run these commands:
sudo apt-get update
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade
My opinion is that there is serious problem in Ubuntu with regard to SSD disks. The community should fix it.
I have found a possible cause of this problem: Probably the system did not shutdown normally.
edited May 26 '17 at 7:11
Zanna
50.9k13136241
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
4
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
add a comment |
I have noticed that even if you do a fsck on the disk the problem may occur again in a few days.
I have found that the problem is worse on SSD disks than the regular HDD disks. I have found some steps that may fix the problem temporarily.
fsck -fy /dev/sda1
if sda1 is the right partition - the prompt will tell you exactly which one requires fsck.
After that if the systems boots up you may have another problem with the package management system, so if you open a terminal and type sudo apt-get update you may get an error. Do not worry. Run these commands:
sudo apt-get update
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade
My opinion is that there is serious problem in Ubuntu with regard to SSD disks. The community should fix it.
I have found a possible cause of this problem: Probably the system did not shutdown normally.
edited May 26 '17 at 7:11
Zanna
50.9k13136241
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
I have noticed that even if you do a fsck on the disk the problem may occur again in a few days.
I have found that the problem is worse on SSD disks than the regular HDD disks. I have found some steps that may fix the problem temporarily.
fsck -fy /dev/sda1
if sda1 is the right partition - the prompt will tell you exactly which one requires fsck.
After that if the systems boots up you may have another problem with the package management system, so if you open a terminal and type sudo apt-get update you may get an error. Do not worry. Run these commands:
sudo apt-get update
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade
My opinion is that there is serious problem in Ubuntu with regard to SSD disks. The community should fix it.
I have found a possible cause of this problem: Probably the system did not shutdown normally.
edited May 26 '17 at 7:11
Zanna
50.9k13136241
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
edited May 26 '17 at 7:11
Zanna
50.9k13136241
edited May 26 '17 at 7:11
Zanna
50.9k13136241
edited May 26 '17 at 7:11
Zanna
50.9k13136241
50.9k13136241
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
answered Sep 8 '16 at 9:44
farmuel Angelfarmuel Angel
67144
67144
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
4
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
add a comment |
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
4
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
After the fsck command type he command exit to force the system to boot again in runlevel 5 or just reboot with init 6.! Your choice.!
– farmuel Angel
Sep 8 '16 at 9:47
4
4
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
Please edit your own posts if you want to add or clarify something.
– David Foerster
Sep 8 '16 at 10:28
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
I was facing such problem for at least ~10 times for now and actually now I recall that before that I was always installing something. But not every installation followed by such problem.
– Slav
Aug 7 '17 at 16:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
That's what happened to me: no normal shutdown on an SSD. Worked beautifully. Thank you!
– linhares
Oct 18 '17 at 20:33
add a comment |
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY means there is some file system error in the disk. Run the fsck command manually. After that it will ask some more questions - just answer y and press enter and finally reboot the server.
answered Dec 8 '16 at 14:13
GNKGNK
9161713
add a comment |
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY means there is some file system error in the disk. Run the fsck command manually. After that it will ask some more questions - just answer y and press enter and finally reboot the server.
answered Dec 8 '16 at 14:13
GNKGNK
9161713
add a comment |
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY means there is some file system error in the disk. Run the fsck command manually. After that it will ask some more questions - just answer y and press enter and finally reboot the server.
answered Dec 8 '16 at 14:13
GNKGNK
9161713
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY means there is some file system error in the disk. Run the fsck command manually. After that it will ask some more questions - just answer y and press enter and finally reboot the server.
answered Dec 8 '16 at 14:13
GNKGNK
9161713
edited Feb 4 at 18:45
answered Dec 8 '16 at 14:13
GNKGNK
9161713
answered Dec 8 '16 at 14:13
GNKGNK
9161713
answered Dec 8 '16 at 14:13
GNKGNK
9161713
9161713
add a comment |
add a comment |
protected by Community♦ Apr 13 '16 at 9:40
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
Have you been able to find out the root cause? I experienced exactly the same issue two times within two days using Kubuntu 16.04. Is this some software problem or an indication for defective hardware?
– Silicomancer
Aug 14 '16 at 10:19
1
@Silicomancer, I had this, and other related issues, and it seems quite likely to be related to a failing hard drive. I know my hard drive failed some of the S.M.A.R.T diagnostics right around when this problem occurred. Sometimes a manual 'fsck /dev/sdaX' would fix it, but other times the problem wouldn't be resolved and I'd get a kernel panic on the next boot. I've got a new HD in the mail.
– gammapoint
Apr 14 '17 at 21:05