1

Topic: Inline data flag after resizing? can't repare grub

Hi

I'll try to describe what i remember and what, i think, is important:

I installed gentoo alongside with Windows.
I did it on two partitions (root and swap).
I intslled grub on partition (not in MBR)

I lern a lot, and starting use system.

When i want to try virtualbox there was insufficient disk space for virtual disks so i used gparted to enlarge my / partition. After that gentoo stop booting (grub rescue - if I good remember, or nothing). Windows start well. I think that grub stops wrotking becose partition on which genntoo was installes change its position (it change the beginning). So i prepare again windows boot loader menu with easyBCD.

It did'n help. Grub start in rescue mode. So i boot from gentoo livecd and chrooted. I try to rebuild grub. I'm not sure if i used grub-install, but grub-mkconfig for sure.

Then it start booting to minimal bash mode. After setting: root, kernel and inird it boots, and then ask about root device which cant be found, after providing proper device its boot the system.

And now more trusted information with listings:

I cant instal grub:

elgentoo home # grub-install /dev/sda5
Installing for i386-pc platform.
grub-install: error: unknown filesystem.

I thought its a filesystem issue so i try:

elgentoo ~ # e2fsck -n /dev/sda5
e2fsck 1.42.13 (17-May-2015)
Warning!  /dev/sda5 is mounted.
/dev/sda5 has unsupported feature(s): inline_data
e2fsck: Get a newer version of e2fsck!

I read a little about that. If I'm not wrong, its not turn on by default, I'm sure, i wasn't turn it on during instalation. To be honest I'm not sure if i choose ext3 or ex4.

So i try to check if its really have inline_date flag on:

elgentoo ~ # dumpe2fs /dev/sda5
dumpe2fs 1.42.13 (17-May-2015)
dumpe2fs: Filesystem has unsupported feature(s) while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
elgentoo ~ # debugfs -R features /dev/sda5
debugfs 1.42.13 (17-May-2015)
/dev/sda5: Filesystem has unsupported feature(s) while opening filesystem
features: Filesystem not open

In portage (package menager of gentoo) thers is not newer version of e2fsprogs. I don't want to mess with it, so i boot from liveusb (gparted) with newer e2fsprogs and:

Cose info >>  Couldn't find valid filesystem superblock. <<
I checked it:

root@debian:/home/user# e2fsck -n /dev/sda5
e2fsck 1.43.1 (08-Jun-2016)
/dev/sda5: clean, 497127/6576960 files, 4359091/13174784 blocks

it was clean, so force to check

r

oot@debian:/home/user# e2fsck -nf /dev/sda5
e2fsck 1.43.1 (08-Jun-2016)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 497127/6576960 files (4.8% non-contiguous), 4359091/13174784 blocks

So i assume there is no problem with inconsistent filesystem.

I used bootinfoscript and analyse it with my knowleage and cant find any couses.
So i assume, my knowleage is to small.

                  Boot Info Script 0.61      [1 April 2012]

============================= Boot Info Summary: ===============================

 => Windows is installed in the MBR of /dev/sda.
 => Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdf.

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /bootmgr /BOOTMGR /boot/bcd /BOOT/bcd /Boot/bcd 
                       /boot/BCD /BOOT/BCD /Boot/BCD 
                       /Windows/System32/winload.exe 
                       /WINDOWS/system32/winload.exe 
                       /WINDOWS/SYSTEM32/winload.exe 
                       /windows/system32/winload.exe

sda2: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: 

sda3: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  Unknown
    Boot sector info: 

sda5: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub2 (v1.99)
    Boot sector info:  Grub2 (v1.99) is installed in the boot sector of sda5 
                       and looks at sector 475494181 of the same hard drive 
                       for core.img. core.img is at this location and looks 
                       in partition 135 for .
    Operating System:   This is .()
    Boot files:        /boot/grub/grub.cfg /etc/fstab

sdf1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 6.03 2014-10-06................................................2....0............A20 gate n
    Boot sector info:  Syslinux looks at sector 30439240 of /dev/sdf1 for 
                       its second stage. SYSLINUX is installed in the 
                       syslinux directory. No errors found in the Boot 
                       Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/grub.cfg /syslinux/syslinux.cfg 
                       /efi/boot/bootia32.efi /efi/boot/bootx64.efi 
                       /syslinux/ldlinux.sys

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 232.9 GiB, 250058268160 bytes, 488395055 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *             63   378,796,634   378,796,572   7 NTFS / exFAT / HPFS
/dev/sda2         484,200,448   488,395,054     4,194,607  82 Linux swap / Solaris
/dev/sda3         378,798,080   484,199,099   105,401,020   f W95 Extended (LBA)
/dev/sda5         378,800,128   484,198,399   105,398,272  83 Linux


Drive: sdf _____________________________________________________________________
Disk /dev/sdf: 14.9 GiB, 16008609792 bytes, 31266816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdf1    *          2,048    31,266,815    31,264,768  83 Linux


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        6C0E74A20E7466CC                       ntfs       
/dev/sda2        37f7c345-8da5-4074-8977-f84465bc28f9   swap       
/dev/sda5        5956ce50-1027-0000-2263-806e6f6e6963   ext4       
/dev/sdf1        AA02-C959                              vfat       

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sda1        /mnt/win                 ntfs       (ro,nosuid,nodev,noexec,relatime,uid=0,gid=0,umask=0222,nls=utf8,errors=continue,mft_zone_multiplier=1,user=fares)
/dev/sda5        /                        ext4       (rw,noatime,errors=remount-ro,data=ordered)


=========================== sda5/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if loadfont unicode ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-/dev/sda5' {
    load_video
    insmod gzio
    insmod part_msdos
    echo    'Loading Linux x86_64-4.4.6-gentoo ...'
    linux    /boot/kernel-genkernel-x86_64-4.4.6-gentoo root=/dev/sda5 ro  
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
}
submenu 'Advanced options for Gentoo GNU/Linux' $menuentry_id_option 'gnulinux-advanced-/dev/sda5' {
    menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.4.6-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.4.6-gentoo-advanced-/dev/sda5' {
        load_video
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux x86_64-4.4.6-gentoo ...'
        linux    /boot/kernel-genkernel-x86_64-4.4.6-gentoo root=/dev/sda5 ro  
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.4.6-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.4.6-gentoo-recovery-/dev/sda5' {
        load_video
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux x86_64-4.4.6-gentoo ...'
        linux    /boot/kernel-genkernel-x86_64-4.4.6-gentoo root=/dev/sda5 ro single 
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.4.6-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.4.6-gentoo-advanced-/dev/sda5' {
        load_video
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux x86_64-4.4.6-gentoo ...'
        linux    /boot/kernel-forX-x86_64-4.4.6-gentoo root=/dev/sda5 ro  
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-forX-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.4.6-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.4.6-gentoo-recovery-/dev/sda5' {
        load_video
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux x86_64-4.4.6-gentoo ...'
        linux    /boot/kernel-forX-x86_64-4.4.6-gentoo root=/dev/sda5 ro single 
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux 4.4.6-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.6-gentoo-advanced-/dev/sda5' {
        load_video
        if [ "x$grub_platform" = xefi ]; then
            set gfxpayload=keep
        fi
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux 4.4.6-gentoo ...'
        linux    /boot/vmlinuz-4.4.6-gentoo root=/dev/sda5 ro  
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux 4.4.6-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.6-gentoo-recovery-/dev/sda5' {
        load_video
        if [ "x$grub_platform" = xefi ]; then
            set gfxpayload=keep
        fi
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux 4.4.6-gentoo ...'
        linux    /boot/vmlinuz-4.4.6-gentoo root=/dev/sda5 ro single 
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux 4.4.6-gentoo.old' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.6-gentoo.old-advanced-/dev/sda5' {
        load_video
        if [ "x$grub_platform" = xefi ]; then
            set gfxpayload=keep
        fi
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux 4.4.6-gentoo.old ...'
        linux    /boot/vmlinuz-4.4.6-gentoo.old root=/dev/sda5 ro  
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
    menuentry 'Gentoo GNU/Linux, with Linux 4.4.6-gentoo.old (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.6-gentoo.old-recovery-/dev/sda5' {
        load_video
        if [ "x$grub_platform" = xefi ]; then
            set gfxpayload=keep
        fi
        insmod gzio
        insmod part_msdos
        echo    'Loading Linux 4.4.6-gentoo.old ...'
        linux    /boot/vmlinuz-4.4.6-gentoo.old root=/dev/sda5 ro single 
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
    }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sda5/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't 
# needed); notail increases performance of ReiserFS (at the expense of storage 
# efficiency).  It's safe to drop the noatime options if you want and to 
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# <fs>                            <mountpoint>    <type>        <opts>        <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#/dev/BOOT                        /boot        ext2        noauto,noatime    1 2
UUID=5956ce50-1027-0000-2263-806e6f6e6963        /        ext3        noatime        0 1
#/dev/sda5                        /        ext3        noatime        0 1
/dev/sda3                        none        swap        sw        0 0
/dev/cdrom                        /mnt/cdrom    auto        noauto,ro    0 0
/dev/fd0                        /mnt/floppy    auto        noauto        0 0
UUID=6C0E74A20E7466CC                    /mnt/win    auto        noauto,user,umask=0222        0 0
--------------------------------------------------------------------------------

=================== sda5: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)


=========================== sdf1/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
# This file is for compatibility to Ubuntu Linux's uEFI secure boot. 
# The real config file for grub is /EFI/boot/grub.cfg.
configfile /EFI/boot/grub.cfg
--------------------------------------------------------------------------------

========================= sdf1/syslinux/syslinux.cfg: ==========================

--------------------------------------------------------------------------------
# Created by generate-pxe-menu! Do NOT edit unless you know what you are doing! 
# Keep those comment "MENU DEFAULT" and "MENU HIDE"! Do NOT remove them.
# Note!!! If "serial" directive exists, it must be the first directive
default vesamenu.c32
timeout 300
prompt 0
noescape 1
MENU MARGIN 5
 MENU BACKGROUND Gsplash.png
# Set the color for unselected menu item and timout message
 MENU COLOR TITLE    1;36;44    #ffffffff #00000000
 MENU COLOR SEL      7;37;40    #FF000000 #FFC0C0C0
 MENU COLOR HOTSEL   1;7;37;40  #FF000000 #FFC0C0C0

# MENU MASTER PASSWD

say **********************************************************************
say GParted.
say Gnome Partition Editor.
say gparted.org
say THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! 
say **********************************************************************

# Allow client to edit the parameters
ALLOWOPTIONS 1

# simple menu title
MENU TITLE gparted.org

# Since no network setting in the squashfs image, therefore if ip=, the network is disabled. That's what we want.
label GParted Live
  MENU DEFAULT
  # MENU HIDE
  MENU LABEL GParted Live (Default settings)
  # MENU PASSWD
  kernel /live/vmlinuz
  append initrd=/live/initrd.img boot=live union=overlay username=user config components quiet noswap  ip= net.ifnames=0  nosplash 
  TEXT HELP
  * Boot menu for BIOS machine
  * GParted live version: 0.26.1-5-amd64. Live version maintainer: Steven Shiau
  * Disclaimer: GParted live comes with ABSOLUTELY NO WARRANTY
  ENDTEXT

MENU BEGIN Other modes of GParted Live
label GParted Live KMS
  # MENU DEFAULT
  # MENU HIDE
  MENU LABEL GParted Live (Default settings, KMS)
  # MENU PASSWD
  kernel /live/vmlinuz
  append initrd=/live/initrd.img boot=live union=overlay username=user config components quiet noswap vga=791 ip= net.ifnames=0  nosplash
  TEXT HELP
  KMS mode. OK for ATI, Intel and NVIDIA VGA cards.
  ENDTEXT

label GParted Live (To RAM)
  # MENU DEFAULT
  # MENU HIDE
  MENU LABEL GParted Live (To RAM. Boot media can be removed later)
  # MENU PASSWD
  kernel /live/vmlinuz
  append initrd=/live/initrd.img boot=live union=overlay username=user config components quiet noswap  toram=filesystem.squashfs ip= net.ifnames=0  nosplash 
  TEXT HELP
  All the programs will be copied to RAM, so you can
  remove boot media (CD or USB flash drive) later
  ENDTEXT

label GParted Live without framebuffer
  # MENU DEFAULT
  # MENU HIDE
  MENU LABEL GParted Live (Safe graphic settings, vga=normal)
  # MENU PASSWD
  kernel /live/vmlinuz
  append initrd=/live/initrd.img boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nomodeset vga=normal nosplash
  TEXT HELP
  Disable console frame buffer support
  ENDTEXT

label GParted Live failsafe mode
  # MENU DEFAULT
  # MENU HIDE
  MENU LABEL GParted Live (Failsafe mode)
  # MENU PASSWD
  kernel /live/vmlinuz
  append initrd=/live/initrd.img boot=live union=overlay username=user config components quiet noswap acpi=off irqpoll noapic noapm nodma nomce nolapic nosmp ip= net.ifnames=0 nomodeset vga=normal nosplash
  TEXT HELP
  acpi=off irqpoll noapic noapm nodma nomce nolapic 
  nosmp nomodeset vga=normal nosplash
  ENDTEXT

MENU END
label local
  # MENU DEFAULT
  # MENU HIDE
  MENU LABEL Local operating system in harddrive (if available)
  # MENU PASSWD
  # 2 method to boot local device:
  # (1) For localboot 0, it is decided by boot order in BIOS, so uncomment the follow 1 line if you want this method:
  # localboot 0

  # (2) For chain.c32, you can assign the boot device.
  # Ref: extlinux.doc from syslinux
  # Syntax: APPEND [hd|fd]<number> [<partition>]
  # [<partition>] is optional.
  # Ex:
  # Second partition (2) on the first hard disk (hd0);
  # Linux would *typically* call this /dev/hda2 or /dev/sda2, then it's "APPEND hd0 2"
  #
  kernel chain.c32
  append hd0
  TEXT HELP
  Boot local OS from first hard disk if it's available
  ENDTEXT


# Note! *.bin is specially purpose for syslinux, 
# Do NOT use memtest.bin, use memtest instead of memtest.bin
label memtest
  # MENU DEFAULT
  # MENU HIDE
  MENU LABEL Memory test using Memtest86+
  # MENU PASSWD
  kernel /live/memtest
  TEXT HELP
  Run memory test using Memtest86+
  ENDTEXT

--------------------------------------------------------------------------------

=================== sdf1: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)


================= sdf1: Location of files loaded by Syslinux: ==================

           GiB - GB             File                                 Fragment(s)


============== sdf1: Version of COM32(R) files used by Syslinux: ===============

 syslinux/chain.c32                 :  not a COM32/COM32R module
 syslinux/ldlinux.c32               :  not a COM32/COM32R module
 syslinux/libcom32.c32              :  not a COM32/COM32R module
 syslinux/libutil.c32               :  not a COM32/COM32R module
 syslinux/menu.c32                  :  not a COM32/COM32R module
 syslinux/vesamenu.c32              :  not a COM32/COM32R module

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sda3

00000000  38 3e 93 d5 37 ca 23 5d  b4 d0 7e 1c 51 67 22 e9  |8>..7.#]..~.Qg".|
00000010  53 bc 44 62 1b 14 ef 99  a6 bb cd 84 25 8c 4d 48  |S.Db........%.MH|
00000020  20 53 3d ad 73 71 4f 39  69 ee 64 ea 5c 6d e0 30  | S=.sqO9i.d.\m.0|
00000030  ee 98 96 19 26 32 02 80  6c 84 69 4d 43 10 6c 23  |....&2..l.iMC.l#|
00000040  0a 2b d4 05 58 52 8a 26  68 d9 14 75 df 3e 85 98  |.+..XR.&h..u.>..|
00000050  d6 be b3 e6 cb 26 d6 db  6d 6d 7d d6 7d f2 d4 6a  |.....&..mm}.}..j|
00000060  bd 13 b8 74 8e ea 76 63  69 0e 0b 96 fa 1d 61 04  |...t..vci.....a.|
00000070  aa 8e 4c 96 c9 6c bb a9  eb 7c d7 d8 f0 6b 4f 2f  |..L..l...|...kO/|
00000080  b7 b8 52 59 06 07 a7 90  c8 17 4c e5 6a 95 12 39  |..RY......L.j..9|
00000090  77 24 89 e4 a4 60 e8 5e  3c 86 1a 21 1b 5d c6 91  |w$...`.^<..!.]..|
000000a0  56 d0 d9 ce 48 d3 b4 93  e8 3e 00 00 00 bf 78 0e  |V...H....>....x.|
000000b0  9b 12 eb 68 a8 c3 01 10  14 7f ad a0 e8 bc 77 49  |...h..........wI|
000000c0  1e 67 e1 2a 79 60 92 22  98 3e 59 91 d3 9c 24 3e  |.g.*y`.".>Y...$>|
000000d0  4d 4e dc d2 59 ad 6b 20  f9 d3 9b 53 55 06 af 17  |MN..Y.k ...SU...|
000000e0  ce 86 1e 2a 77 16 b7 b8  86 cc bf cc 04 75 4e e0  |...*w........uN.|
000000f0  93 a8 a0 4a d9 b0 21 b4  34 af 08 a5 55 59 e0 7d  |...J..!.4...UY.}|
00000100  2c d1 57 85 e6 22 e5 59  2e 52 9d 07 07 61 54 d5  |,.W..".Y.R...aT.|
00000110  5a e9 aa c7 6c 50 56 a5  99 91 22 32 d5 9c 16 01  |Z...lPV..."2....|
00000120  62 24 96 ae 33 48 98 35  19 ee 30 be c3 d0 d2 72  |b$..3H.5..0....r|
00000130  66 dd 88 93 7d 3d 5b 49  de 18 1d c8 dd 5d 6d 49  |f...}=[I.....]mI|
00000140  aa 4f 93 10 90 b4 1f da  18 5b 9b 6b 6d 3b 37 5f  |.O.......[.km;7_|
00000150  fc 71 08 8c 08 a6 fd 5b  5e 00 d5 3a b1 c6 8c 70  |.q.....[^..:...p|
00000160  1e 73 58 3c 68 ec aa 88  ca b2 42 80 94 98 c2 1c  |.sX<h.....B.....|
00000170  ca 46 05 4c cd 9e 5b 38  db e8 33 05 10 23 66 78  |.F.L..[8..3..#fx|
00000180  46 22 32 89 74 a3 3a 12  cc 9b d8 ec 31 89 e8 de  |F"2.t.:.....1...|
00000190  2c 02 05 12 57 93 b2 d4  49 09 8b 88 db a4 e7 a5  |,...W...I.......|
000001a0  0b 77 c1 d1 1e 40 e1 df  fd c9 80 7d fe b2 e8 20  |.w...@.....}... |
000001b0  1c 20 3e 87 04 14 40 4a  88 89 aa ee 10 6b 00 fe  |. >...@J.....k..|
000001c0  ff ff 83 fe ff ff 00 08  00 00 00 40 48 06 00 00  |...........@H...|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200


========= Devices which don't seem to have a corresponding hard drive: =========

sdb sdc sdd sde 

=============================== StdErr Messages: ===============================

cat: /tmp/BootInfo-5lO7Rnkj/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-5lO7Rnkj/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-5lO7Rnkj/Tmp_Log: No such file or directory

I do it mostly for eductaional purpouse.
I dont have any crucial data, anyway i can acces all my data.
I want to repare existing system, not backup data, prepare new partition and load data from backup, dont want to sparate boot partition. It will be possibly next steps.

1 I want to know what (how it would) happend and
2 How i can repare it
3 if i can check if any data is written to inode
4 could gparted change inline_data flag (used the same grub-install version)

2

Re: Inline data flag after resizing? can't repare grub

There have been many fixes to the e2fsprogs package which is responsible for ext2/ext3/ext4 file systems.  It is possible that you have encountered a problem that is fixed by a newer version of e2fsprogs.

Currently the latest packaged version in Debian is 1.43.3.  We plan to include an updated version of e2progs in the GParted Live image once we finish preparing a new version of the GParted application.

3 (edited by fares 2016-10-05 04:30:19)

Re: Inline data flag after resizing? can't repare grub

Thank you for your answer but...

As I mention above i used quite new version of e2fsprogs (e2fsck 1.43.1 (08-Jun-2016)) and it not show any problems (as far as i know what and where to use and how to interpret the results)

Can you point any possible reason of described above behaviour?

Do you need any more info? Superblock or anything else what you could use to improve e2fsprogs, or find a possible bug, or just help me to diagnose what happend to my partition/fs.

Be as much verbose as you can. For me its mainly educational purposes, but maybe it will save somone other live.

4 (edited by fares 2016-10-05 04:38:14)

Re: Inline data flag after resizing? can't repare grub

I prepared main/first post offline, and forgot to to attach some info:

root@debian:/home/user# debugfs /dev/sda5 -R features
debugfs 1.43.1 (08-Jun-2016)
Filesystem features: has_journal ext_attr dir_index needs_recovery inline_data large_file

root@debian:/home/user# tune2fs /dev/sda5 -l
tune2fs 1.43.1 (08-Jun-2016)
Filesystem volume name:   <none>
Last mounted on:          /mnt
Filesystem UUID:          5956ce50-1027-0000-2263-806e6f6e6963
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr dir_index needs_recovery inline_data large_file
Filesystem flags:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Unknown (continue)
Filesystem OS type:       Linux
Inode count:              6576960
Block count:              13174784
Reserved block count:     658739
Free blocks:              8815693
Free inodes:              6079833
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16320
Inode blocks per group:   510
Last mount time:          Fri Sep 30 03:33:27 2016
Last write time:          Fri Sep 30 03:33:27 2016
Mount count:              10
Maximum mount count:      20
Last checked:             Wed Sep 28 06:18:54 2016
Check interval:           0 (<none>)
Lifetime writes:          29 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   legacy
Journal backup:           inode blocks

5 (edited by gedakc 2016-10-05 17:54:13)

Re: Inline data flag after resizing? can't repare grub

I mentioned the e2fsprogs version because we have a few reports of problems with version 1.43.1.  The release notes point to problems with resizing and file system checking.

See E2fsprogs 1.43.3 Release Notes.

EDIT:  Another thought.  What version of grub are you using?  If it is Grub 1 (Legacy) then I don't think it supports ext4, only ext2 and ext3.

6 (edited by fares 2016-10-06 05:56:29)

Re: Inline data flag after resizing? can't repare grub

gedakc wrote:

I mentioned the e2fsprogs version because we have a few reports of problems with version 1.43.1.  The release notes point to problems with resizing and file system checking.

See E2fsprogs 1.43.3 Release Notes.

To be honest, After Reading notes i don't see, that could be it.. but maybe I know to little, and you fill me with hope :). Thank you.

And now some new info:

EDIT:  Another thought.  What version of grub are you using?  If it is Grub 1 (Legacy) then I don't think it supports ext4, only ext2 and ext3.

Bootinfoscript (as showed in first post):

Boot sector type:  Grub2 (v1.99)

but

elgentoo home # grub-install -V
grub-install (GRUB) 2.02~beta2

I checked defaults sets for newly created filesystems (and there is no inlina_data):

        ext4 = {
                features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
                auto_64-bit_support = 1
                inode_size = 256

But I begin to convince, that i made ext3 filesystem, moslty due to the entry in fstab:

UUID=5956ce50-1027-0000-2263-806e6f6e6963        /        ext3        noatime        0 1

And AFAIK ext3 don't even have inline_data flag.

7

Re: Inline data flag after resizing? can't repare grub

You might try checking the file system using the latest e2fsprogs.  It may or may not find any issues.

In terms of restoring grub2 boot, the instructions on how to do this can be found in the GParted Manual - Restoring GRUB 2 Boot Loader.  Note that there are extra steps required if using LVM or RAID.

8 (edited by fares 2016-10-12 01:16:46)

Re: Inline data flag after resizing? can't repare grub

gedakc wrote:

You might try checking the file system using the latest e2fsprogs.  It may or may not find any issues.

Compile newest e2fsprogs, and as i expected "nihil novi" (nothing new - in latin),  it doesn't find anything:
Was clean:

elgentoo grub-2.00 # e2fsck /dev/sda5
e2fsck 1.43.3 (04-Sep-2016)
/dev/sda5: clean, 505910/4210560 files, 4332275/8438784 blocks

so force it

elgentoo grub-2.00 # e2fsck /dev/sda5 -f
e2fsck 1.43.3 (04-Sep-2016)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 505910/4210560 files (4.8% non-contiguous), 4332275/8438784 blocks
elgentoo grub-2.00 #
gedakc wrote:

In terms of restoring grub2 boot, the instructions on how to do this can be found in the GParted Manual - Restoring GRUB 2 Boot Loader.  Note that there are extra steps required if using LVM or RAID.

About grub restore. Thank you for your trying, but it's not a common case, i searching a lot and trying many solution, and this, what you mention above too, but it even not cover my case, U can see it all in first post, I install grub to partition, not to mbr:

elgentoo home # grub-install /dev/sda5
Installing for i386-pc platform.
grub-install: error: unknown filesystem.

I think its quite uncommon case and need someone more experienced then me, who dig a little in info and symptoms which i provide.

I'll just describe what i want to do next:
- I'll try compile grub with patch for inline data and try install-grub again
- then, I'll try to just remove (yes yes, and i think it will destroy fs, but want to try, if nothing else comes to my head, or any post with advice will not come) inline_data flag. No one answer, and i couldn't find information how to check if any data was stored in inode. It could be interesting experience.

9

Re: Inline data flag after resizing? can't repare grub

If you learn how to resolve the issue you are experiencing the please post the answer in this thread.  That can help others searching for answers to similar questions.

10

Re: Inline data flag after resizing? can't repare grub

No success, but here is what i have tried:

Install newest, unstable grub in gentoo repository (2.02~beta3), and install grub again. failed.

Try to patch grub with inline-data support. Couldn't do it.

Try to change inline-data flag:

elgentoo grub-2.00 # tune2fs  -O ^inline_data /dev/sda5
tune2fs 1.43.3 (04-Sep-2016)
Clearing filesystem feature 'inline_data' not supported.

Don't have time to play bit changes in superblock...but anyway i think it would destroy file system.

So i think I'll just back the data up, and recreate partition, and then the system.

Thank you for all your support gedakc.

If I can in any way help you improve the tools with any of my data, infos, let me know.

11

Re: Inline data flag after resizing? can't repare grub

That you fares for reporting back with the status of your attempts.

Your last suggestion of "just back the data up, and recreate partition, and then the system" should surely work.  :-)