Fedora Installation :: F15: Using Btrfs As Boot Partition?
May 25, 2011is it possible? If I select btrfs as /boot partition I get this error:
"Bootable partitions cannot be on an btrfs filesystem"
edit:should I use this guide? [URL]
is it possible? If I select btrfs as /boot partition I get this error:
"Bootable partitions cannot be on an btrfs filesystem"
edit:should I use this guide? [URL]
In my efforts to resize my BTRFS Partition, I accidentally unmarked my BTRFS partition as being BTRFS, and can't mark it back as I can't find the numeric ID for BTRFS and how to apply.
View 1 Replies View RelatedI have a brand new thinkpad X301 with 4GB of RAM and thinking of getting fedora 11 on it. The plan is to have it triple boot with vista/seven and hopefully OSx86. I am aware of the 4 primary partitions limit on an MBR disk. I was thinking of having a swap file instead of swap partition and not creating a boot partition as well. If I install the boot loader(GRUB?) on the root partition will I be able to boot it without any problems by using vista's boot loader?
Or Maybe I should install GRUB on the MBR and add all the other operating systems on it? Does anyone have any objections for not creating a swap partition or a boot partition? When comes to desktop environment I've been using KDE in the past, is there any major advantage of using Gnome over it? KDE seems to look really nice on fedora where Gnome is maybe more stable?
Im using parted when doing a new disk. If the disk is ext[234], xfs, jfs, parted displays the partition correctly, but if the partition was formated using reiser4 or btrfs the "File System" part there is nothing, like there is no formating done to the partition.
This is how Im using parted:ex.: parted -s /dev/sda print
Does anyone knows a patch to fix this issue?
My most recent F11 -> F12 was a near-fiasco, because I had the bad luck of foolishly having two distinct physical drives in the same system, where the /(root) partition on each drive had exact same UUID (result of partition cloning and neglect to change the UUID on the copy)
BUT! the UUID redundancy was not the initial trigger of my problems (its near-disastrousness played itself out only while I was REMEDYING the initial problem). The initial trigger: insufficient space on my /boot partition. "preupgrade" neglected to properly assess the space and/or warn me about it before proceeding.
In addition, the automatic cycling out of grub kernel entries came to bite me (part of many factors of the near-fiasco) because after the unfinished upgrade i had only one working kernel left to boot into, until I messed up that remaining one (too long a story), and then grub-install messed up my booting because of duplicate UUID. At any rate, at the end of what looked like a good preupgrade-reboot-upgrade-package-install process the post-install phase lingered a looong time, then I found myself booted into the old Fedora 11 kernel with absolutely NO modules (corresponding /lib/modules had been erased by the upgrade!) Somehow the system ran, but no USB, no wifi, no ethernet, no way to easily place the right kernel rpm onto the hard drive (had to unscrew the drive,etc., to copy over the correct kernel rpm). (Plus, file /boot/preupgrade/vmlinuz, left over from the arrested upgrade, was NOT the right target upgrade kernel version (2.6.32.9-70.fc12), so it didn't help either because it didn't have its modules either. The target /lib/modules (version 2.6.32.9-70.fc12) WERE there, but the kernel itself was NOT, due to upgrade running out of space on the /boot partition).
(Oh, and the preupgrade/upgrade had deleted my /var/cache/yum/preupgrade/ packages; hence my inability to quickly (re)install the 2.6.32.9-70.fc12 kernel rpm -- why!? it hadn't successfully finished the process!)
(Also, FWIW, i ended up rescuing the system through "rpm -i --force <kernel>", many an F12 rescue boot, chrooting, /boot/grub/grub.conf & fstab edits, tune2fs/uuidgen, running grub on command-line ("setup (hd0)"), etc., etc.)
So, any tips out there on phasing out the old-school /boot partition scheme, the safest and easiest way (without destroying a working system, of course)?
I upgraded my 9.10 installation to 10.04 and decided to try out btrfs on a some spare drives in the system.sudo mkfs.btrfs -m raid0 /dev/sdb /dev/sdc /dev/sddthe only way the system sees the btrfs array is by running btrfsctl -a and then mounting /dev/sdc. but that has to be done in userland, not at boot. if i try to mount it via fstab, ubuntu won't load because it can't find the mount point./dev/sdc /Images atasum,thread_pool=128,compress,rw,user 0 0so where am i going wrong? I tried mounting via the UUID also but that didn't seem to work for me either.
View 1 Replies View RelatedI installed fedora 10 on my laptop as a partition with vista. However i'm now not able to boot into my vista partition as everytime I try it comes with an error saying "bootmgr" is missing. Below is whats in my grub.conf file. However I am able to access my vista partition through fedora.
default=2
timeout=5
splashimage=(hd0,4)/grub/splash.xpm.gz
[code]....
I was creating dual-boot WinXP on my machine with F10 allready installed.
On my 1st try, windows froze when inspecting hardware, so I deleted boot partition with fdisk and then it works.
I installed succesfully XP on last partition on my drive, but XP won't boot because of hal.dll error (forums says it can be repaired by changing boot.ini).
Now what I want is to create new boot partition to reinstall grub.
I'm trying to do that from gparted live cd:
From gparted live, i entered console and did "fdisk /dev/sda".
When i type 'p', here is my output:
Code:
when I try to type 'n' to create a new partition, it tells me "No free sectors available".
Before /boot was on /dev/sda1 (Start@1, End@13), and NTFS was on /dev/sda13.
How can I recreate boot partition?
I am Quad booting my lappy with Fedora 12, Opensuse Karmic and Vista. Previously Grub2 is not recognising Fedora partition. Now i have managed to add Fedora entry to Grub2. But i got another problem, after selecting Fedora from grub menu, i cant get login window. I can see fedora sign at the bottom right corner of Laptop LCD.
View 2 Replies View RelatedI want to convert the file system on my boot drive from ext4 to btrfs.
I have converted by 2nd drive, unsure of how to convert the boot drive and partitions.
I am about to setup a computer with Maverick. This will be for experiment use only, there will be nothing of any critical nature on it. Should I consider using the BTRFS, yes or no ? What would be the advantages/disadvantages (if any) on using it as opposed to EXT4 ?
View 4 Replies View RelatedTrying to dual-boot OpenSolaris and FC10 is difficult because Solaris grub doesn't know about ext3 and Fedora grub doesn't know about ZFS. I was able to rescue my FC10 installation by creating a new FAT16 partition and restoring /boot to it from a dump, and then doing a grub setup to it. A complication is that anaconda doesn't seem to be able to find /dev/md0 (both the Solaris and FC10 installs use mirrored disks).
This process moved the FC10 ext3 partition from /dev/sda3 to /dev/sda4, but the other half of the mirror is still /dev/sdb3.
When I boot FC10 I get a "can't load image" error from grub, but it still loads FC10 successfully. It makes no difference if menu.1st/grub.conf has "root (hd0,1)" (the FAT16 partition) or "root (hd0,3)" (the FC10 ext3 partition).
If a future yum update were to try to install a new kernel, my FAT16 partition would not be updated. It seems to me both these problems might be solved if I could move /boot from /dev/md0 to /dev/sda2 (/dev/sda2 is the FAT16 partition).
Rather than go through yet another install, would the following work?
from FC10, move /boot to (say) /boot.0
mkdir /boot
edit fstab to include "mount /dev/sda2 /boot"
If I try this and it doesn't work, I can't see any way to undo it since anaconda doesn't seem to be able to mount /dev/md0. If a grub guru sees this, perhaps they could suggest a better alternative, or if not, whether this will work or not.
Additionally, although there are two alternatives in menu.1st/grub.conf, grub doesn't display a menu - it goes directly to boot. Any idea why? I suppose this might be a Solaris stage1 grub problem...
Since FAT16 doesn't support links, it isn't possible to link grub.conf to menu.1st. Are they both required?
I guess this is the right forum category for this. Am using the preupgrade method to go from F10 to F11.Downloading packages now. Just wondering if anybody knows if Anaconda will give me options to set up separate (ext3) partition for boot? (Since current grub won't work in the new ext4 file system scheme.)
View 2 Replies View RelatedIt appears that the default boot partition is too small for F12 preupgrade:[URL].. Did anyone try to see if enough space is freed by following these steps? : http://fedoraproject.org/wiki/PreUpg...ace_in_.2Fboot
Namely,
1. Leave only 1 kernel
2. tune2fs -r 0 /dev/xxx
3. remove /boot/efi and splash.xpm.gz
"preupgrade now requires at least 167MB" means more space could be needed, and I'm unclear if the above is sufficient.
I am triple booting
Windows xp
UBUNTU 10.04
Fedora 13
Everything works fine, the setup went very well. But I got to thinking (A dangerous thing for me). In Ubuntu I am using separate partitions for / (root) and /home. I was wondering, during install of Fedora, could I use the separate partition I am using now for both root and /home for just / (root) and use the Ubuntu /home partition for Fedora (set the mount point for /home to the same partition as I did for Ubuntu and not format the drive)? This would allow me to seamlessly use the /home partition and not require duplication of files. I can mount the Ubuntu /home dir while in Fedora.I can share the /home partition with two different installs of Ubuntu (been there).
You probably know by heart the old tale of the guy who is preupgrading for as long as he can remember and eventually finds out /boot is too small for F13. Since removing old kernels didn't free enough space, I am now considering resizing /boot to 500MB. After reading stuff around the internet I have a rough idea of how to proceed (for instance, that I will need to install GRUB on the relocated /boot, etc. etc.), but since I do not want to run unnecessary risks I would like to ask you to do a sanity check on my plans. My HD is currently laid out like this:
/dev/sda1 : 128GiB, ntfs, contains a (broken) Windows installation and some other stuff.
/dev/sda2 : 131GiB, ntfs, holds the FLAC rips of my CDs and other important space-wasting stuff.
/dev/sda3 : 196 MiB, ext3, /boot of course.
[code]....
just installed Fedora 15 on my system alongside Ubuntu 10.10 on My 500 GB hard disk.However on starting the computer the Fedora 15 partition gets loaded automatically. How do I access
my Ubuntu 10.10 partiion? I want to have a choice at start-up which OS to use. On my previous computer when I used to have Windows and Ubuntu,a menu used to appear asking which operating system to load.
I somehow recalled a rule re the location of the boot partitions with LILO being required to be in the first part of the drive (1024 cylinders, it seems) and I found it indeed in an old doc:
Boot Partition: Your boot partition ought to be a primary partition, not a logical partition. This will ease recovery in case of disaster, but it is not technically necessary. It must be of type 0x83 "Linux native". If you are using lilo, your boot partition must be contained within the first 1024 cylinders of the drive. (Typically, the boot partition need only contain the kernel image.) Is this still valid in GRUB, esp in Fedora 10?
I was impressed to be asked on Fedora 10 if I want to upgrade to Fedora 11 but the first time I tried I had this error:
Not enough space in /boot/upgrade to download install.img.
My boot partition is 99MB and AFAIK that is not unusual so I tried tidying up a bit, uninstalling all except 2 kernels, and now have about 80MB for whatever needs to be downloaded in /boot/upgrade. But I get the same error. I can fix this by using wired instead of wireless networking but I want to know for planning purposes (next time I create a boot partition) how much space is required?
$ ls -l /boot/upgrade
total 21594
-rw-r--r-- 1 root root 18985802 2009-06-03 00:02 initrd.img
-rw-r--r-- 1 root root 3035056 2009-06-03 00:02 vmlinuz
Should I delete these? It looks like they might be left over from last time but I assume preupgrade knows what is junk and what isn't.
I wanted to experiment with Fedora 14.
The machine has Windows XP and Ubuntu 9.10.
Before today when I turned the machine on there was a black screen with many Linux kernels to choose from and Windows.
I created another for Fedora and installed it on there - the Ubuntu root partition is still there.
When I boot now, there is a blue Fedora screen with just it and Windows.
To make matters worse Fedora doesn't work with my graphics card (Matrox). I would like to get Fedora working but still want to have the ability to use Ubuntu again.
What do I need to change to be able to boot into Ubuntu again and how do I do it?
Well Fedora 14 sees my Emu soundcard right out of the gate with the live cd! I have windows 7 installed right now. I would like to install Fedora 14 from the live cd to have a duel boot setup. What I am trying to do is just give Fedora 60GB of the drive and keep the rest for Winows. How can I go about this with the live cd. I am sure it's been covered to death but I couldn't really find it.
View 14 Replies View RelatedI will be installing Fedora 15 on my work laptop this weekend and am wondering: Could I use BTRFS as the default filesystem? Why or why not?
My default layout looks like this:
/boot
LVM
swap
/
/home
This would mean that all the LVM partitions would become BTRFS. Or maybe only the /home would become BTRFS.
Different threads state that you shouldn't use BTRFS yet on production systems, but there are also plans to include it in F16 as the default FS.
Why should (or shouldn't) I use BTRFS as opposed to EXT4?
So I have installed Debian through debootstrap and it seemed to go off without a hitch, the problem came problem came about during the boot process. I am dual-booting with Arch and use Systemd-boot as my bootloader... it finds the kernal and initrd and starts to boot but I run into this problem where it gets to the options part for root and doesn't mount. have done this very same installation on virtualbox with ext4 filesystem and it worked without a hitch.. I know it has something to do with the btrfs subvolumes I'm so new to Debian I haven't made it past this installation process..
here is my lsblk
Code: Select all
sda 8:0 0 /My_Files
sdb 8:32 0 /home
sdc 8:48 0
[code]....
I have installed btrfs-tools and I don't know what the following means... It seems to do the first two fine, vmlinuz and initrd.img but it doesn't find my root because maybe it doesn't recognize the 'rootflags' tag? or Debian doesn't automatically deal with btrfs-subvolumes nicely?
Code:
Select allBegin: checking root file system . . . fsck from util-linux 2.25.2
/sbin/fsck.btrfs: BTRFS file system
mount: mounting PARTUUID=................................................................ on /root failed
Target filesystem doesn't have requested /sbin/init
Having already borked my system once while deciding to nstall Fedora 10 under the influence of a false sense of bravado, alcohol induced, I thought I should ask for a little insight before trying things again. Once I get my system fixed and before consuming alcohol that is.Short version:I thought Id be smart and mount the /home partition I use for openSUSE as /home for Fedora, I mean that why I made /home it own partition right? Well, thatwhen the alcohol took over and I thought I be rilliant(not so much) and just use my SUSE username for Fedora too, since, you know,e already got all my files and settings stored there.
Thus my request for the answer on how to correctly use the same /home partition across multiple OS installations; with the preferred goal of retaining access to email folders, various files, games (WINE) and such no matter what distro I�m using. Would it really be as simple as just not using the same user name for more than one distro? What addtional issues does that solve/create
Finally updates are broken - I've been able to use my upgraded F12 system for some time, faithfully keeping up with f10, then f11. Just yesterday it finally broke:
Test Transaction Errors: installing package kernel-2.6.31.12-174.2.22.fc12.i686 needs 10MB on the /boot filesystem
It would appear that the most recent kernel update has broken the 10MB barrier initially set by the version I first installed (for the boot partition). Needless to say, I have quite an investment in this machine, and of course no time to back it all up and do a fresh F12 install. I am hoping someone out there can give me a bulletproof way to steal some space and expand the boot partition...
I'm trying to achieve my dream (but indeed not perfect) boot scenario: dual-boot OpenSUSE and Fedora with shared /boot, /home and SWAP partitions. First I installed OpenSUSE (sda3 on my layout below) with separate /boot (sda2), /home (sda5, encrypted) and SWAP (sda6), next I installed Fedora on /dev/sda1, and pointed it to mount sda2, sda5, sda6 with respective mount points, without formatting. I proceeded with the installation without installing new GRUB bootloader (overwriting an existing one).
It was successfull and now I'm back in OpenSuSE trying to edit menu.lst file (under /boot/grub) to make GRUB boot Fedora.
I attached a copy of menu.lst I cooked up for now. OK, it's a mess. Life would be allot easier if I didn't have a separate /boot partition, as I could just chainload, but it's no longer possible (or is it?). May be I needed to specify the resume device or problem is in initrd? below are the contents of /boot:
I'm running Maverick on an older Stinkpad. I have a btrfs /home as a second partition on the internal HDDand a brand shiny new 3TB external USB western digital drive also formatted btrfs. I'm having a problem whenever I hibernate/suspend the laptop by closing the lid and start it back up later, the external drive won't remount unless I do a complete reboot. I have no entry in /etc/fstab for the external drive.Quote:Unable to mount "blah" DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending
View 3 Replies View RelatedI have a computer with windows xp on it, and i want to dual boot with fedora 11. I have 2 hard drives in it, 1 500gb HD and 1 350gb HD. the 350 isnt much concern b/c its just sitting there all free and unpartitioned right now. Now my 500gb is split into 3 partitions, a 20gb(with xp installed on it) a 105 gb with pretty much nothing on it and a 350gb with all my data.
My problem is I'm trying to resize my 20gb partition through the fedora 11 installer and when I tell it to resize say to 10gb it starts and fails the resize. its a NTFS partition and the windows stuff on the partition is only about 8gb. any idea whats going on? the only error I get is "The resize has failed"
I hear that the non-live version of F15 has an option to choose the btrfs filesystem. I only see the DVD version as a non-live version and it's 3.4 Gigs. Is there a non-live CD version available?
View 3 Replies View RelatedI'm currently running the XFCE Spin of Fedora 15 (Xedora, as I like to call it (; ) on 64 bit, so sometimes I need a 32 bit environment to try stuff out.
I recently installed Linux Mint on a partition formatted to btrfs, and this is where my problems start, as I have no idea how to add this installation to my existing GRUB configuration. The grub.cfg on the Mint partition looks like this (GRUB2 btw.):
Code:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
[Code].....