7

Just booted up my laptop after its shutdown after a sudden poweroff, caused by a discharged battery. I use Pop!_OS which comes with a disk encryption utility, which, in my case, has been always disabled by default (probably because I installed my distro as a dual-boot to Win8). But even though it was not enabled, in the middle of the booting process it showed me a message that said: "Please enter the passphrase for disk [diskname] (cryptswap)" even though I have disabled my swap partition by commenting it out in /etc/fstab months ago. Anyways as I don't have a passphrase, I pressed escape, which got me to the tty, and from there I pressed Ctrl+C, which let me completely boot up the system. After booting up, I ran dmesg and got this output:

[   26.489543] device-mapper: table: 253:0: crypt: Device lookup failed
[   26.489547] device-mapper: ioctl: error adding target to table
[   26.520538] Swap area shorter than signature indicates
[   26.700214] FAT-fs (sda8): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

My 8th partition is for the bootloader. I ran fsck on /dev/sda8 which said:

There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action

Could it be the cause of said disk encryption pop-up and, also, what are the other consequences that can happen after a sudden shutdown without a proper unmount of the disk partiotions?

1 Answer 1

3

I believe the byte at offset 65 (0x41) is the "dirty bit" that is set when a drive is not unmounted properly. See this output I got:

fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 2

That was soon followed by the same prompt you got

There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 

Not sure if the dirty bit triggers that behaviour, it would surprise me if it did as I imagine a bad unmount is something the OS boot would deal with gracefully. Thought if it's the boot partition...

Sorry this isn't a full answer, just came across this Q on a search for the same message and offset and thought I would share.

1
  • About boot sector - no, it is not because of the dirty bit because I just got a drive that is not dirty but boot sectors differ from 71 to 80th offset 71:42/55, 72:4c/4e, 73:41/54, 74:43/49, 75:4b/54, 76:20/4c, 77:4d/45 , 78:4f/44, 79:4f/20, 80:4e/20. Commented Apr 22 at 12:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .