Bsrgvty

Transiting through Switzerland by coach with lots of cash

What cluster of stars is this with a "dark donut" to one side?

"Es gefällt ihm." How to identify similar exceptions?

How to Skip One Bullet in ITEMIZE?

A sentient carnivorous species trying to preserve life. How could they find a new food source?

Why do previous versions of Debian packages vanish in the package repositories? (highly relevant for version-controlled system configuration)

Remove one or more fields, delimited by a "-", at end of line

Who became a professor?

Is cloning illegal in the Star Trek: TNG continuity?

Was Wayne Brady considered a guest star on the original "Whose Line Is It Anyway?"

Member initialization for non-copyable variable in C++17

How does Donald Trump manage to remain so popular over a rather long period of time?

Which accidental continues through the bar?

Is having your hand in your pocket during a presentation bad?

The work of mathematicians outside their professional environment

80's-90's movie with a brains-powered spaceship

Over powered shield?

What is the good path to become a Judo teacher?

Is there a difference between historical fiction and creative non-fiction?

Difference between $HOME and ~

Scalar `new T` vs array `new T[1]`

Does the Creighton Method of Natural Family Planning have a failure rate of 3.2% or less?

Why didn't he give Sam the antidote?

What if a quote contains an error

Is it possible to repair root partition, LLVM based and protected with LUKS?

How do I resize an encrypted LVM to install another copy of Ubuntu?How to use fsck in Ubuntu?Shut down laptop while booting after update and now can't use itSuperblock invalid, disk in useHow do I move/home folder to a luks encrypted external drive?the root filesystem requires a manual fsckHow to force fix file systems during bootDualbooting Ubuntu 18.04 and Windows 10: manual fsck repeatedly required on Ubuntu partition

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

0

I have following partitions configuration:

NAME FSTYPE SIZE MOUNTPOINT LABEL
sda 447.1G
├─sda1 ext2 487M /boot
├─sda2 1K
└─sda5 crypto_LUKS 446.7G
 └─sda5_crypt LVM2_member 446.7G
 ├─S--1--vg-root ext4 318.8G /
 └─S--1--vg-swap_1 swap 127.9G [SWAP]

As you can see, I have LUKS protected Ubuntu system, and the entrypted volume uses LLVM.

I have errors in filesystem due to electricity supply interruption; when I run fsck, I see a lot of error messages:

sudo fsck -nf /
Inodes that were part of a corrupted orphan linked list found. Fix? no
/dev/mapper/S--1--vg-root: ********** WARNING: Filesystem still has errors **********

Of course, I can not fix the errors while partition is loaded. So, I reboot in system recovery mode, open single user root shell and run:

umount /dev/mapper/S--1--vg-root
sudo fsck -f /

Now fsck runs, however, it can not find any errors. When I reboot and run fsck again from fully loaded system, it still "sees" the same error.

What is the reason of such behavior? Is it possible to fix file system errors in such configuration (when LLVM volume is protected with LUKS)?

partitioning encryption luks fsck

share|improve this question

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  See this which recommends a fsck before a resize (which you do not need). askubuntu.com/questions/262211/…
  
  – oldfred
  Apr 17 at 12:33
  

  
  
  
  

add a comment
 | 

0

I have following partitions configuration:

NAME FSTYPE SIZE MOUNTPOINT LABEL
sda 447.1G
├─sda1 ext2 487M /boot
├─sda2 1K
└─sda5 crypto_LUKS 446.7G
 └─sda5_crypt LVM2_member 446.7G
 ├─S--1--vg-root ext4 318.8G /
 └─S--1--vg-swap_1 swap 127.9G [SWAP]

As you can see, I have LUKS protected Ubuntu system, and the entrypted volume uses LLVM.

I have errors in filesystem due to electricity supply interruption; when I run fsck, I see a lot of error messages:

sudo fsck -nf /
Inodes that were part of a corrupted orphan linked list found. Fix? no
/dev/mapper/S--1--vg-root: ********** WARNING: Filesystem still has errors **********

Of course, I can not fix the errors while partition is loaded. So, I reboot in system recovery mode, open single user root shell and run:

umount /dev/mapper/S--1--vg-root
sudo fsck -f /

Now fsck runs, however, it can not find any errors. When I reboot and run fsck again from fully loaded system, it still "sees" the same error.

What is the reason of such behavior? Is it possible to fix file system errors in such configuration (when LLVM volume is protected with LUKS)?

partitioning encryption luks fsck

share|improve this question

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  See this which recommends a fsck before a resize (which you do not need). askubuntu.com/questions/262211/…
  
  – oldfred
  Apr 17 at 12:33
  

  
  
  
  

add a comment
 | 

I have following partitions configuration:

NAME FSTYPE SIZE MOUNTPOINT LABEL
sda 447.1G
├─sda1 ext2 487M /boot
├─sda2 1K
└─sda5 crypto_LUKS 446.7G
 └─sda5_crypt LVM2_member 446.7G
 ├─S--1--vg-root ext4 318.8G /
 └─S--1--vg-swap_1 swap 127.9G [SWAP]

As you can see, I have LUKS protected Ubuntu system, and the entrypted volume uses LLVM.

I have errors in filesystem due to electricity supply interruption; when I run fsck, I see a lot of error messages:

sudo fsck -nf /
Inodes that were part of a corrupted orphan linked list found. Fix? no
/dev/mapper/S--1--vg-root: ********** WARNING: Filesystem still has errors **********

Of course, I can not fix the errors while partition is loaded. So, I reboot in system recovery mode, open single user root shell and run:

umount /dev/mapper/S--1--vg-root
sudo fsck -f /

Now fsck runs, however, it can not find any errors. When I reboot and run fsck again from fully loaded system, it still "sees" the same error.

What is the reason of such behavior? Is it possible to fix file system errors in such configuration (when LLVM volume is protected with LUKS)?

partitioning encryption luks fsck

share|improve this question

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges

NAME FSTYPE SIZE MOUNTPOINT LABEL
sda 447.1G
├─sda1 ext2 487M /boot
├─sda2 1K
└─sda5 crypto_LUKS 446.7G
 └─sda5_crypt LVM2_member 446.7G
 ├─S--1--vg-root ext4 318.8G /
 └─S--1--vg-swap_1 swap 127.9G [SWAP]

sudo fsck -nf /
Inodes that were part of a corrupted orphan linked list found. Fix? no
/dev/mapper/S--1--vg-root: ********** WARNING: Filesystem still has errors **********

umount /dev/mapper/S--1--vg-root
sudo fsck -f /

share|improve this question

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges

share|improve this question

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges

asked Apr 17 at 12:15

VitaliiVitalii

10655 bronze badges