SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This worked until a few weeks ago and i have a older virtualbox machine with -current for 32bit and there grub-install works. This is the output from grub-probe on the older install of -current/32bit:
Quote:
ext2
I think this should be OK even if the partition is ext4.
I tried to install latest -current three times to make sure there was no problem during install but grub-install continue to fail.
I tried to downgrade e2fsprogs since that was a recent change but that did not help.
Any ideas what's wrong?
Last edited by DarkVision; 05-21-2016 at 08:14 AM.
I will re-install -current again and see if this is possible. Right now i found an old backup of the virtual machine with -current/64bit from 2016/05/04 where i had grub already installed. grub-probe detectes the filesystem as ext2.
I used slackpkg upgrade-all to update to -current as of today, created a new virtual disk with an ext4 filesystem. if i use grub-probe to check that partition it says "unknown filesystem".
If i format the partition with ext2 or ext3 instead of ext4 everything is fine. grub-probe detects the filesystem as "ext2".
Looks like a problem with the new e2fsprogs package. If SETUP is using the same programs from e2fsprogs-1.43 then the ext4 partition may be somehow incompatible with grub.
P.S. Just downgraded to e2fsprogs 1.42.13 and that did not help, i then replaced the mke2fs.conf with the one installed by the 1.42.13 package and then everything is fine again. I compared both configs:
OK, looks like adding 64bit to the mke2fs.conf from 1.42.13 then the ext4-parition will not be detected by grub. I upgraded to e2fsprogs 1.43 and removed 64bit support and then an ext4 partition is detected by grub-probe.
Do we really need 64Bit filesystem support for ext4? Or is there a patch for grub to detect those partitions? If not best thing i can do is to use ext3 when setting up -current since i like to have grub installed.
Fixed: just upgraded to grub 2.02beta3 and everything is fine now even with 64bit support. So i suggest an grub2-update for -current
Last edited by DarkVision; 05-21-2016 at 10:30 AM.
It could be a problem that I am facing while installing last current on a new ssd. Got to test with last grub as you did...
You can also try to format the target partition without 64bit support. Therefore you need to "patch" mke2fs.conf before running setup:
Quote:
I just did a reinstall of -current but before running setup to start the install i removed the 64bit option from mke2fs.conf:
Code:
sed -i "s:,64bit::g" /etc/mke2fs.conf
This way setup will format the ext4 partitions without 64bit like the previous version of e2fsprogs did. This fixed my issues with the old version of grub shipped with slackware-current.
But of course grub 2.02beta3 will work also. Still not sure if that 64bit-by-default option is a good idea.
Latest grub works fine. I upgraded my long time 64-14.1 and that installed the latest grub2 and did the the
Code:
grub-mkconfig -o /boot/grub/grub.cfg
and it did everything perfect. I clicked reboot. then selected the vimlinuz-huge even though I still had my old intrid. the it booted fine. Then I made my new intrid.gz. and edited my grub.cfg like I wanted it. So it would select the vmlinuz-generic. No problems on none of my machines.
@Drakeo : what I've understood is that there's a problem while you format in ext4 with the new e2fs which defaults to 64 bits. Then the actual slackware grub will not boot. Your boot partition might have been formatted in 32 bits with previous e2fs utility.
@Tonus: From what i understand is that Drakeo updated to latest grub which is 2.02beta3. That update fixes the 64bit issue for -current but it is good to hear that this update does even work for 14.1. Hopefully grub2-update will not break other things
Last edited by DarkVision; 05-22-2016 at 04:25 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.