On Fri, Sep 04, 2020 at 08:50:32PM -0700, Gregory Nowak wrote:
> On Fri, Sep 04, 2020 at 11:25:21PM -0400, Hendrik Boom wrote:
> > Delete the contents all you want, but keep the lost and found directory.
>
> If you delete lost+found by accident, you can recreate it with
> mklost+found(8).
So
On Sat, Sep 05, 2020 at 09:07:10PM +0900, Simon Walter wrote:
> On 9/5/20 3:34 PM, goli...@devuan.org wrote:
> ...
> > Yes we do! I checked a log I had saved from before I did the e2fsck and
> > those values are identical to the post-e2fsck log.
>
> If they are identical, then it would seem that
On Saturday 05 September 2020 at 19:28:24, Hendrik Boom wrote:
> On Fri, Sep 04, 2020 at 08:50:32PM -0700, Gregory Nowak wrote:
>
> > If you delete lost+found by accident, you can recreate it with
> > mklost+found(8).
>
> So lost+found isn't identified by its file name but by something else
>
On Fri, 04 Sep 2020 20:22:56 -0500
goli...@devuan.org wrote:
> On 2020-09-04 19:24, spiralofhope wrote:
> > On Fri, 04 Sep 2020 15:03:55 -0500
> > goli...@devuan.org wrote:
> >
> >> ...2 new 500 GB WD Black drives...
>
> Not sure if they still have the 5 yr. warranty though . . .
They do,
On 2020-09-04 22:33, Gregory Nowak wrote:
On Fri, Sep 04, 2020 at 09:19:42PM -0500, goli...@devuan.org wrote:
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error medium or hardware error
(serious)
SMART overall-health self-assessment test result: PASSED
Warning:
On 9/5/20 3:34 PM, goli...@devuan.org wrote:
...
Yes we do! I checked a log I had saved from before I did the e2fsck and
those values are identical to the post-e2fsck log.
If they are identical, then it would seem that the fsck did not trigger
the reallocation. However, what caused the
On 9/5/20 3:21 PM, goli...@devuan.org wrote:
My board doesn't have an eSATA port. Neither does the new dock but at
least it is USB 3.0. Current enclosures are 2.0 . . .
...
If you are a data hoarder and like disks, I'd suggest getting your
hands on some hardware that has a SATA
On 2020-09-04 22:26, Simon Walter wrote:
On 9/5/20 11:19 AM, goli...@devuan.org wrote:
On 2020-09-04 20:46, Simon Walter wrote:
On 9/5/20 1:34 AM, Andreas Messer wrote:
Hi golinux,
On Fri, Sep 04, 2020 at 01:50:07AM -0500, goli...@devuan.org wrote:
On 2020-09-01 00:07, goli...@devuan.org
On 9/5/20 12:50 PM, Gregory Nowak wrote:
On Sat, Sep 05, 2020 at 12:26:21PM +0900, Simon Walter wrote:
Reallocation, to my knowledge, should happen in the background. It's
*possible* that the reallocation event and the FS corruption are unrelated.
My understanding is that the drive won't
On 2020-09-05 13:41, Hendrik Boom wrote:
> This seems to say we now have two independent levels of bad block
> checking.
>
> When the low-level one fails, the other takes over. I't expect the
> file system to be unlikely to see bad blocks until the drive is hosed.
That is true if the drive is
10 matches
Mail list logo
