Re: frequent disk error, need guidance

>> I'd shut down to single user, make a /.snap directory, and do dump -L
>> to tell it to make a snapshot before dumping.  That should work OK.
>
> Thanks.
> (Needed to mount /tmp read-write)
> The -L didn't work because boot -s mounted the filesystem read-only;
> at least that's what it claimed:
>
> dump -0 -L -f - /dev/ada0p2 | restore -r -Dv -f -
> Verify tape and initialize maps
>  DUMP: WARNING: -L ignored for read-only filesystem
>
> Not sure I understand that;
> does -s normally start in read-only mode?
> Has it always done that?  It's been quite a while since I did that.

Don't remember, but if the filesystem is read-only, that's even better 
than -L because you know it won't change at all.

> It looks like the bad blocks/sectors were files in
>  /var/db/freebsd-update/files/xxx.gz
> I unzipped a file in that directory and it appears that they are the
> saved files from the old system when upgrading.  Is that correct?
> Any reason not to remove all files in
>  /var/db/freebsd-update/files
> since the upgraded to 12.x system has been running for several months
> now?

I think that should be OK too.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly