Bad magic number in super-block: dm-crypt device The Next CEO of Stack OverflowRecovering ext4 superblocksWhat's the difference between e2fsck and fsck and which one I should use?An existing mdadm RAID5 is not mounting, Either a problem drive or SuperblockAbysmal general dm-crypt (LUKS) write performanceHow to fix BTRFS superblock error after resize/shrink (BTRFS: couldn't get super buffer head for bytenr 274877906944)How can I identify the filesystem/partition typeI/O error after power failure, filesystem remounting as read-onlyUnlock Android encrypted DISK IMAGE FILE of SD card on desktop LinuxOpenBSD /dev/sd0k unexpected inconsistency - bad super blockbad magic number in superblock
Trouble understanding the speech of overseas colleagues
Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis
How to use tikz in fbox?
Rotate a column
What is the point of a new vote on May's deal when the indicative votes suggest she will not win?
What is the difference between "behavior" and "behaviour"?
Does it take more energy to get to Venus or to Mars?
Solution of this Diophantine Equation
MAZDA 3 2006 (UK) - poor acceleration then takes off at 3250 revs
Can I equip Skullclamp on a creature I am sacrificing?
Why doesn't a table tennis ball float on the surface? How do we calculate buoyancy here?
How do we know the LHC results are robust?
When did Lisp start using symbols for arithmetic?
How to be diplomatic in refusing to write code that breaches the privacy of our users
How to get regions to plot as graphics
% symbol leads to superlong (forever?) compilations
How should I support this large drywall patch?
Is it my responsibility to learn a new technology in my own time my employer wants to implement?
What is meant by a M next to a roman numeral?
Can a caster that cast Polymorph on themselves stop concentrating at any point even if their Int is low?
Does the Brexit deal have to be agreed by both Houses?
How to Reset Passwords on Multiple Websites Easily?
Why is there a PLL in CPU?
What is the purpose of the Evocation wizard's Potent Cantrip feature?
Bad magic number in super-block: dm-crypt device
The Next CEO of Stack OverflowRecovering ext4 superblocksWhat's the difference between e2fsck and fsck and which one I should use?An existing mdadm RAID5 is not mounting, Either a problem drive or SuperblockAbysmal general dm-crypt (LUKS) write performanceHow to fix BTRFS superblock error after resize/shrink (BTRFS: couldn't get super buffer head for bytenr 274877906944)How can I identify the filesystem/partition typeI/O error after power failure, filesystem remounting as read-onlyUnlock Android encrypted DISK IMAGE FILE of SD card on desktop LinuxOpenBSD /dev/sd0k unexpected inconsistency - bad super blockbad magic number in superblock
I have a device that is encrypted using dm-crypt. This is a mini SD card that I use on my laptop.
I've had some issues with my laptop freezing recently, and in the journal these messages come up:
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): warning: mounting fs with errors, running e2fsck is recommended
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): recovery complete
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
...
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): error count since last fsck: 84
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): initial error at time 1505289981: ext4_journal_check_start:60
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): last error at time 1551543757: ext4_reserve_inode_write:5903: inode 1054920: block 4194732
I have tried running fsck, but I get this error:
Bad magic number in super-block
Before attempting to resolve this, I just want to make sure that I should indeed be able to run fsck on a dm-encrypted drive. Or is this error expected? The reason why I am mystified is because I can mount this device just fine. For all intents and purposes, the drive works well. It mounts, it can read and write all data... the only problem is that I get this error at boot. So is there really a problem with the super block?
fsck dm-crypt superblock
asked yesterday
useruser
7717
add a comment |
I have a device that is encrypted using dm-crypt. This is a mini SD card that I use on my laptop.
I've had some issues with my laptop freezing recently, and in the journal these messages come up:
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): warning: mounting fs with errors, running e2fsck is recommended
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): recovery complete
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
...
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): error count since last fsck: 84
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): initial error at time 1505289981: ext4_journal_check_start:60
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): last error at time 1551543757: ext4_reserve_inode_write:5903: inode 1054920: block 4194732
I have tried running fsck, but I get this error:
Bad magic number in super-block
Before attempting to resolve this, I just want to make sure that I should indeed be able to run fsck on a dm-encrypted drive. Or is this error expected? The reason why I am mystified is because I can mount this device just fine. For all intents and purposes, the drive works well. It mounts, it can read and write all data... the only problem is that I get this error at boot. So is there really a problem with the super block?
fsck dm-crypt superblock
asked yesterday
useruser
7717
add a comment |
I have a device that is encrypted using dm-crypt. This is a mini SD card that I use on my laptop.
I've had some issues with my laptop freezing recently, and in the journal these messages come up:
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): warning: mounting fs with errors, running e2fsck is recommended
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): recovery complete
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
...
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): error count since last fsck: 84
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): initial error at time 1505289981: ext4_journal_check_start:60
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): last error at time 1551543757: ext4_reserve_inode_write:5903: inode 1054920: block 4194732
I have tried running fsck, but I get this error:
Bad magic number in super-block
Before attempting to resolve this, I just want to make sure that I should indeed be able to run fsck on a dm-encrypted drive. Or is this error expected? The reason why I am mystified is because I can mount this device just fine. For all intents and purposes, the drive works well. It mounts, it can read and write all data... the only problem is that I get this error at boot. So is there really a problem with the super block?
fsck dm-crypt superblock
asked yesterday
useruser
7717
I have a device that is encrypted using dm-crypt. This is a mini SD card that I use on my laptop.
I've had some issues with my laptop freezing recently, and in the journal these messages come up:
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): warning: mounting fs with errors, running e2fsck is recommended
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): recovery complete
Mar 20 17:18:30 gorgonzola kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
...
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): error count since last fsck: 84
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): initial error at time 1505289981: ext4_journal_check_start:60
Mar 20 17:23:30 gorgonzola kernel: EXT4-fs (dm-0): last error at time 1551543757: ext4_reserve_inode_write:5903: inode 1054920: block 4194732
I have tried running fsck, but I get this error:
Bad magic number in super-block
Before attempting to resolve this, I just want to make sure that I should indeed be able to run fsck on a dm-encrypted drive. Or is this error expected? The reason why I am mystified is because I can mount this device just fine. For all intents and purposes, the drive works well. It mounts, it can read and write all data... the only problem is that I get this error at boot. So is there really a problem with the super block?
fsck dm-crypt superblock
fsck dm-crypt superblock
asked yesterday
useruser
7717
asked yesterday
useruser
7717
asked yesterday
useruser
7717
asked yesterday
useruser
7717
asked yesterday
useruser
7717
7717
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Are you trying to run fsck on the /dev/sd* (or whatever) device that refers to the actual SD or its partition, just like on an unencrypted device?
If so, that device is fully encrypted, and that's why fsck cannot make any sense of it at all. If it found anything recognizable as a filesystem, that would be a sign of dm-crypt not working: the encrypted data is supposed to look like nondescript pseudorandom noise.
You need to point the fsck to the dm-crypt target, which will probably be named /dev/mapper/<something>. And that requires using cryptsetup to open the encrypted device first, just like when preparing to mount the encrypted device, before trying to run fsck on it. Since dm-crypt has several possible modes, I cannot suggest a correct cryptsetup command without knowing more about your setup. Perhaps your /etc/crypttab file might contain the necessary details?
answered yesterday
telcoMtelcoM
20.1k12450
add a comment |
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
);
);
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%2f508891%2fbad-magic-number-in-super-block-dm-crypt-device%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
Are you trying to run fsck on the /dev/sd* (or whatever) device that refers to the actual SD or its partition, just like on an unencrypted device?
If so, that device is fully encrypted, and that's why fsck cannot make any sense of it at all. If it found anything recognizable as a filesystem, that would be a sign of dm-crypt not working: the encrypted data is supposed to look like nondescript pseudorandom noise.
You need to point the fsck to the dm-crypt target, which will probably be named /dev/mapper/<something>. And that requires using cryptsetup to open the encrypted device first, just like when preparing to mount the encrypted device, before trying to run fsck on it. Since dm-crypt has several possible modes, I cannot suggest a correct cryptsetup command without knowing more about your setup. Perhaps your /etc/crypttab file might contain the necessary details?
answered yesterday
telcoMtelcoM
20.1k12450
add a comment |
Are you trying to run fsck on the /dev/sd* (or whatever) device that refers to the actual SD or its partition, just like on an unencrypted device?
If so, that device is fully encrypted, and that's why fsck cannot make any sense of it at all. If it found anything recognizable as a filesystem, that would be a sign of dm-crypt not working: the encrypted data is supposed to look like nondescript pseudorandom noise.
You need to point the fsck to the dm-crypt target, which will probably be named /dev/mapper/<something>. And that requires using cryptsetup to open the encrypted device first, just like when preparing to mount the encrypted device, before trying to run fsck on it. Since dm-crypt has several possible modes, I cannot suggest a correct cryptsetup command without knowing more about your setup. Perhaps your /etc/crypttab file might contain the necessary details?
answered yesterday
telcoMtelcoM
20.1k12450
add a comment |
Are you trying to run fsck on the /dev/sd* (or whatever) device that refers to the actual SD or its partition, just like on an unencrypted device?
If so, that device is fully encrypted, and that's why fsck cannot make any sense of it at all. If it found anything recognizable as a filesystem, that would be a sign of dm-crypt not working: the encrypted data is supposed to look like nondescript pseudorandom noise.
You need to point the fsck to the dm-crypt target, which will probably be named /dev/mapper/<something>. And that requires using cryptsetup to open the encrypted device first, just like when preparing to mount the encrypted device, before trying to run fsck on it. Since dm-crypt has several possible modes, I cannot suggest a correct cryptsetup command without knowing more about your setup. Perhaps your /etc/crypttab file might contain the necessary details?
answered yesterday
telcoMtelcoM
20.1k12450
Are you trying to run fsck on the /dev/sd* (or whatever) device that refers to the actual SD or its partition, just like on an unencrypted device?
If so, that device is fully encrypted, and that's why fsck cannot make any sense of it at all. If it found anything recognizable as a filesystem, that would be a sign of dm-crypt not working: the encrypted data is supposed to look like nondescript pseudorandom noise.
You need to point the fsck to the dm-crypt target, which will probably be named /dev/mapper/<something>. And that requires using cryptsetup to open the encrypted device first, just like when preparing to mount the encrypted device, before trying to run fsck on it. Since dm-crypt has several possible modes, I cannot suggest a correct cryptsetup command without knowing more about your setup. Perhaps your /etc/crypttab file might contain the necessary details?
answered yesterday
telcoMtelcoM
20.1k12450
answered yesterday
telcoMtelcoM
20.1k12450
answered yesterday
telcoMtelcoM
20.1k12450
answered yesterday
telcoMtelcoM
20.1k12450
20.1k12450
add a comment |
add a comment |
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.
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%2f508891%2fbad-magic-number-in-super-block-dm-crypt-device%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
