Formatting a external HDD and the computer turn off
I was running the command "sudo fsck -cfvr / dev / sdc1" on an external hard drive, when I return to the computer, it was off. I do not know if the task was finished or not.
How can I know if before the computer was turned off the task would have finished or not?
external-hdd format fsck
asked 9 hours ago
MiguelMiguel
61
New contributor
Miguel 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 was running the command "sudo fsck -cfvr / dev / sdc1" on an external hard drive, when I return to the computer, it was off. I do not know if the task was finished or not.
How can I know if before the computer was turned off the task would have finished or not?
external-hdd format fsck
asked 9 hours ago
MiguelMiguel
61
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I don't think that the command worked as you expected. The command you used tried to check the root file system and should have aborted because the root file system is mounted. You should have usedsudo fsck -cfvr /dev/sdc1instead ofsudo fsck -cfvr / dev / sdc1.
– mook765
8 hours ago
Yes, the command was working correctly, the file system was not mounted at the time of running the command. I already had a percentage greater than 50% the last time I checked it. but then it suddenly went out and I do not know if 100% of the process would end
– Miguel
8 hours ago
Please see my answer. Please remember to accept it if it was helpful. Thanks!
– heynnema
8 hours ago
add a comment |
I was running the command "sudo fsck -cfvr / dev / sdc1" on an external hard drive, when I return to the computer, it was off. I do not know if the task was finished or not.
How can I know if before the computer was turned off the task would have finished or not?
external-hdd format fsck
asked 9 hours ago
MiguelMiguel
61
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I was running the command "sudo fsck -cfvr / dev / sdc1" on an external hard drive, when I return to the computer, it was off. I do not know if the task was finished or not.
How can I know if before the computer was turned off the task would have finished or not?
external-hdd format fsck
external-hdd format fsck
asked 9 hours ago
MiguelMiguel
61
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 9 hours ago
MiguelMiguel
61
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 9 hours ago
MiguelMiguel
61
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 9 hours ago
MiguelMiguel
61
asked 9 hours ago
MiguelMiguel
61
61
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Miguel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I don't think that the command worked as you expected. The command you used tried to check the root file system and should have aborted because the root file system is mounted. You should have usedsudo fsck -cfvr /dev/sdc1instead ofsudo fsck -cfvr / dev / sdc1.
– mook765
8 hours ago
Yes, the command was working correctly, the file system was not mounted at the time of running the command. I already had a percentage greater than 50% the last time I checked it. but then it suddenly went out and I do not know if 100% of the process would end
– Miguel
8 hours ago
Please see my answer. Please remember to accept it if it was helpful. Thanks!
– heynnema
8 hours ago
add a comment |
I don't think that the command worked as you expected. The command you used tried to check the root file system and should have aborted because the root file system is mounted. You should have usedsudo fsck -cfvr /dev/sdc1instead ofsudo fsck -cfvr / dev / sdc1.
– mook765
8 hours ago
Yes, the command was working correctly, the file system was not mounted at the time of running the command. I already had a percentage greater than 50% the last time I checked it. but then it suddenly went out and I do not know if 100% of the process would end
– Miguel
8 hours ago
Please see my answer. Please remember to accept it if it was helpful. Thanks!
– heynnema
8 hours ago
I don't think that the command worked as you expected. The command you used tried to check the root file system and should have aborted because the root file system is mounted. You should have used
sudo fsck -cfvr /dev/sdc1 instead of sudo fsck -cfvr / dev / sdc1.– mook765
8 hours ago
I don't think that the command worked as you expected. The command you used tried to check the root file system and should have aborted because the root file system is mounted. You should have used
sudo fsck -cfvr /dev/sdc1 instead of sudo fsck -cfvr / dev / sdc1.– mook765
8 hours ago
Yes, the command was working correctly, the file system was not mounted at the time of running the command. I already had a percentage greater than 50% the last time I checked it. but then it suddenly went out and I do not know if 100% of the process would end
– Miguel
8 hours ago
Yes, the command was working correctly, the file system was not mounted at the time of running the command. I already had a percentage greater than 50% the last time I checked it. but then it suddenly went out and I do not know if 100% of the process would end
– Miguel
8 hours ago
Please see my answer. Please remember to accept it if it was helpful. Thanks!
– heynnema
8 hours ago
Please see my answer. Please remember to accept it if it was helpful. Thanks!
– heynnema
8 hours ago
add a comment |
2 Answers
2
active
oldest
votes
If the computer just fell asleep, the command most likely completed, but if the computer shut down, you might have to run the command again.
answered 8 hours ago
The MATE ManThe MATE Man
3115
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
add a comment |
If the computer shut off because the battery ran out... and if you were trying to badblock the /dev/sdc1 partition... then it didn't complete. Never run fsck whilst on battery alone.
And... if you were trying to badblock /dev/sdc1, you didn't give it a proper command. It should be...
sudo e2fsck -fck /dev/sdc1 # read-only test
or
sudo e2fsck -fcck /dev/sdc1 # non-destructive read/write test
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fcck parameter...
-f Force checking even if the file system seems clean.
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks.
If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or direc‐
tory. If this option is specified twice, then the bad block
scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the
bad blocks list are preserved, and any new bad blocks found by
running badblocks(8) will be added to the existing bad blocks
list.
answered 8 hours ago
heynnemaheynnema
19.4k22158
add a comment |
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
});
}
});
Miguel 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%2faskubuntu.com%2fquestions%2f1119868%2fformatting-a-external-hdd-and-the-computer-turn-off%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If the computer just fell asleep, the command most likely completed, but if the computer shut down, you might have to run the command again.
answered 8 hours ago
The MATE ManThe MATE Man
3115
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
add a comment |
If the computer just fell asleep, the command most likely completed, but if the computer shut down, you might have to run the command again.
answered 8 hours ago
The MATE ManThe MATE Man
3115
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
add a comment |
If the computer just fell asleep, the command most likely completed, but if the computer shut down, you might have to run the command again.
answered 8 hours ago
The MATE ManThe MATE Man
3115
If the computer just fell asleep, the command most likely completed, but if the computer shut down, you might have to run the command again.
answered 8 hours ago
The MATE ManThe MATE Man
3115
answered 8 hours ago
The MATE ManThe MATE Man
3115
answered 8 hours ago
The MATE ManThe MATE Man
3115
answered 8 hours ago
The MATE ManThe MATE Man
3115
3115
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
add a comment |
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
The computer turned off because it was disconnected and the battery ran out, the battery only lasts a few seconds.
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
There is no way to know if the command ended its process?
– Miguel
8 hours ago
add a comment |
If the computer shut off because the battery ran out... and if you were trying to badblock the /dev/sdc1 partition... then it didn't complete. Never run fsck whilst on battery alone.
And... if you were trying to badblock /dev/sdc1, you didn't give it a proper command. It should be...
sudo e2fsck -fck /dev/sdc1 # read-only test
or
sudo e2fsck -fcck /dev/sdc1 # non-destructive read/write test
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fcck parameter...
-f Force checking even if the file system seems clean.
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks.
If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or direc‐
tory. If this option is specified twice, then the bad block
scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the
bad blocks list are preserved, and any new bad blocks found by
running badblocks(8) will be added to the existing bad blocks
list.
answered 8 hours ago
heynnemaheynnema
19.4k22158
add a comment |
If the computer shut off because the battery ran out... and if you were trying to badblock the /dev/sdc1 partition... then it didn't complete. Never run fsck whilst on battery alone.
And... if you were trying to badblock /dev/sdc1, you didn't give it a proper command. It should be...
sudo e2fsck -fck /dev/sdc1 # read-only test
or
sudo e2fsck -fcck /dev/sdc1 # non-destructive read/write test
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fcck parameter...
-f Force checking even if the file system seems clean.
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks.
If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or direc‐
tory. If this option is specified twice, then the bad block
scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the
bad blocks list are preserved, and any new bad blocks found by
running badblocks(8) will be added to the existing bad blocks
list.
answered 8 hours ago
heynnemaheynnema
19.4k22158
add a comment |
If the computer shut off because the battery ran out... and if you were trying to badblock the /dev/sdc1 partition... then it didn't complete. Never run fsck whilst on battery alone.
And... if you were trying to badblock /dev/sdc1, you didn't give it a proper command. It should be...
sudo e2fsck -fck /dev/sdc1 # read-only test
or
sudo e2fsck -fcck /dev/sdc1 # non-destructive read/write test
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fcck parameter...
-f Force checking even if the file system seems clean.
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks.
If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or direc‐
tory. If this option is specified twice, then the bad block
scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the
bad blocks list are preserved, and any new bad blocks found by
running badblocks(8) will be added to the existing bad blocks
list.
answered 8 hours ago
heynnemaheynnema
19.4k22158
If the computer shut off because the battery ran out... and if you were trying to badblock the /dev/sdc1 partition... then it didn't complete. Never run fsck whilst on battery alone.
And... if you were trying to badblock /dev/sdc1, you didn't give it a proper command. It should be...
sudo e2fsck -fck /dev/sdc1 # read-only test
or
sudo e2fsck -fcck /dev/sdc1 # non-destructive read/write test
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fcck parameter...
-f Force checking even if the file system seems clean.
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks.
If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or direc‐
tory. If this option is specified twice, then the bad block
scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the
bad blocks list are preserved, and any new bad blocks found by
running badblocks(8) will be added to the existing bad blocks
list.
answered 8 hours ago
heynnemaheynnema
19.4k22158
edited 8 hours ago
answered 8 hours ago
heynnemaheynnema
19.4k22158
answered 8 hours ago
heynnemaheynnema
19.4k22158
answered 8 hours ago
heynnemaheynnema
19.4k22158
19.4k22158
add a comment |
add a comment |
Miguel is a new contributor. Be nice, and check out our Code of Conduct.
Miguel is a new contributor. Be nice, and check out our Code of Conduct.
Miguel is a new contributor. Be nice, and check out our Code of Conduct.
Miguel is a new contributor. Be nice, and check out our Code of Conduct.
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.
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%2faskubuntu.com%2fquestions%2f1119868%2fformatting-a-external-hdd-and-the-computer-turn-off%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
I don't think that the command worked as you expected. The command you used tried to check the root file system and should have aborted because the root file system is mounted. You should have used
sudo fsck -cfvr /dev/sdc1instead ofsudo fsck -cfvr / dev / sdc1.– mook765
8 hours ago
Yes, the command was working correctly, the file system was not mounted at the time of running the command. I already had a percentage greater than 50% the last time I checked it. but then it suddenly went out and I do not know if 100% of the process would end
– Miguel
8 hours ago
Please see my answer. Please remember to accept it if it was helpful. Thanks!
– heynnema
8 hours ago