Thanks Chris,
I have a "smartctl -l /dev/sda" running now.
I'll read over your writing below... If I have questions or problems, I'll
ask... otherwise, I'll report what happens.
Thanks!
George...
On Mon, Aug 22, 2022, at 7:41 PM, George R Goffe via test wrote:
> Howdy,
>
> Thanks to all
On Mon, Aug 22, 2022, at 7:41 PM, George R Goffe via test wrote:
> Howdy,
>
> Thanks to all who responded...
>
> Chris,
>
> I tried the superblock mount but that still fails. Then I tried the
> rescue=all mount. That succeeded... I have copied all the files I need.
> From what I read, corrupted
Howdy,
Thanks to all who responded...
Chris,
I tried the superblock mount but that still fails. Then I tried the rescue=all
mount. That succeeded... I have copied all the files I need. From what I read,
corrupted files get copied too... and there were some which I removed from the
copies.
Fr
Attending the meeting today
On Fri, Aug 19, 2022 at 8:51 PM Ben Cotton wrote:
> Action summary
>
>
> Accepted blockers
> -
>
> 1. kde-settings — KDE needs to pick up F37 backgrounds — ON_QA
> ACTION: None
>
> 2. sddm — Logout from KDE session on Rawhide goes
On Mon, Aug 22, 2022, at 11:47 AM, Chris Murphy wrote:
> On Mon, Aug 22, 2022, at 11:46 AM, Chris Murphy wrote:
>
>> After that, you can umount the file system. And mount again with '-o
>> rescue=usebackuproot' and hopefully it finds a good backup root, and
>> can fix itself. If it gets confuse
On Mon, Aug 22, 2022, at 11:46 AM, Chris Murphy wrote:
> After that, you can umount the file system. And mount again with '-o
> rescue=usebackuproot' and hopefully it finds a good backup root, and
> can fix itself. If it gets confused again, it'll go read only to avoid
> making things worse.
On Sun, Aug 21, 2022, at 11:02 PM, George R Goffe via test wrote:
> Hi,
>
> I started getting i/o error messages accessing this filesystem so I
> rebooted the system. This might have been the wrong thing to do. This
> subsequent boot went to maintenance mode due the filesystem's path
> being i
Hello This is a good question for ask.fp.o and discussion.fp.o.
There may be an answer there already.
Regards,
Stephen
On Mon, 2022-08-22 at 03:02 +, George R Goffe via test wrote:
> Hi,
>
> I started getting i/o error messages accessing this filesystem so I
> rebooted the system. This mig
At some point, we do need to wrap up the TCMS conversation. If not this week
then hopefully next week or the week after.
Tim
On 8/22/22 00:25, Adam Williamson wrote:
Hi folks! I'm proposing we cancel the QA meeting today/tomrrow. I
don't have anything much for the agenda again. There will be a
