Re: all files moved to lost+found
- Date: Tue, 2 Oct 2018 07:07:22 +0300
- From: Abdullah Ramazanoğlu <ar018@xxxxxxxxx>
- Subject: Re: all files moved to lost+found
On Mon, 1 Oct 2018 21:31:27 -0300 Beco said:
> I've done the bootable seagate HD test. It came up 100% ok, all tests. The
> HD is new, I wouldn't expect different, but it is always reassuring to do
> the real test and see the results.
I am not familiar with seatools, but there are usually destructive and
non-destructive test suites in such tools. I hope you have run a destructive
one (which destroys data on disk) as some marginal errors can only be caught by
> Is the "swap" partition something that could cause that if turned off by
I don't think so.
> I read above from Abdullah, that it is very unlike to have such major FS
> fail, and it looks like it didn't "flush" the night I turned off. This is
> also my guess, it is the only thing that make sense. Maybe the inode table
> was in the memory and got corrupted. But it is strange to figure that,
> since the filesystem is EXT4, and it is very stable nowadays.
But the journal is passing through on-disk controller, too. If the drive is
mishandling its on-drive cache, then an FS corruption is still possible. Even
if journal writes are "direct", the drive could be ignoring that (i.e. caches
it nevertheless) without flushing it prior to power-off, corrupting the journal
If the FS survives through reboots, but falters when the laptop is power
cycled, then a cache flush issue is still probable.
Another test method might be hibernation. If resume from hibernation works,
then that rules out on-disk caching problem.