https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c2 --- Comment #2 from Michael Chang <mchang@suse.com> 2012-03-07 10:55:30 UTC --- Try to use grub2-setup directly .. $ grub2-setup -f /dev/sda2 grub2-setup: error: unable to identify a filesystem in hd0; safety check can't be performed. Yes. Extended partition definitely had no file system (this the safety check becomes superfluous?). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c4 --- Comment #4 from Michael Chang <mchang@suse.com> 2012-03-08 16:29:36 UTC --- (In reply to comment #3)

Use --skip-fs-probe, I can embed core,img into extended partition

s/core/boot/ -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c6 --- Comment #6 from Michael Chang <mchang@suse.com> 2012-03-09 04:32:42 UTC --- The error returning : /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/sda2. Check your device.map. was due to extended partition is neglected in msdos partition iteration intentionally (not treated as normal partition), hooks would not trigger for it thus it wouldn't get any chance be added to internal structure, which leads to above error due to it's absent in it(and unfortunately the message is a bit misleading). Simply get rid of the extended partition check would make it be iterated, but got a lot of seek error. After checking the size of extended partition block device I realized why : $ dd if=/dev/sda2 of=/dev/null 2+0 records in 2+0 records out 1024 bytes (1.0kB) copied, 0.0107428 s, 95.3 kB/s We have to trim it's partition size to 2 (the size in partition table covers all logical partition).. it's not a disk block device like /dev/sda but a partition device which should not overlap others .. otherwise some tools may accidentally overwrites it. The test now works for me .. $ /usr/sbin/grub2-probe --device-map=/boot/grub2/device.map --target=drive --device /dev/sda2 (hd0,msdos2) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c8 --- Comment #8 from Michael Chang <mchang@suse.com> 2012-03-09 07:26:40 UTC --- With above two patches, grub2 installation works on extended partition. $ grub2-install --skip-fs-probe --force /dev/sda2 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c10 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #10 from Michael Chang <mchang@suse.com> 2012-03-09 09:00:30 UTC --- According to http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory SR to factory for review .. cool. :) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c12 --- Comment #12 from Michael Chang <mchang@suse.com> 2012-03-12 02:48:31 UTC --- citing the kernel source for about the size of extended partition .. fs/partitions/msdos.c int msdos_partition(struct parsed_partitions *state) sector_t sector_size = bdev_logical_block_size(state->bdev) / 512; ... if (is_extended_partition(p)) { /* * prevent someone doing mkfs or mkswap on an * extended partition, but leave room for LILO * FIXME: this uses one logical sector for > 512b * sector, although it may not be enough/proper. */ sector_t n = 2; n = min(size, max(sector_size, n)); put_partition(state, slot, start, n); strlcat(state->pp_buf, " <", PAGE_SIZE); parse_extended(state, start, size); strlcat(state->pp_buf, " >", PAGE_SIZE); continue; } The "sector_size" is logical block size in unit or sector, which defaults to 1 (512 byte) on most hardware (See below). The "size" is extended partition size on msdos table which is unlikely be less than 2 (just one sector .. can't wonder any setup would it be created this way). /** * blk_queue_logical_block_size - set logical block size for the queue * @q: the request queue for the device * @size: the logical block size, in bytes * * Description: * This should be set to the lowest possible block size that the * storage device can address. The default of 512 covers most * hardware. **/ void blk_queue_logical_block_size(struct request_queue *q, unsigned short size) { q->limits.logical_block_size = size; if (q->limits.physical_block_size < size) q->limits.physical_block_size = size; if (q->limits.io_min < q->limits.physical_block_size) q->limits.io_min = q->limits.physical_block_size; } EXPORT_SYMBOL(blk_queue_logical_block_size); -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c14 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #14 from Neil Rickert <nrickert@ameritech.net> 2012-03-19 23:04:58 UTC --- I have experienced this, and a related problem. This was with M2 installs. First system, a laptop. I installed 32 bit from the DVD image. The installer defaulted to putting grub2 on the extended partition (sda4). That failed, similar to what Chang is reporting, with an error message about a failure to map sda4. The failover to grub1 went smoothly enough. Second system, a desktop. I installed 64 bit from the DVD image. The installer defaulted to putting grub2 on the extended partition (sda4). Based on my experience with the laptop, I changed that to install on "/boot" (sda6). The grub install went fine, but the reboot to complete the install failed. Booting to rescue mode, I noticed that the extended partition had been marked active even though grub2 was not installed there. That is surely a bug. I switched the active partition back to where it should have been, and rebooted. That got me to my grub boot menu for 12.1, and there I selected the entry I already had to boot the 12.2 M2 system. Things went fine. If the installer had done something like: dd if=/dev/sda6 of=/dev/sda4 bs=440 count=1 after the grub2 install, that would probably also have worked. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c16 --- Comment #16 from Neil Rickert <nrickert@ameritech.net> 2012-03-20 02:55:07 UTC --- If it didn't work, there is something buggy about that. As I recall, the grub1 install might do something similar (switch the active flag). However, there's an option to have it not do that. And I always select that option when installing on a logical drive. That option was not available on the grub2 configuration screen. I'm hoping it will get there by the time of the final 12.2 release. Flagging "/dev/sda5" active would not help. I flagged "/dev/sda3" active, since that's what I normally use. That gets me to the grub menu for my 12.1 install. I have an entry in the 12.1 menu to boot "/dev/sda6" (chainloader), and using that got me to the grub2 menu. My personal opinion: If grub is not installed on one of the primary partition sectors, then the installer should leave the active flag the way it is, and perhaps display a notice that the user will need to find a way to boot from the logical partition where it was installed. In any case, if installing to the extended partition will work for future versions, that should solve the problem. I added my comments above just to provide feedback on where there might be problems with M2. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=750897 https://bugzilla.novell.com/show_bug.cgi?id=750897#c18 --- Comment #18 from Bernhard Wiedemann <bwiedemann@suse.com> 2012-03-20 16:00:32 CET --- This is an autogenerated message for OBS integration: This bug (750897) was mentioned in https://build.opensuse.org/request/show/110168 Factory / grub2 -- 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.