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)

Similar Messages

Why my Mountain Lion recovery partition cannot boot ?

Hi
I cannot boot from the recovery partition on Mountain Lion.
I am only offered Internet Recovery - which is slow.
I installed Mountain Lion from scratch on my Mid-2010 macbook pro.
I was running Lion, got the Mountain Lion app from the app store and created an USB stick
I have no bootcamp but enabled filevault after installation.
The recovery HD appears to be there and to be ok - see output below.
So why am I forced into Interent Recovery?
Can I 'recover' the Recovery partition ?
Edoardos-MacBook-Pro:~ edoardo$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         499.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS MacOSX                 *498.9 GB   disk1
Using the DiskUtility debug option:
defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
I can even mount it and list its contents:
Edoardos-MacBook-Pro:~ edoardo$ ls -la /Volumes/
MacOSX/      Recovery HD/
Edoardos-MacBook-Pro:~ edoardo$ ls -la /Volumes/Recovery\ HD/
total 0
drwxrwxr-x 11 root wheel 442 31 Jul 23:00 .
drwxrwxrwt@ 4 root admin 136 2 Aug 13:19 ..
drwxrwxrwt@ 3 root wheel 102 31 Jul 11:54 .TemporaryItems
d-wx-wx-wt   3 root wheel 102 2 Aug 13:19 .Trashes
drwxr-xr-x   3 root wheel 102 31 Jul 11:54 .fseventsd
-rw-r--r--   1 root wheel    0 31 Jul 11:54 .metadata_never_index
drwxr-xr-x   3 root wheel 102 31 Jul 12:38 System
drwxr-xr-x   5 root wheel 170 31 Jul 23:00 com.apple.boot.S
drwxr-xr-x 10 root wheel 340 31 Jul 11:54 com.apple.recovery.boot
Edoardos-MacBook-Pro:~ edoardo$ diskutil info disk0s3
   Device Identifier:        disk0s3
   Device Node:              /dev/disk0s3
   Part of Whole:            disk0
   Device / Media Name:      Recovery HD
   Volume Name:              Recovery HD
   Escaped with Unicode:     Recovery%FF%FE%20%00HD
   Mounted:                  Yes
   Mount Point:              /Volumes/Recovery HD
   Escaped with Unicode:     /Volumes/Recovery%FF%FE%20%00HD
   File System Personality: Journaled HFS+
   Type (Bundle):            hfs
   Name (User Visible):      Mac OS Extended (Journaled)
   Journal:                  Journal size 8192 KB at offset 0x7000
   Owners:                   Enabled
   Partition Type:           Apple_Boot
   OS Can Be Installed:      Yes
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified
   Volume UUID:              2FB278E4-2FC8-3CCB-8F6A-4EF280037F15
   Total Size:               650.0 MB (650002432 Bytes) (exactly 1269536 512-Byte-Blocks)
   Volume Free Space:        125.0 MB (125001728 Bytes) (exactly 244144 512-Byte-Blocks)
   Device Block Size:        512 Bytes
   Read-Only Media:          No
   Read-Only Volume:         No
   Ejectable:                No
   Whole:                    No
   Internal:                 Yes
   Solid State:              No

What if I need recovery on the road ??
Recovery HD
This version of the installer doesn’t actually include all of the necessary files and data, so installing Mountain Lion from within recovery mode requires an Internet connection to download the actual OS.
If you are worried about backups/being on the road, you should always create a bootable back up of your system onto a USB or Fireware drive. Use Carbon Copy Cloner, and it will automate the incremental backups and have a fully bootable running system if your internal should ever stop working.
If you download the installer from the store, make sure to create a bootable install disk also;

Cannot mount cifs filesystems [solved]

I have a usb drive plugged into my router that I have set up to mount via autofs. However, it is failing because for some reason my system suddenly cannot recognize cifs filesystems. cifs-utils is installed and the latest version
mount error: cifs filesystem not supported by the system
Last edited by tlmiller (2012-03-24 05:02:36)

BAH...
I could have SWORN I had rebooted already after doing an update, apparently I was mistaken.

Cannot boot into safe mode

Have a later '09 MP (3.3 quad). Aside from the main OS drive, I formatted a separae drive with a fresh OS and still cannot boot into Safe Mode from either drive. It does start to enter Safe Mode but the progress bar ends about a third way through and the MP restarts. Even tried disconnecting all externals and restarting into Safe Mode. No diff. Note, there is no separte chime when starting the OS (hasn't been for quite some time). Though, there is a multiple chime (3) when resetting the PRAM. Also did the SMC reset. An suggestions or idea?

Three beeps on startup means there is a problem with the memory. Try removing and reseatng each memory module. If that is still a problem, look at your memory map from the apple menu, About This Mac, More Info, System Report, Hardware, Memory and see if each module shows correctly.

Can't get lvm/luks to boot - cannot find root partition

Hi,
I'm trying to get a dm-crypt on top of lvm to boot but without success so far. I followed http://wiki.archlinux.org/index.php/Sys … r_dm-crypt and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM, everything works fine (I can mount the partition) but when I try to boot from it, it cannot find the crypted partition and fails.
USELVM="yes"
HOOKS="base udev usb usbinput lvm2 encrypt filesystems"
root=/dev/mapper/sda2 cryptdevice=/dev/sda2:root2-lvol0 ro
jan@jan ~/src/xf86-video-ati $ ll /dev/mapper/
insgesamt 0
crw-rw---- 1 root root 10, 62 21. Feb 2008 control
brw------- 1 root disk 254, 0 21. Feb 2008 root
brw------- 1 root disk 254, 1 21. Feb 2008 root2-lvol0
brw------- 1 root disk 254, 2 21. Feb 2008 sda2
/dev/mapper/root is my current encrypted / without lvm
The boot process successfully identifies the lvm /dev/mapper/root2-lvol0 and continues with hook 'encrypt' but doesn't ask me for a passphrase but goes on to hook 'filesystems' and fails then because it can't mount the correct root-partition obviously.
There's only /dev/mapper/root2-lvol0 and /dev/mapper/control when I'm in the rescue sh from initrd.
Anyone got that combination to work?
- Jan

Reboot, at the sound of the chime (not before) depress the option key, when the startup manager appears choose OSX.

[SOLVED] Root fs cannot be found on boot (initramfs works)

Hi all! Long time lurker, first time poster.
I'd been using catalyst drivers since I started out on Arch. I knew there were conflicts during updates involving catalyst, so I've never updated my kernel or Xorg during "pacman -Syu" updates. I'd specifically blocked them in pacman.conf. However, I recently decided to switch to open source ati drivers and in doing so, decided to update my entire system including the kernel. Everything went smoothly, but upon reboot I'm getting the dreaded "root filesystem cannot be found" error.
Root device '/dev/sdb6' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sdb6' unknown
ERROR: Unable to create/detect root device, '/dev/sdb6'
Dropping to recovery shell.. type 'exit' to reboot
Note that the initramfs worked, it's just it couldn't get into my root partition even though I can mount it without any problems from the live CD.
I set about trying to fix my problem. Here is a list of things I've tried.
1) Using the liveCD, I chrooted into my install (mounting proc, dev, etc. in the process) and did
depmod -a
followed by
pacman -Sf kernel26
which completed with no errors problems. This didn't solve my issue.
2) Using the liveCD, performing
mkinitcpio -M
and ensuring my mkinitcpio.conf file contained all the listed modules. I then rebuilt the initramfs with another
pacman -Sf kernel26
This didn't solve my issue.
3) Playing with grub, replacing my UUID lookups with /dev/sdb6. I also tried different combinations (see this thread) to check the bios and grub were matching up. I did the suggested rootdelay=8 and rootfstype=ext3 stuff, too. This didn't solve my issue.
4) Using the liveCD, I did another depmod -a then downgraded my kernel to the older package found on the 2008.6 CD. Mkinitcpio completed successfully, everything seemed fine, but... This didn't solve my issue.
I've done these steps over and over again in various orders, trying different combinations, but I've not had any luck.
Here is my current mkinitcpio.conf file:
MODULES="pata_acpi pata_jmicron ata_generic scsi_mod ahci ata_piix ext3 ahci libata cdrom ide-core ide-pci-generic jmicron ieee1394 ohci1394 atl1 mii sr_mod usbcore ehci-hcd uhci-hcd jbd"
BINARIES=""
FILES=""
HOOKS="base udev autodetect pata scsi sata usb net usbinput keymap encrypt filesystems"
Here is the important bit of my grub file:
Without UUIDs:
title Arch Linux
root (hd1,5)
kernel /vmlinuz26 root=/dev/sdb6 quiet vga=869 rootdelay=8 rootfstype=ext3
initrd /boot/kernel26.img
title Arch Linux (fallback)
root (hd1,5)
kernel /vmlinuz26 root=/dev/sdb6 ro quiet vga=869 rootdelay=8
initrd /boot/kernel26-fallback.img
With UUIDs:
title Arch Linux
uuid ec450c30-5197-4330-9831-914eafad66ce
kernel /vmlinuz26 root=/dev/disk/by-uuid/ec450c30-5197-4330-9831-914eafad66ce ro quiet vga=869
initrd /boot/kernel26.img
title Arch Linux (fallback)
uuid ec450c30-5197-4330-9831-914eafad66ce
kernel /vmlinuz26 root=/dev/disk/by-uuid/ec450c30-5197-4330-9831-914eafad66ce ro quiet vga=869
initrd /boot/kernel26-fallback.img
Any ideas, help, suggestions, fixes, etc would be greatly appreciated. I just felt like my arch install was damn near perfect - I'd hate to have to install everything again!
(Edit: Just fixing something I'd messed up in my attempts to fix it, as kindly pointed out by Karol. It didn't fix the problem, though.)
Last edited by binarymonster (2009-06-04 10:03:19)

karol wrote:
If you've read http://bbs.archlinux.org/viewtopic.php?id=63033 I assume you've tried to use 'root=/dev/sdb6' w/
root (hd0,5)
instead of
root (hd1,5)
but didn't work, right?
This one's old (and odd) but you may want to have a look at it anyway http://bbs.archlinux.org/viewtopic.php?pid=376939
And the very bottom of http://bbs.archlinux.org/viewtopic.php?id=44921
I read that first link - though I might have misinterpreted it. I tried keeping (hd1,5) the same and changing /dev/sdb6 to /dev/sda6, etc. I always through that the grub root (hd0,5) wasn't correct, the initramfs would not be able to show up and I'd just get a grub error. What I have tried so far hasn't worked, but I might try changing to (hd0,5) instead of (hd1,5) in a little while.
With regards to the other links, they seem to suggested lots of things I've already tried. The list is getting quite long now!
I have tried reinstalling kernel26, downgrading kernel26, using the fallback image, made sure mkinitcpio.conf contains my filesystem type, made sure mkinitcpio.conf contains my hdd controller module, tried rootdelay=8 a few times... and my mkinitcpio seems to work, so I don't think the problem is with my mkinitcpio.conf file.
Phew! Thanks for your continued help... I'm sure this problem will get solved eventually (and I bet it'll be something simple!). At least I'm learning about chrooting, initramfs, etc.
Do you think it's worth trying to change root (hd1,5) to (hd0,5)? I imagine that would only cause grub to give me and error and not even be able to find the initramfs!

[SOLVED] USB installation, booting: root fs cannot be detected

I followed this guide: http://wiki.archlinux.org/index.php/Ins … _a_USB_key
SYMPTOMS
I installed arch linux on a USB stick.
I can see Grub, I can boot. After the HOOKS get loaded (udev is loaded as well: Loading udev...done.) I get errors as follows:
Attempting to create root device '/dev/disk/by-uuid/myHdUUID'
unknown
ERROR: root fs cannot be detected. Try using rootfstype= kernel parameter.
If the device '/dev/disk/by-uuid/myHdUUID' gets created while you are here, try adding 'rootdelay=8' or higher to the kernel command-line...
Then I get a prompt that doesn't even let me issue the command "ls" (error: /bin/bash: ls: not found
SOLUTION: use the fallback image, or better, rebuild your mkinitcpio kernel image, see: Configuring mkinitcpio
My problem was that "usb" was not included in the HOOKS, it was present, yes but after the "autodetect".
So, in the /etc/mkinitcpio.conf place "usb" before "autodetect", e.g. as follows:
HOOKS="base udev autodetect sata filesystems"
then regenerate the image (refer to the previous link to understand why the autodetect was creating the problems and to see exactly how to regenerate the image)
Last edited by firepol (2008-10-09 19:18:34)

Same problem, seems the new kernel broke UUID.
@tim: as I stated above it seems that you fixed the problem with the kernel image file but did not adjust the grub menu to compensate for the fact that UUID is broken and thats why you got the same result even after fixing the image, lucky for me I had some broken hooks and only my fallback image generated properly so I figured it out, although it took me a little while.
Anyhow this is basically what needs to be done to correct the problem.
1. Boot ArchLive
2. mkdir /media/disk
3. mount /dev/sdxX /media/disk
4. chroot /media/disk
5. mkinitcpio -k 2.6.28-ARCH -g /boot/kernel26.img
6. nano /boot/grub/menu.lst
7. Replace any references to UUID with /dev/sdxX (where xX represents your drive and partition) instead, save and exit nano.
8. reboot
Make sure and pay attention to the output of the mkinitcpio command in my step 5. If there are any errors relating to one or more of the hooks you'll need to edit /etc/mkinitcpio.conf and remove the hook it complains about !!IF POSSIBLE!!. I for example had some problem with the autodetect hook which caused my regular kernel to fail to create an image.
If mkinicpio doesn't complain and tells you it SUCCEEDED generating the images then you should be good to go.
Last edited by blazercist (2009-01-29 18:47:25)

[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

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.

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]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

Btrfs root filesystem

The release notes for OL6.3 indicate that its possible to create a btrfs root filesystem on install using the alternative boot ISO media (excerpt from release notes at https://oss.oracle.com/ol6/docs/RELEASE-NOTES-U3-en.html):
Note: The standard installation media does not have support for creating a btrfs root filesystem on initial install. If you want to install Oracle Linux 6 Update 3 and use btrfs as your root filesystem, please use the alternative boot ISO media which uses btrfs as the default root filesystem. Using the boot.iso requires that the full installation source be available via a network method, i.e. FTP, HTTP or NFS.
However I still don't see how to do this. Just as with the full DVD install there isn't an option to use btrfs when laying out the fileystem in the installer. Anyone know how to do this?

Oracle Linux uses the RHEL 6 installer, which has no btrfs support. However, it is not difficult to convert your existing installation to btrfs. It takes only several minutes. You can boot the system from V33412-01 (Oracle 6.3 boot.iso) available from https://edelivery.oracle.com/linux
The following worked for me:
Start the system from Oracle 6.3 boot DVD
Select "Rescue installed system"
When prompted select "local cd/dvd" as installation source (we don't need it)
When prompted to start the network interface choose "no" (we don't need it)
When prompted "The rescue environment…." select "Skip"
Open "shell"
To find your system volume group, e.g. vg_vm003:
<pre>
vgscan
</pre>
Activate the LVM volume
<pre>
lvchange -ay vg_vm003
</pre>
To find your system partition (now ACTIVE), e.g. /dev/vg_vm003/lv_root
<pre>
lvscan
</pre>
Verify/Repair the filesystem and convert it to btrfs
<pre>
fsck -fy /dev/vg_vm003/lv_root
btrfs-convert /dev/vg_vm003/lv_root
</pre>
Mount the system partition (Do NOT use /mnt!)
<pre>
mkdir /me
mount /dev/vg_vm003/lv_root /me
</pre>
Modify fstab to change the fstype of your lv_root partition from "ext4" to "btrfs"
<pre>
vi /me/etc/fstab
</pre>
To address problems with SELinux, do the following to prevent "Respawning too fast. Stopped" errors at startup.
<pre>
touch /me/.autorelabel
</pre>
Finally dismount the partition
<pre>
umount /me
</pre>
Then remove the boot DVD and reset the computer. When the system restarts use default Oracle UEK kernel with btrfs support builtin.

Filesystem check failed, root partition not found

Hi all,
Since yesterday I receive the following error message when booting into Arch:
:: Mounting root filesystem read-only [ OK ]
:: Checking filesystems [BUSY]
/dev/sda4: no such file or directory
*************** FILESYSTEM CHECK FAILED *******************
* Please repair manually and reboot ...
The device /dev/sda4 is my root partition, which is - after entering the root
password - mounted as /dev/root. Checking the partition with 'reiserfsck
/dev/sda4' does not give any error or warning messages. I can also
successfully remount and access it with 'mount -n -o remount,rw /'.
'ls -l /dev/sda*' gives me the following:
brw-rw---- 1 root disk 8, 0 Apr 28 16:32 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 28 16:32 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 28 16:32 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 28 16:32 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 28 16:32 /dev/sda4
So the device itself seems to be there. Rebooting doesn't help, neither does
using older, working kernel versions.
I also checked other topics on similar subjects, but I couldn't find any solution.

Hmm, it doesn't work even with the UUID. But the error looks similar:
Failed to open the device UUID=672f076e-131c-4220-81ba-b30639ef9285: No such file or directory
But when I call rc.sysinit manually directly after entering the root password,
everything works fine. It does work with sda as well as uuid notation.
I manually added some code before the output of the '*** FILESYSTEM CHECK FAILED ***' message:
ls -l /dev/sda*
sleep 1
ls -l /dev/sda*
The result was:
ls: cannot access /dev/sda*: No such file or directory
brw-rw---- 1 root disk 8, 0 Apr 30 09:12 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 30 09:12 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 30 09:12 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 30 09:12 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 30 09:12 /dev/sda4
So it seems that the devices are really not yet created. Is it a udev problem?
I am not aware of changing anything udev specific, maybe an updated version?

[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

Copied my Arch root partition to a new one but I can't boot [SOLVED]

I booted to my arch live cd and copied my Arch / partition (/dev/sda1) to an empty partition (/dev/sda9) via a cp -a command. The new partition should now contains an exact copy of my old root partition. I also modified the /etc/fstab in the new partition to reflect the new block device for the root filesystem. I also added a line to my menu.lst to boot it. I didn't do something right because I get a kernel panic when grub boots into the new partition.
menu.lst entry:
title Arch Testing
root (hd0,8)
kernel /boot/vmlinuz26 root=/dev/sda9 ro quiet vga=773 acpi_enforce_resources=lax vga=773
initrd /boot/kernel26.img
Ideas?
EDIT: Just read this wiki page
The fix as root:
mount /dev/sda9 /mnt
cd /mnt/dev
rm console ; mknod -m 600 console c 5 1
rm null ; mknod -m 666 null c 1 3
rm zero ; mknod -m 666 zero c 1 5
mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
mount -o bind /sys /mnt/sys
cd /
chroot /mnt /bin/bash
mkinitcpio -p kernel26
Last edited by graysky (2009-12-05 15:14:01)

Since you can't delete Apple IDs and having multiple Apple IDs can cause confusion, what you may want to do is rename your existing Apple ID to the new email (desired Apple ID). That would in effect do what you want, get rid of the old and give you the new.
See "Apple ID: Changing your Apple ID"
ivan

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

Similar Messages

Maybe you are looking for