You are not logged in.

#1 2012-06-16 18:42:07

slughappy1
Member
Registered: 2009-03-20
Posts: 75

Unknown filesystem when mounting ntfs?

I just upgraded to GRUB2 from GRUB and now I can't boot into my Windows 7 install. When I try to use the command grub-probe to find the uuid of the partition I get the following error.

#  grub-probe --target=fs_uuid /run/media/jason/DE5A335A5A332EA1/bootmgr 
grub-probe: error: unknown filesystem.

I can mount it using Nautilus and I can browse the filesystem, but I can't seem to find out what the problem is. I installed ntfs-config and when I try load that I get a popup that says READ/WRITE NTFS drivers not installed. I'm not sure how they are not installed when I have ntfs-3g installed and I can mount and write to the drive.

Any ideas?

Offline

#2 2012-06-16 22:09:18

DSpider
Member
From: Romania
Registered: 2009-08-23
Posts: 2,273

Re: Unknown filesystem when mounting ntfs?

Run:

$ sudo fdisk -l

GRUB 2 starts counting drives from 0, partitions from 1: https://wiki.archlinux.org/index.php/GR … gacy_users

So create a "/etc/grub.d/11_Windows" file with:

#! /bin/sh -e
echo "Adding Windows 7.." >&2
cat << EOF
menuentry "Windows 7" {
set root=(hd0,1)     <--- You'll need to point this at the 100 MB "System Reserved" partition if you use one.
chainloader +1
}
EOF

Set the executable bit.

$ sudo chmod +x /etc/grub.d/11_Windows

And re-generate the .cfg.

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

GRUB 2 is definitely a step in the WRONG direction if you want to stick to the KISS principle. I would recommend Syslinux over GRUB 2 any day because it uses only one configuration file (just like GRUB Legacy) instead of many (like the /etc/default/grub file and the stuff from the /etc/grub.d folder).


"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

Offline

#3 2012-06-16 22:39:33

slughappy1
Member
Registered: 2009-03-20
Posts: 75

Re: Unknown filesystem when mounting ntfs?

I have Windows installed on the first partition without the use of the 100 MB System Reserved partition. fdisk -l gave me the results of

$ sudo fdisk -l
Password: 

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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
Disk identifier: 0x000b69c2

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   245762369   122881153+   7  HPFS/NTFS/exFAT
/dev/sda2       245764096   246173695      204800   83  Linux
/dev/sda3       620943360   625139711     2098176   82  Linux swap / Solaris
/dev/sda4       246173696   620943359   187384832   83  Linux

Partition table entries are not in disk order

So when following your instructions I get to the last step to generate grub and I get the following error

#  grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-linux-ck
Found initrd image: /boot/initramfs-linux-ck.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Adding Windows 7..
  No volume groups found
grub-probe: error: unknown filesystem.
done

If I try and install Syslinux would I have any problems because of this unknown filesystem error?

Last edited by slughappy1 (2012-06-16 22:40:17)

Offline

#4 2012-06-16 23:15:03

DSpider
Member
From: Romania
Registered: 2009-08-23
Posts: 2,273

Re: Unknown filesystem when mounting ntfs?

I'm not sure. It could be because of the "Partition table entries are not in disk order" warning from fdisk.

Volume groups usually refer to LVM setups. Do you use LVM? Post your /etc/rc.conf and /etc/mkinitcpio.conf (use pastie.org, please).


Oh, and if you wanna try Syslinux, boot the Arch LiveCD (either from a disc or USB stick, it doesn't matter) and press the Tab key over the "Boot existing OS" entry. Then change "hd0 0" to "hd0 1" and press enter. Easy.       Edit: Or it could be "hd1 1" if it's from a USB stick - meaning the second disk since the stick would be the first boot device in the BIOS. Similar to GRUB 2, Syslinux starts counting drives from 0 and partitions from 1.

Last edited by DSpider (2012-06-16 23:32:01)


"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

Offline

#5 2012-06-16 23:28:39

slughappy1
Member
Registered: 2009-03-20
Posts: 75

Re: Unknown filesystem when mounting ntfs?

I didn't use LVM. I made 4 partitions:
     1-Windows7
     2-/boot (ext2)
     3-swap
     4-/ (ext4)

Rc.conf -> http://pastie.org/4100248
mkinitcpio.conf -> http://pastie.org/4100252

I'll try booting from a usb in a bit

Offline

#6 2012-06-16 23:43:42

DSpider
Member
From: Romania
Registered: 2009-08-23
Posts: 2,273

Re: Unknown filesystem when mounting ntfs?

Why is your mkinitcpio.conf fragmented like that?

http://pastie.org/4100252


"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

Offline

#7 2012-06-16 23:49:38

slughappy1
Member
Registered: 2009-03-20
Posts: 75

Re: Unknown filesystem when mounting ntfs?

DSpider wrote:

Why is your mkinitcpio.conf fragmented like that?

http://pastie.org/4100252

I have no idea why pastie is doing that it should look like

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="i915"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
#    FILES="/etc/modprobe.d/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect pata scsi sata filesystems"
#
##   This is identical to the above, except the old ide subsystem is
##   used for IDE devices instead of the new pata subsystem.
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev pata scsi sata usb filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev pata mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Offline

#8 2012-06-17 00:57:33

slughappy1
Member
Registered: 2009-03-20
Posts: 75

Re: Unknown filesystem when mounting ntfs?

I'm having another problem with a flash card having a ntfs partition and it won't mount that either. Actually it's 50/50 on whether or not it will mount any usb period, but ntfs it wont mount at all

Offline

#9 2012-06-17 01:23:43

ZekeSulastin
Member
Registered: 2010-09-20
Posts: 266

Re: Unknown filesystem when mounting ntfs?

You could also use the Windows entry template from the Grub2 wiki which works perfectly well on my system (I stuck it in 40_custom); you could do chainloader as well, but meh:

menuentry "Microsoft Windows 7" {
	insmod part_msdos
	insmod ntfs
	insmod search_fs_uuid
	insmod ntldr
	search --fs-uuid --no-floppy --set=root YOUR_UUID_HERE
	ntldr (${root})/bootmgr
}

Aside from grub-probe, you can also get the uuid from blkid /dev/sdxy, ls -l /dev/disk/by-uuid, etc. although it seems that GNOME mounted it for you using its uuid as the mount point (that 16-character thing).  Alternately, you can install os-prober and rerun grub-mkconfig, which also picked up my Win 7 installation easily (with the System Reserved partition, no less!).

Can't help with GNOME automounting woes - I just mount my fixed ntfs partitions in /etc/fstab and use plain udisks1 for transient mounts hmm

(p.s. for what it's worth, there is not a single thing stopping you from manually writing a grub2 cfg if you really want to - I didn't use grub-mkconfig on my growing USB-stick-of-isos ...)

Last edited by ZekeSulastin (2012-06-17 01:48:13)

Offline

Board footer

Powered by FluxBB