Your message dated Sun, 16 Sep 2007 19:18:59 -0400
with message-id <[EMAIL PROTECTED]>
and subject line close #247416
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: installation-reports
Debian-installer-version: 2004-05-04:
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-i386-businesscard.iso
uname -a: <The result of running uname -a on a shell prompt>
Date: 2004-05-04 16:00 EDT (or so)
Method: Boot and install from CD only
Machine: Dell precision 330
Processor: PIII 1.5GHz
Memory: 1GB
Root Device: IDE /dev/hda1
Root Size/partition table:
/dev/hda1 / ext3 248 GB
/dev/hda2 swap 2 GB
Output of lspci: <sorry, didn't grab this>
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [ ]
Config network: [ ]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
After completing the installation process and rebooting, I was left with
a system that failed to boot, giving me little more information than:
Grub
Error 18
I did some digging around and found that this might be a BIOS limitation
in concert with the 250GB hard drive. I was able to get the machine
booting by upgrading the BIOS.
But, I was really caught off guard by this as I had booted Debian
previously in the same machine with the same hard drive, (but using lilo
instead of grub).
I don't know what the right fix is here, but I know that the end result
of an unbootable system is not acceptable. Some options might be:
1) Fix grub?
2) Allow the installer to use lilo rather than grub?
3) Detect the problem? Use lilo if necessary?
4) Detect the possibility of the problem and warn the user?
Keep up the great work with debian-installer. It is certainly many times
better than the last time I ran the installer on this machine, (which
was several years ago, many thanks to apt).
-Carl
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
It seems that it is now time to close that bug since there are many
disks larger than 250GB nowadays. Moreover, this seemed to be a BIOS
problem since there was a fix that consisted in upgrading it.
Three years later, one can hope that any user of that motherboard
would upgrade the BIOS in such a case.
Cédric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG7bnjh8mVmA5jLbkRAp8JAKDYYV4OcdlEtat8i5J8Lp6oE4U37wCgxB17
09InltBx6/MI/gN9NQs0fWc=
=zgZW
-----END PGP SIGNATURE-----
--- End Message ---
