About dualboot installation

[satimis]

Hi,

Fedora 17 64bit

I installed Fedora 17 on a HD which is running Ubuntu 9.04, 64bit. The HD has not been running for sometimes sitting on the shelves. It is a SATA3 HD with 1T in size and 32M memory. Ubuntu 9.04 only takes up about 100G capacity of the HD. I performed following steps to install Fedora 17 for testing Cloud.

- running Fedora 17 live on USB
- selecting shrieking existing OS to get space for installation
- installation completed without complaint
- running yum update

Now Fedora can start up without problem. But I can't resolve how to boot Ubuntu 9.04. Please help. TIA

If I made wrong steps installing Fedora 17, is there any way wiping it out to start again?

B.R.
satimis

[yancek]

Now Fedora can start up without problem. But I can't resolve how to boot Ubuntu 9.04. Please help.

Do you not see an entry for Ubuntu 9.04 in the Fedora Grub2 boot menu? If not, run this command as root in Fedora:

grub2-mkconfig -o /boot/grub2/grub.cfg

If that's not the problem, more details such as the fdisk output.

[satimis]

[QUOTE=yancek;901469]Do you not see an entry for Ubuntu 9.04 in the Fedora Grub2 boot menu?

Hi,

$ sudo ~/Downloads/Bootinfoscript/bootinfoscript

Boot Info Script 0.61      [1 April 2012]

Identifying MBRs...
Computing Partition Table of /dev/sda...
Searching sda1 for information... 
Searching sda2 for information... 
Searching sda5 for information... 
Searching sda3 for information... 
Searching sda4 for information... 
Searching vg_fedora17-lv_swap' for information... 
Searching vg_fedora17-lv_home' for information... 
Searching vg_fedora17-lv_root' for information... 

Finished. The results are in the file "RESULTS.txt"
located in "/home/satimis/Downloads/Bootinfoscript/".

Please see RESULTS.txt attached to this posting. Thanks

B.R.
satimis

[yancek]

What was the result of running the grub2-mkconfig command?

Your sda1 has a problem as you can see in the results.txt file. Looks in partition 256 for Grub?? I'm not familiar with LVM so I don't know what all the messages regarding those partitions mean. Obviously, there is no menuentry for Ubuntu in Fedora. The last time I installed Fedora, it picked up and created entries for other Linux systems which is a change from previous Fedora installs. I don't know why it didn't pick up Ubuntu unless the filesystem is damaged? Try the grub2-mkconfig and see if you can boot. See if you can mount sda1 and access any directories/files in Ubuntu.

[satimis]

What was the result of running the grub2-mkconfig command?

# grub2-mkconfig -o /boot/grub2/grub.cfg

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.5.2-1.fc17.x86_64
Found initrd image: /boot/initramfs-3.5.2-1.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.3.4-5.fc17.x86_64
Found initrd image: /boot/initramfs-3.3.4-5.fc17.x86_64.img
done

Your sda1 has a problem as you can see in the results.txt file. Looks in partition 256 for Grub?? I'm not familiar with LVM so I don't know what all the messages regarding those partitions mean. Obviously, there is no menuentry for Ubuntu in Fedora. The last time I installed Fedora, it picked up and created entries for other Linux systems which is a change from previous Fedora installs. I don't know why it didn't pick up Ubuntu unless the filesystem is damaged? Try the grub2-mkconfig and see if you can boot. See if you can mount sda1 and access any directories/files in Ubuntu.

# mount /dev/sda1 /mnt

mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

# dmesg | tail

[   31.754555] device-mapper: ioctl: error adding target to table
[   32.344504] fuse init (API version 7.19)
[   32.348459] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[   32.359735] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts
[ 1013.757557] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[ 1013.777232] JFS: nTxBlock = 8192, nTxLock = 65536
[ 1013.855761] Btrfs loaded
[ 1014.283746] EXT4-fs (sda1): bad geometry: block count 186880000 exceeds size of device (186879992 blocks)
[ 1142.301148] EXT4-fs (sda1): bad geometry: block count 186880000 exceeds size of device (186879992 blocks)
[ 1190.433776] EXT4-fs (sda1): bad geometry: block count 186880000 exceeds size of device (186879992 blocks)

Thanks

B.R.
satimis

[yancek]

It looks like sda1 does have problems as the grub2-mkdconfig script doesn not detect Ubuntu. In your initial post you indicated that Ubuntu took up about 100GB of a 1TB drive but the info on your partitions from the bootinfoscript indicates that it (sda1) takes up about three fourths of the drive (sector 63 thru 1,495,039,999) and there seems to be a big gap before the next partition?? Have you looked at partitions in GParted or Parted Magic? Does it show similar output?

[satimis]

It looks like sda1 does have problems as the grub2-mkdconfig script doesn not detect Ubuntu. In your initial post you indicated that Ubuntu took up about 100GB of a 1TB drive but the info on your partitions from the bootinfoscript indicates that it (sda1) takes up about three fourths of the drive (sector 63 thru 1,495,039,999) and there seems to be a big gap before the next partition??

It was only from my recollection. The HD was on the shelves and has NOT been used for long time.

Have you looked at partitions in GParted or Parted Magic? Does it show similar output?

$ which gparted

/usr/bin/which: no gparted in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/satimis/.local/bin:/home/satimis/bin)

$ which parted

/usr/sbin/parted

How to run "parted" to check /dev/sda1
?

Thanks

Edit:

IIRC during installation I made about 200G for Fedora 17 leaving the rest for Ubuntu 9.04


B.R.
satimis