I used initctl to see services running.
Stopped them using stop.
Then mount -o remount,ro /
On karmic
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
I agree a backport is needed here.
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
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.ubu
+1 for backport to karmic.
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
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/
Lucid has re-added fsck now in the recovery menu we should consider
backporting it.
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Two points:
1 - The bug in jaunty IS specific to ext4, and has existed since jaunty betas.
Looks like in the end this bug has been "hijacked" by a related but more
critical bug, so I'm not complaining just want to make sure we don't overlook
that forever.
2 - I'd like to echo what others have s
After update, in recovery mode selecting "dpkg" appears this message, in
red:
mountall: Cancelled. General error mounting filesystem. A maintenance
shell will be now started. CONTROL-D will terminate this shell and re-try.
Press enter for maintenance (or type Control-D to continue):
but neither E
This bug was fixed in the package friendly-recovery - 0.2.8.2
---
friendly-recovery (0.2.8.2) karmic; urgency=low
* usr/share/recovery-mode/options/fsck:
- Drop fsck option because we can not reliable remount the
filesystem readonly for a fsck (LP: #363271). In karmic
** Summary changed:
- can't fsck / if ext4 from friendly-recovery
+ can't fsck / from friendly-recovery
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
#19: Actually it was working in early betas of Karmic, and I had my
Jaunty systmes converted to ext4 and they all worked; or at least
"appeared" to work.
This is insane, IMHO; that something fundamental, a GRUB2 entry
selection has a feature that is BROKEN, and is not being addressed
BEFORE relea
emarkay, true. But bear in mind, it's been broken with ext4 since
jaunty. I'd love to see one sooner, but I'm guessing we won't see a fix
until after karmic's release.
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are
I think we all missed the point. The point is - it DOES NOT WORK AT ALL.
All I see is a flash of "Mount is busy" and nothing more.
This is on 2 PC's here; it's RC time, now!
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because
On Tue, 2009-10-20 at 10:50 +, ski wrote:
> But your point about having daemons running does have some truth to it,
> and to answer that, I don't see why the functionality of friendly
> recovery couldn't be whittled down to things that can be put in a single
> binary located on /, statically l
> In System V, the only services missing in single user mode compared to
> multi-user mode are login services, such as getty, gdm, sshd, etc. It's
> not intended as a "recovery" mode.
Well, I'll admit that I come from a mostly BSD background. I had no idea
that sysV used runlevel 1 like that, or t
On Tue, 2009-10-20 at 08:40 +, ski wrote:
> I just want to make sure we aren't considering losing the option of
> booting to single user mode.
>
You seem to not understand what single user mode is.
In System V, the only services missing in single user mode compared to
multi-user mode are log
Scott - I disagree strongly that the root filesystem is usually already
read-only when friendly-recovery is invoked. I don't just go to friendly
recovery only when there is a problem (in fact I'm not sure I ever have
in reaction to a problem). I admit I'm not a usual user, but there are
plenty of c
James: only luck makes it work on Jaunty, usually you only tend to go to
"friendly recovery" when you have a problem - and that problem usually
means the root filesystem is already read-only.
This needs to be reimplemented so that when any fsck fails, or any
critical boot component, you get a frie
James & emarkay - it does NOT work in jaunty, at least with ext4 and
amd64 architecture, as in the initial bug report (which i reconfirmed
yesterday).
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubunt
James (#10) - It does work in Jaunty, but NOTHING happens in Karmic,
aside from the aforementioned short message.
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
On Thu Oct 15 18:02:09 UTC 2009 Scott James Remnant wrote:
> At a guess, init, udev, dbus, etc. All the usual system services.
So what changed that this no longer works? Brian confirmed that it
worked on Jaunty on IRC.
Thanks,
James
--
can't fsck / from friendly-recovery
https://bugs.launchpa
#6 - James, that message only appears for about 1/4 second!
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
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.ubun
On Thu, 2009-10-15 at 11:26 +, James Westby wrote:
> Could you please also provide the output of
>
> sudo fuser -v -m /
>
> when you get the "busy" message?
>
At a guess, init, udev, dbus, etc. All the usual system services.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
can't fsck /
screenshot of fuser output
** Attachment added: "9.10-friendly-recovery-fsck.png"
http://launchpadlibrarian.net/33739303/9.10-friendly-recovery-fsck.png
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of
Hi,
Could you please also provide the output of
sudo fuser -v -m /
when you get the "busy" message?
Thanks,
James
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
As a sanity check, I've reconfirmed the problem on a jaunty/ext4/amd64
system. When I select 'fsck' from the recovery menu, I am told: "mount:
/ is busy" (at the bottom of the screen, it goes away very quickly as
the menu seems to refresh immediately after fsck errors out. When I
select a root shel
When recovering from a lockup or when system crashes, if you select the
recovery option and then select fsck the screen blanks for a second and
then returns to the original recovery screen. This also happens any
time you select the this combination. Thus, there is no current way
other than the l
This worked fine for me on a Jaunty system with the same version of
friendly-recover however the filesystem was ext3. I wonder if that has
something to do with it.
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a m
** Also affects: friendly-recovery (Ubuntu Karmic)
Importance: High
Status: Triaged
** Changed in: friendly-recovery (Ubuntu Karmic)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs
Confirmed using friendly-recovery version 0.2.8.1 on Karmic.
** Changed in: friendly-recovery (Ubuntu)
Importance: Undecided => High
** Changed in: friendly-recovery (Ubuntu)
Status: New => Triaged
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You recei
PS - by jaunty, i mean jaunty RC1 with all updates from the net applied
as of Sat Apr 18 08:16:32 GMT 2009
--
can't fsck / from friendly-recovery
https://bugs.launchpad.net/bugs/363271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
29 matches
Mail list logo
