After a clean install of Lucid AMD64 server, grub has no knowledge of root or boot
Bug #523543 reported by
Patrick Goetz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Distro: Lucid AMD64 Server Daily Build 2010-02-15
Package: grub-common 1.98~20100128-
After a clean install of this OS from CD, the machine reboots to a grub> prompt with no knowledge of root or boot information (i.e. the ls command produces nothing). The only added functionality selected were (openssh+samba).
I recently installed Karmic 9.10 AMD64 Server on the same machine using basically exactly the same steps and didn't run into any problems.
The one change: The root partition increased in size from 2TB to 3TB.
Could the size of the / partition be a problem?
affects: | ubuntu → grub (Ubuntu) |
affects: | grub (Ubuntu) → grub2 (Ubuntu) |
To post a comment you must log in.
OK, I've determined that the problem was indeed the partition size. I did another clean install, but this time set the size of the root partition to a more manageable 50GB, and -- although the system insisted on leaving the booted system at a non-existent vt7 prompt (server install generally means no gdm/X), the machine booted fine, and I was able to login in and do stuff after using <Ctrl>-<Alt>-<F1> to get to console running getty. Note that the second installation was step-by-step identical to the first on exactly the same hardware with exactly the same number of partitions. The only difference was / = 3TB (grub-install appears to fail) vs. / = 50GB (grub2 just works).
Not sure if anyone cares about this, but there likely will be other Ubuntu server users trying to use large root partitions who will be stymied by this.