systemd-fsck failed with error code 8. Unable to repair disk on bootup
I have two partitions, one for the RO root filesystem (mmcblk3p1), and the other is the RW home partition (mmcblk3p2). I can't figure out why systemd-fsck is unable to fix my partition when I manually corrupt it with:
dd if=/dev/zero bs=1 count=1000 of=/dev/mmcblk3p2 seek=1000
I can repair my partition manually in under 5 seconds, so the issue must be inside of libsystemd-fsck
e2fsck /dev/mmcblk3p2 -y
My fstab is configured so that both partitions are checked upon bootup and the kernel config tells fsck to attempt a repair.
Kernel command line: console= consoleblank=0 vt.global_cursor_default=0 fsck.mode=auto fsck.repair=yes root=/dev/mmcblk3p1 rootfstype=ext4 rootwait ro
It appears that fsck is receiving an immediate error when it attempts to repair during bootup. I can see the errors inside of my journal.
journalctl | grep fsck
Jan 02 21:43:05 systemd-fsck[192]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:05 systemd-fsck[192]: /dev/mmcblk3p1: clean, 9287/192576 files, 139802/192512 blocks
Jan 02 21:43:07 systemd-fsck[673]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2: recovering journal
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2 contains a file system with errors, check forced.
Jan 02 21:43:07 systemd-fsck[673]: Pass 1: Checking inodes, blocks, and sizes
Jan 02 21:43:07 systemd-fsck[673]: fsck: Warning... fsck.ext4 for device /dev/mmcblk3p2 exited with signal 13.
Jan 02 21:43:07 systemd-fsck[673]: fsck failed with error code 8.
Jan 02 21:43:07 systemd-fsck[673]: Ignoring error.
Jan 02 21:43:07 kernel: EXT4-fs (mmcblk3p2): warning: mounting unchecked fs, running e2fsck is recommended
Signal 13 and error code 8 don't help me too much in digging into the root cause of the problem. The only other issue I could find online is this one from the Ubuntu Mailing lists, but it concerns a bug related to the systemd-fsck 30s timeout.
I'm using systemd-229 with 4.1.38 kernel which are dated, but it is what I have to work with.
systemd fsck
asked 1 hour ago
User3219
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have two partitions, one for the RO root filesystem (mmcblk3p1), and the other is the RW home partition (mmcblk3p2). I can't figure out why systemd-fsck is unable to fix my partition when I manually corrupt it with:
dd if=/dev/zero bs=1 count=1000 of=/dev/mmcblk3p2 seek=1000
I can repair my partition manually in under 5 seconds, so the issue must be inside of libsystemd-fsck
e2fsck /dev/mmcblk3p2 -y
My fstab is configured so that both partitions are checked upon bootup and the kernel config tells fsck to attempt a repair.
Kernel command line: console= consoleblank=0 vt.global_cursor_default=0 fsck.mode=auto fsck.repair=yes root=/dev/mmcblk3p1 rootfstype=ext4 rootwait ro
It appears that fsck is receiving an immediate error when it attempts to repair during bootup. I can see the errors inside of my journal.
journalctl | grep fsck
Jan 02 21:43:05 systemd-fsck[192]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:05 systemd-fsck[192]: /dev/mmcblk3p1: clean, 9287/192576 files, 139802/192512 blocks
Jan 02 21:43:07 systemd-fsck[673]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2: recovering journal
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2 contains a file system with errors, check forced.
Jan 02 21:43:07 systemd-fsck[673]: Pass 1: Checking inodes, blocks, and sizes
Jan 02 21:43:07 systemd-fsck[673]: fsck: Warning... fsck.ext4 for device /dev/mmcblk3p2 exited with signal 13.
Jan 02 21:43:07 systemd-fsck[673]: fsck failed with error code 8.
Jan 02 21:43:07 systemd-fsck[673]: Ignoring error.
Jan 02 21:43:07 kernel: EXT4-fs (mmcblk3p2): warning: mounting unchecked fs, running e2fsck is recommended
Signal 13 and error code 8 don't help me too much in digging into the root cause of the problem. The only other issue I could find online is this one from the Ubuntu Mailing lists, but it concerns a bug related to the systemd-fsck 30s timeout.
I'm using systemd-229 with 4.1.38 kernel which are dated, but it is what I have to work with.
systemd fsck
asked 1 hour ago
User3219
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have two partitions, one for the RO root filesystem (mmcblk3p1), and the other is the RW home partition (mmcblk3p2). I can't figure out why systemd-fsck is unable to fix my partition when I manually corrupt it with:
dd if=/dev/zero bs=1 count=1000 of=/dev/mmcblk3p2 seek=1000
I can repair my partition manually in under 5 seconds, so the issue must be inside of libsystemd-fsck
e2fsck /dev/mmcblk3p2 -y
My fstab is configured so that both partitions are checked upon bootup and the kernel config tells fsck to attempt a repair.
Kernel command line: console= consoleblank=0 vt.global_cursor_default=0 fsck.mode=auto fsck.repair=yes root=/dev/mmcblk3p1 rootfstype=ext4 rootwait ro
It appears that fsck is receiving an immediate error when it attempts to repair during bootup. I can see the errors inside of my journal.
journalctl | grep fsck
Jan 02 21:43:05 systemd-fsck[192]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:05 systemd-fsck[192]: /dev/mmcblk3p1: clean, 9287/192576 files, 139802/192512 blocks
Jan 02 21:43:07 systemd-fsck[673]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2: recovering journal
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2 contains a file system with errors, check forced.
Jan 02 21:43:07 systemd-fsck[673]: Pass 1: Checking inodes, blocks, and sizes
Jan 02 21:43:07 systemd-fsck[673]: fsck: Warning... fsck.ext4 for device /dev/mmcblk3p2 exited with signal 13.
Jan 02 21:43:07 systemd-fsck[673]: fsck failed with error code 8.
Jan 02 21:43:07 systemd-fsck[673]: Ignoring error.
Jan 02 21:43:07 kernel: EXT4-fs (mmcblk3p2): warning: mounting unchecked fs, running e2fsck is recommended
Signal 13 and error code 8 don't help me too much in digging into the root cause of the problem. The only other issue I could find online is this one from the Ubuntu Mailing lists, but it concerns a bug related to the systemd-fsck 30s timeout.
I'm using systemd-229 with 4.1.38 kernel which are dated, but it is what I have to work with.
systemd fsck
asked 1 hour ago
User3219
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have two partitions, one for the RO root filesystem (mmcblk3p1), and the other is the RW home partition (mmcblk3p2). I can't figure out why systemd-fsck is unable to fix my partition when I manually corrupt it with:
dd if=/dev/zero bs=1 count=1000 of=/dev/mmcblk3p2 seek=1000
I can repair my partition manually in under 5 seconds, so the issue must be inside of libsystemd-fsck
e2fsck /dev/mmcblk3p2 -y
My fstab is configured so that both partitions are checked upon bootup and the kernel config tells fsck to attempt a repair.
Kernel command line: console= consoleblank=0 vt.global_cursor_default=0 fsck.mode=auto fsck.repair=yes root=/dev/mmcblk3p1 rootfstype=ext4 rootwait ro
It appears that fsck is receiving an immediate error when it attempts to repair during bootup. I can see the errors inside of my journal.
journalctl | grep fsck
Jan 02 21:43:05 systemd-fsck[192]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:05 systemd-fsck[192]: /dev/mmcblk3p1: clean, 9287/192576 files, 139802/192512 blocks
Jan 02 21:43:07 systemd-fsck[673]: e2fsck 1.43-WIP (18-May-2015)
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2: recovering journal
Jan 02 21:43:07 systemd-fsck[673]: /dev/mmcblk3p2 contains a file system with errors, check forced.
Jan 02 21:43:07 systemd-fsck[673]: Pass 1: Checking inodes, blocks, and sizes
Jan 02 21:43:07 systemd-fsck[673]: fsck: Warning... fsck.ext4 for device /dev/mmcblk3p2 exited with signal 13.
Jan 02 21:43:07 systemd-fsck[673]: fsck failed with error code 8.
Jan 02 21:43:07 systemd-fsck[673]: Ignoring error.
Jan 02 21:43:07 kernel: EXT4-fs (mmcblk3p2): warning: mounting unchecked fs, running e2fsck is recommended
Signal 13 and error code 8 don't help me too much in digging into the root cause of the problem. The only other issue I could find online is this one from the Ubuntu Mailing lists, but it concerns a bug related to the systemd-fsck 30s timeout.
I'm using systemd-229 with 4.1.38 kernel which are dated, but it is what I have to work with.
systemd fsck
systemd fsck
asked 1 hour ago
User3219
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
User3219
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
User3219
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
User3219
1
asked 1 hour ago
User3219
1
1
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
User3219 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
User3219 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f492128%2fsystemd-fsck-failed-with-error-code-8-unable-to-repair-disk-on-bootup%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
User3219 is a new contributor. Be nice, and check out our Code of Conduct.
User3219 is a new contributor. Be nice, and check out our Code of Conduct.
User3219 is a new contributor. Be nice, and check out our Code of Conduct.
User3219 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f492128%2fsystemd-fsck-failed-with-error-code-8-unable-to-repair-disk-on-bootup%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
