I currently have an issue with mounting an array(RAID6) on 18.04 LTS. sudo mdadm -D /dev/md6 Version : 1.2 Creation Time : Mon Nov 27 07:03:26 2017 Raid Level : raid6 Array Size : 42975741952 (40984.86 GiB 44007.16 GB) Used Dev Size : 3906885632 (3725.90 GiB 4000.65 GB) Persistence : Superblock is persistent Intent Bitmap : Internal Layout : left-symmetric Chunk Size : 512K Consistency Policy : bitmap Attempting to mount: sudo mount /dev/mapper/enc6 /encrypted mount: /encrypted: mount(2) system call failed: Structure needs cleaning. >From dmesg: [ +11.907528] EXT4-fs error (device dm-0): ext4_iget:4748: inode #2: comm mount: root inode unallocated [ +0.193901] EXT4-fs (dm-0): get root inode failed [ +0.000003] EXT4-fs (dm-0): mount failed Tune2fs: tune2fs 1.44.1 (24-Mar-2018) Filesystem volume name: <none> Last mounted on: /mnt/test Filesystem UUID: 95566633-08c8-4288-88d8-a6aaa6251fab Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: ext_attr dir_index filetype extent 64bit flex_bg spars e_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: not clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 671496192 Block count: 10743934848 Reserved block count: 537196740 Free blocks: 1698072388 Free inodes: 663921293 First block: 0 Block size: 4096 Fragment size: 4096 Group descriptor size: 64 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 2048 Inode blocks per group: 128 RAID stride: 128 RAID stripe width: 640 Flex block group size: 16 Filesystem created: Sat Sep 9 23:49:19 2017 Last mount time: Sat Jun 16 22:28:53 2018 Last write time: Wed Sep 12 16:56:39 2018 Mount count: 0 Maximum mount count: -1 Last checked: Sun Jul 15 07:10:54 2018 Check interval: 0 (<none>) Lifetime writes: 36 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Default directory hash: half_md4 Directory Hash Seed: d4528343-c8ed-4888-8888-444c251063da Journal backup: inode blocks FS Error count: 8 First error time: Sat Sep 8 05:05:59 2018 First error function: ext4_iget First error line #: 4748 First error inode #: 2 First error block #: 0 Last error time: Wed Sep 12 16:56:39 2018 Last error function: ext4_iget Last error line #: 4748 Last error inode #: 2 Last error block #: 0 It was suggested that I perform e2fsck on this array. However, every time I run the check it gets to a certain point(sometimes 24+ hours later) and crashes. Causing all of the LAN in my house to drop offline until I reboot or remove the CAT from this system (This is also happening when using debugfs). The bad mounting issue was first observed after adding another drive to the array and performing a resize. sudo e2fsck /dev/mapper/enc6 sudo resize2fs -p /dev/mapper/enc6 Both of those procedures went through successfully. Once I attempted to mount the now resized array it gave me the error mentioned at the top. I have been looking for somebody that has gone through this situation and not had to wipe the array and start over, so far no luck. I can share more logs or details if needed! Thank you in advance. Regards, Nathan
