[SOLVED] mkfs.ext4 issue? Slackware64 with Fri May 20 updates

dr.s · 05-22-2016, 10:30 PM

Not sure what went wrong here, I've set up a new test partition using gdisk then ran mkfs.ext4 as usual, done this successfully dozens of times in the past.

Code:

mkfs.ext4 -L test /dev/sda11

I reboot. I'm using Grub2 so I go into the grub console to verify

Code:

ls (hd0,gpt11)
  Partion hd0,11: No known filesystem detected - Partition start at ...

Re-tried with an old test partition on sda8, ran mkfs.ext4 on it, rebooted, went into the Grub2 console and got the same result, "No known filesystem".
Then I try again using the Slackware ISO install media, run setup, pick and format a partition etc then reboot into Grub2, same result, newer ext4 partitions are not recognizable. I give this another shot by rebooting into my work partition and trying ntfs this time:

Code:

mkfs.ntfs -f -L testing /dev/sda11

Another reboot, go into Grub2 console and this time Grub2 can see the partition and the filesystem on it

Code:

ls (hd0,gpt11)
  Partition hd0,11: Filesystem type ntfs - Label 'testing', UUID...

A couple more tries, using mkfs.ext2 and ext3, no issues, test partitions are visible in Grub2. Also, existing older ext4 partitions are recognizable in Grub2.
Any ideas?

bassmadrigal · 05-22-2016, 10:52 PM

It's due to the e2fsprogs update. No word yet on if it'll be reverted or grub updated.

http://www.linuxquestions.org/questi...4/#post5548681

You can fix it with a quick sed (provided by DarkVision) followed by reformatting the partition.

Code:

sed -i "s:,64bit::g" /etc/mke2fs.conf

ReaperX7 · 05-22-2016, 11:07 PM

I would update your Grub to the latest 2.02~beta3 if you have persistent issues.

USUARIONUEVO · 05-23-2016, 02:59 PM

There is the entiry old .conf file

it Works for me

Quote:

[defaults]
base_features = sparse_super,large_file,filetype,resize_inode,dir_index,ext_attr
default_mntopts = acl,user_xattr
enable_periodic_fsck = 0
blocksize = 4096
inode_size = 256
inode_ratio = 16384

[fs_types]
ext3 = {
features = has_journal
}
ext4 = {
features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
auto_64-bit_support = 1
inode_size = 256
}
ext4dev = {
features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
inode_size = 256
options = test_fs=1
}
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
floppy = {
blocksize = 1024
inode_size = 128
inode_ratio = 8192
}
big = {
inode_ratio = 32768
}
huge = {
inode_ratio = 65536
}
news = {
inode_ratio = 4096
}
largefile = {
inode_ratio = 1048576
blocksize = -1
}
largefile4 = {
inode_ratio = 4194304
blocksize = -1
}
hurd = {
blocksize = 4096
inode_size = 128
}

Tonus · 05-23-2016, 03:51 PM

Editing the mk2fs.conf with default 64-bit to 0 was enough for me : backed up the files on boot part, format the part, restore the files and the grub boots :-)

Thanks to DarkVision for showing the way !

dr.s · 05-24-2016, 07:01 AM

Thanks for your suggestions. The immediate workaround was to use ext3.

dr.s · 05-26-2016, 06:17 PM

Marking as solved.

Code:

Wed May 25 04:20:09 UTC 2016
...
a/e2fsprogs-1.43-x86_64-2.txz:  Rebuilt.
  Do not use 64-bit by default on ext4, since some bootloaders cannot handle
  it yet.  But use "auto_64-bit_support = 1", which will enable 64-bit if the
  number of blocks for the file system requires the feature to be enabled.