busybox and e2fsck
Bug #1777920 reported by
Bougron
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bugs-everywhere (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I think the software should be able to solve himself this problem without human intervention.
http://
On the trace, i see
fsck.ext4 -a -CO /dev/sda1
Why it is not possible to continue automatically with
fsck.ext -v /dev/sda1
instead of writing things that are useless to a non-computer user?
Revision history for this message
| Bougron (francis-bougron) wrote | #1 |
To post a comment you must log in.
i find an other case with theses words
/dev/sda1 contrains a file system with errors check forced
error reading block 524409
(ahempt to read block from file system
resvited in short read) while getting next inode from scan.
/dev/sda1/ UNEXPECTED INCONSISTENCY run fsck MANUALY (i.e. without -a or -p options)
fsck exited with statut code 4
the root file system on /dev/sda1 requires a manual fsck