LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-24-2016, 03:23 AM   #1
rsamurti
Member
 
Registered: Dec 2003
Location: Mysore
Distribution: Mandrake, Libranet, Slackware
Posts: 104

Rep: Reputation: 15
grub-mkconfig error in Slackware Current (64-bit)


Hello,

In Slackware Current of 20-May-2016, I am getting this error:

grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
/usr/sbin/grub-probe: error: unknown filesystem.

But, before this update, GRUB was working fine and it was detecting Windows 10 on the same hard disk.

When I run os-prober I get this message:

/dev/sda1:Windows 10 (loader):Windows:chain

Any pointers to correct this?

Thanks for your help.

Anand
 
Old 05-24-2016, 03:59 AM   #2
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,203

Rep: Reputation: 381Reputation: 381Reputation: 381Reputation: 381
problems in the e2fsprogs

http://www.linuxquestions.org/questi...es-4175580455/
 
Old 05-24-2016, 04:30 AM   #3
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,449
Blog Entries: 15

Rep: Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020
The new e2fsprogs package introduced some nasty issues detecting ext2/3/4 partitions with Grub-2.00. Currently the work around is to try and reconfigure /etc/mk2fs.conf to drop 64-bit partition support or use Grub-2.02~beta3.

Although tampering with the mk2fs.conf file is tempting and works, updating Grub is the more logical solution, and allows you to use 64-bit partitioning. Currently this is being discussed in the -Current updates topic, so right now, either solution is up to you.

The problem with reseting the configuration is you have to reformat any existing ext2/3/4 partitions to remove 64-bit default partitioning.

Last edited by ReaperX7; 05-24-2016 at 04:31 AM.
 
Old 05-24-2016, 06:17 AM   #4
DarkVision
Member
 
Registered: Jul 2007
Posts: 189

Rep: Reputation: Disabled
Quote:
Originally Posted by ReaperX7 View Post
Although tampering with the mk2fs.conf file is tempting and works, updating Grub is the more logical solution, and allows you to use 64-bit partitioning.
Still this does not only affect Grub2 but also SysLinux (at least the old version tested/used in this thread) i'm unsure if the solution to update Grub is the more logical solution.

Grub 2.02b3 is stable enough for me and some others and i really would like to have the update in -current, but maybe it's a good idea anyway to revert just the default ext4 features to pre-e2fsprogs-1.43 which would format by default with 32bit which allows up to 16Tb (AFAIK). If someone formats a partition >16Tb auto_64bit_support=1 in mke2fs.conf should use 64bit then. And with the "-O 64Bit" switch someone can force mke2fs to use 64Bit when formatting ext4 partitions <16Tb.

Maybe i'm wrong but i can't see a reason to have a >16Tb root/boot partition but this way we would not break existing boot loaders (any maybe other applications that make use of mkfs... gparted?).

Since there has been no reply from anyone of the dev-team about this yet i'm sure they are either on vacation or trying to make sure the solution they will provide to "fix" that will not break other things again

Just some other idea: Would it be possible to format a small partition for /boot with ext2/3 and the /-partition as ext4? Shouldn't that work with old grub2.00 and with ext4 with 64Bit also?
 
1 members found this post helpful.
Old 05-24-2016, 12:31 PM   #5
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 498
Blog Entries: 3

Rep: Reputation: 134Reputation: 134
There might be an option to pass to specify 32 or 64 bits since the previous conf file for mk2fs had a default 64-bit option set to 1, (I think the last update changed the config file, didn't really check, just gave a quick look to the diff from slackpkg) but I couldn't find it with a search. I will have a look to the man page when on my computer.
 
Old 05-24-2016, 01:05 PM   #6
DarkVision
Member
 
Registered: Jul 2007
Posts: 189

Rep: Reputation: Disabled
Quote:
Originally Posted by Tonus View Post
There might be an option to pass to specify 32 or 64 bits since the previous conf file for mk2fs had a default 64-bit option set to 1, (I think the last update changed the config file, didn't really check, just gave a quick look to the diff from slackpkg) but I couldn't find it with a search. I will have a look to the man page when on my computer.
The change was indeed that the mke2fs.conf file now include the option "64bit" as default option. if you have a look to "man ext4" you will see there is no 32bit option. The developers simply decided to use 64bit as default for now. On up-2-date distributions that might not be an issue, but Slackware is always a bit behind which caused grub-2.00 to fail on this new default setting for ext4. Same for syslinux (inlcuded in Slackware also, v4.06 for -current).

The old way users could force 64bit by using the -O switch. So it was already possible to use 64bit just not by the installer/setup from Slackware. Maybe it would be a good idea to add a question during setup "Do you want 64Bit-Support to support filesystems >16Tb? Warning! This could break old bootloaders!". If the user want that even with the old mke2fs.conf the installer/setup could format the target partition with "mkfs.ext4 -O 64bit /dev/xyz". Anyway... i still don't see a reason for a boot partition >16Tb?!?

I'm unsure what partitioning applications will use when formatting ext4 partitions. If they rely on the settings from mkfs.ext4 they will also format partitions by default with ext4. If you will use this formatted partition to install another distro and still have old grub2 installed it might fail to boot this partition. So it's up to the developers if they only update grub+syslinux to ext4/64bit versions or also revert this 64bit-default which is not really needed in my opinion. The only thing where this might be an issue is if you have a partition with less then 16Tb and without 64Bit support and want to increase it to a size >16Tb. I'm usure about that but with auto_64-bit_support=1 you would still have to reformat it, because from what i understand the auto-mode only works when you format the partition: If the partition is >16Tb it will automatically use 64Bit.

Here are (again) the differences between 1.42.13 and 1.43:
Code:
--- mke2fs.conf.in	2016-05-24 19:49:40.000000000 +0200
+++ mke2fs.conf	2016-05-20 18:56:57.000000000 +0200
@@ -11,12 +11,11 @@
 		features = has_journal
 	}
 	ext4 = {
-		features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
-		auto_64-bit_support = 1
+		features = has_journal,extent,huge_file,flex_bg,64bit,dir_nlink,extra_isize
 		inode_size = 256
 	}
 	ext4dev = {
-		features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
+		features = has_journal,extent,huge_file,flex_bg,inline_data,64bit,dir_nlink,extra_isize
 		inode_size = 256
 		options = test_fs=1
 	}
 
Old 05-24-2016, 01:27 PM   #7
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,203

Rep: Reputation: 381Reputation: 381Reputation: 381Reputation: 381
I see archlinux have exactly our old config in the new 1.43 e2fsprogs , at this point i edit the config and put exactly the old ...and all working again.

we need return to the old mke2fs.conf file config.
 
Old 05-24-2016, 02:17 PM   #8
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,449
Blog Entries: 15

Rep: Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020Reputation: 2020
SysLinux may need either a rebuild, patch, or update to work with 64-bit partitioning.

The author(s) may need to be contacted to inform the new issue.

However, if you want Grub-2.00 to work with the edited mk2fs.conf, the e2fsprogs used in the installation system will have to be reset as well, which is yet more work for Patrick and honestly, if the e2fsprogs is defaulting to 64-bit now, in the future will the edit to the configuration even be viable?

This is why it's more logical to update Grub and see if SysLinux may need an update or patch as well.

Slackware currently still uses syslinux-4.06 and the latest is 6.03 so there's the issue maybe.

Last edited by ReaperX7; 05-24-2016 at 02:26 PM.
 
Old 05-24-2016, 05:29 PM   #9
gordydawg
Member
 
Registered: Sep 2013
Distribution: slackware
Posts: 41

Rep: Reputation: Disabled
The recent 64 bit options in mke2fs affect not only Syslinux and Grub, but if some setups of even Lilo. When chaining from Slackware14.1 to 64current. I had to apply Darkvisions sed hack before selecting setup in -current. Only then, would it boot normally.

Solutions may require updating either all the bootloaders or modifiying mke2fs to have an option to accommodate the differences between very large hard drives and the rest during setup.



Edit 5/25/2016:

From the latest slackware64-current changelog:

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.

Last edited by gordydawg; 05-25-2016 at 07:44 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware 14.2 (current ) some 64 bit programs not working waynelloydsmith Slackware - Installation 8 03-26-2016 04:44 PM
Unable to run grub-mkconfig, can't get system to boot. orsty9001 Linux - Desktop 1 01-24-2016 04:11 PM
[SOLVED] grub-mkconfig menu changes mikenash Linux - Newbie 13 04-23-2015 04:49 PM
unrecognized initrd file with grub-mkconfig (Arch linux). hen770 Linux - General 2 09-06-2011 02:30 PM
Slackpkg slackware current-64 bit todders Slackware 7 07-15-2009 06:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:06 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration