reboot -f is the same as those other two commands, and insulting people
is not helpful. If you can't abide by the Ubuntu code of conduct and be
respectful of others, you are welcome to look elsewhere for people who
support a free OS and enjoy being insulted.
If you feel the man page for reboot is
The following is equivalent to "yanking out the power cord":
echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger
AFAIK not reboot -f.
Now, it's not like reboot -f had been triggerred at the millisecond
where th update-grub or kernel upgrade process has been completed... or
used in conju
Philip: I certainly hope you don't do IT support for a living or I would
seriously consider changing careers.
Let's see the manpage for: reboot "-f" option .
-f Force halt or reboot, don?t call shutdown(8).
Oh, yes, I can clearly see where we clearly shouldn't be using the "-f" s
reboot -f does *not* flush the disk caches, thus what you just wrote (
grub ) is lost. This is like complaining there is a bug because you ran
rm -rf / and successfully deleted all of your files. There are many
things you shouldn't do including yanking out the drive while it is in
use and droppin
I found the same thing. I was required to use "reboot -f" during the
rescue CD, otherwise it complained that it wouldn't let me reboot simply
using "reboot". But that "reboot -f" did NOT cause any side effects.
Only the one issued from the running OS. AND, I didn't even have to do
the "grub-inst
+1 ;)
Seriously, there is no reason why, when flushing disk cache through
reboot -f, makes grub being corrupted afterwards.
BTW, using the install CD when I do the recovery procedure i'm still
using reboot -f. Mount options perhaps?
Although, nothing special in here...
#
proc
Seriously ?
First you blew off Vincent by saying "you probably just should have run
dpkg-reconfigure".
Now you're blowing me off by saying "Don't do that".
By this measure, nothing is a bug because once you know how to avoid anything,
that
would be the simple answer: Don't do that.
At a minim
reboot -f means to reboot without doing a proper shutdown and flushing
disk caches and the like, and so will result in data loss. Don't do
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051280
ahah! ... I'm pretty sure every time it did happend to me I was indeed
using reboot -f right after... good catch!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051280
Title:
reboot into grub prompt
Vincent: you are NOT out of your mind :-)
Philip: this is real
I have had the exact same problem/symptoms for the last 3 days. It's
been killing me. This morning I finally discovered what was causing the
issue, although not the underlying problem.
I have been attempting to bring up two brand new
Most likely the problem was simply that grub was not installed to the
MBR and you just needed to run a dpkg-reconfigure grub-pc to make sure
sda was selected. Since you have resolved the problem, I'm closing the
bug.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received t
Today I updated the kernel to 3.5.0-18-generic and resulted into a grub
rescue again with a message "ELF smaller than expected".
Again, booted using the live-cd (old 11.10 version), ensure to have
network access through the GUI then hit CTRL-ALT-F1 to get to a shell
then did the following (with /d
I now presume there are two bugs, most probably related...
1- Failure to reconfigure grub properly OR update the init image when invoked
through regular apt process. I cannot tell for sure but, if I only apply a
kernel update using dist-upgrade it seems to work ok but when there are a lot
of
What I get after about any action related to grub.
Lastly, this is hapening on my HP laptop ProBook 6460b with an SSD
drive.
** Attachment added: "error: ELF header smaller than expected. (grub rescue)"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1051280/+attachment/3395985/+files/g
More infos on this:
- it seems to happend about each time either grub package gets upgrade OR when
there is an update to grub configurations
- seems to be totally unrelated to kernel updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
15 matches
Mail list logo
