https://bugzilla.novell.com/show_bug.cgi?id=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c21 --- Comment #21 from Michael Chang <mchang@suse.com> 2013-10-18 11:14:41 UTC --- (In reply to comment #20)
NO, uEFI can't found the start Partition.
Could it be the -F32 option that made the trouble ? In your btrfs log there's some warning on formatting /dev/md126p1 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mkdosfs -F32 '/dev/md126p1'" 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "WARNING: Not enough clusters for a 32 bit FAT!" 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:4036 added lines:1 stderr:true 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "mkfs.fat 3.0.22 (2013-07-19)" 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:4036 added lines:1 stderr:false 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 0.020440s for "/sbin/mkdosfs -F32 '/dev/md126p1 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:0 However your ext3 log didn't use -F32 and looked fine. 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mkdosfs '/dev/md126p1'" 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "mkfs.fat 3.0.22 (2013-07-19)" 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:3941 added lines:1 stderr:false 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 0.011264s for "/sbin/mkdosfs '/dev/md126p1'" 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:0
The only way to start the system is without Btrfs.
I have no idea on how Btrfs would be related. :( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.