You are not logged in.
I'm not sure if it was my fault, but the last upgrade of grub make my system unbootable, because moved /boot/grub.cfg to /boot/grub.cfg.pacsave and there was no /boot/grub.cfg anymore. When I rebooted the system showed the grub mini-shell.
I had to restore using an usb-arch-install
Offline
yes sorry about that....
it's already fixed in -3...failed to notice that grub.cfg would be removed when removing it from the backup array --> moved it back.
also the example file is now installed as grub.cfg.example.
Offline
aha thanx. How to get back to arch with sh:grub shell?
Last edited by matsche (2010-03-16 19:55:06)
THX!!
cu matsche
Offline
if I'm not mistaken you should be able to enter the commands you normally have in your grub.cfg file. First define kernel/initrd/root device and such, in the end I believe you should enter 'boot'. Never tried it though.
Offline
yes sorry about that....
it's already fixed in -3...failed to notice that grub.cfg would be removed when removing it from the backup array --> moved it back.
also the example file is now installed as grub.cfg.example.
You can be lucky about the fact, that I am not in the same room as you ![]()
Here it is 24:00 CET and I just wanted to reboot my macbook, to test "all the new updates" and got the shock of my life!
But in fact I thank you for your work, now I can boot manually with Grub2 ![]()
Everyone who is in panic and need help, read this:
http://grub.enbug.org/Manual#head-4ec5b … a094d943bb
*Read with cat /boot/grub/grub.conf.pacsave
*load kernel configuration with linux /boot/kernelname root=/dev/... initrd ...
*boot
As Picard would say "Engage!".
Goodnight from europe/germany.
Offline
yes sorry about that....
it's already fixed in -3...failed to notice that grub.cfg would be removed when removing it from the backup array --> moved it back.
also the example file is now installed as grub.cfg.example.
I upgraded grub2 to 1.98-3 this morning and my grub.cfg was renamed to grub.cfg.pacnew, so grub remained stuck in command line. I fixed it, but I don't understand when pressh says that it has been fixed in -3, since I still got the error. Maybe I misunderstand or maybe the error is still there?
Offline
I upgraded grub2 to 1.98-3 this morning and my grub.cfg was renamed to grub.cfg.pacnew, so grub remained stuck in command line. I fixed it, but I don't understand when pressh says that it has been fixed in -3, since I still got the error. Maybe I misunderstand or maybe the error is still there?
I can confirm this. Upgraded grub2 from 1.97.2-1 to 1.98-3. Luckily I noticed this thread and found /boot/grub/grub.cfg was missing prior to attempting to boot. ![]()
Offline
I, too, was lucky enough to see the bug before restarting. Instead of not upgrading, I simply went back to GRUB. After all, GRUB2 is still in development. ![]()
Offline
I, too, was lucky enough to see the bug before restarting. Instead of not upgrading, I simply went back to GRUB. After all, GRUB2 is still in development.
It's simply a matter of renaming grub.cfg.pacnew to grub.cfg. I think teher's no drawback in using grub2 instead of grub (at least, I haven't noticed yet).
I wasn't so lucky to notice this thread before upgrading, so I found myself stuck in grub command line without remembering the syntax to load the kernel manually. Luckily I had a PartedMagic LiveCD so I could connect to the web and found this thread.
Offline
In addition to 98-3 not creating grub.cfg, I also have no grub.cfg.example, though pacman.log said it made both
I booted my arch install flash drive, mounted my /boot and copied the .pacsave.
Last edited by vacant (2010-03-17 09:44:30)
Offline
Mmm, the grub.cfg file is still removed when upgrading from 1.97... this pacman is weird. It should keep the file when it is in the backup array but it apperently does not if the file is not in the package anymore... let me see how I can fix this
[edit]
well not so weird maybe as it backs it up to .pacsave like it says it does, but not really what we would want here of course
Last edited by pressh (2010-03-17 10:56:02)
Offline
changes in -4:
- fix the removal of the grub.cfg file with an ugly workaround (this time really I hope)
- remove .install file -> just run grub-mkconfig -o /boot/grub/grub.cfg yourself. Modify /etc/default/grub and /etc/grub.d/40* if you need some changes (graphics and such)
- add the three files mentioned above to backup array
- add the patches previously posted in the forums a few days ago by darkcoder
Offline
This can be a serious issue. Don't you think it deserves a post in the site main page?
Offline
Totally deserves a post on the main page. I don't understand how this kind of things can happen in the stable repository ...
Offline
lol... rule #1 when installing or upgrading GRUB/GRUB2 is to always make sure you have a menu.lst or grub.cfg (whichever is needed) file in place before rebooting. Glad I remembered that because low and behold, I didn't have one after the upgrade. Otherwise, GRUB2 has been working pretty well for me the last 18 months.
Last edited by ozar (2010-03-17 16:09:53)
oz
Offline
lol... rule #1 when installing or upgrading GRUB/GRUB2 is to always make sure you have a menu.lst or grub.cfg (whichever is needed) file in place before rebooting. Glad I remembered that because low and behold, I didn't have one after the upgrade. Otherwise, GRUB2 has been working pretty well for me the last 18 months.
Better someone write this rule #1 on a place where it can be easily found and read...
Offline
When upgrading to grub2-1.98-4:
error: failed to commit transaction (conflicting files)
grub2: /boot/grub/grub.cfg exists in filesystem
Errors occurred, no packages were upgraded.Offline
just force it and move your config file back in place after that. I'll post a news item shortly.
Offline
When upgrading to grub2-1.98-4:
error: failed to commit transaction (conflicting files) grub2: /boot/grub/grub.cfg exists in filesystem Errors occurred, no packages were upgraded.
I got that problem, so I just renamed the conflicting file until the upgrade was completed.
Offline
changes in -4:
- fix the removal of the grub.cfg file with an ugly workaround (this time really I hope)
- remove .install file -> just run grub-mkconfig -o /boot/grub/grub.cfg yourself. Modify /etc/default/grub and /etc/grub.d/40* if you need some changes (graphics and such)
- add the three files mentioned above to backup array
- add the patches previously posted in the forums a few days ago by darkcoder
So are we not going to need to put everything we have in /etc/default/grub ? The one thing I really liked about grub2 in Arch was not having to mess with that.
Offline