I've just filed bug 0004634. Grub won't install onto my pata drive now that I have a sata drive installed. This is grub 0.97 on CentOS5.5. Has anyone else encountered this? I'm guessing that I can always install Fedora on hda, which should give me a working grub, but I was hoping for something a little less involved.
Thanks, Dave Mackay
On Mon, 22 Nov 2010, David G. Mackay wrote:
To: centos@centos.org From: David G. Mackay mackay_d@bellsouth.net Subject: [CentOS] Grub, pata, and sata
I've just filed bug 0004634. Grub won't install onto my pata drive now that I have a sata drive installed. This is grub 0.97 on CentOS5.5. Has anyone else encountered this? I'm guessing that I can always install Fedora on hda, which should give me a working grub, but I was hoping for something a little less involved.
Thanks, Dave Mackay
Is the PATA drive on your Primary Master connection?
If you use Gparted live CD or Parted Magic, how do those drives show up?
Regards,
Keith
On Tue, 2010-11-23 at 18:12 +0000, Keith Roberts wrote:
On Mon, 22 Nov 2010, David G. Mackay wrote:
To: centos@centos.org From: David G. Mackay mackay_d@bellsouth.net Subject: [CentOS] Grub, pata, and sata
I've just filed bug 0004634. Grub won't install onto my pata drive now that I have a sata drive installed. This is grub 0.97 on CentOS5.5. Has anyone else encountered this? I'm guessing that I can always install Fedora on hda, which should give me a working grub, but I was hoping for something a little less involved.
Thanks, Dave Mackay
Is the PATA drive on your Primary Master connection?
If you use Gparted live CD or Parted Magic, how do those drives show up?
Regards,
Keith
(parted) print all
Model: Hitachi HDT725032VLAT80 (ide) Disk /dev/hda: 320GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 107MB 107MB primary ext3 boot 2 107MB 320GB 320GB primary lvm
Model: WDC WD450AA-00BAA0 (ide) Disk /dev/hdb: 45.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 107MB 107MB primary ext3 boot 2 107MB 45.0GB 44.9GB primary lvm
Model: ATA SAMSUNG HD502HI (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 105GB 105GB primary ext3 boot 2 105GB 500GB 395GB primary ext3 3 500GB 500GB 107MB primary ext3
Error: Unable to open /dev/md0 - unrecognised disk label.
Thanks, Dave
On Tue, Nov 23, 2010 at 01:04:03PM -0600, David G. Mackay wrote:
(parted) print all
Model: Hitachi HDT725032VLAT80 (ide) Disk /dev/hda: 320GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 107MB 107MB primary ext3 boot 2 107MB 320GB 320GB primary lvm
Model: WDC WD450AA-00BAA0 (ide) Disk /dev/hdb: 45.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 107MB 107MB primary ext3 boot 2 107MB 45.0GB 44.9GB primary lvm
Model: ATA SAMSUNG HD502HI (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 105GB 105GB primary ext3 boot 2 105GB 500GB 395GB primary ext3 3 500GB 500GB 107MB primary ext3
Error: Unable to open /dev/md0 - unrecognised disk label.
shouldn't have boot,raid flags on the members of tour /dev/md0 array?
cat /proc/mdstat df -P cat /grub/grub.conf (from hda1) and from hdb1
Tru
On Tue, 2010-11-23 at 22:17 +0100, Tru Huynh wrote:
On Tue, Nov 23, 2010 at 01:04:03PM -0600, David G. Mackay wrote:
(parted) print all
Model: Hitachi HDT725032VLAT80 (ide) Disk /dev/hda: 320GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 107MB 107MB primary ext3 boot 2 107MB 320GB 320GB primary lvm
Model: WDC WD450AA-00BAA0 (ide) Disk /dev/hdb: 45.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 107MB 107MB primary ext3 boot 2 107MB 45.0GB 44.9GB primary lvm
Model: ATA SAMSUNG HD502HI (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 32.3kB 105GB 105GB primary ext3 boot 2 105GB 500GB 395GB primary ext3 3 500GB 500GB 107MB primary ext3
Error: Unable to open /dev/md0 - unrecognised disk label.
shouldn't have boot,raid flags on the members of tour /dev/md0 array?
cat /proc/mdstat df -P cat /grub/grub.conf (from hda1) and from hdb1
[root@vorpal ~]# cat /proc/mdstat Personalities : unused devices: <none> [root@vorpal ~]# df -P Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sda1 99188468 4853368 89215188 6% / /dev/sda2 373793320 235981428 118517828 67% /home/dave /dev/hda1 101086 25176 70691 27% /boot /dev/sda3 101105 5665 90219 6% /boot2 tmpfs 647588 0 647588 0% /dev/shm /dev/hdc 4087030 4087030 0 100% /media/CentOS_5.5_Final
[root@vorpal ~]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda1 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-194.26.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.26.1.el5 ro root=LABEL=/ rhgb quiet psmouse.proto=bare initrd /initrd-2.6.18-194.26.1.el5.img
Following is boot from hdb [root@vorpal ~]# cat /mnt/util/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd1,0) # kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd1,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-194.26.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.26.1.el5 ro root=LABEL=/ rhgb quiet psmouse.proto=bare initrd /initrd-2.6.18-194.26.1.el5.img title CentOS (2.6.18-194.17.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.17.1.el5 ro root=LABEL=/ rhgb quiet psmouse.proto=bare initrd /initrd-2.6.18-194.17.1.el5.img title CentOS (2.6.18-194.11.3.el5) root (hd1,0) kernel /vmlinuz-2.6.18-194.11.3.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet psmouse.proto=bare initrd /initrd-2.6.18-194.11.3.el5.img title CentOS5.5 (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5 ro root=LABEL=/ rhgb quiet psmouse.proto=bare initrd /initrd-2.6.18-194.el5.img
Thanks, Dave
On Tue, Nov 23, 2010 at 06:17:17PM -0600, David G. Mackay wrote:
On Tue, 2010-11-23 at 22:17 +0100, Tru Huynh wrote:
On Tue, Nov 23, 2010 at 01:04:03PM -0600, David G. Mackay wrote:
(parted) print
...
Error: Unable to open /dev/md0 - unrecognised disk label.
shouldn't have boot,raid flags on the members of tour /dev/md0 array?
so where is the /dev/md0 from?
cat /proc/mdstat df -P cat /grub/grub.conf (from hda1) and from hdb1
[root@vorpal ~]# df -P Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sda1 99188468 4853368 89215188 6% / /dev/sda2 373793320 235981428 118517828 67% /home/dave /dev/hda1 101086 25176 70691 27% /boot /dev/sda3 101105 5665 90219 6% /boot2 tmpfs 647588 0 647588 0% /dev/shm
maybe something like this?
cat <<EOF| grub --batch --no-floppy device (hd0) /dev/hda # setup hda for 1st disk root (hd0,0) # /dev/hda1 for /boot setup (hd0) # install on MBR of /dev/hda EOF
Tru
2010/11/23 David G. Mackay mackay_d@bellsouth.net
I've just filed bug 0004634. Grub won't install onto my pata drive now that I have a sata drive installed. This is grub 0.97 on CentOS5.5. Has anyone else encountered this? I'm guessing that I can always install Fedora on hda, which should give me a working grub, but I was hoping for something a little less involved.
Thanks, Dave Mackay
every time i reported this bug on some previous fedora versions, it was closed with notabug: "As mentioned in other bug reports, this isn't really a bug. There's no way for the drive order to be consistently detected."
https://bugzilla.redhat.com/show_bug.cgi?id=458138
On Wed, 2010-11-24 at 08:05 +0200, cornel panceac wrote:
every time i reported this bug on some previous fedora versions, it was closed with notabug: "As mentioned in other bug reports, this isn't really a bug. There's no way for the drive order to be consistently detected."
It's not a matter of drive order. Grub simply will not install on hda.
Even if the order were wrong it should still let me install. If it was installing on the wrong drive, that would be a separate issue.
Dave