On Mon, 2014-07-28 at 21:14 -0300, Cesar Linhares Rosa wrote:
> Hello Christopher.
> 
> 
> I had trouble once with GRUB 2 for booting with this message "unknown
> filesystem". It was a while ago, but as far as I remember, the GRUB
> files on the /boot partition aren't right, so an grub-intall on the
> chroot partition solve. Don't forget to mount
> the /dev /dev/pts /proc /sys on the partition that you'll install GRUB
> before chroot.
> 
> 
> Is the grub.cfg pointing to the right partition at the 'set root'
> option?
> 
> What file-system is the boot partition? Is EXT4?
> 
> When the 'BIOS' boot from the external hard drive, it is 'hd0' or
> 'hd1' for GRUB?
> 
> 
> 
> If possible, send your grub.cfg and the partition table with the fdisk
> command print, so I can try to help you in your setup...
> 
> 
> 
> 
> My computer uses GPT partition. I will try to make an usb flash drive
> bootable with the version of LFS that I'm using, an see if I can boot
> from it. Then I will run the grub-install command on the partition
> instead of the device to see what happens.
> 
> 
> Below I'll send some of my system configuration. I hope it can help
> you:
> 
> 
> $ cat /boot/grub/grub.cfg
> 
> menuentry "LFS GNU/Linux 2014-04-21, kernel 3.15.7 (on /dev/sda2)"
> --class gnu-linux --class gnu --class os {
>         insmod part_gpt
>         insmod ext2
>         set root='(hd0,gpt2)'
>         linux /boot/vmlinuz-3.15.7 root=/dev/sda2
> }
> 
> 
> # fdisk /dev/sda
> 
> Welcome to fdisk (util-linux 2.24.2).
> Changes will remain in memory only, until you decide to write them.
> Be careful before using the write command.
> 
> 
> Command (m for help): p
> Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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: gpt
> Disk identifier: A49FCFCE-6DAA-4AB5-AFFC-A51B5002FC48
> 
> Device           Start          End   Size Type
> /dev/sda1         2048    130025471    62G Linux filesystem
> /dev/sda2    130025472    260048895    62G Linux filesystem
> /dev/sda3    260048896    390072319    62G Linux filesystem
> /dev/sda4    390072320    486541311    46G Linux filesystem
> /dev/sda5    486541312    488384511   900M Linux swap
> /dev/sda6    488384512    488397134   6.2M BIOS boot partition
> 
> 
> 
> ### Files on /boot/grub... Maybe you can find something missing...
> 
> $ find /boot/grub/
> 
> /boot/grub/
> /boot/grub/i386-pc
> /boot/grub/i386-pc/raid6rec.mod
> /boot/grub/i386-pc/fs.lst
> /boot/grub/i386-pc/tftp.mod
> /boot/grub/i386-pc/aout.mod
> /boot/grub/i386-pc/password.mod
> /boot/grub/i386-pc/videotest.mod
> /boot/grub/i386-pc/cpio.mod
> /boot/grub/i386-pc/video_fb.mod
> /boot/grub/i386-pc/hashsum.mod
> /boot/grub/i386-pc/search_fs_uuid.mod
> /boot/grub/i386-pc/part_sun.mod
> /boot/grub/i386-pc/gfxmenu.mod
> /boot/grub/i386-pc/gcry_camellia.mod
> /boot/grub/i386-pc/cat.mod
> /boot/grub/i386-pc/minix_be.mod
> /boot/grub/i386-pc/lspci.mod
> /boot/grub/i386-pc/pxe.mod
> /boot/grub/i386-pc/lsapm.mod
> /boot/grub/i386-pc/partmap.lst
> /boot/grub/i386-pc/ohci.mod
> /boot/grub/i386-pc/fat.mod
> /boot/grub/i386-pc/vga_text.mod
> /boot/grub/i386-pc/pxeboot.img
> /boot/grub/i386-pc/drivemap.mod
> /boot/grub/i386-pc/part_plan.mod
> /boot/grub/i386-pc/normal.mod
> /boot/grub/i386-pc/diskfilter.mod
> /boot/grub/i386-pc/zfscrypt.mod
> /boot/grub/i386-pc/date.mod
> /boot/grub/i386-pc/all_video.mod
> /boot/grub/i386-pc/adler32.mod
> /boot/grub/i386-pc/odc.mod
> /boot/grub/i386-pc/gfxterm.mod
> /boot/grub/i386-pc/gdb.mod
> /boot/grub/i386-pc/part_gpt.mod
> /boot/grub/i386-pc/ufs2.mod
> /boot/grub/i386-pc/elf.mod
> /boot/grub/i386-pc/mdraid1x.mod
> /boot/grub/i386-pc/functional_test.mod
> /boot/grub/i386-pc/minix3_be.mod
> /boot/grub/i386-pc/part_dvh.mod
> /boot/grub/i386-pc/affs.mod
> /boot/grub/i386-pc/lvm.mod
> /boot/grub/i386-pc/bfs.mod
> /boot/grub/i386-pc/terminfo.mod
> /boot/grub/i386-pc/memrw.mod
> /boot/grub/i386-pc/usb_keyboard.mod
> /boot/grub/i386-pc/backtrace.mod
> /boot/grub/i386-pc/password_pbkdf2.mod
> /boot/grub/i386-pc/gcry_tiger.mod
> /boot/grub/i386-pc/datetime.mod
> /boot/grub/i386-pc/squash4.mod
> /boot/grub/i386-pc/ufs1.mod
> /boot/grub/i386-pc/xnu_uuid.mod
> /boot/grub/i386-pc/part_msdos.mod
> /boot/grub/i386-pc/gcry_sha1.mod
> /boot/grub/i386-pc/exfctest.mod
> /boot/grub/i386-pc/afs.mod
> /boot/grub/i386-pc/gcry_cast5.mod
> /boot/grub/i386-pc/net.mod
> /boot/grub/i386-pc/moddep.lst
> /boot/grub/i386-pc/play.mod
> /boot/grub/i386-pc/testload.mod
> /boot/grub/i386-pc/configfile.mod
> /boot/grub/i386-pc/btrfs.mod
> /boot/grub/i386-pc/parttool.lst
> /boot/grub/i386-pc/pbkdf2.mod
> /boot/grub/i386-pc/usbms.mod
> /boot/grub/i386-pc/multiboot2.mod
> /boot/grub/i386-pc/hfs.mod
> /boot/grub/i386-pc/gcry_whirlpool.mod
> /boot/grub/i386-pc/gcry_serpent.mod
> /boot/grub/i386-pc/part_apple.mod
> /boot/grub/i386-pc/vga.mod
> /boot/grub/i386-pc/exfat.mod
> /boot/grub/i386-pc/bitmap.mod
> /boot/grub/i386-pc/gcry_md4.mod
> /boot/grub/i386-pc/msdospart.mod
> /boot/grub/i386-pc/usbtest.mod
> /boot/grub/i386-pc/gptsync.mod
> /boot/grub/i386-pc/setpci.mod
> /boot/grub/i386-pc/http.mod
> /boot/grub/i386-pc/luks.mod
> /boot/grub/i386-pc/gcry_seed.mod
> /boot/grub/i386-pc/biosdisk.mod
> /boot/grub/i386-pc/pxechain.mod
> /boot/grub/i386-pc/bsd.mod
> /boot/grub/i386-pc/scsi.mod
> /boot/grub/i386-pc/usbserial_pl2303.mod
> /boot/grub/i386-pc/search_fs_file.mod
> /boot/grub/i386-pc/lnxboot.img
> /boot/grub/i386-pc/minicmd.mod
> /boot/grub/i386-pc/xzio.mod
> /boot/grub/i386-pc/gcry_sha512.mod
> /boot/grub/i386-pc/acpi.mod
> /boot/grub/i386-pc/diskboot.img
> /boot/grub/i386-pc/loopback.mod
> /boot/grub/i386-pc/minix.mod
> /boot/grub/i386-pc/png.mod
> /boot/grub/i386-pc/serial.mod
> /boot/grub/i386-pc/minix3.mod
> /boot/grub/i386-pc/usbserial_ftdi.mod
> /boot/grub/i386-pc/multiboot.mod
> /boot/grub/i386-pc/crc64.mod
> /boot/grub/i386-pc/minix2_be.mod
> /boot/grub/i386-pc/fshelp.mod
> /boot/grub/i386-pc/command.lst
> /boot/grub/i386-pc/efiemu.mod
> /boot/grub/i386-pc/loadenv.mod
> /boot/grub/i386-pc/sleep.mod
> /boot/grub/i386-pc/time.mod
> /boot/grub/i386-pc/bufio.mod
> /boot/grub/i386-pc/minix2.mod
> /boot/grub/i386-pc/gcry_arcfour.mod
> /boot/grub/i386-pc/read.mod
> /boot/grub/i386-pc/xfs.mod
> /boot/grub/i386-pc/hexdump.mod
> /boot/grub/i386-pc/parttool.mod
> /boot/grub/i386-pc/gzio.mod
> /boot/grub/i386-pc/part_bsd.mod
> /boot/grub/i386-pc/pci.mod
> /boot/grub/i386-pc/raid5rec.mod
> /boot/grub/i386-pc/memdisk.mod
> /boot/grub/i386-pc/tga.mod
> /boot/grub/i386-pc/video_bochs.mod
> /boot/grub/i386-pc/true.mod
> /boot/grub/i386-pc/zfsinfo.mod
> /boot/grub/i386-pc/setjmp.mod
> /boot/grub/i386-pc/sfs.mod
> /boot/grub/i386-pc/terminal.mod
> /boot/grub/i386-pc/core.img
> /boot/grub/i386-pc/hdparm.mod
> /boot/grub/i386-pc/sendkey.mod
> /boot/grub/i386-pc/udf.mod
> /boot/grub/i386-pc/gcry_blowfish.mod
> /boot/grub/i386-pc/mmap.mod
> /boot/grub/i386-pc/bitmap_scale.mod
> /boot/grub/i386-pc/cmostest.mod
> /boot/grub/i386-pc/keystatus.mod
> /boot/grub/i386-pc/regexp.mod
> /boot/grub/i386-pc/crypto.lst
> /boot/grub/i386-pc/video.lst
> /boot/grub/i386-pc/crypto.mod
> /boot/grub/i386-pc/gcry_md5.mod
> /boot/grub/i386-pc/priority_queue.mod
> /boot/grub/i386-pc/linux16.mod
> /boot/grub/i386-pc/ahci.mod
> /boot/grub/i386-pc/tar.mod
> /boot/grub/i386-pc/search_label.mod
> /boot/grub/i386-pc/ehci.mod
> /boot/grub/i386-pc/echo.mod
> /boot/grub/i386-pc/usb.mod
> /boot/grub/i386-pc/trig.mod
> /boot/grub/i386-pc/cmp.mod
> /boot/grub/i386-pc/ata.mod
> /boot/grub/i386-pc/gcry_rijndael.mod
> /boot/grub/i386-pc/iorw.mod
> /boot/grub/i386-pc/gcry_sha256.mod
> /boot/grub/i386-pc/search.mod
> /boot/grub/i386-pc/relocator.mod
> /boot/grub/i386-pc/halt.mod
> /boot/grub/i386-pc/ext2.mod
> /boot/grub/i386-pc/part_acorn.mod
> /boot/grub/i386-pc/datehook.mod
> /boot/grub/i386-pc/video.mod
> /boot/grub/i386-pc/chain.mod
> /boot/grub/i386-pc/romfs.mod
> /boot/grub/i386-pc/gcry_des.mod
> /boot/grub/i386-pc/ntfs.mod
> /boot/grub/i386-pc/gcry_rfc2268.mod
> /boot/grub/i386-pc/nilfs2.mod
> /boot/grub/i386-pc/gcry_rmd160.mod
> /boot/grub/i386-pc/geli.mod
> /boot/grub/i386-pc/terminal.lst
> /boot/grub/i386-pc/jfs.mod
> /boot/grub/i386-pc/iso9660.mod
> /boot/grub/i386-pc/lzma_decompress.img
> /boot/grub/i386-pc/legacycfg.mod
> /boot/grub/i386-pc/cryptodisk.mod
> /boot/grub/i386-pc/newc.mod
> /boot/grub/i386-pc/video_cirrus.mod
> /boot/grub/i386-pc/linux.mod
> /boot/grub/i386-pc/pata.mod
> /boot/grub/i386-pc/vbe.mod
> /boot/grub/i386-pc/font.mod
> /boot/grub/i386-pc/videoinfo.mod
> /boot/grub/i386-pc/boot.mod
> /boot/grub/i386-pc/help.mod
> /boot/grub/i386-pc/plan9.mod
> /boot/grub/i386-pc/zfs.mod
> /boot/grub/i386-pc/kernel.img
> /boot/grub/i386-pc/jpeg.mod
> /boot/grub/i386-pc/lzopio.mod
> /boot/grub/i386-pc/cs5536.mod
> /boot/grub/i386-pc/cpuid.mod
> /boot/grub/i386-pc/uhci.mod
> /boot/grub/i386-pc/cdboot.img
> /boot/grub/i386-pc/usbserial_common.mod
> /boot/grub/i386-pc/hfsplus.mod
> /boot/grub/i386-pc/ntfscomp.mod
> /boot/grub/i386-pc/part_sunpc.mod
> /boot/grub/i386-pc/keylayouts.mod
> /boot/grub/i386-pc/probe.mod
> /boot/grub/i386-pc/at_keyboard.mod
> /boot/grub/i386-pc/blocklist.mod
> /boot/grub/i386-pc/boot.img
> /boot/grub/i386-pc/test_blockarg.mod
> /boot/grub/i386-pc/test.mod
> /boot/grub/i386-pc/lsacpi.mod
> /boot/grub/i386-pc/ntldr.mod
> /boot/grub/i386-pc/part_amiga.mod
> /boot/grub/i386-pc/ldm.mod
> /boot/grub/i386-pc/cpio_be.mod
> /boot/grub/i386-pc/reboot.mod
> /boot/grub/i386-pc/xnu.mod
> /boot/grub/i386-pc/freedos.mod
> /boot/grub/i386-pc/ls.mod
> /boot/grub/i386-pc/extcmd.mod
> /boot/grub/i386-pc/lsmmap.mod
> /boot/grub/i386-pc/mdraid09_be.mod
> /boot/grub/i386-pc/dm_nv.mod
> /boot/grub/i386-pc/hello.mod
> /boot/grub/i386-pc/gettext.mod
> /boot/grub/i386-pc/gcry_twofish.mod
> /boot/grub/i386-pc/gcry_crc.mod
> /boot/grub/i386-pc/reiserfs.mod
> /boot/grub/i386-pc/mdraid09.mod
> /boot/grub/locale
> /boot/grub/locale/pa.mo
> /boot/grub/locale/it.mo
> /boot/grub/locale/de.mo
> /boot/grub/locale/da.mo
> /boot/grub/locale/[email protected]
> /boot/grub/locale/nl.mo
> /boot/grub/locale/ru.mo
> /boot/grub/locale/ca.mo
> /boot/grub/locale/[email protected]
> /boot/grub/locale/[email protected]
> /boot/grub/locale/id.mo
> /boot/grub/locale/vi.mo
> /boot/grub/locale/zh_TW.mo
> /boot/grub/locale/ast.mo
> /boot/grub/locale/ja.mo
> /boot/grub/locale/pl.mo
> /boot/grub/locale/fi.mo
> /boot/grub/locale/[email protected]
> /boot/grub/locale/[email protected]
> /boot/grub/locale/sv.mo
> /boot/grub/locale/hu.mo
> /boot/grub/locale/fr.mo
> /boot/grub/locale/[email protected]
> /boot/grub/locale/eo.mo
> /boot/grub/locale/uk.mo
> /boot/grub/locale/[email protected]
> /boot/grub/locale/de_CH.mo
> /boot/grub/locale/zh_CN.mo
> /boot/grub/grubenv
> /boot/grub/grub.cfg
> 
> 
> 
> Good Luck! :)
> 
> 
> 
> PS: I'll try to build xorg-server-1.16.0 on my laptop with intel
> driver to see if I can get "screens". When I did it, I share the
> results.
> 
> 
> Cesar
> 
> 
> 
> On Mon, Jul 28, 2014 at 3:40 AM, Christopher Gregory
> <[email protected]> wrote:
>         Hello Everyone,
>         
>         This is going to be long and somewhat complicated.
>         
>         A bit of background:
>         
>         I found that xorg-server 1.16.0 would not detect any screens
>         when
>         booting, so I went hunting on google and found that in at
>         least one
>         instance that it was due to dri2 not being loaded in the
>         display driver.
>         
>         I have an intel i915 onboard (as this is an hp compaq
>         laptop).  I then
>         checked on xorgs site and found that they had a later version
>         of the
>         devleopment driver that we have listed to use in the TRUNK
>         book.
>         
>         After compiling that along with re-compiling the vesa,
>         synaptics, udev,
>         drivers I rebooted and the same error came up.
>         
>         I decided to go and update my kernel to the latest version and
>         this is
>         when my true nightmare began.
>         
>         My setup is possibly somewhat unique.
>         
>         I am using  GUID Partition Table (gpt) for my drives and using
>         UUID and
>         PARTUUID to identify the partitions in fstab and grub.cfg.
>         
>         This requires a separate grub_bios partition of between 1 and
>         2mb.
>         Using this eliminates the need for the extended partitions as
>         everything
>         is created as primary partitions.
>         
>         I have an internal drive on my laptop and an external USB
>         drive.
>         
>         I went ahead and did grub-install /dev/sdb9 at first as I was
>         over tired
>         when doing it.  That of course was the wrong command to use,
>         it should
>         have been /dev/sdb, but in my tired state I very stupidly
>         used:
>         
>         grub-install -f /dev/sdb9
>         
>         Upon re-booting I got the glorious error message of unknown
>         filesystem.
>         
>         Again instead of leaving it at that point, I booted the
>         internal
>         harddrive and went ahead and messed things up with trying to
>         do a
>         grub-install /dev/sdb from there to see if that would work,
>         but still
>         the nasty error.
>         
>         I have since done the following on the external drive:
>         
>         1) Deleted the grub_bios partition and re-created it.
>         
>         2) Deleted the /boot partition and re-created it.
>         
>         3) ran grub-install /dev/sdb
>         
>         4) corrected the PARTUUID line in grub.cfg and the UUID
>         in /etc/fstab
>         
>         I then re-booted and got exactly the same error about unknown
>         file
>         system.
>         
>         I then entered charroot and:
>         
>         1) Went to re-compile and re-install grub from the source
>         tarball,
>         following the instructions from development LFS-SYSTEMD as I
>         am on a
>         systemd system.
>         
>         This lead to another problem that I can not recall having,
>         namely grub
>         would NOT compile.  Another google search revealed that there
>         is a bug
>         in grub-mkfont.c
>         
>         http://patchwork.openwrt.org/patch/4480/
>         
>         I manually edited the affected file and compilation completed.
>         
>         After re-installing grub and re-creating grub.cfg, whilst I
>         was still in
>         char-root I went ahead and re-compiled the kernel.
>         
>         After installing the new kernel I re-booted and I STILL get
>         the unknown
>         file system error.
>         
>         I just do not know what else to try.  I have already deleted
>         the content
>         of /tmp.
>         
>         Oh and I also managed to screw up grub on /dev/sda but have
>         now got that
>         working correctly.
>         
>         Please also bear in mind that this base build was done by
>         JHALFS and it
>         is what I have built the development gnome section of the new
>         BLFS
>         systemd book on.
>         
>         If someone could point out what to try next it would be
>         greatly
>         appreciated.
>         
>         Regards,
>         
>         Christopher.
>         
>         --
>         http://lists.linuxfromscratch.org/listinfo/blfs-dev
>         FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>         Unsubscribe: See the above information page
> 
> 

Hello Cesar,

Many thanks for your reply.

I have managed to solve it.  I had totally failed to see that I had
messed up the set root entries.  After I had deleted both grub_bios
partitions and both /boot partitions and re-created them, I failed to
notice my error for hours, even though it was staring me in the face.

After I solved that I learnt something else about grub.  You can only
seem to have ONE boot partition per drive.  My setup is so that I have
two separate installations of lfs/blfs on my external drive, and when I
added the second boot partition it went back to the crazy unrecognised
file system error.

Out of shear desperation I copied the kernel image for the installation
I am using to edit the BLFS systemd/gnome book onto the first boot
partition and added a second menu entry for it, commented out the boot
partition in fstab and when I rebooted everything was normal again.

Hopefully this posting will help others who have a similar thought about
adding a second boot partition.

As far as xorg-server 1.16.0 is concerned, its a no go.  Even with the
latest stable kernel, and the latest intel driver from the
xorg-developers it just gives a black screen.  At least that was an
improvement over the no screens found, but at this stage I have reverted
to xorg-server 1.15.1.

Regards,

Christopher.

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to