Windows 10 - Storage Space Healthy but stuck on multiple operations
I have a 2 identical disk storage space that I hadn't used in a while. Yesterday when I plugged them in, it was showing a warning on one disk (no details, just the warning icon). So, I figured I could just remove that disk and re-add it to see if it would sort it self out. However, it just got suspended in removing state. I had also previously tried optimizing the storage space thinking the error would go away. Now I find that the space is stuck on both operations I had left it overnight thinking it would just be trying to move data from the disk being removed to the other. However, the status didn't change after 8+ hrs. I plugged them in to a different machine and the status is the same.
When I try to copy files from the space to another drive, I get this error:
Here are some info that were requested in other forums that might be useful to troubleshoot:
(Disk 2 and 3 are the ones in the Storage Space)
How can I get around this issue?
Update 1:
As suggested by @shawn, ran chkdsk which came up with ended with:
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
556 data files processed.
CHKDSK is verifying Usn Journal...
A disk read error occurredc0e7001c
Insufficient disk space to fix the Usn Journal $J data stream.
windows-10 storage-spaces
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
add a comment |
I have a 2 identical disk storage space that I hadn't used in a while. Yesterday when I plugged them in, it was showing a warning on one disk (no details, just the warning icon). So, I figured I could just remove that disk and re-add it to see if it would sort it self out. However, it just got suspended in removing state. I had also previously tried optimizing the storage space thinking the error would go away. Now I find that the space is stuck on both operations I had left it overnight thinking it would just be trying to move data from the disk being removed to the other. However, the status didn't change after 8+ hrs. I plugged them in to a different machine and the status is the same.
When I try to copy files from the space to another drive, I get this error:
Here are some info that were requested in other forums that might be useful to troubleshoot:
(Disk 2 and 3 are the ones in the Storage Space)
How can I get around this issue?
Update 1:
As suggested by @shawn, ran chkdsk which came up with ended with:
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
556 data files processed.
CHKDSK is verifying Usn Journal...
A disk read error occurredc0e7001c
Insufficient disk space to fix the Usn Journal $J data stream.
windows-10 storage-spaces
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
have you tried a chkdsk on it yet?chkdsk e: /f /r /x
– shawn
Dec 23 '18 at 8:29
@shawn Thanks! I updated the question with output. As it saysA disk read error occurredc0e7001c Insufficient disk space to fix the Usn Journal $J data stream.would adding a new disk to the pool help in this case? (but, it does have plenty more space already).
– Scorpion
Dec 23 '18 at 13:50
add a comment |
I have a 2 identical disk storage space that I hadn't used in a while. Yesterday when I plugged them in, it was showing a warning on one disk (no details, just the warning icon). So, I figured I could just remove that disk and re-add it to see if it would sort it self out. However, it just got suspended in removing state. I had also previously tried optimizing the storage space thinking the error would go away. Now I find that the space is stuck on both operations I had left it overnight thinking it would just be trying to move data from the disk being removed to the other. However, the status didn't change after 8+ hrs. I plugged them in to a different machine and the status is the same.
When I try to copy files from the space to another drive, I get this error:
Here are some info that were requested in other forums that might be useful to troubleshoot:
(Disk 2 and 3 are the ones in the Storage Space)
How can I get around this issue?
Update 1:
As suggested by @shawn, ran chkdsk which came up with ended with:
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
556 data files processed.
CHKDSK is verifying Usn Journal...
A disk read error occurredc0e7001c
Insufficient disk space to fix the Usn Journal $J data stream.
windows-10 storage-spaces
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
I have a 2 identical disk storage space that I hadn't used in a while. Yesterday when I plugged them in, it was showing a warning on one disk (no details, just the warning icon). So, I figured I could just remove that disk and re-add it to see if it would sort it self out. However, it just got suspended in removing state. I had also previously tried optimizing the storage space thinking the error would go away. Now I find that the space is stuck on both operations I had left it overnight thinking it would just be trying to move data from the disk being removed to the other. However, the status didn't change after 8+ hrs. I plugged them in to a different machine and the status is the same.
When I try to copy files from the space to another drive, I get this error:
Here are some info that were requested in other forums that might be useful to troubleshoot:
(Disk 2 and 3 are the ones in the Storage Space)
How can I get around this issue?
Update 1:
As suggested by @shawn, ran chkdsk which came up with ended with:
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
556 data files processed.
CHKDSK is verifying Usn Journal...
A disk read error occurredc0e7001c
Insufficient disk space to fix the Usn Journal $J data stream.
windows-10 storage-spaces
windows-10 storage-spaces
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
edited Dec 23 '18 at 13:49
Scorpion
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
asked Dec 23 '18 at 5:00
ScorpionScorpion
11829
11829
have you tried a chkdsk on it yet?chkdsk e: /f /r /x
– shawn
Dec 23 '18 at 8:29
@shawn Thanks! I updated the question with output. As it saysA disk read error occurredc0e7001c Insufficient disk space to fix the Usn Journal $J data stream.would adding a new disk to the pool help in this case? (but, it does have plenty more space already).
– Scorpion
Dec 23 '18 at 13:50
add a comment |
have you tried a chkdsk on it yet?chkdsk e: /f /r /x
– shawn
Dec 23 '18 at 8:29
@shawn Thanks! I updated the question with output. As it saysA disk read error occurredc0e7001c Insufficient disk space to fix the Usn Journal $J data stream.would adding a new disk to the pool help in this case? (but, it does have plenty more space already).
– Scorpion
Dec 23 '18 at 13:50
have you tried a chkdsk on it yet?
chkdsk e: /f /r /x– shawn
Dec 23 '18 at 8:29
have you tried a chkdsk on it yet?
chkdsk e: /f /r /x– shawn
Dec 23 '18 at 8:29
@shawn Thanks! I updated the question with output. As it says
A disk read error occurredc0e7001c Insufficient disk space to fix the Usn Journal $J data stream. would adding a new disk to the pool help in this case? (but, it does have plenty more space already).– Scorpion
Dec 23 '18 at 13:50
@shawn Thanks! I updated the question with output. As it says
A disk read error occurredc0e7001c Insufficient disk space to fix the Usn Journal $J data stream. would adding a new disk to the pool help in this case? (but, it does have plenty more space already).– Scorpion
Dec 23 '18 at 13:50
add a comment |
1 Answer
1
active
oldest
votes
Adding another device to the pool definitely won't fix it. Most likely your MFT is corrupted. I've seen this same thing where a corrupted MFT made the drive appear to be 200x its actual size, and chkdsk would fail as a result. You can try dumping the journal first. Run this in an elevated command prompt:
fsutil usn deletejournal /D e:
Then run chkdsk again.
chkdsk e: /f /r /x
If that works, you're fine. If not, I would get the data off, wipe it (DBAN), reformat, finally running chkdsk again and run a SMART check on it to be sure it's not dead or dying. If everything there goes well, you can re-add it to the pool.
answered Dec 23 '18 at 19:50
shawnshawn
1669
I think I got further with fsutil than before. However, it still ended withStage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546).With most sayingThe disk does not have enough space to replace bad clusters
– Scorpion
Dec 24 '18 at 2:20
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j(assumes your backup copy is going to be on the Q: drive), then replace the drive.
– shawn
Dec 24 '18 at 3:03
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1387063%2fwindows-10-storage-space-healthy-but-stuck-on-multiple-operations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Adding another device to the pool definitely won't fix it. Most likely your MFT is corrupted. I've seen this same thing where a corrupted MFT made the drive appear to be 200x its actual size, and chkdsk would fail as a result. You can try dumping the journal first. Run this in an elevated command prompt:
fsutil usn deletejournal /D e:
Then run chkdsk again.
chkdsk e: /f /r /x
If that works, you're fine. If not, I would get the data off, wipe it (DBAN), reformat, finally running chkdsk again and run a SMART check on it to be sure it's not dead or dying. If everything there goes well, you can re-add it to the pool.
answered Dec 23 '18 at 19:50
shawnshawn
1669
I think I got further with fsutil than before. However, it still ended withStage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546).With most sayingThe disk does not have enough space to replace bad clusters
– Scorpion
Dec 24 '18 at 2:20
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j(assumes your backup copy is going to be on the Q: drive), then replace the drive.
– shawn
Dec 24 '18 at 3:03
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
add a comment |
Adding another device to the pool definitely won't fix it. Most likely your MFT is corrupted. I've seen this same thing where a corrupted MFT made the drive appear to be 200x its actual size, and chkdsk would fail as a result. You can try dumping the journal first. Run this in an elevated command prompt:
fsutil usn deletejournal /D e:
Then run chkdsk again.
chkdsk e: /f /r /x
If that works, you're fine. If not, I would get the data off, wipe it (DBAN), reformat, finally running chkdsk again and run a SMART check on it to be sure it's not dead or dying. If everything there goes well, you can re-add it to the pool.
answered Dec 23 '18 at 19:50
shawnshawn
1669
I think I got further with fsutil than before. However, it still ended withStage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546).With most sayingThe disk does not have enough space to replace bad clusters
– Scorpion
Dec 24 '18 at 2:20
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j(assumes your backup copy is going to be on the Q: drive), then replace the drive.
– shawn
Dec 24 '18 at 3:03
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
add a comment |
Adding another device to the pool definitely won't fix it. Most likely your MFT is corrupted. I've seen this same thing where a corrupted MFT made the drive appear to be 200x its actual size, and chkdsk would fail as a result. You can try dumping the journal first. Run this in an elevated command prompt:
fsutil usn deletejournal /D e:
Then run chkdsk again.
chkdsk e: /f /r /x
If that works, you're fine. If not, I would get the data off, wipe it (DBAN), reformat, finally running chkdsk again and run a SMART check on it to be sure it's not dead or dying. If everything there goes well, you can re-add it to the pool.
answered Dec 23 '18 at 19:50
shawnshawn
1669
Adding another device to the pool definitely won't fix it. Most likely your MFT is corrupted. I've seen this same thing where a corrupted MFT made the drive appear to be 200x its actual size, and chkdsk would fail as a result. You can try dumping the journal first. Run this in an elevated command prompt:
fsutil usn deletejournal /D e:
Then run chkdsk again.
chkdsk e: /f /r /x
If that works, you're fine. If not, I would get the data off, wipe it (DBAN), reformat, finally running chkdsk again and run a SMART check on it to be sure it's not dead or dying. If everything there goes well, you can re-add it to the pool.
answered Dec 23 '18 at 19:50
shawnshawn
1669
answered Dec 23 '18 at 19:50
shawnshawn
1669
answered Dec 23 '18 at 19:50
shawnshawn
1669
answered Dec 23 '18 at 19:50
shawnshawn
1669
1669
I think I got further with fsutil than before. However, it still ended withStage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546).With most sayingThe disk does not have enough space to replace bad clusters
– Scorpion
Dec 24 '18 at 2:20
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j(assumes your backup copy is going to be on the Q: drive), then replace the drive.
– shawn
Dec 24 '18 at 3:03
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
add a comment |
I think I got further with fsutil than before. However, it still ended withStage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546).With most sayingThe disk does not have enough space to replace bad clusters
– Scorpion
Dec 24 '18 at 2:20
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j(assumes your backup copy is going to be on the Q: drive), then replace the drive.
– shawn
Dec 24 '18 at 3:03
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
I think I got further with fsutil than before. However, it still ended with
Stage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546). With most saying The disk does not have enough space to replace bad clusters– Scorpion
Dec 24 '18 at 2:20
I think I got further with fsutil than before. However, it still ended with
Stage 5: Looking for bad, free clusters ... 374963571 free clusters processed. Free space verification is complete. Adding 166177 bad clusters to the Bad Clusters File. Correcting errors in the Volume Bitmap. An unspecified error occurred (6e74667363686b2e 1546). With most saying The disk does not have enough space to replace bad clusters– Scorpion
Dec 24 '18 at 2:20
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -
robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j (assumes your backup copy is going to be on the Q: drive), then replace the drive.– shawn
Dec 24 '18 at 3:03
I'd replace any drive with that many bad clusters. 166177 in a single pass is huge. robocopy your stuff to a safe place -
robocopy "e:" "q:backup" /r:5 /w:1 /mir /e /xj /copyall /zb /j (assumes your backup copy is going to be on the Q: drive), then replace the drive.– shawn
Dec 24 '18 at 3:03
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
Got it, thanks! Ordered a new drive and will move them as soon as it arrives. Unfortunately, looks like some of the files will not be recoverable :( I guess I knew I'd be in that spot when I didn't set up the space for resilience.
– Scorpion
Dec 24 '18 at 4:53
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1387063%2fwindows-10-storage-space-healthy-but-stuck-on-multiple-operations%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
have you tried a chkdsk on it yet?
chkdsk e: /f /r /x– shawn
Dec 23 '18 at 8:29
@shawn Thanks! I updated the question with output. As it says
A disk read error occurredc0e7001c Insufficient disk space to fix the Usn Journal $J data stream.would adding a new disk to the pool help in this case? (but, it does have plenty more space already).– Scorpion
Dec 23 '18 at 13:50