** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577331
Title:
fsck cannot be ignored with plymouth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
** Changed in: mountall (Ubuntu Lucid)
Assignee: trustroy (trustroy) => (unassigned)
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Cannot mount usb drives or cd drives
** Changed in: mountall (Ubuntu Lucid)
Assignee: (unassigned) => trustroy (trustroy)
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Reported Bug #582035 against e2fsprogs.
The bug here should be considered fixed then I take it.
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
On Sun, May 16, 2010 at 02:47:18PM -, arand wrote:
> If running fsck from a liveCD, cancelling it will produce the same error:
> "
> ^C/dev/sda1: e2fsck canceled
> fsck.ext4: Inode bitmap not loaded while setting block group checksum info
> ~$ echo $?
> 8
> "
> Is this error from fsck correct?
On Mon, May 17, 2010 at 08:25:25PM -, yeti wrote:
> I think this bug may be a byproduct of the bug described in 540801.
It is not.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu D
I think this bug may be a byproduct of the bug described in 540801.
A work-around for 540801 confirmed by many is proposed there.
I'd be interested to know if anyone else sees the (or a) connection.
I haven't tried that fix myself, because I don't understand it well enough.
--
fsck cannot be igno
Also running on Maverick with the same issue, another virtualbox.
This is what is printed to the plymouth VT (similar to above screenshot):
"
fsck from util-linux-ng 2.17.2
User cancelled filesystem checks
/dev/sda1: e2fsck canceled
fsck.ext4: Inode bitmap not loaded while setting block group chec
Should this bug be reopened? Or should the fsck error/fail on user
cancellation be considered a separate issue, since it is in fact
possible to ignore the fsck with the current fix?
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received this bug notification b
This bug was fixed in the package mountall - 2.15
---
mountall (2.15) lucid-proposed; urgency=low
[ Scott James Remnant ]
* Fix an obvious thinko error that meant that the "I"gnore fsck error key
for a "hard" failure was ignored.
* When cancelling filesystem checks, only can
Using mountall from lucid-proposed, I also still get the "Serious errors
were found..." message when I press c to cancel the fsck. I am not
testing on VirtualBox -- this is happening on my actual hardware. The
situation is somewhat improved, since pressing i to ignore the error
message now resumes
yes, and yes.
Also tested on a fresh lucid->maverick machine, and same issue is seen there.
It could be isolated to virtualbox, since that is the only thing I'm
using. Although I don't see why it would...
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received
Ok, so you seem to get the specific error "Inode bitmap not loaded while
setting block group checksum info". This is an error from fsck, and not
a bug in mountall - it sounds like you may genuinely have an error on
your root filesystem, because cancelling fsck should not result in this
error being
Side note.
Concerning the habit of plymouth to happily suggest skip mounting the root FS
I've put down separately Bug #578184
** Description changed:
Binary package hint: plymouth
PROBLEM
There seems to be no way to skip an fsck with plymouth.
TEST CASE
1. sudo touch /force
Yes, for me I still get the message "serious errors were found while checking
the disk drive for /" whenever I cancel the fsck.
The error messages on the screenshot in comment #10 are still the same and
present if I cancel and switch to the plymouth VT (arrowkey left).
I am using mountall 2.15 f
arand,
With the mountall in proposed, you should not be getting the 'serious
error was encountered' message after pressing 'c'. Are you saying that
you still get this message?
The mountall code is subtle and quick to anger, so other issues should
certainly be filed as separate bug reports and ta
copied from lucid-proposed to maverick.
** Changed in: mountall (Ubuntu Maverick)
Status: Fix Committed => Fix Released
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Released => Fix Committed
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You r
This bug was fixed in the package mountall - 2.15
---
mountall (2.15) lucid-proposed; urgency=low
[ Scott James Remnant ]
* Fix an obvious thinko error that meant that the "I"gnore fsck error key
for a "hard" failure was ignored.
* When cancelling filesystem checks, only can
Ignoring seems to work as it should with proposed update.
(I had one random occurance where plymouth hung after i was pressed and the
interactive section had been cleared, but I have been unable to reproduce this,
and otherwise it has worked exactly as expected)
"Skip mounting" issue is still u
Accepted mountall into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: mountall (Ubuntu Lucid)
comments, fwiw:
1.#577485 re showfsck is related.
2.my installation says it will fsck every 20 boots.
3.no fsck has ever shown any errors.
4.why are we doing so often an fsck on a journalled fs, anyway?
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received th
** Package changed: plymouth (Ubuntu) => mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Importance: Undecided => High
** Changed in: mountall (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: mountall (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also af
** Branch linked: lp:ubuntu/mountall
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
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.u
** Description changed:
Binary package hint: plymouth
PROBLEM
There seems to be no way to skip an fsck with plymouth.
-
+
TEST CASE
1. sudo touch /forcefsck && sudo reboot
2. While fsck is in progress, press c
3. press i for ignore
* Plymouth locks up and reboo
When running fsck manually (recovery mode -> service rsyslog stop;
screen; plymouthd; plymouth --show-splash; mount -o ro,remount /;
mountall --force-fsck --no-events -v) I get this output [screenshot]
when I switch over to plymouth and press c.
** Attachment added: "Screenshot-2dreamer (Snapshot
Confirming as per
https://bugs.edge.launchpad.net/ubuntu/+source/plymouth/+bug/571707/comments/83
--
fsck cannot be ignored with plymouth
https://bugs.launchpad.net/bugs/577331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
26 matches
Mail list logo
