Marking this bug as Invalid because the original reporter (andy baxter)
is no longer able to reproduce, and there was a good hypothesis that it
was not the same filesystem that was bad but a different one.
Leaving this bug open has confused it with other people's problems, who
may be experiencing
Alright, Ted is not listening anymore, and he was not totally belligerent
this time, so I will bite my tongue with some of what I have to say to him.
What I will say is this. The error I experienced is not from multiple file
systems labeled /. And, deleting fsck is not that big of a deal! If you
PS
Please pardon my imperfect spelling...
On Sat, Jun 6, 2009 at 12:43 PM, hyperfitz hyperf...@gmail.com wrote:
Alright, Ted is not listening anymore, and he was not totally belligerent
this time, so I will bite my tongue with some of what I have to say to him.
What I will say is this. The
On Thu, Jun 04, 2009 at 04:26:20AM -, Hyperfitz wrote:
Wow, this is constructive. For the record, there is nothing wrong with my
file system. There is, however, something wrong with the check that happens
at boot. It is not user error, sorry if you think otherwise--doesn't change
the
Wow, this is constructive. For the record, there is nothing wrong with my
file system. There is, however, something wrong with the check that happens
at boot. It is not user error, sorry if you think otherwise--doesn't change
the facts. My suggestion is hardly (in the slightest) like telling
PS
Good idea Andy. That may really be better. Getting belligerently yelled at,
however, has not changed my opinion that this is, in fact, a bug. Like I
said, if it happens again then I will do a more thorough job of
investigating and reporting the problem; and, I will open an new bug report.
--
Theodore Ts'o wrote:
Hyperfitz,
Can you open a new bug report, please?*Please* don't assume that
just because you have the same symptoms as someone else, that it is the
same bug.
If two people went to the doctor, both complaining of a headache, one
might just have the flu, and another
Sure,
Sure, if I have this problem again I will do all of this stuff that you ask.
But the name of the thread is filesystem check fails on boot, but
filesystem isn't bad. This is a problem that it seems that not only I have
had. I think it is probably is helpful to tell people that they can
On Sat, May 30, 2009 at 04:28:53PM -, Hyperfitz wrote:
Sure, if I have this problem again I will do all of this stuff that you ask.
But the name of the thread is filesystem check fails on boot, but
filesystem isn't bad. This is a problem that it seems that not only I have
had. I think it
Hyperfitz,
Can you open a new bug report, please?*Please* don't assume that
just because you have the same symptoms as someone else, that it is the
same bug.
If two people went to the doctor, both complaining of a headache, one
might just have the flu, and another might have brain cancer.
Sorry to bug you folks again:
Had this problem again with 64bit Ubuntu 9.04...
Again fixed it by deleting fsck binaries.
If it happens again I will capture the output and post it here.
--
filesystem check fails on boot, but filesystem isn't bad
https://bugs.launchpad.net/bugs/48563
You
Marking as incomplete. Please send the actual output of blkid and
contents of /etc/fstab. Thanks.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Incomplete
--
filesystem check fails on boot, but filesystem isn't bad
https://bugs.launchpad.net/bugs/48563
You received this bug
Julien Plissonneau Duquene wrote:
Marking as incomplete. Please send the actual output of blkid and
contents of /etc/fstab. Thanks.
Would do, but I'm using a different machine now, and no longer using ubuntu.
--
filesystem check fails on boot, but filesystem isn't bad
I had this problem in 64bit Ubuntu 8.10 and fixed it by deleting all
fsck binaries from my sbin directory. This, of course, means that I
cannot run this function unless I boot into a different install (or run
off a live CD), but since the only thing fsck has ever done for me is
cause my system not
Theodore Ts'o wrote:
OK, so it looks like you fixed /media/md4, but I'm guessing you have yet
*another* filesystem that is labelled as '/'.
Can you send me the output of the bllkid command. And can you make
sure you don't have another filesystem that is labelled as '/'?I'm
guessing that
Hi theodore,
I've just booted up my old machine again. You were right in that one of
the non-root filesystems had a label of '/'. However, having fixed this
(it's now labelled as /media/hda4), the error still happens.
When I boot up now, it says (edited version typed in manually)
Checking
OK, so it looks like you fixed /media/md4, but I'm guessing you have yet
*another* filesystem that is labelled as '/'.
Can you send me the output of the bllkid command. And can you make
sure you don't have another filesystem that is labelled as '/'?I'm
guessing that at one point for some
Hi Andy,
I have a sneaking suspicion that what's confusing you is that there is
some other filesystem which is NOT your root filesystem that has a label
of /. E2fsck will use the label assuming it is more human friendly
than the raw device name. However, if some other device (say,
/dev/hda1)
Thanks. I haven't been using that machine for some time (I bought a
laptop), so as far as I am concerned this bug is not a problem at the
moment. If I go back to using the other machine, I'll try installing the
latest ubuntu on it and then see if it's still a problem.
cheers,
andy baxter
Andy, is the Ubuntu installation on your old machine still intact?
Although you are currently not annoyed by this bug anymore, your input
would still be helpful to either prove Theodore's thesis, or to prove
it wrong.
--
filesystem check fails on boot, but filesystem isn't bad
Andy,
If you have the time to check your old machine, assuming it is still
intact, I would greatly appreciate it. That way we can determine
whether or not we really have a bug, and hopefully either fix the bug,
or close out this bug report.
Thanks!!!
--
filesystem check fails on boot, but
Thanks! I filed a new bug report against dosfstools and linked to this
one: https://launchpad.net/distros/ubuntu/+source/dosfstools/+bug/72293
--
filesystem check fails on boot, but filesystem isn't bad
https://launchpad.net/bugs/48563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thank you very much for your help. Sadly, the problem hasn't been solved.
Alt+SysReq+R made the following line appear: [some_number|some_number] SysReq:
Keyboard mode set to XLATE
The 'some_number' things I saw probably expressed a 32-bit time (the time
passed since 1970 -- or whatever date is
A google search turned up this thread:
The guy in that thread not only inhibits checking the volume on boot,
but also sets it no not mount automatically at boot. Mhh, I thought
'noauto' was the default setting for vfat partitions after installation.
It should be worth trying to comment out the
It falls back into the shell while checking /hda1.
In the shell, I see several things. At the top, there are error messages about
bcm43xx (Damn you, Broadcom!), but they don't seem to make Ubuntu fall back to
the shell.
After that, there's info about checking the file systems:
*Checking root
Mathiasdm wrote:
/dev/hda1 FAT32 +-3GB (Acer recovery partition)
I've never heard of this Acer recovery before, but it may be liable to
confuse dosfsck, causing it to take so long and ultimately fail. It may
be worth a try to investigate if older versions of dosfsck have this
problem, too.
Why
When booting, the system falls back to a shell while checking
/dev/hda1.
Could you please quote the output of fsck just before Ubuntu enters the
shell? Which boot loader does your system use (GRUB, NTLDR, LiLo)?
The /boot partition being the last one on disk looks problematic, too.
Is there any
I have a similar problem in Edgy, only it's not the root filesystem that
causes problems.
My layout is as follows:
Primary: /dev/hda1 FAT32 +-3GB (Acer recovery partition)
Primary: /dev/hda2 FAT32 +-55 GB (Windows partition)
Primary: /dev/hda4 ext2 +-100 MB (/boot)
Logical /dev/hda5 ext3 +- 20 GB
/: Root inode is not a directory.
Now this is interesting. If the root inode of any file system wasn't a
directory, how could you traverse the file system at all? I'm not too
much into the internals of inode-based fs', but the output of ls -ld
/ /. /.. may prove useful.
--
filesystem check
The weird thing is that / (/dev/hda5) shouldn't be being checked at all at
this point
The root filesystem is first checked by /etc/init.d/checkroot.sh, but is
checked again by checkfs.sh together with all other filesystems.
Interestingly, during the aftermath of a power failure, I've come to
On Sat, 2006-10-07 at 16:02 +, Daniel Werner wrote:
The weird thing is that / (/dev/hda5) shouldn't be being checked at all at
this point
The root filesystem is first checked by /etc/init.d/checkroot.sh, but is
checked again by checkfs.sh together with all other filesystems.
The line
On Tue, 2006-09-26 at 15:08 +, Daniel Werner wrote:
Could you please include the error messages you mentioned, even the
minor ones?
I've tried again checking /dev/hda5 from the live CD, and it passes
clean. here is the log:
[EMAIL PROTECTED]:~# e2fsck /dev/hda5 -d -f
e2fsck 1.38
Could you please include the error messages you mentioned, even the
minor ones?
--
filesystem check fails on boot, but filesystem isn't bad
https://launchpad.net/bugs/48563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
33 matches
Mail list logo
