Hallo Steffen,
fsck -y /dev/sda2
sollte zum Erfolg führen.
Gruß Jürgen
Am 07.03.2015 um 11:09 schrieb Steffen Auer:
> Hallo,
>
> jetzt bin ich mal auf die Suche nach Infos zum Problem gegangen.
>
> /var/log/boot
> ---
> /dev/mapper/pve-data: Superblock needs_recovery flag is clear, but
> journal has data.
> Sat Mar 7 07:31:29 2015: /dev/mapper/pve-data: Run journal anyway
> Sat Mar 7 07:31:29 2015:
> Sat Mar 7 07:31:29 2015: /dev/mapper/pve-data: UNEXPECTED
> INCONSISTENCY; RUN fsck MANUALLY.
> [...]
> Sat Mar 7 07:31:30 2015: File system check failed. A log is being
> saved in /var/log/fsck/checkfs if that location is writable. Please
> repair the file system manually. ... failed!
> Sat Mar 7 07:31:30 2015: A maintenance shell will now be started.
> CONTROL-D will terminate this shell and resume system boot. ... (warning).
> Sat Mar 7 07:31:30 2015: Give root password for maintenance
> Sat Mar 7 07:31:30 2015: (or type Control-D to continue):
> ---
>
> Da hatte ich dann eben Control-D gedrückt.
>
> In der /var/log/fsck/checkfs steht im Prinzip auch nichts anderes:
> ---
> Log of fsck -C -R -A -a
> Sat Mar 7 07:31:28 2015
>
> fsck from util-linux 2.20.1
> /dev/mapper/pve-data: Superblock needs_recovery flag is clear, but
> journal has data.
> /dev/mapper/pve-data: Run journal anyway
>
> /dev/mapper/pve-data: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> (i.e., without -a or -p options)
> /dev/sda2 has gone 372 days without being checked, check forced.
> /dev/sda2: 333/130560 files (3.6% non-contiguous), 58363/522240 blocks
> fsck died with exit status 4
>
> Sat Mar 7 07:31:30 2015
> ----------------
>
> Viele Grüße
> Steffen
>
> _______________________________________________
> linuxmuster-user mailing list
> linuxmuster-user@lists.linuxmuster.net
> https://mail.lehrerpost.de/mailman/listinfo/linuxmuster-user
>
_______________________________________________
linuxmuster-user mailing list
linuxmuster-user@lists.linuxmuster.net
https://mail.lehrerpost.de/mailman/listinfo/linuxmuster-user
