Comment 5 for bug 387692
Revision history for this message
| Stéphane Gourichon (stephane-gourichon-lpad) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Had the same problem as imperia777 : data intact, error message and unable to fix it, (though no actual power failure).
Here's fsck output:
e2fsck 1.42.9 (4-Feb-2014)
myfsname: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
fsck.ext4: unable to set superblock flags on myfsname
Final verdict was: defective storage.
Data was transferred to a new storage medium with a new filesystem.
Problem solved.
As additional check, we made a copy from the defective medium to another and observed that fsck could run flawlessly on the sane medium.
Looks like fsck is extra cautious and checks if every operations indeed happened, which allowed it to spot the trouble.
Anyway, to say it again: "fsck.ext4: unable to set superblock flags on myfsname" meant (at least in my case): change your storage medium.
Thank you for your attention.