Activity log for bug #32357

Date Who What changed Old value New value Message
2006-02-21 19:10:22 IbeeX bug added bug
2006-05-03 12:09:46 Simon Law description I have nforce4 motherboard, sata and pata HD primary HD is sata and it is configured via bios as boot disk, but installer writed GRUB to MBR off PATA disk so I needed to change in bios primary disk in order to boot ubuntu. The user has an nForce4 motherboard with both SATA and ATA drives attached. He set the SATA drive to be the first boot disk, but the installer installed GRUB on to the ATA drive instead.
2006-05-03 12:09:46 Simon Law title Installer fials to recognize primry HD Installer doesn't recognise SATA disks as primary.
2006-05-11 16:53:15 Simon Law description The user has an nForce4 motherboard with both SATA and ATA drives attached. He set the SATA drive to be the first boot disk, but the installer installed GRUB on to the ATA drive instead. The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive.
2006-05-11 16:55:43 Simon Law grub-installer: status Unconfirmed Confirmed
2006-05-11 16:55:43 Simon Law grub-installer: severity Normal Wishlist
2006-05-11 16:55:43 Simon Law grub-installer: statusexplanation I don't think this is a bug, but rather a consequence of hardware detection order in Linux.
2006-10-19 20:43:26 D.E.R.Daniel description The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive. The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB to MBR on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive.
2007-01-02 14:12:32 Matthew East grub-installer: importance Wishlist High
2007-01-02 14:12:32 Matthew East grub-installer: statusexplanation I don't think this is a bug, but rather a consequence of hardware detection order in Linux. You are correct that bugs involving dataloss should be of high importance. I'm adjusting the importance accordingly.
2007-08-22 12:29:47 Duncan Lithgow description The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB to MBR on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive. The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB to MBR on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive. ---------------- Added by Duncan-Lithgow so it can be edited: These bugs all have probelms installing GRUB on a SATA disc. Some with PATA present, some without. I do not have enough technical understanding to find exact duplicates. Bug #8497 #75676 #32357 #110292
2007-08-22 12:30:08 Duncan Lithgow description The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB to MBR on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive. ---------------- Added by Duncan-Lithgow so it can be edited: These bugs all have probelms installing GRUB on a SATA disc. Some with PATA present, some without. I do not have enough technical understanding to find exact duplicates. Bug #8497 #75676 #32357 #110292 The user has an nForce4 motherboard with both SATA and PATA drives attached. He set the SATA drive to be the first boot disk in the BIOS, but the installer installed GRUB to MBR on to the PATA drive instead. Linux recognizes the PATA as /dev/sda and the SATA as /dev/sdb. To work around the problem, he has set the first boot disk to the PATA drive. ---------------- Added by Duncan-Lithgow so it can be edited: These bugs all have probelms installing GRUB on a SATA disc. Some with PATA present, some without. I do not have enough technical understanding to find exact duplicates. Bug #8497 bug #75676 bug #32357 bug #110292
2008-06-16 20:45:52 Will Nowak bug assigned to grub-installer (Debian)
2008-06-16 21:00:26 Bug Watch Updater grub-installer: status Unknown Incomplete
2010-01-08 08:08:18 lynxie removed subscriber lynxie
2010-08-20 15:52:50 Dimitrios Symeonidis removed subscriber Dimitrios Symeonidis
2010-11-01 14:33:47 Phillip Susi grub-installer (Ubuntu): status Confirmed Invalid
2011-01-12 16:15:40 Bug Watch Updater grub-installer (Debian): status Incomplete Fix Released