The Root filesystem on dev/sda1 requires a manual fsck[This one needs a diffrent approach,others wont work]












-1















I know this could be a duplicate but none of the solutions in ask ubuntu is working for me. I have tried almost all the solutions in ask ubuntu and still, I get an error either on startup or after login.

I tried this one- Root file system requires manual fsck
I tried the answer by @heynnema ,but it returned no errors and on reboot,I was able to log in but after that, I tried



sudo apt-get update


But I got an error as



W: problem unlinking the file /var/cache/apt/pkgcache.bin RemoveCaches (30: read-only filesystem )
E: could not open file -open (2: No such file or directory)
E: problem opening
E: The package lists or status file could not be parsed or opened



I tried again with sudo apt full-upgrade and sudo apt-get update but I get the error as



bash /usr/bin/sudo input/output error


Also after the system sleeps when I move the mouse while it asks for the password it also says authentication error and I can't enter my password.
If I try shutdown from there or anywhere I get a long list of errors
The only way out is to force the power button.



I am using Ubuntu 18.04, which was updated just last week. I was using firefox the other day when the problems started. Now even if I keep my screen idle after successful login on startup, after a few minutes the sidebar and top bar will disappear and the buttons to log off, shutdown will also disappear only 3 circles will remain when I hover to the top right corner



Please help me out @heynnema @David Foerster @farmuel Angel , I am sharing some images here on the issues I am facing.



https://drive.google.com/drive/folders/101Jl8M2Nigobkg83jLaddGhWF3vUw68T?usp=sharing



NOTE: Please don't mark this a duplicate and keep it aside, none of the solutions are working for me










share|improve this question

























  • Possible duplicate of fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

    – Kristopher Ives
    1 hour ago











  • Welcome to Ask Ubuntu! While I understand you have looked at existing answers, they do indeed include the most information available on the subject. Consider that your disk is actually damaged and therefor running fsck once to resolve errors won't stop it from continuing to fail. The problem you get when using apt are related to cached files on disk that are corrupted and while you can run apt clean to remove these cached files, you'll likely find them corrupted again since the disk is broken.

    – Kristopher Ives
    1 hour ago











  • so does that mean I have to change or service my Harddisk???

    – Jose Ben
    54 mins ago






  • 1





    About what? If a filesystem is forced to unmount (powered off) at best it will leave a "flag" that it wasn't cleanly unmounted & should be fsck'd, at worst it will loose or corrupt some data. The syslog is usually at /var/log/syslog, and you can just run dmesg | less to see it. And see man e2fsck for it's badblocks / -c section (if your filesystem is ext2/3/4)

    – Xen2050
    44 mins ago








  • 1





    i am a newbie, can you please decribe them in steps i mean direct codes, i really cant understand what you write since i usually just copy everything others write.Sorry and please. Can you explain what to do in this line--- for it's badblocks / -c section--- And where should i type them the terminal???But i dont get much time there it goes into blank page and errors

    – Jose Ben
    40 mins ago


















-1















I know this could be a duplicate but none of the solutions in ask ubuntu is working for me. I have tried almost all the solutions in ask ubuntu and still, I get an error either on startup or after login.

I tried this one- Root file system requires manual fsck
I tried the answer by @heynnema ,but it returned no errors and on reboot,I was able to log in but after that, I tried



sudo apt-get update


But I got an error as



W: problem unlinking the file /var/cache/apt/pkgcache.bin RemoveCaches (30: read-only filesystem )
E: could not open file -open (2: No such file or directory)
E: problem opening
E: The package lists or status file could not be parsed or opened



I tried again with sudo apt full-upgrade and sudo apt-get update but I get the error as



bash /usr/bin/sudo input/output error


Also after the system sleeps when I move the mouse while it asks for the password it also says authentication error and I can't enter my password.
If I try shutdown from there or anywhere I get a long list of errors
The only way out is to force the power button.



I am using Ubuntu 18.04, which was updated just last week. I was using firefox the other day when the problems started. Now even if I keep my screen idle after successful login on startup, after a few minutes the sidebar and top bar will disappear and the buttons to log off, shutdown will also disappear only 3 circles will remain when I hover to the top right corner



Please help me out @heynnema @David Foerster @farmuel Angel , I am sharing some images here on the issues I am facing.



https://drive.google.com/drive/folders/101Jl8M2Nigobkg83jLaddGhWF3vUw68T?usp=sharing



NOTE: Please don't mark this a duplicate and keep it aside, none of the solutions are working for me










share|improve this question

























  • Possible duplicate of fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

    – Kristopher Ives
    1 hour ago











  • Welcome to Ask Ubuntu! While I understand you have looked at existing answers, they do indeed include the most information available on the subject. Consider that your disk is actually damaged and therefor running fsck once to resolve errors won't stop it from continuing to fail. The problem you get when using apt are related to cached files on disk that are corrupted and while you can run apt clean to remove these cached files, you'll likely find them corrupted again since the disk is broken.

    – Kristopher Ives
    1 hour ago











  • so does that mean I have to change or service my Harddisk???

    – Jose Ben
    54 mins ago






  • 1





    About what? If a filesystem is forced to unmount (powered off) at best it will leave a "flag" that it wasn't cleanly unmounted & should be fsck'd, at worst it will loose or corrupt some data. The syslog is usually at /var/log/syslog, and you can just run dmesg | less to see it. And see man e2fsck for it's badblocks / -c section (if your filesystem is ext2/3/4)

    – Xen2050
    44 mins ago








  • 1





    i am a newbie, can you please decribe them in steps i mean direct codes, i really cant understand what you write since i usually just copy everything others write.Sorry and please. Can you explain what to do in this line--- for it's badblocks / -c section--- And where should i type them the terminal???But i dont get much time there it goes into blank page and errors

    – Jose Ben
    40 mins ago
















-1












-1








-1








I know this could be a duplicate but none of the solutions in ask ubuntu is working for me. I have tried almost all the solutions in ask ubuntu and still, I get an error either on startup or after login.

I tried this one- Root file system requires manual fsck
I tried the answer by @heynnema ,but it returned no errors and on reboot,I was able to log in but after that, I tried



sudo apt-get update


But I got an error as



W: problem unlinking the file /var/cache/apt/pkgcache.bin RemoveCaches (30: read-only filesystem )
E: could not open file -open (2: No such file or directory)
E: problem opening
E: The package lists or status file could not be parsed or opened



I tried again with sudo apt full-upgrade and sudo apt-get update but I get the error as



bash /usr/bin/sudo input/output error


Also after the system sleeps when I move the mouse while it asks for the password it also says authentication error and I can't enter my password.
If I try shutdown from there or anywhere I get a long list of errors
The only way out is to force the power button.



I am using Ubuntu 18.04, which was updated just last week. I was using firefox the other day when the problems started. Now even if I keep my screen idle after successful login on startup, after a few minutes the sidebar and top bar will disappear and the buttons to log off, shutdown will also disappear only 3 circles will remain when I hover to the top right corner



Please help me out @heynnema @David Foerster @farmuel Angel , I am sharing some images here on the issues I am facing.



https://drive.google.com/drive/folders/101Jl8M2Nigobkg83jLaddGhWF3vUw68T?usp=sharing



NOTE: Please don't mark this a duplicate and keep it aside, none of the solutions are working for me










share|improve this question
















I know this could be a duplicate but none of the solutions in ask ubuntu is working for me. I have tried almost all the solutions in ask ubuntu and still, I get an error either on startup or after login.

I tried this one- Root file system requires manual fsck
I tried the answer by @heynnema ,but it returned no errors and on reboot,I was able to log in but after that, I tried



sudo apt-get update


But I got an error as



W: problem unlinking the file /var/cache/apt/pkgcache.bin RemoveCaches (30: read-only filesystem )
E: could not open file -open (2: No such file or directory)
E: problem opening
E: The package lists or status file could not be parsed or opened



I tried again with sudo apt full-upgrade and sudo apt-get update but I get the error as



bash /usr/bin/sudo input/output error


Also after the system sleeps when I move the mouse while it asks for the password it also says authentication error and I can't enter my password.
If I try shutdown from there or anywhere I get a long list of errors
The only way out is to force the power button.



I am using Ubuntu 18.04, which was updated just last week. I was using firefox the other day when the problems started. Now even if I keep my screen idle after successful login on startup, after a few minutes the sidebar and top bar will disappear and the buttons to log off, shutdown will also disappear only 3 circles will remain when I hover to the top right corner



Please help me out @heynnema @David Foerster @farmuel Angel , I am sharing some images here on the issues I am facing.



https://drive.google.com/drive/folders/101Jl8M2Nigobkg83jLaddGhWF3vUw68T?usp=sharing



NOTE: Please don't mark this a duplicate and keep it aside, none of the solutions are working for me







boot apt updates filesystem fsck






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 30 mins ago







Jose Ben

















asked 3 hours ago









Jose BenJose Ben

12




12













  • Possible duplicate of fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

    – Kristopher Ives
    1 hour ago











  • Welcome to Ask Ubuntu! While I understand you have looked at existing answers, they do indeed include the most information available on the subject. Consider that your disk is actually damaged and therefor running fsck once to resolve errors won't stop it from continuing to fail. The problem you get when using apt are related to cached files on disk that are corrupted and while you can run apt clean to remove these cached files, you'll likely find them corrupted again since the disk is broken.

    – Kristopher Ives
    1 hour ago











  • so does that mean I have to change or service my Harddisk???

    – Jose Ben
    54 mins ago






  • 1





    About what? If a filesystem is forced to unmount (powered off) at best it will leave a "flag" that it wasn't cleanly unmounted & should be fsck'd, at worst it will loose or corrupt some data. The syslog is usually at /var/log/syslog, and you can just run dmesg | less to see it. And see man e2fsck for it's badblocks / -c section (if your filesystem is ext2/3/4)

    – Xen2050
    44 mins ago








  • 1





    i am a newbie, can you please decribe them in steps i mean direct codes, i really cant understand what you write since i usually just copy everything others write.Sorry and please. Can you explain what to do in this line--- for it's badblocks / -c section--- And where should i type them the terminal???But i dont get much time there it goes into blank page and errors

    – Jose Ben
    40 mins ago





















  • Possible duplicate of fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

    – Kristopher Ives
    1 hour ago











  • Welcome to Ask Ubuntu! While I understand you have looked at existing answers, they do indeed include the most information available on the subject. Consider that your disk is actually damaged and therefor running fsck once to resolve errors won't stop it from continuing to fail. The problem you get when using apt are related to cached files on disk that are corrupted and while you can run apt clean to remove these cached files, you'll likely find them corrupted again since the disk is broken.

    – Kristopher Ives
    1 hour ago











  • so does that mean I have to change or service my Harddisk???

    – Jose Ben
    54 mins ago






  • 1





    About what? If a filesystem is forced to unmount (powered off) at best it will leave a "flag" that it wasn't cleanly unmounted & should be fsck'd, at worst it will loose or corrupt some data. The syslog is usually at /var/log/syslog, and you can just run dmesg | less to see it. And see man e2fsck for it's badblocks / -c section (if your filesystem is ext2/3/4)

    – Xen2050
    44 mins ago








  • 1





    i am a newbie, can you please decribe them in steps i mean direct codes, i really cant understand what you write since i usually just copy everything others write.Sorry and please. Can you explain what to do in this line--- for it's badblocks / -c section--- And where should i type them the terminal???But i dont get much time there it goes into blank page and errors

    – Jose Ben
    40 mins ago



















Possible duplicate of fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

– Kristopher Ives
1 hour ago





Possible duplicate of fsck error on boot: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

– Kristopher Ives
1 hour ago













Welcome to Ask Ubuntu! While I understand you have looked at existing answers, they do indeed include the most information available on the subject. Consider that your disk is actually damaged and therefor running fsck once to resolve errors won't stop it from continuing to fail. The problem you get when using apt are related to cached files on disk that are corrupted and while you can run apt clean to remove these cached files, you'll likely find them corrupted again since the disk is broken.

– Kristopher Ives
1 hour ago





Welcome to Ask Ubuntu! While I understand you have looked at existing answers, they do indeed include the most information available on the subject. Consider that your disk is actually damaged and therefor running fsck once to resolve errors won't stop it from continuing to fail. The problem you get when using apt are related to cached files on disk that are corrupted and while you can run apt clean to remove these cached files, you'll likely find them corrupted again since the disk is broken.

– Kristopher Ives
1 hour ago













so does that mean I have to change or service my Harddisk???

– Jose Ben
54 mins ago





so does that mean I have to change or service my Harddisk???

– Jose Ben
54 mins ago




1




1





About what? If a filesystem is forced to unmount (powered off) at best it will leave a "flag" that it wasn't cleanly unmounted & should be fsck'd, at worst it will loose or corrupt some data. The syslog is usually at /var/log/syslog, and you can just run dmesg | less to see it. And see man e2fsck for it's badblocks / -c section (if your filesystem is ext2/3/4)

– Xen2050
44 mins ago







About what? If a filesystem is forced to unmount (powered off) at best it will leave a "flag" that it wasn't cleanly unmounted & should be fsck'd, at worst it will loose or corrupt some data. The syslog is usually at /var/log/syslog, and you can just run dmesg | less to see it. And see man e2fsck for it's badblocks / -c section (if your filesystem is ext2/3/4)

– Xen2050
44 mins ago






1




1





i am a newbie, can you please decribe them in steps i mean direct codes, i really cant understand what you write since i usually just copy everything others write.Sorry and please. Can you explain what to do in this line--- for it's badblocks / -c section--- And where should i type them the terminal???But i dont get much time there it goes into blank page and errors

– Jose Ben
40 mins ago







i am a newbie, can you please decribe them in steps i mean direct codes, i really cant understand what you write since i usually just copy everything others write.Sorry and please. Can you explain what to do in this line--- for it's badblocks / -c section--- And where should i type them the terminal???But i dont get much time there it goes into blank page and errors

– Jose Ben
40 mins ago












0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113705%2fthe-root-filesystem-on-dev-sda1-requires-a-manual-fsckthis-one-needs-a-diffrent%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113705%2fthe-root-filesystem-on-dev-sda1-requires-a-manual-fsckthis-one-needs-a-diffrent%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

GameSpot

connect to host localhost port 22: Connection refused

Getting a Wifi WPA2 wifi connection