I/O error when reading data from /dev/mapper/veracrypt1
Issue I'm having is similar to can't read superblock on /dev/mapper/veracrypt1 with the exception that mapper device cannot be read at all. Underlying physical disk can be read.
I.e. Veracrypt can decrypt the encrypted container, but cannot return a single byte from it.
More specifically:
- Ubuntu server 18.04 with four disks fully encrypted with Veracrypt 1.23.
- One disk fails to mount after power loss.
- Unable to quickly figure out what is wrong with the failed disk, I re-create the veracrypt partition and re-copy the data on it.
- After second power loss two disks fail to mount. The same one as before, and another one.
- Of the two failing, first one has one encrypted partition and the other one is completely encrypted. (So they have different setup.)
- Veracrypt mount fails due to can't read superblock error.
- Mounting with
--filesystem=noneoption works and allows access to mapper device. - Resulting
/dev/mapper/veracrypt1cannot be inspected nor fixed with normal toolsmke2fs, e2fscksince it cannot be read at all. - Even
ddfrom/dev/mapper/veracrypt1fails. While trying syslog is populated withFAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,Sense Key : Medium Error [current]andAdd. Sense: Unrecovered read error - auto reallocate failedmessages.
ddfrom underlying hard drive device/dev/sdeor/dev/sdb1works with no problems and allows reading of the whole disk in it's encrypted form.
I was suspecting some kind of a hardware failure but:
- SMART reports both failed disks have never had any issues. They can also be read as mentioned above.
- The failed disks are connected to different SATA cards and both are the only disk connected to their respective card.
I am mystified. Any ideas what might be going and what to try?
mount hard-drive encryption veracrypt
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
add a comment |
Issue I'm having is similar to can't read superblock on /dev/mapper/veracrypt1 with the exception that mapper device cannot be read at all. Underlying physical disk can be read.
I.e. Veracrypt can decrypt the encrypted container, but cannot return a single byte from it.
More specifically:
- Ubuntu server 18.04 with four disks fully encrypted with Veracrypt 1.23.
- One disk fails to mount after power loss.
- Unable to quickly figure out what is wrong with the failed disk, I re-create the veracrypt partition and re-copy the data on it.
- After second power loss two disks fail to mount. The same one as before, and another one.
- Of the two failing, first one has one encrypted partition and the other one is completely encrypted. (So they have different setup.)
- Veracrypt mount fails due to can't read superblock error.
- Mounting with
--filesystem=noneoption works and allows access to mapper device. - Resulting
/dev/mapper/veracrypt1cannot be inspected nor fixed with normal toolsmke2fs, e2fscksince it cannot be read at all. - Even
ddfrom/dev/mapper/veracrypt1fails. While trying syslog is populated withFAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,Sense Key : Medium Error [current]andAdd. Sense: Unrecovered read error - auto reallocate failedmessages.
ddfrom underlying hard drive device/dev/sdeor/dev/sdb1works with no problems and allows reading of the whole disk in it's encrypted form.
I was suspecting some kind of a hardware failure but:
- SMART reports both failed disks have never had any issues. They can also be read as mentioned above.
- The failed disks are connected to different SATA cards and both are the only disk connected to their respective card.
I am mystified. Any ideas what might be going and what to try?
mount hard-drive encryption veracrypt
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
add a comment |
Issue I'm having is similar to can't read superblock on /dev/mapper/veracrypt1 with the exception that mapper device cannot be read at all. Underlying physical disk can be read.
I.e. Veracrypt can decrypt the encrypted container, but cannot return a single byte from it.
More specifically:
- Ubuntu server 18.04 with four disks fully encrypted with Veracrypt 1.23.
- One disk fails to mount after power loss.
- Unable to quickly figure out what is wrong with the failed disk, I re-create the veracrypt partition and re-copy the data on it.
- After second power loss two disks fail to mount. The same one as before, and another one.
- Of the two failing, first one has one encrypted partition and the other one is completely encrypted. (So they have different setup.)
- Veracrypt mount fails due to can't read superblock error.
- Mounting with
--filesystem=noneoption works and allows access to mapper device. - Resulting
/dev/mapper/veracrypt1cannot be inspected nor fixed with normal toolsmke2fs, e2fscksince it cannot be read at all. - Even
ddfrom/dev/mapper/veracrypt1fails. While trying syslog is populated withFAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,Sense Key : Medium Error [current]andAdd. Sense: Unrecovered read error - auto reallocate failedmessages.
ddfrom underlying hard drive device/dev/sdeor/dev/sdb1works with no problems and allows reading of the whole disk in it's encrypted form.
I was suspecting some kind of a hardware failure but:
- SMART reports both failed disks have never had any issues. They can also be read as mentioned above.
- The failed disks are connected to different SATA cards and both are the only disk connected to their respective card.
I am mystified. Any ideas what might be going and what to try?
mount hard-drive encryption veracrypt
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
Issue I'm having is similar to can't read superblock on /dev/mapper/veracrypt1 with the exception that mapper device cannot be read at all. Underlying physical disk can be read.
I.e. Veracrypt can decrypt the encrypted container, but cannot return a single byte from it.
More specifically:
- Ubuntu server 18.04 with four disks fully encrypted with Veracrypt 1.23.
- One disk fails to mount after power loss.
- Unable to quickly figure out what is wrong with the failed disk, I re-create the veracrypt partition and re-copy the data on it.
- After second power loss two disks fail to mount. The same one as before, and another one.
- Of the two failing, first one has one encrypted partition and the other one is completely encrypted. (So they have different setup.)
- Veracrypt mount fails due to can't read superblock error.
- Mounting with
--filesystem=noneoption works and allows access to mapper device. - Resulting
/dev/mapper/veracrypt1cannot be inspected nor fixed with normal toolsmke2fs, e2fscksince it cannot be read at all. - Even
ddfrom/dev/mapper/veracrypt1fails. While trying syslog is populated withFAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,Sense Key : Medium Error [current]andAdd. Sense: Unrecovered read error - auto reallocate failedmessages.
ddfrom underlying hard drive device/dev/sdeor/dev/sdb1works with no problems and allows reading of the whole disk in it's encrypted form.
I was suspecting some kind of a hardware failure but:
- SMART reports both failed disks have never had any issues. They can also be read as mentioned above.
- The failed disks are connected to different SATA cards and both are the only disk connected to their respective card.
I am mystified. Any ideas what might be going and what to try?
mount hard-drive encryption veracrypt
mount hard-drive encryption veracrypt
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
asked Jan 31 at 23:06
steelmonkeysteelmonkey
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Turns out it was a case of faulty memory.
I noticed random looking crashes of various services in syslog, and started to suspect that it was kernel panic causing the reboot which had caused the filesystem corruption.
Replaced the memory module and suddenly you could read from the encrypted container and fix the filesystem as instructed in can't read superblock on /dev/mapper/veracrypt1 .
Also enabled apport to catch core dumps for the future.
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
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
});
}
});
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%2f1114573%2fi-o-error-when-reading-data-from-dev-mapper-veracrypt1%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
Turns out it was a case of faulty memory.
I noticed random looking crashes of various services in syslog, and started to suspect that it was kernel panic causing the reboot which had caused the filesystem corruption.
Replaced the memory module and suddenly you could read from the encrypted container and fix the filesystem as instructed in can't read superblock on /dev/mapper/veracrypt1 .
Also enabled apport to catch core dumps for the future.
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
add a comment |
Turns out it was a case of faulty memory.
I noticed random looking crashes of various services in syslog, and started to suspect that it was kernel panic causing the reboot which had caused the filesystem corruption.
Replaced the memory module and suddenly you could read from the encrypted container and fix the filesystem as instructed in can't read superblock on /dev/mapper/veracrypt1 .
Also enabled apport to catch core dumps for the future.
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
add a comment |
Turns out it was a case of faulty memory.
I noticed random looking crashes of various services in syslog, and started to suspect that it was kernel panic causing the reboot which had caused the filesystem corruption.
Replaced the memory module and suddenly you could read from the encrypted container and fix the filesystem as instructed in can't read superblock on /dev/mapper/veracrypt1 .
Also enabled apport to catch core dumps for the future.
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
Turns out it was a case of faulty memory.
I noticed random looking crashes of various services in syslog, and started to suspect that it was kernel panic causing the reboot which had caused the filesystem corruption.
Replaced the memory module and suddenly you could read from the encrypted container and fix the filesystem as instructed in can't read superblock on /dev/mapper/veracrypt1 .
Also enabled apport to catch core dumps for the future.
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
answered Feb 8 at 7:14
steelmonkeysteelmonkey
12
12
add a comment |
add a comment |
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%2f1114573%2fi-o-error-when-reading-data-from-dev-mapper-veracrypt1%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
