** Description changed:

  Binary package hint: grub2
  
  []Well, I hope people can find this bug report by its summary, because
  it was a bitch to troubleshoot.[/]
- 
  
  ###################################################################
  
  Operating Systems, Software in use
  
  Windows 7 ultimate 64bit
  
  $ lsb_release -rd
  Description:  Ubuntu 10.04 LTS
  Release:      10.04
  x86_64
  
  $ apt-cache policy grub-pc
  grub-pc:
-   Instalados: 1.98-1ubuntu6
-   Candidato: 1.98-1ubuntu6
-   Tabla de versión:
-  *** 1.98-1ubuntu6 0
-         500 http://es.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
-         100 /var/lib/dpkg/status
-      1.98-1ubuntu5 0
-         500 http://es.archive.ubuntu.com/ubuntu/ lucid/main Packages
+   Instalados: 1.98-1ubuntu6
+   Candidato: 1.98-1ubuntu6
+   Tabla de versión:
+  *** 1.98-1ubuntu6 0
+         500 http://es.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
+         100 /var/lib/dpkg/status
+      1.98-1ubuntu5 0
+         500 http://es.archive.ubuntu.com/ubuntu/ lucid/main Packages
  
  ###################################################################
  
  This bug is suspected to be related to bugs (possibly more):
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/454930
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/448889
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/484102
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/592798
  
  ###################################################################
  
  The Setup:
  
  processor: corei7 920, ram: 12GB, motherboard: p6t deluxe (x58 chipset).
  hard drives: Three 1TB SATA hard drives in AHCI mode.
  
  /dev/sda  contains(in order; size, type, flags):
  
  1MB(unallocated) || 100GB NTFS primary active boot || 831GB NTFS primary
  
  MBR and Boot sector:
  
  http://i25.tinypic.com/se0qi9.jpg
  
- 
  /dev/sdb *unrelated
  
  ******************************
- 
  
  /dev/sdc contains(in order; size, type, flags, mountpoint):
  
  196MB ext3 primary active /boot || 93GB ext4 primary / || 7GB (swap) ||
  831GB NTFS extended
- 
  
  40_custom:
  
  #!/bin/sh
  exec tail -n +3 $0
  # 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.
  
  menuentry "Microsoft Windows 7 Ultimate x64"  {
-       insmod ntfs
-       set root='(hd0,1)'
-         parttool (hd0,1) boot+
-       search --no-floppy --fs-uuid --set 3c78235378230aea
-       chainloader +1
+  insmod ntfs
+  set root='(hd0,1)'
+         parttool (hd0,1) boot+
+  search --no-floppy --fs-uuid --set 3c78235378230aea
+  chainloader +1
  }
  
  menuentry "Mac OS X Snow Leopard"  {
-          insmod hfsplus
-          insmod part_gpt
-          set root='(hd1,2)'
-          search --no-floppy --fs-uuid --set 
6080d08c-e796-35b3-8365-9cc05a3b7943
-          search --file --set=root /boot
-          multiboot /boot
+          insmod hfsplus
+          insmod part_gpt
+          set root='(hd1,2)'
+          search --no-floppy --fs-uuid --set 
6080d08c-e796-35b3-8365-9cc05a3b7943
+          search --file --set=root /boot
+          multiboot /boot
  }
- 
- 
  
  ###################################################################
  
  * What did I EXPECT:
  
  - Boot record is loaded correctly.
  - Windows boot manager is loaded, or "custom" boot manager is loaded.
  - Boot manager finds and loads BCD storage archive (Boot Configuration Data).
  - Windows Boot menu is presented, boot into windows.
  - in a privileged cmd, bcdedit loads system BCD; easyBCD, if present, loads 
system BCD.
  - Boot tab in msconfig is "unlocked", and values are editable.
- 
  
  * What did I GET:
  
  - Boot record is loaded correctly.
  - Windows boot manager is loaded, or "custom" boot manager is loaded.
  - Boot manager DOES NOT find BCD storage archive, some backup is loaded.
  - Windows Boot menu is presented, boot into windows.
  - In privileged cmd, bcdedit DOES NOT load system BCD, throws error:
  
  C:\Windows\system32>bcdedit
  No se pudo abrir el almacén de datos de configuración de arranque (BCD).
  El sistema no puede encontrar el archivo especificado.
  
  - EasyBCD is unable to load system BCD, offers to load alternative BCD.
  - In msconfig, the Boot tab is locked and unusable.
  
-  Other side effects:
+  Other side effects:
  
  - Is not possible to change certain file or archive permissions in c:\, 
c:\boot, and other places.
  - Problems with backup software acronis, error on restore image "autochk.exe 
program not found skipping autocheck"
-   is related.
+   is related.
  - Problems with "custom" loaders
  
  ###################################################################
  
  Conducted tests:
  
  In a "locked" state, entered in Repair Mode:
  
-  No windows installation is recognized.
-  Startup Fix does not solve the problem.
+  No windows installation is recognized.
+  Startup Fix does not solve the problem.
  
  In Repair Mode, tried to run from a repair console:
  
+  bootsect /nt60 c:
+  command success
+  still locked
  
-  bootsect /nt60 c:
-  command success
-  still locked
+  bootrec /fixboot
+  command error:
+  "Element Not Found"
  
-  bootrec /fixboot
-  command error:
-  "Element Not Found"
-  
-  bootrec /FixMbr
-  command success, no point
-  still locked
-  
-  bootrec /RebuildBcd
-  finds windows installation [c:] on sda1
-  option to add to BCD
-  command error:
-  "The volume does not contain a recognized file system"
-  still locked
+  bootrec /FixMbr
+  command success, no point
+  still locked
  
+  bootrec /RebuildBcd
+  finds windows installation [c:] on sda1
+  option to add to BCD
+  command error:
+  "The volume does not contain a recognized file system"
+  still locked
  
-  bootrec /scanOs
-  command success
-  finds windows installation [c:] on sda1
-  still locked
+  bootrec /scanOs
+  command success
+  finds windows installation [c:] on sda1
+  still locked
  
-  Load system again, this time booting from sda directly (configure boot from 
1st disk in BIOS)
-  
-  Repeat steps above.
-  Still locked.
+  Load system again, this time booting from sda directly (configure boot
+ from 1st disk in BIOS)
+ 
+  Repeat steps above.
+  Still locked.
  
  ###################################################################
  
-  Found Workaround, Temporal Fix:
+  Found Workaround, Temporal Fix:
  
-  Load system again, booting from sda directly.
+  Load system again, booting from sda directly.
  
-  Launch administrative console, and run commands:
+  Launch administrative console, and run commands:
  
-  diskpart
+  diskpart
  
-  select volume 1      (the system volume)
+  select volume 1      (the system volume)
  
-  select partition 1    (the system partition)
+  select partition 1    (the system partition)
  
-  active                    (make partition active)
+  active                    (make partition active)
  
+  System is now unlocked, BCD is found by loader, boot tab in msconfig is 
unlocked and works
+  easybcd loads system bcd without problem, bcdedit command throws current 
boot menu configuration.
  
-  System is now unlocked, BCD is found by loader, boot tab in msconfig is 
unlocked and works
-  easybcd loads system bcd without problem, bcdedit command throws current 
boot menu configuration.
+  The problem:
  
-  The problem:
- 
-  Everytime windows system loads through Grub2, system is locked.
-  If system loads "offline", system is unlocked.
+  Everytime windows system loads through Grub2, system is locked.
+  If system loads "offline", system is unlocked.
  
  ###################################################################
  
-  Conclussion:
+  Conclusion:
  
-  Grub2 loads the bootsector directly.
-  My guess is that grub2 doesn't pass the "active" parameter to the target 
partition properly.
-  parttool (hdx,y) boot+     doesn't work as advertised.
-  parttool ---- boot+   should work as "makeactive" command from legacy grub.
- 
+  Grub2 loads the bootsector directly.
+  My guess is that grub2 doesn't pass the "active" parameter to the target 
partition properly.
+  parttool (hdx,y) boot+     doesn't work as advertised.
+  parttool ---- boot+   should work as "makeactive" command from legacy grub.
  
  ###################################################################

-- 
Grub2 doesn't properly flag a partition as "active" or "boot", problems on 
windows 7 BCD
https://bugs.launchpad.net/bugs/607109
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to