** Changed in: grub-installer (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/32357
Title:
Installer doesn't recognise SATA disks as primary.
--
ubu
@ Dexus
+1
--
Installer doesn't recognise SATA disks as primary.
https://bugs.launchpad.net/bugs/32357
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
@Phillip Susi
I just swallow what i wanted to write and just quote you:
"I'd like to continue working to improve Ubuntu, so it can be the best
OS it can be, and encourage people to use it. "
--
Installer doesn't recognise SATA disks as primary.
https://bugs.launchpad.net/bugs/32357
You received
I'm going to go ahead and close this old bug out. The reason it is now
4 years old and has not been fixed is because this report does not
adequately describe an actual bug. There is simply no way for the
system to know which drive your bios is configured to boot from, so it
is up to you to instal
much of this silliness could probably be avoided by not pretending IDE
drives are SCSI drives.
This mess seems to affect most distros now.
The kernel PATA driver still exists and is maintained. The kernel team's
stated policy is that it will remain in existence and be fully
supported. It is not "
this bug will soon celebrate it's 3rd birthday. it's marked as
confirmed, high importance, and reported upstream (debian). are we going
to do something about it, or are we just waiting for debian to resolve
this?
--
Installer doesn't recognise SATA disks as primary.
https://bugs.launchpad.net/bug
yes, the problem seems to come from the order of the hard disks, something that
is decided by the bios.
unplugging disks, like X3 suggested, is a workaround, but it obviously cannot
be the solution. we need to find a better way to do this...
--
Installer doesn't recognise SATA disks as primary.
Right after I downloaded and started installing the Ubuntu 8.04.1 LTS on
a mixed sata/ide drive environment I experienced similar issues when
placing the MBR onto the IDE drive that I had partinoned and hadson
partition 1 XP Pro and on Partions 2 Ubuntu and on partition 3 linux
swap the other s
** Changed in: grub-installer (Debian)
Status: Unknown => Incomplete
--
Installer doesn't recognise SATA disks as primary.
https://bugs.launchpad.net/bugs/32357
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailin
Added a link to the Debian bug report #283312. It and it's relatives have been
open for ~4 years now.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283312
** Bug watch added: Debian Bug tracker #283312
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283312
** Also affects: grub-installer
I have the same problem on AMD64 box with a single IDE drive where the
installation completes and then won't boot, hanging at "waiting for root
fllesystem".
The installer sees my IDE drive as a SCSI but i suspect the boot process fails
to see a non existant SCSI drive and then hangs.
If I add a
I'm not sure is just for primary SATA since my SATA drive is the
secondary, the PATA drive is my primary. In fact I couldn't boot Hardy
AMD64 live CD 'till I used as boot option "all_generic_ide". I've got
the same problem with Gutsy AMD64. Installers for 32 bit versions have
no problems with my dr
I actually do find this as a bug.
I have a 20G ATA drive in my system for backup purposes (I haven't spent the
money, and don't really find it necessary to, on an external backup drive)...
My primary drive is an 80G SATA.
Anyhow, when installing the system the installer finds the 80G as the prima
sorry, installation was on a P4, intel D865PERL motherboard, 32 bit processor,
i686 install, Kubuntu 7.10...
I think this is a serious bug within the install routine for the GRUB
bootloader and should be taken QUITE SERIOUS... if I had an operating system
that required certain boot routines set
Yesterday I tried to install KUBUNTU 7.10 RC to an Intel 945G series M/B with a
SATA Seagate HDD (80 GB).
The installation crashed every time at the 15% "Detecting file systems."
and after that I found it had write 530 MB to the root partition ( 3
partitions, Windows, Linux Swap and roo
Maybe your /boot/grub/device.map is wrong? Perhaps try --recheck option
of grub-install?
--
Installer doesn't recognise SATA disks as primary.
https://bugs.launchpad.net/bugs/32357
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubunt
After kernel upgrade grub again rewrote grub menus with hd0 and hd1 wrong way
round.
Thanks be to goodness :) it left a /boot/grub/menu.lst~ (backup of old
menu.lst) so quick edit to
that and everything is happy again.
--
Installer doesn't recognise SATA disks as primary.
https://bugs.launchpad
Same problem for me feisty 7.04. Two SATA drives sda and sdb. Dell optiplex
desktop.
There seem to be a few problems for users coming up related to grub + sata
difficulties
and the issue seems to be ongoing so I'll just add my piece.
bios before was booting from hd0 (suse + grub)
kubuntu new in
I have had the same problem trying to install Ubuntu Fiesty Fawn onto a
mixed SATA/IDE system. The SATA is my new drive - the IDE is my old XP
one, which I am keeping just in case I need any of the old data on it.
I am very dissapointed that Ubuntu is not able to do what it says -
which is perform
I have a mixed SATA / ATA system and same thing happens.
During the installation, it seems that the ATA drive was detected as hd0
and grub installed itself there. SATA were hd1, hd2.
During the boot, grub detects SATA discs as hd0 and hd1, while ATA is
hd2.
I fixed it by re-doing the grub-instal
I just encountered this same bug (I think) installing the Gutsy Beta. I
have a SATA drive which I use for my main linux system and an old PATA
drive for backups. My motherboard is an MSI K9N (nForce 570) which by
default orders the PATA drive first, but I change the order in the BIOS
to boot from
Reporting same bug:
No problem to install kubuntu 7.04 on ATAPI disk
but got an error at grub installation on SATA2 disk on the same PC.
I tried to change BIOS settings on SATA2 from IDE to AHCI => same result.
Now i 'm trying to install grub on SATA2 disk at console command from Live CD...
--
In
** Description changed:
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
I've just been hit by the same bug. In my desktop comuter with nForce2
I've got two drives. One SATA and one PATA. During Ubuntu install (Edgy)
I choose to install system and all stuff on sda and use hda only as
media storage (music, movies, etc.). Yesterday to my PATA drive failed
and to my aston
I'm gonna bump this bug with pretty much the same problem.
I have a SATA and IDE drive. And although the SATA is defined as hd0
grub keeps reverting it back to hd1... I installed to hd0 though so it
should have recognized that.
I have a feeling this issue has to deal with converting the hda ->
I have a SATA disk and a ATA one.
I installed dapper to the SATA disk, but grub-install set linux to boot
from the ATA disk.
I noted also that every time a grub security upgrade is performed in
edgy, update-grub again invert the disks.
--
Installer doesn't recognise SATA disks as primary.
https
You are correct that bugs involving dataloss should be of high
importance. I'm adjusting the importance accordingly.
** Changed in: grub-installer (Ubuntu)
Importance: Wishlist => High
--
Installer doesn't recognise SATA disks as primary.
https://launchpad.net/bugs/32357
--
ubuntu-bugs mail
** Description changed:
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.
+ but the installer installed GRUB to MBR on to the PATA drive ins
I think it is not special to nforce4.
I had the same bug on an Intel P4 board.
For me the bug should be promoted to SEVERE because
additional SATA drives are getting more common.
Using the SATA drive for linux and leaving windows alone on the PATA drive has
alot of charme for "non-experts"
If an
This *definitely* is a bug and a quite serious! I had attached a PATA-
drive encrypted with TrueCrypt which stores its required information to
mount the drive in the first 512 bytes. You can already guess what
happened? GRUB was written there and all my data are gone!
--
Installer doesn't recogni
This *definitely* is a bug and a quite serious! I had attached a PATA-
drive encrypted with TrueCrypt which stores its required information to
mount the drive in the first 512 bytes. You can already guess what
happened? GRUB was written there and all my data are gone!
--
Installer doesn't recogni
31 matches
Mail list logo
