Grub2 doesn't show Vista

[arilyn]

I recently installed Ubuntu 9.10 onto my second hard drive, and now I can't boot into Vista (installed on hard drive #1). Grub2 just doesn't seem to be recognizing that there is a Windows Vista installation on the first hard drive.

I followed this guide (http://erickoo.wordpress.com/2009/06/14/how-to-add-vista-partition-to-grub-2-ubuntu-9-10-karmic-koala/) (with Fabien's changes) because it seemed like they were having the exact same problem. But after rebooting, Vista is still not showing in the GRUB menu. In fact, the GRUB menu doesn't even show up unless I press Shift because it thinks that Ubuntu is the only OS installed on my computer.

My results with boot_info_script:


============================= Boot Info Summary: ==============================

=> Grub 2 is installed in the MBR of /dev/sda and looks for
(UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd)/boot/grub.
=> Windows is installed in the MBR of /dev/sdb
sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /Windows/System32/winload.exe

sdb1: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 9.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdb2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sdb5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x474a18c1

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 1,250,258,943 1,250,256,896 7 HPFS/NTFS


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x11d63aec

Partition Boot Start End Size Id System

/dev/sdb1 63 952,991,864 952,991,802 83 Linux
/dev/sdb2 952,991,865 976,768,064 23,776,200 5 Extended
/dev/sdb5 952,991,928 976,768,064 23,776,137 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 C64661004660F29B ntfs
/dev/sdb1 e94a058d-1d19-4a98-924b-1a5fce405bdd ext4
/dev/sdb5 af30f475-dad5-45fa-a92b-1f728bd74482 swap

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/sdb1 / ext4 (rw,errors=remount-ro)


=========================== sdb1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-19-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro quiet splash
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-19-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro single
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/11_Windows ###
menuentry "Microsoft Windows" {
insmod ntfs
insmod chain
insmod drivemap
set root=(hd0,1)
drivemap -s (hd0) (hd1)
chainloader +1
}
### END /etc/grub.d/11_Windows ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# 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.
### END /etc/grub.d/40_custom ###

=============================== sdb1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sdb1 during installation
UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=af30f475-dad5-45fa-a92b-1f728bd74482 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
=======Devices which don't seem to have a corresponding hard drive==============

sdc


Another weird thing:
When I was installing Ubuntu to HD2 (the 500gb one), I got a peculiar message saying that Windows was installed on it. There wasn't anything on HD2 though, because Windows Vista was most definitely installed on HD1.

However, if I chose to overwrite HD1 with Ubuntu, the message wouldn't come up. It seemed like the installer was confused as to which hard drive actually held my Windows Vista install.

I wonder if that's related to this current GRUB issue.

Thank you for any help, it's highly appreciated.

[amsterdamharu]

In your bios change the boot order of your harddisks, usually you get into the bios by pressing del on startup.

There is a way grub can fix this but have to look into it.

Please let me know if changing the bios will boot windows (you will have no option for ubuntu).

You can try this as well:
http://grub.enbug.org/ChainLoadWindows
You need the uuid of sda1 but some if the info you posted suggested boot sector is in sdb, this makes no sense to me since that's your ubuntu drive.

[presence1960]

This is what I would do. Put GRUB2 on MBR of sdb and restore sda MBR to windows. Set sdb (500 GB) to boot first in the hard disk boot order in BIOS.

Boot the Ubuntu Live Cd & choose "try ubuntu without any changes." When the desktop loads open a terminal & run
sudo mount /dev/sdb1 /mnt This will mount your Ubuntu / partition. next in terminal run
sudo grub-install --root-directory=/mnt/ /dev/sdb This will put GRUB2 on MBR of sdb

next still from the Live CD repair windows (sda) MBR. In terminal run
sudo apt-get install lilo This will install lilo to Live CD session only. Next in terminal run
sudo lilo -M /dev/sda mbr This will fix sda MBR to boot windows.

Now reboot without the Live Cd. Go into BIOS and set sdb (500 GB) as first hard disk in the hard disk boot order. Save changes to CMOS and continue booting into Ubuntu. Open a terminal and run
echo "SET grub-pc/install_devices /dev/sdb" | sudo debconf-communicate This will make sure all updates to GRUB (grub-pc) go to the sdb disk where you have GRUB.

If Vista is not in the GRUB menu run in terminal from Ubuntu
sudo update-grub

[darkod]

Another weird thing:
When I was installing Ubuntu to HD2 (the 500gb one), I got a peculiar message saying that Windows was installed on it. There wasn't anything on HD2 though, because Windows Vista was most definitely installed on HD1.

However, if I chose to overwrite HD1 with Ubuntu, the message wouldn't come up. It seemed like the installer was confused as to which hard drive actually held my Windows Vista install.

I wonder if that's related to this current GRUB issue.

Thank you for any help, it's highly appreciated.

It seems not the installer but you were the one confused. Looking at the results file now, I can only assume but here is my opinion:
Yes, you do have the vista system partition on HD1 but it seems you also had a vista boot partition on HD2. This would be marked System Reserved and it wouldn't show in Computer as a drive. So it's very easy to think it's not there or that it is on HD1. However, the boot partition is holding the boot files and hence the ubuntu installer telling you you have vista on HD2. When you selected Erase and use whole disk option you destroyed it.
You see in the top of the results file, under /dev/sda1 you are missing the vista boot files. You have only winload.exe and you also need to have /bootmgr and /Boot/BCD there. Those boot files are sometimes on separate small boot partition (it's similar with the new win7).
With those boot files missing, ubuntu has no clue you have vista at all, so it's not making a grub menu entry for it.
You need to repair the vista boot process, and as presence said, keep windows bootloader on the MBR of /dev/sda.
Move grub2 to /dev/sdb following the instructions posted.
But I don't think vista will be detected until vista boot process is repaired and the boot info script shows all three files: /bootmgr, /boot/BCD and winload.exe.
For instructions about repairing vista boot process manually with commands (preferred way):
http://ubuntuforums.org/showthread.php?t=1014708

PS. I forgot to mentioned. Before repairing the vista boot make sure you go into BIOS and make the windows disk first in hdd boot order. Windows always put it's bootloader on the first disk in the boot order. That is one option how your vista could end up on HD1, and the bootloader and boot files on HD2.

[presence1960]

It seems not the installer but you were the one confused. Looking at the results file now, I can only assume but here is my opinion:
Yes, you do have the vista system partition on HD1 but it seems you also had a vista boot partition on HD2. This would be marked System Reserved and it wouldn't show in Computer as a drive. So it's very easy to think it's not there or that it is on HD1. However, the boot partition is holding the boot files and hence the ubuntu installer telling you you have vista on HD2. When you selected Erase and use whole disk option you destroyed it.
You see in the top of the results file, under /dev/sda1 you are missing the vista boot files. You have only winload.exe and you also need to have /bootmgr and /Boot/BCD there. Those boot files are sometimes on separate small boot partition (it's similar with the new win7).
With those boot files missing, ubuntu has no clue you have vista at all, so it's not making a grub menu entry for it.
You need to repair the vista boot process, and as presence said, keep windows bootloader on the MBR of /dev/sda.
Move grub2 to /dev/sdb following the instructions posted.
But I don't think vista will be detected until vista boot process is repaired and the boot info script shows all three files: /bootmgr, /boot/BCD and winload.exe.
For instructions about repairing vista boot process manually with commands (preferred way):
http://ubuntuforums.org/showthread.php?t=1014708

PS. I forgot to mentioned. Before repairing the vista boot make sure you go into BIOS and make the windows disk first in hdd boot order. Windows always put it's bootloader on the first disk in the boot order. That is one option how your vista could end up on HD1, and the bootloader and boot files on HD2.


sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /Windows/System32/winload.exe


Good catch Darko. I did not notice bootmgr & BCD are missing from Vista boot files. With all the snow we are getting I think cabin fever is setting in on me. I need to take a break...lol. I agree Vista needs to have it's boot files fixed- that is why Vista isn't being detected by GRUB.

[darkod]

Good catch Darko. I did not notice bootmgr & BCD are missing from Vista boot files. With all the snow we are getting I think cabin fever is setting in on me. I need to take a break...lol. I agree Vista needs to have it's boot files fixed- that is why Vista isn't being detected by GRUB.

A little snow is your excuse now? :) Come on, you showed me the script. Pay attention to the results dude. ;):P

PS. No offense, just joking a bit. :popcorn:

[arilyn]

Thanks for all of the help so far. I've moved Grub2 to /dev/sdb, and I did what was required to restore the Vista bootloader (http://ubuntuforums.org/showthread.php?t=1014708).

However, Grub2 is still not detecting Vista.

My new results from boot_info_script are below:


============================= Boot Info Summary: ==============================

=> Windows is installed in the MBR of /dev/sda
=> Grub 2 is installed in the MBR of /dev/sdb and looks on the same drive in
partition #1 for /boot/grub.
sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows Vista
Boot files/dirs: /Windows/System32/winload.exe

sdb1: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 9.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdb2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sdb5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x474a18c1

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 1,250,258,943 1,250,256,896 7 HPFS/NTFS


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x11d63aec

Partition Boot Start End Size Id System

/dev/sdb1 63 952,991,864 952,991,802 83 Linux
/dev/sdb2 952,991,865 976,768,064 23,776,200 5 Extended
/dev/sdb5 952,991,928 976,768,064 23,776,137 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 C64661004660F29B ntfs
/dev/sdb1 e94a058d-1d19-4a98-924b-1a5fce405bdd ext4
/dev/sdb5 af30f475-dad5-45fa-a92b-1f728bd74482 swap

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/sdb1 / ext4 (rw,errors=remount-ro)


=========================== sdb1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-19-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro quiet splash
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-19-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro single
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd1,1)
search --no-floppy --fs-uuid --set e94a058d-1d19-4a98-924b-1a5fce405bdd
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# 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.
### END /etc/grub.d/40_custom ###

=============================== sdb1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sdb1 during installation
UUID=e94a058d-1d19-4a98-924b-1a5fce405bdd / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=af30f475-dad5-45fa-a92b-1f728bd74482 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
=======Devices which don't seem to have a corresponding hard drive==============

sdc


Update: When I set my Vista disk (HD1) to boot first in my BIOS hdd boot order, I'm getting a BOOTMGR is missing, press CTRL+ALT+DEL error.

It looks like Vista is still missing its bootloader. I'm going to play around with my Vista CD's system recovery options unless someone has a better suggestion.

[darkod]

Boot files/dirs: /Windows/System32/winload.exe

Hmm, you can see still no /bootmgr and /boot/BCD in the boot files list. I wonder if vista somehow knows it has a boot partition and does not restore those files on this system partition (because they were never there).
I'm not sure what to do next. Of course reinstalling vista would repair that but that's the last option, you would have to reinstall all software too.

I wonder if copying /bootmgr file and /boot/BCD folder from the vista dvd can help. Using ubuntu, you can try copying them from the dvd onto /dev/sda1. But this is pure speculation, I haven't done that before.

Until the files are there grub will ignore vista.

[arilyn]

Darko, I was able to solve the problem with my Vista CD's auto repair utility. Thanks for all your help. :)

[darkod]

Darko, I was able to solve the problem with my Vista CD's auto repair utility. Thanks for all your help. :)

Excellent. I would suggest running the script again. Don't post the results, just look for yourself, to make sure all is as supposed to be.
You should have windows bootloader on /dev/sda, and grub2 on /dev/sdb. You should also have all three boot files/folders in partition /dev/sda1 now. :)

PS. sudo update-grub should find your vista right away now.

[presence1960]

A little snow is your excuse now? :) Come on, you showed me the script. Pay attention to the results dude. ;):P

PS. No offense, just joking a bit. :popcorn:

No offense taken darko, it made me laugh. I was digging myself & my neighbors out for a few hours. :popcorn: