LinuxQuestions.org
Review your favorite Linux distribution.
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 04-25-2020, 02:28 PM   #1
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,542
Blog Entries: 1

Rep: Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908
F2FS and LILO, "Fatal: hole found in map file (zero sector)"


The short version,
Formatted the SSD with F2FS, created lilo.conf, but the attempted installation (of lilo) returned the error:

Fatal: Hole found in map file (zero sector)

This does not happen when using ext4. I've spent an hour or so researching a solution, but only have found "report this error."

Any ideas would be greatly appreciated.
For now the machine is being booted from a USB stick.
Other than that, F2FS runs just fine.

Last edited by cwizardone; 04-26-2020 at 11:34 AM.
 
Old 04-25-2020, 02:57 PM   #2
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 16,382

Rep: Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496
I found this: https://f2fs.wiki.kernel.org/
grub does not support f2fs, probably the same reason is valid for lilo (but probably not).
I think it should have been built into lilo (I mean a basic filesystem support), but it is missing.
 
1 members found this post helpful.
Old 04-25-2020, 03:05 PM   #3
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,864

Rep: Reputation: Disabled
Quote:
Originally Posted by pan64 View Post
I found this: https://f2fs.wiki.kernel.org/
grub does not support f2fs, probably the same reason is valid for lilo (but probably not)
This information is out of date, grub now does support f2fs (since release 2.04, IIRC).
Code:
didier[~]$ locate f2fs.module| grep ^/usr
/usr/lib64/grub/i386-pc/f2fs.module
/usr/lib64/grub/i386-efi/f2fs.module
/usr/lib64/grub/x86_64-efi/f2fs.module
/usr/lib64/grub/x86_64-emu/f2fs.module
PS commit. So this has been the case since two years in Git master and since 4 Jul 2019 for the released archive.

PS2 Support is now also available in Debian.

Last edited by Didier Spaier; 04-25-2020 at 03:16 PM.
 
2 members found this post helpful.
Old 04-25-2020, 03:16 PM   #4
pan64
LQ Guru
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 16,382

Rep: Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496Reputation: 5496
Hm. Thanks. The internet is full of outdated info. So it was now a wrong example.
 
Old 04-25-2020, 03:33 PM   #5
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,864

Rep: Reputation: Disabled
Quote:
Originally Posted by pan64 View Post
The internet is full of outdated info.
Right. In this case, ironically the outdated information has been written by the same person (Jaegeuk Kim) who later authored the module. Which is just one more illustration that developers prefer coding than writing documentation. In the specific case of grub, though, Daniel Kiper generally won't accept a patch for a new or modified feature if not at least properly documented in the code. And "info grub" in grub 2.06 will be way more complete and accurate, thanks mostly to the hard work done by Hans Ulrich Niedermann.
 
1 members found this post helpful.
Old 04-25-2020, 04:29 PM   #6
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,542

Original Poster
Blog Entries: 1

Rep: Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908
I've continued to research the problem, but haven't found much in the way of a solution.

It would appear that if I want to use lilo I could create a small /boot partition, format it with ext4, and have lilo boot from that partition.
Would that work?
If so, how big of a partition would be needed?

Last edited by cwizardone; 04-25-2020 at 04:34 PM.
 
Old 04-25-2020, 05:00 PM   #7
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,864

Rep: Reputation: Disabled
Quote:
Originally Posted by cwizardone View Post
It would appear that if I want to use lilo I could create a small /boot partition, format it with ext4, and have lilo boot from that partition.
Would that work?
I guess it would. And then you could use an ext2 file system as well, as you won't need a journal. But indeed ext4 won't hurt
Quote:
If so, how big of a partition would be needed?
Big enough to host your kernels and initrds. To be safe I'd say 200M.
 
1 members found this post helpful.
Old 04-25-2020, 05:14 PM   #8
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,542

Original Poster
Blog Entries: 1

Rep: Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908
Quote:
Originally Posted by Didier Spaier View Post
........Big enough to host your kernels and initrds. To be safe I'd say 200M.
Presently, the /boot directory with two installed kernels is 91.7 megs, so 200 megs sounds just about right. Gives one a
little "wiggle room."

Thanks.

Last edited by cwizardone; 04-25-2020 at 05:15 PM.
 
Old 04-25-2020, 09:02 PM   #9
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,542

Original Poster
Blog Entries: 1

Rep: Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908
Well, that didn't work.
While working with F2FS over the last couple of days I've done a few "fresh installs" and F2FS is obviously faster than ext4. No doubt about it.
I'm tempted to go back to booting off a USB stick just for the performance improvement.... well... almost.

We'll see.....
 
Old 04-25-2020, 09:28 PM   #10
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,864

Rep: Reputation: Disabled
Why not use grub instead of lilo in this case? This should work if running -current. If running 14.2 you could build grub from the current sources, or use this package from Slint, md5.

Last edited by Didier Spaier; 04-25-2020 at 09:32 PM.
 
1 members found this post helpful.
Old 04-25-2020, 09:31 PM   #11
BrianW
Member
 
Registered: Jul 2003
Location: Montana
Distribution: Slackware
Posts: 271

Rep: Reputation: Disabled
I have no words of wisdom for you, only sympathy. I just battled this a week ago with a secondhand HP probook 4530s and Intel SSD. lilo only wanted to install cleanly if Windows was installed first. If I dd'ed the drive and formatted as a single partition ext4 (GPT or MBR), lilo threw the aforementioned error and I never could actually find much about the error, like you.

I gave up on lilo, enabled UEFI and all seems to be fine minus the laptop being picky about the /EFI/BOOT structure.
 
1 members found this post helpful.
Old 04-25-2020, 09:48 PM   #12
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,542

Original Poster
Blog Entries: 1

Rep: Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908
Quote:
Originally Posted by Didier Spaier View Post
Why not use grub instead of lilo in this case? This should work if running -current. If running 14.2 you could build grub from the current sources, or use this package from Slint, md5.
Yes, I've given grub some consideration and it would, most likely work, but I'm big fan of "KISS" and would prefer to use lilo, if at all possible.
The motherboard supports all that newfangled stuff like uefi, etc., so I might have to bite the bullet.
We'll see...

Last edited by cwizardone; 04-25-2020 at 09:50 PM.
 
Old 04-25-2020, 09:54 PM   #13
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,542

Original Poster
Blog Entries: 1

Rep: Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908Reputation: 3908
Quote:
Originally Posted by BrianW View Post
I have no words of wisdom for you, only sympathy. I just battled this a week ago with a secondhand HP probook 4530s and Intel SSD. lilo only wanted to install cleanly if Windows was installed first. If I dd'ed the drive and formatted as a single partition ext4 (GPT or MBR), lilo threw the aforementioned error and I never could actually find much about the error, like you.

I gave up on lilo, enabled UEFI and all seems to be fine minus the laptop being picky about the /EFI/BOOT structure.
Thanks for taking the time to reply.
Things may have changed, but back when I use to dual boot ms-windows, the only way I could get it to work was to install windows first. No choice. Their way or the highway.
 
Old 04-26-2020, 03:13 AM   #14
ZhaoLin1457
Member
 
Registered: Jan 2018
Posts: 628

Rep: Reputation: 729Reputation: 729Reputation: 729Reputation: 729Reputation: 729Reputation: 729Reputation: 729
You may call me Captain Obvious, but I cannot help to not notice two things:

1. The F2FS is a quite new filesystem, then I would put my bet on that that ancient technology named LILO have no support for it. Or, no one bothered yet and will not bother to add it, just like nobody bothered to build a bigger pyramid than the Egyptian ones, even certainly today we are quite capable to do that...

2. Nobody stops Mr. Cwizardone to use a dedicated /boot partition formatted with one of LILO supported filesystems, like is ext4fs. And certainly a little 500MB partition formatted with ext4fs would be much much much more robust than a FAT32 one, like are the ones which Microsoft Overlords blessed us for EFI boot.

PS. Imitating the Darth's style of speaking was intentional and a hattip to OP, who I know that was a good friend of this particular forum member with unconventional ways of thinking.

Last edited by ZhaoLin1457; 04-26-2020 at 03:20 AM.
 
1 members found this post helpful.
Old 04-26-2020, 04:38 AM   #15
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 491

Rep: Reputation: 118Reputation: 118
Just a couple of observations:

grub contains simplified filesystem drivers that load the file at boot time as if the "real" filesystem driver was present. Hence filesystem support must be included in the grub source code.

lilo creates a block list at installation time, essentially via an ioctl(FIBMAP) call. At boot time it only loads the block list. Hence lilo generally does NOT require filesystem support in the source code.

It so happens that some filesystems do not or not fully support FIBMAP (for instance because they reserve the right to change file locations on the fly). Btrfs is known for that. I am not sure about F2FS.

In closing, the advice of using a small ext4 boot partition is probably a good one.
 
2 members found this post helpful.
  


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] No package 'x11' found No package 'xext' found No package 'xdamage' found No package 'xfixes' found No package 'x11-xcb' found Jigsaw Linux From Scratch 14 02-23-2021 08:35 PM
lilo 23.2: Fatal: trying to map files from unnamed device 0x001 stf92 Debian 6 04-23-2014 06:26 PM
Warning: The boot sector and map file are on different disks (lilo). stf92 Slackware - Installation 5 07-10-2012 09:13 AM
lilo fatal: first sector..... HmmLinux Linux - General 7 01-08-2009 12:10 PM
"Fatal: empty map section" lilo error kaz2100 Linux - Software 2 12-25-2007 09:42 AM

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

All times are GMT -5. The time now is 11:28 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
Open Source Consulting | Domain Registration