Howdy, New ECC ram installed after my last two issues. Woke up this morning to more errors. 

 

Looks like the first error was just cache then loop2 later?

 

thelibrary-diagnostics-20210327-0921.zip

1 hour ago, DuzAwe said:

Looks like the first error was just cache then loop2 later?

Correct, cache filesystem corrupted first, then it's normal to cause issues with any images using it.

A reboot seems to have put everything back to normal? Scrub came back with nothing. 

 

Should a reboot have done that?

Sometimes rebooting can temporarily help, but you'll likely run into issues again.

Anything in the logs to point at what it is? The disk have run fine for months the rc for 6.9 is when this stuff started.

3 minutes ago, DuzAwe said:

Scrub came back with nothing. 

Also, a scrub only checks data and metadata consistency, it doesn't look for filesystem corruption you can do that with the pool offline by typing:

 

btrfs check /dev/sdX1

 

Note that if errors are found running btrfs check in repair model (btrfs check --repair) is considered dangerous, should only be done if told so.

2 minutes ago, DuzAwe said:

Anything in the logs to point at what it is?

Not that I can see, only that corruption was detected.

1 minute ago, JorgeB said:

Also, a scrub only checks data and metadata consistency, it doesn't look for filesystem corruption you can do that with the pool offline by typing:

 

btrfs check /dev/sdX1

 

Note that if errors are found running btrfs check in repair model (btrfs check --repair) is considered dangerous, should only be done if told so.

 

Comes back with:

root@thelibrary:~# btrfs check /dev/sdX1
Opening filesystem to check...
ERROR: mount check: cannot open /dev/sdX1: No such file or directory
ERROR: could not check mount status: No such file or directory

2 minutes ago, DuzAwe said:

 

Comes back with:

root@thelibrary:~# btrfs check /dev/sdX1
Opening filesystem to check...
ERROR: mount check: cannot open /dev/sdX1: No such file or directory
ERROR: could not check mount status: No such file or directory

You have to replace 'X' with the correct letter for the drive as shown in the unPaid GUI.

 

You need to replace X with correct letter, and since it's an NVMe device it would be:

 

btrfs check /dev/nvme1n1p1

 

Well I feel like a fool. Ok Looks clean.

 

Opening filesystem to check...
Checking filesystem on /dev/nvme1n1p1
UUID: cdb12f2a-8005-48a1-b8f7-bd0e1fc9fd43
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 266705154048 bytes used, no error found
total csum bytes: 225909672
total tree bytes: 698073088
total fs tree bytes: 379420672
total extent tree bytes: 46546944
btree space waste bytes: 119030509
file data blocks allocated: 2601829400576
 referenced 262717333504

 

That looks all fine to me.

Welp, Thanks for your help again. I guess Ill be back at some point.