El lun, 16-11-2009 a las 09:28 +0100, Gabriel Paubert escribió: > On Sun, Nov 15, 2009 at 05:57:12PM -0200, Mariano Pardo wrote: > > The root filesystem is currently mounted un read-only mode. A maintenance > > shell will now be started. After performing system maintenance, press > > CONTROL-D to terminate the maintenance shell and restart the system. ... > > (waring). > > Give root password for maintenance > > (or type Control-D to continue): _ > > > > > > mytwm:~# fsck -p > > fsck from util-linux-ng 2.16.1 > > /dev/sda1 contains a file system with errors, check forced. > > /dev/sda1: Inodes that were part of a corrupted orphan linked list found. > > > > /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > (i.e., without -a or -p options) > > mytwm:~# fsck -a > > fsck from util-linux-ng 2.16.1 > > /dev/sda1 contains a file system with errors, check forced. > > /dev/sda1: Inodes that were part of a corrupted orphan linked list found. > > > > /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > (i.e., without -a or -p options) > > mytwm:~# _ > > > > ¿Porque haces un fsck con las opciones -a y -p cuando te dice > que lo hagas sin ninguna de esas opciones?
es para asegurarse que le contestes las preguntas. Las dos o tres veces que tuve ese problema lo que hice fue iniciar on un live-cd y lanzar el fsck desde ahí, para asegurarme que el disco no esté montado ni como solo lectura. Una vez que lo arregles ya se puede montar en lectura-escritura -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
