[opensuse] Btrfs: Error Upon Installation
Hi, I installed btrfs over an EXT4 operating system partition (/), and I got a strange error message. The options the dialogue box gave pertaining to the error were Continue and Abort. I clicked Continue, and then I got a lengthy error message about a problem creating initrd. I clicked continue or ignore (I forget), and if I recall correctly the installation finished. I think when I rebooted the system, all I got was a black grub screen with a flashing cursor. Has anyone else gotten this? I installed btrfs on another test laptop and there were no problems. The drive I'm using has no bad sectors and passes SMART, so I don't think it's that. Here is the error message: "Failure occured during the following action: Formatting partition /dev/sda3 (20.00 GiB) with btrfs System error code was: -3043 /bin/mount -t btrfs -o subvolid=0,acl,user_xattr '/dev/sda3' '/tmp/libstorage-CDkTv4/tmp-mp-MB9Er9': mount: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try ... Continue despite the error" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
By the way, here's my partition setup on my workstation: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 156M 0 part /boot/efi ├─sda2 8:2 0 2G 0 part [SWAP] ├─sda3 8:3 0 20G 0 part / └─sda4 8:4 0 909.4G 0 part /home sr0 11:0 1 1024M 0 rom After the btrfs install failed, I couldn't import mount points in YaST as that failed. I had to go into expert partitioner, and YaST wanted to create another 2 partitions in what looked like what was free on my sda4 partition. I deleted those entries and now I'm all back up and running on EXT4 and everything is great. I don't mind using btrfs if I can get past the error. On Fri, Nov 7, 2014 at 5:00 AM, Sam M. <backgroundprocess@gmail.com> wrote:
Hi,
I installed btrfs over an EXT4 operating system partition (/), and I got a strange error message. The options the dialogue box gave pertaining to the error were Continue and Abort. I clicked Continue, and then I got a lengthy error message about a problem creating initrd. I clicked continue or ignore (I forget), and if I recall correctly the installation finished. I think when I rebooted the system, all I got was a black grub screen with a flashing cursor. Has anyone else gotten this? I installed btrfs on another test laptop and there were no problems. The drive I'm using has no bad sectors and passes SMART, so I don't think it's that. Here is the error message:
"Failure occured during the following action: Formatting partition /dev/sda3 (20.00 GiB) with btrfs
System error code was: -3043
/bin/mount -t btrfs -o subvolid=0,acl,user_xattr '/dev/sda3' '/tmp/libstorage-CDkTv4/tmp-mp-MB9Er9': mount: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
...
Continue despite the error" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/07/2014 08:12 AM, Sam M. wrote:
After the btrfs install failed, I couldn't import mount points in YaST as that failed. I had to go into expert partitioner, and YaST wanted to create another 2 partitions in what looked like what was free on my sda4 partition. I deleted those entries and now I'm all back up and running on EXT4 and everything is great. I don't mind using btrfs if I can get past the error.
How did you get "back up and running"? How did you rebuild your seemingly corrupted root? My setup is much simpler # Start End Size Type Name 1 34 3906250 1.9G EFI System primary 2 3907584 15624191 5.6G Microsoft basic primary 3 15624192 1953523711 924.1G Linux LVM primary and then everything lives in the LVM # lvscan -v ACTIVE '/dev/vgmain/vDocuments' [5.00 GiB] inherit ACTIVE '/dev/vgmain/vDownloads' [5.00 GiB] inherit ACTIVE '/dev/vgmain/vROOT' [20.00 GiB] inherit ACTIVE '/dev/vgmain/vMail' [5.00 GiB] inherit ACTIVE '/dev/vgmain/vMusic' [10.00 GiB] inherit ACTIVE '/dev/vgmain/vImages' [5.00 GiB] inherit ACTIVE '/dev/vgmain/vSRV' [5.00 GiB] inherit ACTIVE '/dev/vgmain/vTMP' [10.00 GiB] inherit ACTIVE '/dev/vgmain/vUsrShare' [5.00 GiB] inherit ACTIVE '/dev/vgmain/vHome' [8.00 GiB] inherit ACTIVE '/dev/vgmain/VirtualBox' [30.00 GiB] inherit # pvscan -v PV /dev/sda3 VG vgmain lvm2 [924.06 GiB / 776.06 GiB free] As you see, I have the same size disk as you, but LVM gives me the ability to partition it with more granularity. Those are a mix of BtrFS and ReiserFS. You can tell i like btrees. Most of those partitions live under ~anton/. Using LVM I can take snapshots, which makes backing up much simpler. Having /tmp on a separate partition is a preventative control against (1) link bug security problems and (2) to limit resource consumption by any runaway process. Yes, (1) has been fixed but could recur. And (2) can always recur. Having BtrFS as one global FS is not the best idea I've heard of this century. Yes, the root FS fits on a 20G drive if you move /tmp and /usr/share and /tmp off it. Strictly speaking it will fit on a 10G FS. # df -h / Filesystem Size Used Avail Use% Mounted on /dev/mapper/vgmain-vROOT 20G 8.3G 11G 45% / Provided, that is, you use ReiserFS or BtrFS. Ext3/4 you might meet inode exhaustions while data space is still available. The 5G partitions (or not filled 8G) fir on a DVD for easy backup. Realistically, ~anton/ fits because I don't backup the various 'cache' files that live there. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/07/2014 08:00 AM, Sam M. wrote:
Hi,
I installed btrfs over an EXT4 operating system partition (/),
What do you mean by that? Did you reformat the partition? BtrFS has the ability to read in and sort-of-convert an extFS into itself. Is that what you did? Was this part of a new installation from a distribution DVD?
got a strange error message. The options the dialogue box gave pertaining to the error were Continue and Abort. I clicked Continue, and then I got a lengthy error message about a problem creating initrd. I clicked continue or ignore (I forget), and if I recall correctly the installation finished. I think when I rebooted the system, all I got was a black grub screen with a flashing cursor. Has anyone else gotten this? I installed btrfs on another test laptop and there were no problems. The drive I'm using has no bad sectors and passes SMART, so I don't think it's that. Here is the error message:
I think your problem was you rebooted even though you had been told that the rebuild of the initrd had failed. Given that I would not trust the initrd. In such situation I would have either backed up /boot or told the build process to rebuild one and only one initrd.
"Failure occured during the following action: Formatting partition /dev/sda3 (20.00 GiB) with btrfs
Without more detail about at the error was you can only assume that the partition is in an indeterminate and therefore unusable state. One reason I use LVM is so that, in such circumstances, I can mirror a partition before doing anything 'drastic', and lets face it, converting a FS is non-trivial! Wrote You don't say whether the 'test laptop' was similar process or a 'new install'. I don't think what you describe can be counted as a failure of BtrFS. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
What do you mean by that?
Did you reformat the partition? BtrFS has the ability to read in and sort-of-convert an extFS into itself. Is that what you did?
Was this part of a new installation from a distribution DVD?
I used a USB key that I created with dd, the same one I had no problems with on the test laptop and with my earlier 13.2 install on my workstation. I did reformat sda3 (/). I don't remember seeing any option to read-in and convert the EXT4 partition. I had it set to create the btrfs partition for sda3 within the same block ranges that the previous EXT4 partition was in, so the size was exactly the same. The "F" option was toggled (for format). I can do the whole process over again if needed, but I'm going to create another backup first.
I think your problem was you rebooted even though you had been told that the rebuild of the initrd had failed. Given that I would not trust the initrd.
In such situation I would have either backed up /boot or told the build process to rebuild one and only one initrd.
I didn't either, in fact, I didn't trust anything after that first error message. I can't have this workstation be down very long so I just reinstalled and went back to EXT4.
You don't say whether the 'test laptop' was similar process or a 'new install'
It was a new install over NTFS, on a laptop somebody gave to me. The only element which was the same was that I used (as I wrote above) my USB key for the install. On Fri, Nov 7, 2014 at 5:56 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
On 11/07/2014 08:00 AM, Sam M. wrote:
Hi,
I installed btrfs over an EXT4 operating system partition (/),
What do you mean by that?
Did you reformat the partition? BtrFS has the ability to read in and sort-of-convert an extFS into itself. Is that what you did?
Was this part of a new installation from a distribution DVD?
got a strange error message. The options the dialogue box gave pertaining to the error were Continue and Abort. I clicked Continue, and then I got a lengthy error message about a problem creating initrd. I clicked continue or ignore (I forget), and if I recall correctly the installation finished. I think when I rebooted the system, all I got was a black grub screen with a flashing cursor. Has anyone else gotten this? I installed btrfs on another test laptop and there were no problems. The drive I'm using has no bad sectors and passes SMART, so I don't think it's that. Here is the error message:
I think your problem was you rebooted even though you had been told that the rebuild of the initrd had failed. Given that I would not trust the initrd.
In such situation I would have either backed up /boot or told the build process to rebuild one and only one initrd.
"Failure occured during the following action: Formatting partition /dev/sda3 (20.00 GiB) with btrfs
Without more detail about at the error was you can only assume that the partition is in an indeterminate and therefore unusable state.
One reason I use LVM is so that, in such circumstances, I can mirror a partition before doing anything 'drastic', and lets face it, converting a FS is non-trivial!
Wrote You don't say whether the 'test laptop' was similar process or a 'new install'.
I don't think what you describe can be counted as a failure of BtrFS. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/07/2014 09:26 AM, Sam M. wrote:
What do you mean by that?
Did you reformat the partition? BtrFS has the ability to read in and sort-of-convert an extFS into itself. Is that what you did?
Was this part of a new installation from a distribution DVD?
I used a USB key that I created with dd, the same one I had no problems with on the test laptop and with my earlier 13.2 install on my workstation.
In another thread, James Knott describes problems install from a USB key. My not be pertinent but I suggest you review that thread.
I did reformat sda3 (/). I don't remember seeing any option to read-in and convert the EXT4 partition.
Well, since it was reformatted, of course not, but I recall on a older install that exists. I don't recall if its for ext4 or just ext3.
I had it set to create the btrfs partition for sda3 within the same block ranges that the previous EXT4 partition was in, so the size was exactly the same. The "F" option was toggled (for format). I can do the whole process over again if needed, but I'm going to create another backup first.
"block ranges"? I've never needed to go down to that level. Mind you, I usually follow Felix Miata's advice and format/partition the disk before hand with something like Knoppix, or just upgrade from the previous version of suse. Windows hasn't touched a disk of mine this century. (I'm considering install VirtualBox and running a virtual Windows, probably XP, just to remind myself what I'm missing, and then delete it all!, but that's a separate issue.)
I think your problem was you rebooted even though you had been told that the rebuild of the initrd had failed. Given that I would not trust the initrd.
In such situation I would have either backed up /boot or told the build process to rebuild one and only one initrd.
I didn't either, in fact, I didn't trust anything after that first error message. I can't have this workstation be down very long so I just reinstalled and went back to EXT4.
You don't say whether the 'test laptop' was similar process or a 'new install'
It was a new install over NTFS,
HIC! I presume you mean that it was over-writing a NTFS file system HIC! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/11/2014 15:22, Anton Aylward a écrit :
century. (I'm considering install VirtualBox and running a virtual Windows, probably XP, just to remind myself what I'm missing, and then delete it all!, but that's a separate issue.)
for such see the hell thing, better try Vista :-) (or windows 8) :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2014 10:56 AM, jdd wrote:
Le 10/11/2014 15:22, Anton Aylward a écrit :
century. (I'm considering install VirtualBox and running a virtual Windows, probably XP, just to remind myself what I'm missing, and then delete it all!, but that's a separate issue.)
for such see the hell thing, better try Vista :-) (or windows 8)
Why bother? I found a set of XP installation disks & upgrades in the Closet Of Anxieties with the (broken, useless) machine they had been installed on (along with a a yellow sticky with some rude comments). The Vista licenses are in use. People here say they don't want to have anything to do with "8" (and ask whatever happened to "9"[1]) and I don't plan to add to MS's coffers. Its not as if this is serious, just do it to show I can and add a line to my resume, what ho, what ho :-) Of course some people _have_ to take it seriously. I'm glad I don't. [1] I know but they won't believe me. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 11/07/2014 09:26 AM, Sam M. wrote:
I had it set to create the btrfs partition for sda3 within the same block ranges that the previous EXT4 partition was in, so the size was exactly the same. The "F" option was toggled (for format). I can do the whole process over again if needed, but I'm going to create another backup first.
"block ranges"? I've never needed to go down to that level.
"block ranges" = partition limits. -- Per Jessen, Zürich (6.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
jdd -
Per Jessen -
Sam M.