You don't need to fsck - mount/unmount will do.
Unfortunately there's no simple solution to this. The prior situation
caused filesystem corruption in the context of hibernation.
** Changed in: os-prober (Ubuntu)
Status: Won't Fix => Triaged
** Summary changed:
- Natty os-prober fails to
It's to the point that I actually created a launcher script on Natty:
$ sudo fsck /dev/sda5 && sudo update-grub
And when I get my Maverick partion back I have one on there as well:
$ sudo grub-install && sudo update-grub
Please chance the status from 'Won't Fix' as this is a critical issue
tha
As did I. My grub is installed from Maverick & slightly customised, so
after I am able to get back into Maverick I need to reinstall from
Maverick as Natty has overtaken grub during the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
With todays upgrade I had to fsck my Maverick-Installation again:
sudo fsck /dev/sdaX
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
/dev/sdaX: stelle das Journal wieder her
Bereinige verwaist Inode 27918417 (uid=0, gid=0, mode=0100644, size=2719432)
Afterwards I was able to recover Ma
Still occuring. I've been following 672177 and applied all the 'fixes'
there. However the most recent update to 2.6.38.5-generic on natty
reinstalls grub2 and again finds no maverick partition. fsck of the
maverick partition (from natty) is still necessary & have to reinstall
grub2 from the maveric
On 01/25/2011 03:13 AM, Colin Watson wrote:
> ext3 or ext4 - they have the same relevant property.
>
> requires recovery - this doesn't necessarily mean requires *manual*
> recovery; the kernel can often do automatic recovery without you knowing
> it. It just means that it wasn't unmounted cleanl
ext3 or ext4 - they have the same relevant property.
requires recovery - this doesn't necessarily mean requires *manual*
recovery; the kernel can often do automatic recovery without you knowing
it. It just means that it wasn't unmounted cleanly.
This may well be happening as a consequence of bug
Same issue, same relevant error messages, same solution (fsck) on my
system today that was updated to 2.6.37-12-generic #26 (I only boot into
Natty ever occasionally).
Re: comment #3 (Colin): I'm confused by "Unfortunately, there is no way
to mount an ext3 filesystem that requires recovery"; my Ma
Yes that worked. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683355
Title:
Natty os-prober fails to detect Maverick installation
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Renate, here is what you need to do to work around the problem. You will
need to know wher hardware device Maverick is installed on, e.g.,
/dev/sda2 - yours may be the same, or it may be different.
Then, when booted into Natty, run command "sudo fsck /dev/sda2" <== Maks
sure to use the correct dev
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
error: line no: 285
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.n
These are the relevant errors:
EXT4-fs (sda2): INFO: recovery required on readonly filesystem
EXT4-fs (sda2): write access unavailable, cannot proceed
Unfortunately, there is no way to mount an ext3 filesystem that requires
recovery without replaying the journal and thus causing writes to tha
I am starting to make some headway on my os-prober / grub2 issue.
Today, there was a new kernel for Natty. When it installed, it gave a
grub2 syntax error. I got around the error by running install-grub,
which ran without error, but again failed to detect Maverick on the
other partition. When I re
--
Natty os-prober fails to detect Maverick installation
https://bugs.launchpad.net/bugs/683355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
14 matches
Mail list logo
