*** This bug is a duplicate of bug 110138 ***
https://bugs.launchpad.net/bugs/110138
Hi,
I had the same error message, and now I found the solution for my problem, hope
it will help you.
I installed Ubuntu 9.04 and created 2 partitions, the first one encrypted and
the second one unencrypted
*** This bug is a duplicate of bug 110138 ***
https://bugs.launchpad.net/bugs/110138
** This bug has been marked a duplicate of bug 110138
findfs/blkid detects ext3 partition as ntfs (without UUID)
--
fsck.ext3: Unable to resolve
https://bugs.launchpad.net/bugs/66032
You received this
Data point:
I ran into a similar error on a recent feisty install. I checked the fstab for
this UID, and found that it mapped to hdd1, which I'd just
pulled from the system. (Old disk, failed during or right after the install.)
After removing the mount point for hdd1 from /etc/fstab, along
If you have a filesystem mentioned in /etc/fstab, and you remove it,
then of course you will have this failure.
At this point, I believe that this bug was fixed in 1.40, for people who
had problems with filesystems that were getting misidentified by NTFS.
There may also be some users who are
I'm pretty sure this bug is related to bug #110138, where the partition
is getting mis-identified as an NTFS parition.
Due to a bug in e2fsprogs previous to version 1.30, the initial
bootsector (which is where the NTFS signature is stored) wasn't getting
erased.This could cause blkid to
** Changed in: e2fsprogs (Ubuntu)
Assignee: (unassigned) = Theodore Ts'o
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed = In Progress
--
fsck.ext3: Unable to resolve
https://bugs.launchpad.net/bugs/66032
You received this bug notification because you are a member of Ubuntu
** Tags added: corruption ext3
--
fsck.ext3: Unable to resolve
https://bugs.launchpad.net/bugs/66032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Eric Christiansen fix worked. Thanks
I have edgy. I planned to give fiesty a try. I installed it seerately in a new
partition. But i got fsck errors like ppl mentioned in thread. And it was
incorrect UUID tht fsck was not able to resolve.
--
fsck.ext3: Unable to resolve
I was able to resolve this problem.
/etc/fstab still had entries that corresponded to old partitions that I
had deleted. To fix this, I simply commented them out.
If you're dealing with a UUID mismatch, use sudo vol_id the
partition to figure out the correct UUID for each partition, so that
you
Setting to confirmed. I have the same issue on my server, where it is
really annoying - a server hanging during boot!
** Changed in: e2fsprogs (Ubuntu)
Status: Unconfirmed = Confirmed
--
fsck.ext3: Unable to resolve
https://bugs.launchpad.net/bugs/66032
You received this bug notification
I recently updated a Dapper installation to Edgy using the recommended
gksu update-manager -c procedure. On booting into Edgy, it failed to
the enter root password to repair prompt, obviously a bad message for
Ubuntu to show a newbie since root isn't supposed to have a password.
Above that the
So for some months now, every time there is a kernel update and I have
to reboot my system, fsck failes because my fstab lists UUID's and I
have to press Ctrl+D to continue booting. If I can contribute in any way
to help solve this bug, tell me what to do.
Here is my fstab:
# /etc/fstab: static
Forgot to mention I upgraded to Feisty Fawn in the meantime :)
--
fsck.ext3: Unable to resolve
https://launchpad.net/bugs/66032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I got also the message that fsck could not resolve the UID, but it
turned out that that were the UID's of a harddisk I removed.
--
fsck.ext3: Unable to resolve
https://launchpad.net/bugs/66032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I had the same error on kubuntu,
I used blkid to find the good UUID which differ from the one returned by
vol_id which return the UUID used by ubuntu.
I replace the good UUID in my fstab but now I have to create a symlink
every time I boot...
--
fsck.ext3: Unable to resolve
I have the same problem.
I'm running Ubuntu Edgy, clean install, completely updated as of this
post.
My disk: 160 GB
158GB ext3 /dev/sda6
2GB swap /dev/sda5
(both partitions are logical)
--
fsck.ext3: Unable to resolve
https://launchpad.net/bugs/66032
--
ubuntu-bugs mailing
My system worked perfectly with Edgy and new Feisty up to the updates
recently including kernel 2.6.19 which required me to reboot. Edgy
changed my /etc/fstab to mount by UUID and now none of my non-root
partitions are found anymore.
Also I now noticed that fdisk -l reports /dev/sda, /dev/sdb,
In addition to my comment:
I pressed Ctrl+D and everything gets mounted and everything is fine. I
checked the UUID's with vol_id and they match with /etc/fstab.
--
fsck.ext3: Unable to resolve
https://launchpad.net/bugs/66032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi,
Im facing the same problem with the release candidate.
“Fsck –a” is working fine for all with the UUIDs for all my partitions
except for /dev/hda1 (/boot):
fsck.ext3: Unable to resolve 'UUID=7389bc92-c7d5-4e03-a3a0-fd85456210e6'
vol_id is working fine for this volume:
# vol_id /dev/hda1
** Changed in: Ubuntu
Sourcepackagename: None = e2fsprogs
--
fsck.ext3: Unable to resolve
https://launchpad.net/bugs/66032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
20 matches
Mail list logo
