Unknown filesystem type 'nilfs2'

Got this error
Module nilfs2 packed to initrd via MODULES='nilfs2' in /etc/mkinitcpio.conf.
How can I fix this?

A few questions....
What exactly was the problem to begin with?
It was a bit unclear as to whether ot not you wanted or did not wnat nilfs2 in your initramfs, or if it was simply throwing some kind of error at you or what.
What did you do to fix it?
Simply saying that you fixed it and then ending the thread discussion is not very cool. It does nothing for the community, or future users in search of help. So please indicate what you did to fix the problem.
If it is solved, could you mark the thread as such?
Edit the first post and prepend [Solved] to the title. This will help those future seekers of help in finding threads that actually have solutions. Though I would strongly encourage you to actually put a solution before doing this. I guess I would also encourage you to clarify the question as well.

Similar Messages

Can't boot after system update: unknown filesystem type

After running a system update, including updating the kernel, I can't boot to the new kernel.
On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
mount: unknown filesystem type 'ext4'
I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
Thank goodness I happened to keep a spare kernel laying around in /boot.
Thanks in advance.
Last edited by jackrabbit (2012-03-22 23:25:28)

The OP can read their partition initially though, it's only after udev that they can't.
Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

[SOLVED] mount: unknown filesystem type 'ext2'

I probably have the most complicated first-time arch setup that you'll ever hear a n00b post. XD
I just finished setting up an encrypted arch box with a usb boot drive (it contains the key-file), but when I go to boot, the system reports the following:
mount: unknown filesystem type 'ext2'
Of all the things to break! Ext2???!
This is for the default boot mode, when boot into the fallback initramfs mode, the arch box boots up fine (although it takes 2 whole minutes). I think that the issue is that I'm missing a module in my mkinitcpio.conf file.
/etc/fstab file:
UUID=1245ASDF / btrfs discard,autodefrag,compress=lzo,rw,relatime,ssd,space_cache 0 0
UUID=2245ASDF /boot ext2 rw,noatime 0 2
UUID=3245ASDF none swap defaults 0 0
/etc/mkinitcpio.conf file:
HOOKS="base btrfs udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
/etc/default/grub file:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda:enc cryptkey=/dev/sdb2:ext2:/keyfile crypto=sha512:twofish-xts-plain64:512:0:"
Last edited by a-jamesregan (2015-04-13 19:15:48)

Wow, there was literally a note about the exact issue I was having on the wiki...
https://wiki.archlinux.org/index.php/Mkinitcpio#MODULES
Note: If using reiser4, it must be added to the modules list. Additionally, if you will be needing any file system during the boot process that is not live when you run mkinitcpio — for example, if your LUKS encryption key file is on an ext2 file system but no ext2 file systems are mounted when you run mkinitcpio — that file system module must also be added to the MODULES list. See Dm-crypt/System configuration#cryptkey for more details.
PS: How do I mark an issue as solved?
Last edited by a-jamesregan (2015-04-13 10:28:20)

Mounting problem, mount: unknown filesystem type 'vfat'

Can't mount vfat partition.
Mounting problem, mount: unknown filesystem type 'vfat'

takavar wrote:sorry for the necromancy, but this is the top result on Google search with no answer.
I am going to close this thread because (a) the thread is more than two years old, abd (b) may or may not be related to your problem.
Please open a new thread detailing your problem. Define what is "Solved" by rebooting. Does the drive mount during a reboot? Tell us how you are trying to mount the drive, and provide us your /etc/fstab. You may want to share the the output of sudo fdisk -l /dev/sda
If you still think it relevant. provide a link back to this thread.
Thanks

Unknown filesystem type crypto_LUKS

Hi, I have spare space on my HD so I decided to experiment with encryption following this wiki:
https://wiki.archlinux.org/index.php/dm-crypt_with_LUKS
In summary:
created boot (sda6) and root (sda7) partitions
formatted boot as ext2 and root with passphrase and then with ext4
installed the base system
generated a new initramfs as explained in the wiki:
MODULES="dm_mod ext4"
HOOKS="base udev autodetect modconf block keymap encrypt filesystems keyboard fsck"
added cryptdevice=<device>:<dmname> to kernel boot options:
linux /vmlinuz-linux cryptdevice=/dev/sda7:cryptroot root=UUID=d3505fe1-4a29-4841-8e80-e953442d8d30 ro quiet
restarted pc
On boot it asks for passphrase, but after that it stops with an error regarding crypto_LUKS; here the complete message:
A password is required to access the cryptroot volume:
Enter passphrase for /dev/sda7
fsck: fsck.crypto_LUKS: not founf
fsck: error 2 while executing fsck.crypto_LUKS for /dev/sda7
ERROR: fsck failed on '/dev/sda7'
********************* WARNING ***********************
* The root device is not configured to be mounted *
* read-write! It may be fsck'd again later. *
mount: unknown filesystem type 'crypto_LUKS'
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs /]#
Here it is my fstab: http://pastebin.archlinux.fr/474004
and lsblk output: http://pastebin.archlinux.fr/474005
Any idea about the problem?
Thanks for your time.

There are two discrepencies between your kernel parameters and fstab:
1) The kernel parameter UUID for real root differs from the UUID given for /dev/mapper/cryptroot in your fstab; if cryptroot is your real root partition, the UUIDs should be the same.
2) Your fstab instructs the system to mount the root partition as read-write, while the kernel parameters specify read-only. (the kernel parameter should be read-write, which is what the warning in the output above is about).
Change those and see if it helps.

BTRFS not mounting (unknown filesystem type)

Hi everyone,
From a USB drive I have been trying to install Arch in the fashion given in https://wiki.archlinux.org/index.php/In … Btrfs_root, I have upgraded the system to the newest kernel (3.3.6) and using the instructions created 2 partitions on /dev/sda. One being for Grub to boot the system, and the other being the btrfs.
I have been unable to mount the btrfs device (/dev/sda2), I keep getting the error
[root@archiso ~]# mount -o defaults,noatime /dev/sda2 /mnt/btrfs-root
mount: unknown filesystem type 'btrfs'
mount, i.e. util-linux is the newest version 2.21.1
any help is really appreciated

Well, I think the problem is caused by the loaded kernel being unable to find it's modules (the btrfs module included) because they got uninstalled when you upgraded the kernel package. You could try manually loading the module with modprobe (using -f if you get errors regarding versions), but I can't recommend that course of action, nor can I guarantee that it will fix your mounting problem.

Mount: unknown filesystem type 'LVM2_member'

I recently did a pacman -Syu with some consequences. I still had grub1 running and it was automatically upgraded to grub2, which is fine, but apparently grub-install was run on the mbr (I really think that was very inappropriate as that did break my system). Anyhow, on to chroot, I update /etc/default/grub as I have an LVM on top of an encrypted root and add this:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda5:VGarch"
and this to mkinitcpio.conf:
HOOKS="base udev autodetect fsck modconf block encrypt lvm2 filesystems"
then update both:
mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.conf
and then update again for good measure while we're still in the chroot. However, upon reboot I get the ominous error message:
mount: unknown filesystem type ‘LVM2_member’
EDIT: i moved fsck behind filesystems in hooks with no effect
Last edited by thoth (2013-07-03 01:31:06)

Post the entire kernel command line you are using (/proc/cmdline).
Note that the upgrade to grub2 will not have automatically installed grub to disk. So if you have not installed grub to disk, you need to do that in order to configure it correctly.
i.e. grub-install was *not* run on the mbr as part of the package upgrade.
See /var/lib/pacman/local/grub-2.00.5043-2/install.
But your config file for the old grub will have been moved to a .pacsave when that package was removed by pacman.
Last edited by cfr (2013-07-07 23:28:53)

[Solved]Wont boot after installing syslinux; unknown filesystem 'swap'

After installing syslinux to be my boot manager I can no longer boot into Arch, I can however boot into Windows 7. When I try to boot into Arch I get the following error.
Loading ../vmlinuz-linux......
Loading ../initramfs-linux.img......ready.
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda3'
fsck: fsck.swap: not found
fsck: error 2 while executing fsck.swap for /dev/sda3
ERROR: fsck failed on 'dev/sda3'
:: mounting '/dev/sda3' on real root
mount: unknown filesystem type 'swap'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs /]#
What's going on?
Last edited by slughappy1 (2012-07-05 22:50:35)

loafer wrote:Can you post your syslinux.cfg please.
Surely
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
LABEL windows
MENU LABEL Windows7
COM32 chain.c32
APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com

USB disks no longer mount, unknown filesystem

Ran a routine weekly update on an arch box this morning, didn't think anything of it as usual. Until Thunar started spitting errors at me whenever I tried to mount a USB device. gvfs makes the devices appear in the left pane for one-click mounting... usually.
A partition on the hard drive attached has started telling me I don't have permissions to mount it any more - never had issues before, I'm in storage so I don't see why.
The other issue comes with a USB hard drive, and when trying to mount it as above, Thunar throws this at me:
Error mounting /dev/sdb1 at /run/media/pip/HD-PVU2: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid-100,shortname=mixed,dmask=0077,utf8=1,showexec" "/dev/sdb1" "/run/media/pip/HD-PVU2"' exited with non-zero exit status 32: mount: unknown filesystem type 'vfat'
Searching both pacman and AUR gave me no packages to do with vfat filesystems, and the wiki article "USB Storage Devices" provided no solutions at all.
Using XFCE4 DE on 32-bit Arch. All packages have been updated to latest versions as of the time of this post.

I probably experience the same kind of problem as you guys. I'm using udisksvm to mount USB drives and when I plug one, I get something like that:
$ udisksvm
Automounting for non optical devices enabled
Added object : /org/freedesktop/UDisks2/drives/Intenso_Basic_10011100031138
Added object : /org/freedesktop/UDisks2/block_devices/sdb
Added object : /org/freedesktop/UDisks2/block_devices/sdb1
Automounting /dev/sdb1...
Mounting failed with error:
GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
traydvm for /org/freedesktop/UDisks2/block_devices/sdb1 now running with pid : 2694
/usr/lib/python2.7/site-packages/gi/types.py:47: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
return info.invoke(*args, **kwargs)
$ udisksvm
Automounting for non optical devices enabled
Added object : /org/freedesktop/UDisks2/drives/Nokia_S60_359557013658840
Added object : /org/freedesktop/UDisks2/block_devices/sdb
Added interface on object : /org/freedesktop/UDisks2/block_devices/sdb
Automounting /dev/sdb...
Mounting failed with error:
GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
traydvm for /org/freedesktop/UDisks2/block_devices/sdb now running with pid : 3025
/usr/lib/python2.7/site-packages/gi/types.py:47: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
return info.invoke(*args, **kwargs)
And the device is not mounted automatically. I have the packages dosfstools, ntfs-3g, systemd-sysvcompat installed (I use systemd). Mounting manually from console works well.

Unknown filesystem error [solved]

I just updated arch and now when I try to mount my usb harddrive I get this error:
# mount /mnt/usbdrive
mount: unknown filesystem type 'vfat'
Anyone know whats up?

I met the same problem.
the key is that the kernel is updated ( e.g. from 2.23 -> 2.24 ).
the vfat kernel module reside in difference directory (/lib/modules/XXXx-2.24/)after update.
but the kernel version in /proc is the old one , until you reboot.
if you don't reboot, when load the vfat module, the insmod will search the /lib/modules/`uname -r` , which can found nothing to load. well, what you get is nothing but some string like
# modprobe vfat
FATAL: Could not load /lib/modules/2.6.23-ARCH/modules.dep: No such file or directory.
so, you can understand why you are happy now.

AIM-CUE - Filesystem type unknown ?

Hi there,
I am studying IIUC and I am up to the CUE module. Im pretty sure I have done something stupid. I removed the 1GB CF from the AIM-CUE module, put it in my 2801 CF slot and did a format flash: (I dont know why, I just thought it would let me start fresh ) . Now when the AIM-CUE goes through the boot process I get the following output.
Initializing memory. Please wait....
256 MB SDRAM detected
BIOS Version: Cisco SE-AIM 01.02
BIOS Build date: 08/14/03
System Now Booting ...[BOOT-ASM]
Filesystem type unknown, partition type 0x1
kf: a1 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kf: a2 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kernel_func: kt: 0
in boot func: kt: 0ÿ
I can get into the bootloader and use the boot helper to re-install the CUE files, but I guess if they are on the wrong filesystem type they are useless.
I have searched around and it looks like I need to have the "Filesystem type is reiserfs, partition type 0x83".
Now the only way I can see to re-format the flash to the reiserfs file system is the put the 1GB CF into a card reader and format it with my PC. Im going to give it a try now, but I also read somewhere there needs to be 2 partitions, however Im unsure what size each partition should be.
This is a second hand AIM-CUE so I dont have any support for it. Have I rendered my AIM-CUE useless, or is there a way I can dig myself out of this hole I have created ??
Thanks in advance.
JP

Thanks for the reply paolo, however the boot loader / boot helper is the problem. Ive managed to get the right filsesystem type however now its stuck in this constant loop
Initializing memory. Please wait.
256 MB SDRAM detected
BIOS Version: Cisco SE-AIM 01.02
BIOS Build date: 08/14/03
System Now Booting ...[BOOT-ASM]
Please enter '***' to change boot configuration:
Filesystem type is reiserfs,partition type 0x83
kf: a1 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kf: a2 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open1: /bzImage root=/dev/hda1 ro plat=aim
in grub_open2: /bzImage root=/dev/hda1 ro plat=aim
in grub_open3: /bzImage root=/dev/hda1 ro plat=aim 1
in grub_open4: /bzImage root=/dev/hda1 ro plat=aim
kernel_func: kt: 0
in boot func: kt: 0ÿ <--when it gets to here it goes back to the "Initializing memory. Please wait." and just keeps looping.
Any ideas why boot helper keeps looping like this ??
EDIT: Now I am getting "Not a cisco supported CF. Please use cisco supported CF and reinstall the software. System Halted"
Im guessing the CF may have been on its way out and now it has gone faulty ?

First boot fails - Filesystem type unknown, partition type 0x7

Just done a straight forward install of Arch onto it's own disk drive, however there are two other drives present in the system.
Grub menu comes up ok but then Arch errors with:
root (hd2,0)
Filesystem type unknown, partition type 0x7
Error 17: Cannot mount selected partition
Any suggestions?
Thanks,

hokasch wrote:
What you still did not really tell us - how are you booting up? I.e. where is your first grub stage installed? How did you manage things with the debian install? Your problem is the root(x,x) line, not the kernel line. This line specifies the boot partition (grub's root/ where to find the kernel).
Coming from the windows world where for years we have just relied on changing the boot order of drives in the BIOS to choose which MBR to boot from I simply assumed it was just as easy in the Linux world, this is obviously not the case.
If you want to continue that way, just install grub to the MBR of each disk with a linux install and configure grub to use that drive as the first drive (e.g. set the root line to hd(0,0) if /boot is the first partition). IIRC, changing the boot order in the Bios will pull the selected drive to the beginning. That would fit your inital error (but you did not say how you booted into grub then...). You can double-check that behaviour by using the find commands in the grub shell (see my earlier post).
Going with grub2/grub's root by uuid only really makes sense if you put grub2 on the MBR of a drive which is always installed and selected as primary in Bios (obviously, all other grub2 files must be on that drive too).
Just done another completely clean install and noticed that even though I select 'Partition access method - uuid' it doesn't seem to actually work that way, at least checking menu.lst showed no signs of any uuids. What is the point of having an install option if it is then ignored.
This refers to your fstab, not the bootloader config.
Sorry hokasch, it got a bit difficult to answer your earlier post as by the time I read it Debian had been trashed and I think I had redone the Arch install a few times by then as well.
If I have understand you correctly what you are saying is that if I were to install arch on a drive which at install time is the only drive in the machine then root(x,x) would refer to hd0 in my case root (hd0,1) as I have an NTFS partition at the beginning of the drive. Alternatively I could just edit grub's menu.lst afterwards. That way as long as the drive is first in the BIOS boot order it will boot ok. My mistake seems to have been trying to install the first grub stage to somewhere other than the MBR, I may have missunderstood the capabilities of partition identification by uuid.
Ok lets go back to a single drive environment
hd0,0 = NTFS boot partition
hd0,1 = Arch /Boot - this contains grub & vmlinuz-linux
hd0,2 = Arch swap
hd0,3 = Arch /
If I want to boot Windows I set hd0,0 as active/bootable, if I want to boot arch I set hd0,1 as active/bootable. Actually not sure how to change the active partition to a linux one but come back to that later. For the moment hd0,1 is the bootable partition. This is the only drive in the system. I have a by-uuid entry in menu.lst which allows me to boot if the other entries fail. menu.lst looks like this:
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /vmlinuz-linux root=/dev/sda4 ro
initrd /initramfs-linux.img
Now I see part of the confusion, as you advised, the root (hdx,x) line actually refers to the 'grub root' / 'linux boot' not the 'linux root'. And the other confusion is that the kernel line root= does not refer to the location of /vmlinuz-linux but to the actual linux root. Now I think I understand that bit.
Now to add another disk to the system. Change drive order in BIOS so that arch disk is top of the boot order.
Fails to boot: Unable to find root device /dev/sda4!
Boot to knoppix to see the disk & partition layout:
hd0,0 = NTFS
hd0,1 = NTFS
hd0,2 = NTFS
hd0,3 = NTFS
hd0,4 = NTFS
hd0,4 = NTFS
hd0,4 = NTFS
hd1,0 = NTFS boot partition
hd1,1 = Arch /Boot - this contains grub & vmlinuz-linux
hd1,2 = Arch swap
hd1,3 = Arch /
So clearly /dev/sda4 is now an NTFS partition.
If appears that grub & linux do not see disk drives in the same order as the BIOS boot order causing /dev/sda4 to point towards the wrong partition.
Off at a bit of a tangent here but while I think of it is there a way of regenerating the menu.lst to search for instances of windows on NTFS partitions now that I have access to ntfs-3g.
Thanks,
Last edited by NickC_UK (2012-02-21 14:25:04)

Fresh btrfs root partition cannot boot/unknown filesystem [solved]

Just reformatted my SSD with 3 partitions.
1) EFI
2) /boot (ext4)
3) / (btrfs)
I copied over my systefrom tars, adjusted the new fstab to use btrfs, I rebuilt my kernel images, and rebuilt grub.cfg in the chroot. When I reboot, I get:
Welcome to grub!
error: unknown filesystem
Entering rescue mode...
grub rescue>
Per the wiki, there should be no special setup steps to boot to a btrfs root with grub. When did I f-up?
/etc/fstab
LABEL=arch64 / btrfs defaults,discard,noatime,ssd,compress=lzo 0 0
LABEL=boot /boot ext4 defaults,discard,noatime 0 2
Excuse the short post, typing in a phone.
Last edited by graysky (2013-07-29 01:24:47)

Yes, it is dropped to a GRUB rescue shell. I can boot if I manually type the following but WTF?! Why isn't grub doing this by itself?
grub rescue> set prefix=(hd0,2)/grub
grub rescue> insmod (hd0,2)/grub/x86_64-efi/linux.mod
grub rescue> set root=(hd0,2)
grub rescue> linux /vmlinuz-linux-ck root=/dev/sda3
grub rescue> initrd /initramfs-linux-ck.img
grub rescue> boot
Link to my autogenerated /boot/grub/grub.cfg
Last edited by graysky (2013-07-29 00:28:58)

[SOLVED] grub "unknown filesystem" error for big partition layout

Last night / this morning I copied the root and swap partitions of an Arch Linux installation (stushiba) I had on an old Toshiba hard drive, as well as the "system reserved" and other partitions of a Windows 8 install (stuzate) on another 500GB hard drive, onto a new 2TB Western Digital hard drive using Gparted via an external Arch environment I run off of a microSD card + adapter (sturling).
After doing so, I installed GRUB to the new drive to the best of my ability, but when I try to boot the system with just that drive, this is what I see:
GRUB loading.
Welcome to GRUB!
error: unknown filesystem.
Entering rescue mode...
grub rescue>
Running ls doesn't find anything:
grub rescue> ls
(hd0) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)
grub rescue> ls (hd0,msdos4)
(hd0,msdos4): Filesystem is unknown.
grub rescue> ls (hd0,msdos3)
(hd0,msdos3): Filesystem is unknown.
grub rescue> ls (hd0,msdos2)
(hd0,msdos2): Filesystem is unknown.
grub rescue> ls (hd0,msdos1)
(hd0,msdos1): Filesystem is unknown.
The system should be on (hd0,msdos3) - it's ext4, and, if I insert the old Toshiba hard disk to the system and select that as my boot device in BIOS, it boots from the partition on the old drive's grub menu, into the partition in the new drive (because they have the same UUID), so the partition's definitely readable/bootable. (I've tried both regenerating the grub menu and installing grub from this boot scenario, with no change.)
(That said, if I enter a console on my system with a working GRUB installation and do an ls on that partition, I get more "unrecognized filesystem" messages.)
Once the new partition had loaded, I ran
sudo grub-mkconfig -o /boot/grub/grub.cfg
and rebooted, but GRUB was still broken.
I tried fixing this by rebooting into the latest installation media, with only the new hard drive plugged in, and running
mount /dev/sda3 /mnt
arch-chroot /mnt
modprobe dm-mod
grub-install --recheck /dev/sda
But that still hasn't fixed anything: I still get the "error: unknown filesystem." message whenever I try to do anything in GRUB.
My /boot/grub/grub.cfg: http://sprunge.us/RMeD
Help!
Last edited by STUART (2013-09-12 01:55:16)

This is the output when running from sturling (neither partition booted).
/dev/sda is the new disk, /dev/sdb is the microSD card I'm running the system off of, and /dev/sdc is the old disk.
[stuart@sturling ~]$ sudo lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs System Reserved F24C78CE4C788EDB
├─sda2 ntfs F68C7D338C7CF00B
├─sda3 ext4 stushiba 1c8533ed-4a3c-4a4c-907b-682bd2313492
└─sda4 swap 97c30b3e-f763-437b-aa71-0378bef4c017
sdb
├─sdb1 vfat savfat A13A-D130 /vfat
└─sdb2 ext4 saroot 7434b70f-7028-4a8d-ad78-a4975a98e1a6 /
sdc
├─sdc1 ext4 stushiba 1c8533ed-4a3c-4a4c-907b-682bd2313492
└─sdc2 swap 97c30b3e-f763-437b-aa71-0378bef4c017
sr0
[stuart@sturling ~]$ sudo fdisk -l /dev/sda
Disk /dev/sda: 2000.4 GB, 2000365289472 bytes, 3906963456 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 label type: dos
Disk identifier: 0x0005f107
Device Boot Start End Blocks Id System
/dev/sda1 2048 718847 358400 7 HPFS/NTFS/exFAT
/dev/sda2 718848 1937063935 968172544 7 HPFS/NTFS/exFAT
/dev/sda3 1937063936 3873409023 968172544 83 Linux
/dev/sda4 3873409024 3906963455 16777216 82 Linux swap / Solaris
[stuart@sturling ~]$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 31.9 GB, 31914983424 bytes, 62333952 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 label type: dos
Disk identifier: 0x000c314b
Device Boot Start End Blocks Id System
/dev/sdb1 2048 8390655 4194304 c W95 FAT32 (LBA)
/dev/sdb2 * 8390656 62333951 26971648 83 Linux
[stuart@sturling ~]$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 100.0 GB, 100030242816 bytes, 195371568 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 label type: dos
Disk identifier: 0x8bef8bef
Device Boot Start End Blocks Id System
/dev/sdc1 2048 178593791 89295872 83 Linux
/dev/sdc2 178593792 195371007 8388608 82 Linux swap / Solaris

[SOLVED] Grub boots to rescue mode err: unknown filesystem every drive

So I installed Arch and it all seemed to go reasonably well (well, had a little trouble installing GRUB to begin with, but I think that's just because I needed a BIOS boot partition at the start of the drive). I installed it onto a 4TB I have, which due to its size has a GPT partition table even though my mobo (Gigabyte GA-P67A-UD4-B3, don't think it matters though) uses a regular old BIOS. Initially it was two partitions, the Microsoft reserved partition then a big NTFS data partition. I shrunk the NTFS partition and then made (in this order on the disk, starting at third) an ext4 partition for /boot, a swap partition, and a big btrfs partition (in which I created subvolumes for /, /etc, /home and /var). GRUB wouldn't install (I forgot the exact error) but what I could find suggested it was because there needed to be room for it at the start of the disk, so I deleted the Microsoft reserved partition (Windows is installed on an SSD, and its bootloader is on another hard drive entirely, so I didn't think I needed it) and created an empty partition with the right code using gdisk, then I could install GRUB to the 4TB HDD.
Unfortunately, when I try to boot into GRUB it immediately comes up with error: unknown filesystem and dumps me at the GRUB rescue prompt. Using ls, I can see my HDDs and their partitions, but whenever I try to use (for example) ls (hd0,gpt3)/ - which I think should probably be the ext4 boot partition, but it does this for everything - it just says error: unknown filesystem again.
This seems pretty close to (if not exactly the same as) my problem, so I tried what he suggested, but when I tried to run the command he says worked, (grub-install --recheck --disk-module=native /dev/sda) - and don't worry, I didn't do that blindly, I know /dev/sda is my 4TB HDD - I just get the error grub-install: --disk-module: (PROGRAM ERROR) Option should have been recognized!?. So I'm all out of ideas and I've been trying for a few hours. Please help me, before I go insane... more insane. I can boot the USB drive I used to install Arch and chroot into my installation, but I haven't found a way to actually boot the installation yet.
SOLVED: Apparently the partition I was using for /boot was too far back on the drive (past the first 2TB). When I shuffled partitions around so that the /boot partition was near the start of the drive (it starts at sector 2048 now!) that seemed to fix it.
Last edited by Slashee the Cow (2015-04-12 15:36:51)

Tried using insmod btrfs in the grub rescue shell last night. Didn't work, can't remember if the insmod command itself gave me an error or whether it still couldn't see any files or anything. Tried it again today, but that was after I converted /dev/sda3 back to ext4 and mounted it at /boot (since it being ext2 wasn't working, and not using it wasn't working, so I figure what's the harm) and I just got error: unknown filesystem.
Anyway: using grub-install from outside chroot seems to work (still can't use --disk-module), but grub-mkconfig just generates this:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
else
search --no-floppy --fs-uuid --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
if [ "${grub_platform}" == "pc" ]; then
menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
search --fs-uuid --no-floppy --set=root ec4cf3cd-d72d-4988-a2ce-421f45d52824
linux16 /boot/memtest86+/memtest.bin
fi
### END /etc/grub.d/60_memtest86+ ###
I'm not an expert on GRUB configuration files, but I figured that even if that didn't just boot me straight to the rescue shell, it wasn't going to boot anything... other than memtest86+ maybe. So I went back into chroot and run grub-mkconfig and it generated this:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod btrfs
set root='hd0,gpt5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 b21e6211-5e7a-4769-9f53-b9b5d554a242
else
search --no-floppy --fs-uuid --set=root b21e6211-5e7a-4769-9f53-b9b5d554a242
fi
font="/root/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
else
search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
else
search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-b21e6211-5e7a-4769-9f53-b9b5d554a242' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 184916fd-57a7-48cf-858e-93a5d339ade2
else
search --no-floppy --fs-uuid --set=root 184916fd-57a7-48cf-858e-93a5d339ade2
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Vista (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-4E94BAB294BA9C41' {
insmod part_gpt
insmod ntfs
set root='hd1,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 4E94BAB294BA9C41
else
search --no-floppy --fs-uuid --set=root 4E94BAB294BA9C41
fi
chainloader +1
menuentry 'Windows Vista (loader) (on /dev/sde1)' --class windows --class os $menuentry_id_option 'osprober-chain-CEF01053F010445D' {
insmod part_msdos
insmod ntfs
set root='hd4,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 CEF01053F010445D
else
search --no-floppy --fs-uuid --set=root CEF01053F010445D
fi
chainloader +1
menuentry 'Windows Vista (loader) (on /dev/sde5)' --class windows --class os $menuentry_id_option 'osprober-chain-4E94BAB294BA9C41' {
insmod part_msdos
insmod ntfs
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 4E94BAB294BA9C41
else
search --no-floppy --fs-uuid --set=root 4E94BAB294BA9C41
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Still didn't work though.
I don't know grub config, but is the UUID specified in
linux /vmlinuz-linux root=UUID=b21e6211-5e7a-4769-9f53-b9b5d554a242 rw rootflags=subvol=root quiet
supposed to be the UUID for /boot or /? Because the UUID there is for the btrfs partition being mounted at / (which I guess would explain why it has the correct subvol listed, which I'm not sure if it's necessary, given that should be the default subvolume). So... that's probably alright (just something that stood out to me).
As for installing grub on another disk: I suppose I could try, though I'd rather keep it on one drive if I can (sometimes it gets complicated enough having Windows and my Windows bootloader on different drives... I should probably try moving the Windows bootloader to the SSD where Windows is installed. Would it matter which drive? The options are:
sda: 4TB, GPT table, the one I'm having problems with now
sdb: 2TB, MBR table, nothing in boot sector AFAIK
sdc: 240GB SSD, GPT table, would rather not use it since Windows is installed on there, even if its bootloader isn't
sdd: 1TB, MBR table, nothing in boot sector AFAIK
sde: 500GB, MBR table, has the Windows bootloader so I'd rather not mess that up (although given it's the smallest and I have no free SATA ports, it'll be next to go when I need more space, so I might want to move the bootloader)
(sdf and sdg which appear in lsblk earlier are just USB flash drives, and I'd rather not have to rely on having to use one of them to boot Linux).
As for repartitioning /dev/sda: as long as I can do it non-destructively, sure. Well I mean non-destructively for the NTFS partition, which is mostly full of Steam games (and I might have enough room on other drives and portable drives to keep the rest safe), but on my crappy Australian internet connection (aren't they all) it'd probably take me a couple of weeks to redownload them. I don't mind if I have to get rid of the Linux partitions, I already tried going through the install again once before to try to get it to work, another time isn't going to matter. So I guess I could try using gparted to delete the Linux partitions, move the NTFS partition to the end of the disk, and recreate the Linux partitions in front of it (although moving that much data might take a while, so I'd probably want to do it overnight). For reference, right now it's:
128MB of unformatted space (where the Microsoft reserved partition was, but now it's flagged as a BIOS boot partition, even though it's far bigger than it needs to be for that, I didn't feel like moving the other partitions back just to claim less than 128MB)
~2.7TB NTFS data partition (important)
~1GB ext4 /boot partition
8GB swap partition
~1TB btrfs partition with subvolumes mounted at /, /home, /etc and /var

Unknown filesystem type 'nilfs2'

Similar Messages

Maybe you are looking for