Otto Moerbeek <o...@drijf.net> wrote: > On Fri, Feb 11, 2022 at 10:09:25PM +0100, Konrad Sowula wrote: > > > Hello, > > to keep things short, rebooting my vps using 'Server restart' in vultr > > control panel trashed my /usr/local directory (or at least i suppose > > that's all that has been damaged, haven't noticed any changes to > > config files thus far). > > > > Upon rebooting awaited me a message akin to: > > /dev/sd0a (...): UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY > > ... > > Enter path to shell binary: > > > > thus i ran `fsck_ffs /dev/sd0a` in shell and here I am. > > Your subject is wrong. fsck_ffs did not trash your filesystem. It > could not repair the damage automatically. > > Your report is also useless. What does "here I am" mean? Was fsck_ffs > able to repair the fs in non-automatic mode? How about providing the > things it printed/questions it asked on the manual run? > > BTW, /dev/sd0a is your root fs.
Indeed, in particular: > > /dev/sd0a (...): UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY If fsck prints this, it has not done a single write operation. fsck has only read, and decided it cannot perform an automatic repair. When fsck is run in manual mode, it asks questions, and puts part the responsibility for some undermined handling in the hands of the user (who is root). Most of the time that goes well. Sometimes it doesn't. There are papers about fsck design, easy to search for.....
